Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

50 workflow templates, showing 25 to 48

  • Premortem before a decision

    Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.

    Starts it
    Owner
    Brings
    notes
    Gets
    4 outputs

  • Preventive maintenance plan

    For one site, the facilities or operations manager gets every piece of equipment ranked by failure cost, an approach for each (run to failure, scheduled or condition-based), a dated calendar of tasks from the maker's guidance and the failure history, the spare parts to hold and the downtime measures to track.

    Starts it
    Facilities manager
    Brings
    export, notes
    Gets
    6 outputs

  • Program outcome map

    Before an evaluation, the program and evaluation leads get one map linking each activity to the outcome it is meant to serve, with proposed measures, data sources, assumptions and the questions the evidence cannot yet answer. It claims no impact.

    Starts it
    Program lead
    Brings
    export, notes
    Gets
    8 outputs

  • Project handover readiness check

    When a finished deliverable is ready for the team that will run it, the project manager brings one checklist against that team's own requirements: acceptance evidence, instructions, access, training, support owners and open items. The receiving owner accepts or names the conditions still to meet.

    Starts it
    Project manager
    Brings
    export, notes
    Gets
    6 outputs

  • 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

  • Property diligence index

    The transaction lead gets a diligence room in order: every document indexed by workstream, every checklist item and request tracked, and every open finding tied to the report or request that raised it. Specialists judge the findings; nothing is valued or sent.

    Starts it
    Transaction coordinator
    Brings
    export, notes
    Gets
    5 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

  • Recurring repair service history

    When repeated maintenance keeps disturbing guests, the facilities manager gets one brief by equipment and room area: repeated work orders, confirmed service interruptions and missing inspection records side by side. It finds no cause and orders no work.

    Starts it
    Facilities manager
    Brings
    export, notes
    Gets
    5 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

  • Reviewer comments into one resolution list

    The owner of a document that came back from several reviewers gets one checklist: every proposed edit and comment, grouped by section, with clashes between reviewers set side by side. Every item stays open until the owner decides it, and the document itself is never touched.

    Starts it
    Document owner
    Brings
    export, notes, document, pasted text
    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 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

  • Shoot location logistics pack

    When a location joins the shooting schedule, the location manager gets one brief for it: how people and vehicles get in, where they park, what the place offers, who to call and what each department asked for, with every unconfirmed item listed against the production checklist.

    Starts it
    Location manager
    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

  • 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

  • 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

  • Temporary change register

    For a site or operations manager with temporary changes to equipment, layout or process still in place: a register of every change with its expiry date, the checks still outstanding and the procedures and training it touches, ready for the competent person who decides what happens next.

    Starts it
    Site manager
    Brings
    export, notes
    Gets
    7 outputs