Book a fit call

Workflows Directory

Find your team’s next superpower.

Results

59 workflow templates, showing 49 to 59

  • 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

  • Shared folder filing plan

    The office coordinator gets a plan for tidying a shared folder: a proposed folder structure, every file's move with its owner named, and the duplicates and access questions to settle first. Owners approve their own moves; nothing is moved, renamed or deleted.

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

  • Shipment documentation check

    When a job finishes, the shipping or quality lead gets one index comparing the order, the inspection records, the required certificates and the packing details, with each missing record and each quantity that does not agree set out. Nothing is certified or released.

    Starts it
    Shipping lead
    Brings
    export, notes
    Gets
    6 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

  • SOP exception capture

    Turn what your most experienced person does with the awkward cases into an exception register for one procedure. Once the owner approves it, every colleague handles those cases the way your best person does.

    Starts it
    Operations lead
    Brings
    notes, document
    Gets
    2 outputs

  • Spreadsheet check before sharing

    Before a model or schedule goes to a client, a lender or a board, the sender gets one report on it: every error value, short total, buried assumption and hidden row pinned to its cell, each with a fix or a question, and a plain list of what was not checked. Nothing in the workbook is changed.

    Starts it
    Finance manager
    Brings
    export, notes
    Gets
    5 outputs

  • 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

  • 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

  • Supplier quality response check

    A quality or purchasing person who has raised a defect with a supplier gets the supplier's reply set against the finding: what is answered, what is not, the evidence still to ask for, the actions proposed and what has yet to be verified. The person decides whether the answer is accepted.

    Starts it
    Supplier-quality owner
    Brings
    export, notes, document, pasted text
    Gets
    7 outputs

  • Work sample exercise brief

    For one approved role, the hiring manager gets a practical exercise: a bounded task from the role's real work, instructions for the candidate with a time limit and adjustments, and the evidence the panel will look for. The panel judges the work; nothing is rated here.

    Starts it
    Hiring manager
    Brings
    export, notes, document
    Gets
    5 outputs

  • Write an SOP from how the work is done

    Turn a walkthrough of how one piece of work is really done into a written procedure anyone on the team can follow: who does each step, how they know it is done, what to do when it goes wrong and when to stop and ask. The owner approves it before anyone relies on it.

    Starts it
    Operations lead
    Brings
    notes, document, pasted text
    Gets
    2 outputs