Workflows Directory
Find your team’s next superpower.
- Function: Analytics and reporting
- Function: Project and delivery
- Industry: Construction
- Industry: Energy
- Industry: Software technology
- Clear all filters
Results
35 workflow templates, showing 1 to 24
Comparison claim check
A manager holding a claim such as "version B converts better" and two groups of numbers gets back the method used, the size of the difference, how uncertain it is, the assumptions checked, and plain wording for what the data does and does not support. The manager decides what to do.
- Starts it
- Analyst
- Brings
- export, notes, pasted text
- Gets
- 7 outputs
Creative test evidence review
When a batch of ad creative is ready for review, the creative strategist and media lead get an evidence table by creative, angle, format and hook, with tentative learning and next-test options. No winner or loser is named, and thin evidence is held back.
- Starts it
- Creative strategist
- Brings
- export, notes
- Gets
- 6 outputs
Dashboard brief
Before anyone builds the dashboard, the requester gets one brief that settles the work: the decisions it serves, what is shown, each metric's definition, the filters, notes on every source and who refreshes it. The requester approves what is shown and the definitions.
- Starts it
- Analyst
- Brings
- export, notes
- Gets
- 4 outputs
Dataset profile
Before anyone joins or relies on a new export, the analyst gets one profile of it: what one row stands for, where keys repeat, what is missing, which values look odd, and a numbered list of questions for the data owner. No data is changed and no verdict is given.
- Starts it
- Analyst
- Brings
- export, notes
- Gets
- 4 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
Hiring pipeline status report
Each week your people lead or founder sees every open role on one page: applications at each stage, days open against the target, roles running late, pass-through between stages, which sources lead to interviews, and every blocker with its owner. It counts; it never assesses a candidate.
- Starts it
- People lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Implementation blocker brief
When a customer's setup milestone slips, the implementation lead gets one brief: the missing inputs, the unresolved access and data questions and the dependencies behind the delay, each with its source and an owner, plus points to raise with the customer.
- Starts it
- Implementation lead
- Brings
- export, notes
- Gets
- 6 outputs
Launch checklist
Whoever owns a launch date gets one dated checklist for the weeks before, the day itself and the weeks after, with an owner on every line. Each announcement is written out so the approver sees exactly what goes out, to whom and from where before saying go. Nothing is announced by the assistant.
- Starts it
- Owner
- Brings
- export, notes
- Gets
- 6 outputs
Lead form field review
When a client questions a long inquiry form or abandoned submissions, the conversion lead gets a field-by-field review: what each field is used for downstream, where people leave, and proposed labels, error messages and test questions. The lead and the client's data owner decide every change.
- Starts it
- Conversion lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Lead quality pattern review
When sales feedback or results raise a lead-quality concern, the acquisition lead gets a review of leads and their outcomes by source, page, location, device and timing, with cases to verify with sales and possible measurement faults listed.
- Starts it
- Acquisition lead
- Brings
- export, notes
- Gets
- 5 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
Metric definition reconciliation
When two reports give different numbers for one metric, the owner gets a page: the definitions side by side, the gap bridged step by step from supplied records, each cause marked shown or not, and a proposed common measure. The owner chooses.
- Starts it
- Analyst
- Brings
- export, notes, document
- Gets
- 7 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
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