Workflows Directory
Find your team’s next superpower.
- Function: Analytics and reporting
- Function: Customer support and service
- Function: Quality management
- Clear all filters
Results
77 workflow templates, showing 49 to 72
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
Public guest review reply
Answer an online guest review without exposing the guest's stay. Hand over the review and the service actions you have confirmed, and get a short public reply plus separate private notes, each statement tied to its source. The guest relations manager checks and approves.
- Starts it
- Guest relations manager
- Brings
- export, notes, document, pasted text
- 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
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
Range margin by channel review
When a wholesale offer or a promotion changes the economics of a range, the finance lead gets a margin worksheet for every product in every channel, showing which cost layers are in each figure and which gaps are still open. It invents no cost and changes no price.
- Starts it
- Finance lead
- Brings
- export, notes
- Gets
- 5 outputs
Reader correction request brief
When a reader disputes a fact or reports a missing credit, the editor gets one internal note: the request, the published passage, the evidence supplied and the questions only an editor can answer. A draft acknowledgement waits for the audience lead's approval.
- Starts it
- Editor's assistant
- Brings
- notes, document, pasted text
- Gets
- 3 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
Sales pipeline review
Each week your sales lead sees the whole open pipeline on one page: value and age by stage, what moved since last week, the deals at risk and coverage against your target. Every figure traces to your export, and the forecast number is left for a person to commit.
- Starts it
- Sales lead
- Brings
- export, notes
- Gets
- 9 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
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
Slow-moving stock and markdown plan
Before a seasonal reset, the merchandiser or store owner gets one plan from the sales and stock exports: each item's sell-through and weeks of cover, the cash tied up in dead and slow stock, and a markdown plan in dated steps with the margin each leaves and a date to stop. The owner decides every price.
- Starts it
- Merchandiser
- 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
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
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
Support escalation brief
When a support case must move to a specialist or manager, the support lead gets one brief: the customer's impact, a dated timeline from the ticket history, the evidence, the fixes tried, the workaround in place and the decision needed. Nothing goes to the customer.
- Starts it
- Support agent
- Brings
- export, notes, document
- Gets
- 8 outputs
Support service level definition
The support lead gets reply and resolution targets for every priority level, worked out from the team's own ticket history and the hours the team really has. Each target shows how often the team already meets it, and every gap comes back as a question for the lead to settle.
- Starts it
- Support lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Support ticket triage
Your queue manager opens the morning’s tickets already sorted: each one with a category, a priority and a route, and the reason for all three in a line. The tickets that cannot wait sit at the top, stopped for a person to decide.
- Starts it
- Queue manager
- Brings
- export, notes, document
- Gets
- 4 outputs
Tracking event plan
Before analytics goes onto a website or app, the founder or product owner gets one plan: the events and properties worth collecting, when each fires, where it goes, what it is called and who owns it, each tied to a question the business needs answered. The owner approves what is collected.
- Starts it
- Founder
- Brings
- export, notes
- Gets
- 5 outputs