Workflows Directory
Find your team’s next superpower.
Results
66 workflow templates, showing 25 to 48
Incident investigation and corrective actions
After an injury, near miss or property damage, the site, operations or safety manager gets the investigation written up from the evidence: a timeline, the immediate and underlying causes, actions with owners and dates, and a register that follows each action until a check shows it worked.
- Starts it
- Site manager
- Brings
- export, notes, document
- Gets
- 8 outputs
Internal change announcement
One decided change, announced well: managers briefed first, a message for each group in the right order, talking points, and the questions people will ask, answered only from the decision or marked open. Every message is a draft that a person approves and sends.
- Starts it
- Internal communications lead
- Brings
- export, notes
- Gets
- 7 outputs
Interview process review after a hiring round
After a hiring round closes, the recruiting lead gets a review of the interview process: questions that gave no usable evidence, competencies nobody covered, inconsistent rubric use, and revisions to approve before the next search. It reviews the process only; no candidate is assessed.
- Starts it
- Recruiting lead
- Brings
- export, notes
- Gets
- 6 outputs
Job description
A hiring manager’s rough notes become a job description the right people want to answer: why the role exists, the work itself, and only the must-haves that are real. Your approved pay and employer wording go in untouched, and nothing is posted until the hiring manager and the people lead approve it.
- Starts it
- Hiring manager
- Brings
- notes, document
- Gets
- 2 outputs
Job readiness packet
Before an order goes to the floor, the production or quality lead gets one packet: each requirement matched to its approved drawing, specification or inspection plan, with conflicting revisions, gaps and material shortfalls listed. The owners decide; nothing is approved or released.
- Starts it
- Production planner
- Brings
- export, notes
- Gets
- 5 outputs
Journey accessibility findings
When a user journey is ready for accessibility review, the reviewer gets a finding list: each finding with its task impact and evidence, the manual checks still required and the limits of the review. The reviewer verifies every finding and agrees fixes with the design owner.
- Starts it
- Accessibility reviewer
- Brings
- export, notes
- Gets
- 5 outputs
Manager feedback preparation
Every manager walks into a feedback conversation prepared like your best one: specific dated observations, the questions worth asking, a clear ask and the support on offer.
- Starts it
- Team manager
- Brings
- notes, document
- Gets
- 7 outputs
Nonconformity record draft
A quality lead or supervisor who has spotted something wrong gets a draft record: the observation set against the stated requirement, the affected work counted from the register, and the containment options. The quality owner decides every call.
- Starts it
- Quality lead
- Brings
- export, notes
- Gets
- 1 output
Obsolete copy check
The quality lead gets the master document list set against the copies found at each point of use: which copies are out of date, which withdrawn documents are still held, and what proof of withdrawal exists. The document owner withdraws and replaces copies; nothing is changed.
- Starts it
- Document controller
- Brings
- export, notes
- Gets
- 6 outputs
Outgoing work sign-off log
Every item that needs a responsible attorney's sign-off before it leaves the firm sits in one log, in the order it has to go out: waiting, approved or returned, with the attorney's own note. Anything close to its date with no decision is flagged first. The log tracks status and never touches the legal substance.
- Starts it
- Operations manager
- Brings
- export, notes, pasted text
- Gets
- 6 outputs
Packaging artwork handoff check
Before packaging artwork goes to print, the packaging owner gets a checklist that matches each file to the approved product facts, pack sizes, variants and printer specifications, with version conflicts, missing files and missing approvals listed. It writes and judges no label claim.
- Starts it
- Packaging owner
- Brings
- export
- Gets
- 5 outputs
Payroll preparation and timesheet review
Before each payroll run, the owner gets one sheet built from the timesheet and roster exports: hours by person and type, every missing punch and odd entry raised as a question, and an estimated total. Nothing is keyed in, submitted or paid until a person approves.
- Starts it
- Payroll clerk
- Brings
- export, notes
- Gets
- 7 outputs
Pilot build readiness brief
Before a prototype or pilot build, the build lead gets one brief: part shortages, revision conflicts and open actions set against the team’s own build checklist, with allocated parts kept apart from received ones. People confirm; nothing is released.
- Starts it
- Build lead
- Brings
- export, notes, document
- Gets
- 7 outputs
Policy answers from the handbook
Staff questions about leave, hours, expenses and conduct get answers that quote your own handbook, name the section, and say plainly where the handbook is silent. Anything about one person's own entitlement goes to HR, and no reply leaves until a person has read it.
- Starts it
- Office manager
- Brings
- export, notes, document
- Gets
- 4 outputs
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 pricing options
A product owner weighing how to price or package a product gets one options brief: what each customer group uses, the willingness-to-pay evidence held with stated kept apart from observed, what each option would bill every account, the uncertainties and the tests. It recommends no price.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 6 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
Product sample feedback revision list
After each round of samples, your product lead gets one revision list by sample version and feature: the changes people agree on, the feedback that conflicts, and drafted notes for the next supplier brief. The product owner decides.
- Starts it
- Product lead
- Brings
- export, notes, document
- 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
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
Release notes draft
The product owner gets draft release notes for one shipped release, in words users recognize: what is new, changed, removed and fixed, the steps users must take, and the known limitations. Only what was supplied is described. The owner checks and publishes.
- Starts it
- Product owner
- 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
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