Workflows Directory
Find your team’s next superpower.
- Industry: Consumer brands
- Industry: Engineering firms
- Industry: Government
- Industry: Software technology
- Clear all filters
Results
213 workflow templates, showing 73 to 96
Decision log
Your chief of staff keeps one register of what the leadership actually approved, across every meeting and message: each decision with who approved it, each action with one owner and a date, what is overdue, and a flag wherever a new decision clashes with an earlier one or revives a rejected idea.
- Starts it
- Chief of staff
- Brings
- export, notes, pasted text
- Gets
- 5 outputs
Delegation brief and follow-up
Every task a manager hands over goes with a clear brief: what to deliver, in what form, by what date and time, why it matters, who will use it, what the person may decide alone and when the manager will check in. Each week, one list shows what is open, what is late and the next note to send.
- Starts it
- Manager
- 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
Demand and supply review
The operations lead gets one monthly review from the demand plan, confirmed supply and stock: where confirmed and likely demand outrun supply, what that does to inventory, and the decision each function head has to make. Sales ambition stays separate and nothing is forecast beyond your figures.
- Starts it
- Operations lead
- Brings
- export, notes
- Gets
- 7 outputs
Departing-employee knowledge capture
When someone is leaving or changing role, their manager gets an interview guide aimed at what only that person knows, then a handover document the successor can work from, every point traced to the conversations and marked with how sure it is. Nothing is shared until the manager approves.
- Starts it
- Manager
- Brings
- export, notes, pasted text
- Gets
- 2 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
Design handoff record
Before engineering starts, the design owner gets one record built from the approved design: every state, token, breakpoint and content rule either covered or flagged, with each unstated behaviour written as a question. The engineer confirms the questions are resolved.
- Starts it
- Design owner
- 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
Discount request review
Before a price below list goes to a customer, whoever approves it gets one page: the discount and what it costs in margin, every clause of your own written policy met or missed, who approves and in what order, and what the customer gives in return. A person decides; nothing is sent.
- Starts it
- Sales lead
- Brings
- export, notes, document
- Gets
- 7 outputs
Email sequence drafting
People who asked to hear from you get emails worth opening: a welcome, a nurture sequence or a new customer's onboarding, drafted in your voice, each email with one job and one ask, every claim traced to your own facts, and a clear end. You read, load and send them yourself.
- Starts it
- Marketer
- Brings
- notes, document
- Gets
- 4 outputs
Employee offboarding and handover checklist
When someone leaves, your HR lead and their manager share one checklist: every piece of their work handed to a named colleague before the last day, every system on your access register removed by its owner at a set time, and every item of equipment back. Nothing is removed or sent without a person.
- Starts it
- People lead
- Brings
- export, notes
- Gets
- 7 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
Engineering change affected records index
When an engineering change request enters review, the document controller gets one index: the assemblies, revisions, stock and open purchase orders the change reaches in the exports supplied, and a question for each owner wherever the records are unclear.
- Starts it
- Document controller
- Brings
- export, notes
- Gets
- 3 outputs
Estimate basis pack
An estimator pricing a job from drawings, takeoffs and supplier quotes gets one worksheet: every figure with its quantity source, rate source and date beside it, each exclusion listed and every gap already written as a scope question. The estimator verifies; the bid lead decides the figure.
- Starts it
- Estimator
- Brings
- export, notes
- Gets
- 4 outputs
Event plan
Whoever owns one event, a talk, a dinner, a webinar or a stand, gets one plan: the goal and target, who should be in the room, every step before, on and after the day with a date and an owner, and how each conversation is followed up. Nothing is booked, paid or sent by the assistant.
- Starts it
- Owner
- Brings
- export, notes, document
- Gets
- 6 outputs
Executive situation brief
Before a conversation that matters, with a key partner, a major customer or a co-founder, the executive gets one brief from the records they approve: the short version in a sentence, what is already decided and promised, what each side has said, the question to settle and the choices open. The executive decides.
- Starts it
- Executive
- Brings
- export, notes, document
- Gets
- 9 outputs
Expansion whitespace review
For one account or a whole book, the account manager sees what each customer holds against what it could also use, the evidence for every gap, the plays ranked, and one next step and owner for each. A person decides what to propose; nothing goes into the sales system without approval.
- Starts it
- Account manager
- Brings
- export, notes
- Gets
- 5 outputs
Feedback follow-through updates
When a change ships or a decision lands on something customers asked for, your account owner gets the list of who asked, the confirmed status of each request, and an individual draft update for each person in the channel they prefer. No update promises a date or feature the team has not confirmed.
- Starts it
- Account manager
- Brings
- export, notes, document
- Gets
- 5 outputs
Field issue handoff to engineering
When a delivered product misbehaves for a customer, the customer service lead gets one case brief for engineering: the revision and serial references, the symptoms as reported, the photographs supplied, what service has done and the questions still unanswered. It names no cause.
- Starts it
- Customer service lead
- Brings
- export, notes, document, pasted text
- Gets
- 6 outputs
Goal alignment review
Before next period's goals are set, the chief executive sees every team goal mapped to the company priority it serves: goals with no company parent, goals that pull against each other, priorities nobody owns, and the questions for each owner. It judges goals, never people.
- Starts it
- Chief of staff
- Brings
- export, notes
- Gets
- 5 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
Help article from a resolved issue
Turn every answer your team works out once into an article the next customer finds on their own. Hand over a resolved ticket and your list of articles; get back a draft in your customers' words, with their details removed and every step traced to the ticket. Your knowledge-base owner decides what goes live.
- Starts it
- Support agent
- Brings
- export, notes, document, pasted text
- Gets
- 6 outputs
Help centre gap review
Once a period, your support lead sees what the help centre is missing, read from that period's tickets and search log: questions agents answered by hand, articles that fell short, articles search could not find, and one gap list ranked by the tickets an article could have saved. The lead decides what is written.
- Starts it
- Support lead
- Brings
- export, notes
- Gets
- 6 outputs