Workflows Directory
Find your team’s next superpower.
- Function: Leadership
- Function: Quality management
- Industry: Construction
- Industry: Education
- Industry: Government
- Industry: Manufacturing
- Clear all filters
Results
41 workflow templates, showing 25 to 41
Process map and bottleneck review
Map one process step by step: who does each step, how long work waits and how long it takes, where it is handed over and where it gets sent back. Then find the one step that caps how much gets finished, and what to try there first. The owner decides what changes.
- Starts it
- Operations lead
- Brings
- export, notes
- Gets
- 7 outputs
Product recall customer contact plan
Once your business has issued a recall, the customer care lead gets the contact plan: affected customers from the order export, the approved notice word for word, drafts that offer only the remedies you run, and a tracker that counts a customer done only when the item is back or repaired.
- Starts it
- Customer care lead
- Brings
- export, notes, document
- Gets
- 6 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
Quality management review pack
Before the periodic quality review, the quality lead gets one brief for senior leaders: where each measure stands, complaints and defects, audit findings, action status, and the decisions still open. The leaders decide; the brief claims no compliance with any standard.
- Starts it
- Quality lead
- Brings
- export, notes
- Gets
- 8 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
Returned unit review brief
When a failed-unit report or return request arrives, the service coordinator gets one brief tying the customer's report to each unit's shipment record, serial and recorded configuration, with unmatched serials and missing evidence listed. It names no cause.
- Starts it
- Service coordinator
- 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
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
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
Thirteen-week cash flow forecast
The owner sees cash week by week for the next thirteen weeks: what comes in, what goes out, the lowest point and every week below the floor they set, with each assumption written on the page. The forecast informs the decision; the owner makes it, and nothing is paid or moved.
- Starts it
- Bookkeeper
- Brings
- export, notes
- Gets
- 7 outputs
Weekly owner business brief
Each Monday the owner gets about one page built from the exports they supply: cash, last week's sales against the week before, pipeline movement, the week's commitments and a watch list, with one item to look at first. Every figure names its source, and every missing export is named.
- Starts it
- Owner
- Brings
- export, notes
- Gets
- 8 outputs
Workflow fit check: is this piece of work ready for AI?
Before you build anything, run one piece of work through six checks and get a straight answer on one short page: build it, build one part, do something simpler first, not yet, or leave it with your people. The owner decides what gets built first, with the reasons in front of them.
- Starts it
- Owner
- Brings
- notes, pasted text
- Gets
- 6 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