Workflows Directory
Find your team’s next superpower.
- Function: Leadership
- Function: Project and delivery
- Industry: Construction
- Industry: Government
- Industry: Manufacturing
- Business situation: Established businesses
- Clear all filters
Results
27 workflow templates, showing 1 to 24
Academic calendar check
While year, term and session dates are being assembled, your registrar gets a draft calendar with every registration window tied to its term, and every conflicting, missing or out-of-bounds date listed as a question. Nothing is published or changed.
- Starts it
- Registrar
- Brings
- export, notes
- Gets
- 3 outputs
Annual operating budget
For an owner or finance lead preparing next year: revenue and costs by month and by team, built from this year's figures and each budget owner's drivers, every assumption written down, capital purchases listed apart, the whole checked against cash, and the questions leadership has to settle.
- Starts it
- Finance lead
- Brings
- export, notes
- Gets
- 10 outputs
Business line investment review
For leadership with several business lines: each line set side by side on one basis (fit with strategy, finance-reviewed results, shared resources, open questions) and placed as invest, investigate or reduce commitment, for the leadership team to discuss and decide.
- Starts it
- Finance lead
- Brings
- export, notes
- Gets
- 6 outputs
Deliverable issue completeness check
As a calculation, report or drawing package nears issue, the quality reviewer or document controller gets a checklist: missing review records, revisions that disagree between the index, the register and the title block, and citations of out-of-date calculations. Issue stays with the engineers.
- Starts it
- Quality reviewer
- Brings
- export, notes
- Gets
- 5 outputs
Design assumption change register
When client criteria or design assumptions change, the project engineer gets one sourced register: what changed, which recorded requirements it touches, how firm each source is, and what still needs confirmation. No design basis is altered.
- Starts it
- Project engineer
- Brings
- export, notes
- Gets
- 6 outputs
Discipline interface issue register
After a coordination meeting exposes conflicts between disciplines, the design coordinator gets one register: each conflict from the minutes, linked to the clash-export rows and model revisions involved, with the lead who owns each system and the decision still needed. Nothing is resolved.
- Starts it
- Design coordinator
- Brings
- export, notes, document
- Gets
- 5 outputs
Employee health plan comparison
For an owner or people lead at renewal: the broker's health plan options next to each other, with premiums split between company and employee, deductibles, out-of-pocket limits, network notes, the cost to the company and to a typical employee at low, middle and high use, and questions for the broker.
- Starts it
- People lead
- Brings
- export, notes, pasted text
- Gets
- 6 outputs
Inbox triage
The owner, or the assistant who keeps their inbox, starts the day knowing what needs a reply today, what can wait and until when, and what belongs to someone else, with a draft or a forwarding note for each. Nothing is sent, archived, deleted or moved, and no mailbox login is needed.
- Starts it
- Executive assistant
- Brings
- export, notes, pasted text
- Gets
- 6 outputs
Leadership meeting rhythm
Your chief executive gets a proposed calendar of leadership forums and written reports, built from today's meetings and the decisions left waiting: each forum with its purpose, inputs, attendees, frequency and one decision owner, and the hours it gives back. The chief executive chooses; no calendar is changed.
- Starts it
- Chief executive
- Brings
- export, notes
- Gets
- 7 outputs
Meeting agenda, notes and follow-ups
Whoever runs the meeting walks in with an agenda where every topic has an outcome and a time, and walks out with a one-page record: what was decided, who owns each action and by when, and what is still open. Nothing reaches anyone until that person has read it and sends it.
- Starts it
- Team lead
- Brings
- notes
- Gets
- 4 outputs
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
Project handover readiness check
When a finished deliverable is ready for the team that will run it, the project manager brings one checklist against that team's own requirements: acceptance evidence, instructions, access, training, support owners and open items. The receiving owner accepts or names the conditions still to meet.
- Starts it
- Project manager
- Brings
- export, notes
- Gets
- 6 outputs
Project lessons review
When a phase or a project ends, the project manager gets one blameless review: whether it achieved what it was for, how scope, schedule and budget moved and why, whether the success measures were the right ones, and practice changes for the team to choose, each with an owner and a follow-up date.
- Starts it
- Project manager
- Brings
- export, notes
- Gets
- 8 outputs
Project scope baseline
A project manager turns an approved brief into a draft scope baseline: the deliverables, what is excluded, the acceptance criteria for each deliverable, the constraints and the open questions for the sponsor. Nothing implied counts as scope until the sponsor says so.
- Starts it
- Project manager
- Brings
- export, notes, document
- Gets
- 7 outputs
Project status report
The lead of an internal project gets a status report the sponsor can read in two minutes: each workstream red, amber or green with the reason, what moved, who must clear each blocker, the decisions needed and the dates at risk. No milestone is called done without evidence, and the lead confirms every status.
- Starts it
- Project lead
- Brings
- export, notes, pasted text
- 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
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
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
Schedule recovery options
When a committed milestone slips, the project manager brings the sponsor two to four ways back: what each changes, the dates it gives every later milestone and dependency, and the assumptions it rests on. The sponsor chooses; delivery leads confirm the dates.
- Starts it
- Project manager
- Brings
- export, notes
- Gets
- 5 outputs
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
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
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