Workflows Directory
Find your team’s next superpower.
- Function: Information security
- Function: Leadership
- Function: Project and delivery
- Function: Quality management
- Clear all filters
Results
88 workflow templates, showing 73 to 88
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
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
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
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
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
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
Teaching tool vendor data questions
Before a school or college adopts a teaching tool that would handle student or staff information, the privacy or procurement lead gets a scoped question pack on data flows, access, retention and subprocessors, with each supplied vendor document mapped to the questions and the gaps listed.
- Starts it
- Privacy lead
- Brings
- export, notes, document
- Gets
- 5 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
Three-week look-ahead constraint review
Before the coordination meeting, the superintendent gets a brief that sets each planned activity of the next three weeks beside what could hold it up: trades sharing an area, unfinished predecessors, open approvals, late deliveries and unanswered RFIs. The superintendent confirms the sequence and assigns the follow-up.
- Starts it
- Project engineer
- 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