Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

111 workflow templates, showing 73 to 96

  • Project intake and capacity review

    When a new initiative is proposed, the portfolio owner sees it scored on the business's own criteria beside the projects already committed, the delivery days it would use month by month, and what it would crowd out or push later. The owner accepts, defers or rejects it.

    Starts it
    Portfolio owner
    Brings
    export, notes, document
    Gets
    6 outputs

  • Project lessons review

    When a phase or a project ends, the project manager gets one blameless review: whether it achieved what it was for, how scope, schedule and budget moved and why, whether the success measures were the right ones, and practice changes for the team to choose, each with an owner and a follow-up date.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    8 outputs

  • Project scope baseline

    A project manager turns an approved brief into a draft scope baseline: the deliverables, what is excluded, the acceptance criteria for each deliverable, the constraints and the open questions for the sponsor. Nothing implied counts as scope until the sponsor says so.

    Starts it
    Project manager
    Brings
    export, notes, document
    Gets
    7 outputs

  • Project status report

    The lead of an internal project gets a status report the sponsor can read in two minutes: each workstream red, amber or green with the reason, what moved, who must clear each blocker, the decisions needed and the dates at risk. No milestone is called done without evidence, and the lead confirms every status.

    Starts it
    Project lead
    Brings
    export, notes, pasted text
    Gets
    7 outputs

  • Punch list consolidation

    The site manager gets the punch list for the next closeout walk as one list grouped by location and trade, with repeated entries merged, photographs attached and a proposed follow-up date for each open item. Nothing is assigned, closed or accepted.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    7 outputs

  • Record sharing access matrix

    When an approved access policy has to reach the CRM, the system owner lays the current sharing setup beside the proposed one, by record type and by role, internal and external. Every change is a question for its owner; inherited and platform-fixed settings are marked unknown.

    Starts it
    System owner
    Brings
    export, notes
    Gets
    6 outputs

  • Renewal risk review

    Once a month, the account manager sees every contract coming up for renewal on one page: the dates that matter, the warning signs your organization watches for, which accounts are at risk, and the next step for each with an owner and a date. A person decides and makes every contact.

    Starts it
    Account manager
    Brings
    export, notes, document
    Gets
    7 outputs

  • Repeat incident pattern review

    A safety lead with a year of incident records and earlier actions gets them compared in groups: confirmed causes, what was done before, and where incidents recur, with questions for the team. A competent person judges what the pattern means.

    Starts it
    Investigation lead
    Brings
    export, notes
    Gets
    6 outputs

  • Research summary brief

    An executive handed a pile of reports, articles or papers gets one brief: what each source found, where the sources agree and disagree, the limits of each, and exact quotations cited to the page. Built only from the documents supplied. What it means for the business stays the reader's call.

    Starts it
    Analyst
    Brings
    notes, document
    Gets
    7 outputs

  • RFI review package

    The project engineer gets one packet for each request for information: the register entry, the question word for word, the drawing revisions and specification extracts it touches, earlier responses, and a numbered list of what is unresolved. No answer is proposed.

    Starts it
    Project engineer
    Brings
    export, notes, pasted text
    Gets
    8 outputs

  • Safety walk follow-up

    After a safety walk, the manager gets a follow-up brief that ties each concern workers raised to the commitment the manager made, its owner and due date, and the message to give back. Gaps arrive as questions, never as guesses.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    5 outputs

  • Schedule recovery options

    When a committed milestone slips, the project manager brings the sponsor two to four ways back: what each changes, the dates it gives every later milestone and dependency, and the assumptions it rests on. The sponsor chooses; delivery leads confirm the dates.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    5 outputs

  • Scope change impact review

    When new work turns up in a project plan, the project manager gets one review: every deliverable compared with the agreed baseline, each addition marked approved or not, its estimated effect on effort, cost and the end date, and the decision the sponsor has to make. The sponsor accepts or declines each one.

    Starts it
    Project manager
    Brings
    export, notes, document, pasted text
    Gets
    6 outputs

  • Service inbox routing plan

    When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.

    Starts it
    Service owner
    Brings
    export, notes
    Gets
    5 outputs

  • Service visit work packet

    Before a planned visit to a turbine, inverter or terminal asset, the maintenance supervisor gets one packet built from the logs and approved scope supplied: reported symptoms, previous visits, open parts requests and access questions. It judges no condition and sends nothing.

    Starts it
    Maintenance supervisor
    Brings
    export, notes
    Gets
    7 outputs

  • Site observation follow-up

    After a site visit, the visiting engineer and the project manager get one observation report: each field note beside its location, source photograph, drawing revision and any earlier register entry, a proposed follow-up owner, and the questions still open. It assesses no condition.

    Starts it
    Visiting engineer
    Brings
    export, notes
    Gets
    5 outputs

  • Site safety induction pack

    For one named site, the site, facilities or people lead gets an induction built from that site's own emergency arrangements, rules and hazards, with a short check of understanding, a sign-off record for each person and refresher dates by role. A competent person approves it and delivers it.

    Starts it
    Site manager
    Brings
    export, notes, document
    Gets
    6 outputs
    • People and HR
    • Construction (filtered by)
    • Established businesses (filtered by)

  • Staff newsletter and FAQ roundup

    Each month the office manager turns what teams send in into one staff newsletter, with answers to the questions people keep asking, each quoted from an approved source and its owner named. Nothing about one person's pay, health or performance goes in, and a person approves the issue before it goes.

    Starts it
    Office manager
    Brings
    export, notes, document
    Gets
    2 outputs

  • Stakeholder and decision rights map

    Before kickoff, the project manager holds one map of everyone the project touches: each group placed by influence and interest, every key decision with exactly one accountable owner, the decision makers still missing, and who hears what, when and from whom. The sponsor confirms every decision right.

    Starts it
    Project manager
    Brings
    export, notes, document
    Gets
    6 outputs

  • Stale ticket sweep

    Once a week the support lead gets one sheet of what the queue is hiding: tickets with no real activity past their limit, tickets left waiting on the customer with the three ways out of each, likely duplicates, and each person's load weighed by size and age. A person makes every move.

    Starts it
    Support lead
    Brings
    export, notes, document
    Gets
    6 outputs

  • Submittal register review

    The project engineer gets one register of every required submittal: what has arrived, the review status as recorded, the documents still missing and the long-lead items at risk against the date each order must be placed. Nothing is routed, accepted or ordered.

    Starts it
    Project engineer
    Brings
    export, notes
    Gets
    6 outputs

  • Subscription billing exception sheet

    Before a subscription billing run, or when a customer disputes a charge, the billing specialist gets a sheet tying each account's plan, quantity and invoice lines to the approved price mapping and the seat or usage records, with doubtful matches kept open.

    Starts it
    Billing specialist
    Brings
    export, notes
    Gets
    7 outputs

  • Supplier bill review and payment-run preparation

    Before each payment run, the person who approves it gets one sheet: every supplier bill checked against its purchase order and what was received, duplicates and changed bank details stopped, credits shown, and a proposed run with its total. Nothing is paid until a person approves.

    Starts it
    Payables clerk
    Brings
    export, notes
    Gets
    7 outputs

  • Supplier issue notice

    When a supplier bills for more than was ordered or received, or falls short of an agreed delivery or quality target, the buyer gets a formal notice ready for approval: each problem set against the record, the evidence listed, what the supplier must do and the date to reply by. A person approves and sends it.

    Starts it
    Buyer
    Brings
    export, notes, document
    Gets
    3 outputs