Workflows Directory
Find your team’s next superpower.
- Industry: Construction
- Industry: Education
- Industry: Insurance
- Industry: Professional services
- Industry: Software technology
- Clear all filters
Results
237 workflow templates, showing 49 to 72
Contract intake brief
When another party's agreement arrives, counsel gets a one-page intake brief: what it is, read from its titles, the parties as named, what is missing, the requester's purpose and date, and the reviewer your own routing rules name. It comments on no term; counsel decides.
- Starts it
- Contracts manager
- Brings
- notes, document, pasted text
- Gets
- 6 outputs
Prepares work for a lawyer. Not legal advice.
Contract issues table for counsel
Before counsel negotiates a vendor or customer agreement, the contracts team hands over one cited issues table: every clause quoted with its section, the playbook position it meets or departs from, the playbook’s fallback wording copied beside each departure, and the approver your matrix names. Counsel decides.
- Starts it
- Contracts manager
- Brings
- notes, document, pasted text
- Gets
- 7 outputs
Prepares work for a lawyer. Not legal advice.
Contract renewal and notice register
From your signed agreements and amendments, the contracts manager gets a register for counsel to confirm: each term, renewal and notice clause quoted with its section, cancel-by and send-by dates proposed only under counsel's own counting rules, and the windows sorted by proposed send-by date. Nothing is sent.
- Starts it
- Contracts manager
- Brings
- export, notes, document
- Gets
- 5 outputs
Prepares work for a lawyer. Not legal advice.
Contractor safety prequalification
For a named job, the operations, facilities or site manager gets a safety questionnaire scaled to the risk of the work, then a record of the contractor's answers scored only on the evidence supplied, with every gap, the conditions that close it and a review date. A competent person decides.
- Starts it
- Operations manager
- Brings
- export, notes, document
- Gets
- 7 outputs
Copy edit with a change list
Hand over a page, an email or a brochure and get it back plainer and tighter, with no claim stronger than the statements you can support and a change list that shows every edit, its reason and any meaning it moved. You approve each change before the copy is used.
- Starts it
- Marketing coordinator
- Brings
- export, notes, pasted text
- Gets
- 6 outputs
Cost of poor quality worksheet
An owner or operations lead who senses that rework, scrap and returns are costly gets one worksheet: the failure costs already on record, sorted by category, with estimates, gaps and unresolved allocations listed. The owner decides what to fix first.
- Starts it
- Owner
- Brings
- export, notes
- Gets
- 6 outputs
Course catalog quality check
The registrar's office gets one comparison of a department's course updates against the current catalog export: codes, titles, credits, descriptions and linked components, row by row, with every conflict set out as a question for academic review. No catalog record is changed.
- Starts it
- Catalog coordinator
- Brings
- export, document
- Gets
- 5 outputs
Course sequence and workload review
A course lead revising an outline for the next cohort gets a module map: learning goals, prerequisites, activities and the instructor's own time estimates, with crowded weeks and coverage gaps marked and every gap written as a question. The course lead decides what changes.
- Starts it
- Course lead
- Brings
- export, notes
- Gets
- 4 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
CRM field ownership map
Before a CRM sync or field mapping changes, the systems owner gets a field map from the supplied exports and sample records: each field's source, match keys and conflict rule, with unclear keys, consent fields and duplicates left as questions for each field's owner.
- Starts it
- Systems owner
- Brings
- export, notes
- Gets
- 7 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
Current experience baseline
Before a redesign, the design lead gets a baseline built from the captures and page list they supply: each page read with its content and design observations, the patterns that recur, and the pages outside the evidence. The lead confirms the baseline and sets the scope.
- Starts it
- Design lead
- Brings
- export, notes, document
- Gets
- 6 outputs
Customer case study
With a customer who has agreed to help, prepare the interview, then turn their words and the figures they supply into a case study in a short and a long version. Every quotation and number is listed for the customer to approve in writing, and nothing is published or named before they do.
- Starts it
- Marketer
- Brings
- export, notes, document, pasted text
- Gets
- 5 outputs
Customer feedback themes
Each month your support lead sees what customers keep telling you: tickets, disputes, reviews and survey comments grouped into themes with counts and quotations, the three issues most worth fixing with a proposed fix and owner, and a note for customers once a fix ships. A person decides every fix.
- Starts it
- Support lead
- Brings
- export, notes, document
- Gets
- 5 outputs
Customer interview synthesis
Turn a stack of customer call notes into the answer to one question, in your customers’ own words. Every quotation is cited to the note it came from, every theme shows its confidence and the evidence against it, and nothing is claimed that the notes do not say.
- Starts it
- Founder
- Brings
- notes
- Gets
- 5 outputs
Customer onboarding plan
For every new customer, your customer success lead gets one plan for the first weeks: the result the customer must reach, the fewest milestones that get them there with an owner on each side, the promises both sides made, and each message as a draft. Nothing is sent until a person approves it.
- Starts it
- Customer success lead
- Brings
- notes, document
- Gets
- 6 outputs
Customer reply drafting
Every customer gets the reply your best person would write. Hand over the customer's message, your tone guide and your approved answers, and get back a draft in your voice where every statement and every promise traces to something you approved. A person on your team reads it, edits it and sends it.
- Starts it
- Support agent
- Brings
- notes, document, pasted text
- Gets
- 3 outputs
Customer satisfaction detractor follow-up
Every week your support lead gets each low satisfaction or recommendation score with the ticket behind it: the customer's own words, what went wrong as far as the ticket shows, a suggested owner and a draft message, plus the trend and a warning wherever the numbers are too thin to read. A person sends every message.
- Starts it
- Support lead
- Brings
- export, notes, pasted text
- Gets
- 7 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
Deal close plan
Your account executive holds one late-stage deal on two pages: the buyer's case for buying now, counted from the buyer's own figures, and a dated plan of every step to signature with its owner on each side. The seller decides what the buyer sees; nothing reaches the sales system without approval.
- Starts it
- Account executive
- Brings
- export, notes, document
- Gets
- 4 outputs
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