Workflows Directory
Find your team’s next superpower.
- Function: Leadership
- Function: Project and delivery
- Industry: Construction
- Industry: Marketing and advertising
- Clear all filters
Results
34 workflow templates, showing 1 to 24
Client findings validation document
Before research becomes recommendations, the engagement lead sends the client one document: each material finding beside its evidence, the implication proposed and a clear request to confirm, correct or defer it. Nothing is added that the evidence does not show.
- Starts it
- Engagement lead
- Brings
- export, notes, document, pasted text
- Gets
- 5 outputs
Culture health check
A founder or people lead sees whether the company's stated values show up in daily work: each value written as behaviours you could watch for, read against the team's own evidence, with where practice matches, where it drifts, and two or three rituals to try. Reported by team and theme, never about a person.
- Starts it
- Founder
- Brings
- export, notes, document
- Gets
- 7 outputs
Daily production report
When a shoot day wraps, the production coordinator gets a draft daily report from the call sheet, timecards and department reports: hours totaled as written, schedule changes noted, and every missing or overlapping entry listed as a query. The production manager checks it.
- Starts it
- Production coordinator
- Brings
- export, notes, document, pasted text
- Gets
- 5 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
Engagement margin review
Midway or at close, the partner and finance lead get one worksheet for an engagement: recorded time, agreed fee, billed to date and supplied costs by workstream, the gaps that limit it, and the questions the team must answer. No cost rate is invented.
- Starts it
- Finance analyst
- Brings
- export, notes
- Gets
- 6 outputs
Engagement staffing plan
When several engagements want the same people, the resource lead sees the collision before kickoff: role needs against free days, leave and competing assignments, week by week, with two or three staffing options. The resource lead and partners choose.
- Starts it
- Resource lead
- Brings
- export, notes
- Gets
- 6 outputs
Headcount plan
For a founder, people lead or finance lead preparing next year: every role and its cost by team, the new roles and backfills with their months, the fully loaded cost month by month against the budget, and what changes if revenue lands lower or higher. It plans roles and money, never decisions about named people.
- Starts it
- Finance lead
- Brings
- export, notes
- Gets
- 5 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
Missed milestone client reply
When a client challenges a delay, a deliverable or an earlier commitment, the account director gets a draft reply and an internal action note that keep confirmed facts apart from proposed recovery steps and the decisions still needed. Nothing is sent.
- Starts it
- Account director
- Brings
- export, notes, document, pasted text
- Gets
- 2 outputs
Ninety-day marketing plan
An owner or first marketing hire gets the next ninety days of marketing on one plan: the stage the business is really in, the moves that fit it, who owns each one, the money and hours they use, and what is deliberately left undone. Every count comes from your own records, and no budget is invented.
- Starts it
- Owner
- Brings
- export, notes, pasted text
- Gets
- 1 output
Premortem before a decision
Before your team commits to a plan that is hard to undo, such as a move, a launch or a new system, a short workshop pictures it a few months on, already failed. The record ranks the reasons, turns each top risk into a check, a warning sign and an owner, and leaves the go decision with the owner.
- Starts it
- Owner
- Brings
- notes
- Gets
- 4 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 intake and capacity review
When a new initiative is proposed, the portfolio owner sees it scored on the business's own criteria beside the projects already committed, the delivery days it would use month by month, and what it would crowd out or push later. The owner accepts, defers or rejects it.
- Starts it
- Portfolio owner
- Brings
- export, notes, document
- 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
Property diligence index
The transaction lead gets a diligence room in order: every document indexed by workstream, every checklist item and request tracked, and every open finding tied to the report or request that raised it. Specialists judge the findings; nothing is valued or sent.
- Starts it
- Transaction coordinator
- Brings
- export, notes
- 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
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