Workflows Directory
Find your team’s next superpower.
- Function: Legal and contracts
- Function: Product management
- Industry: Manufacturing
- Industry: Software technology
- Clear all filters
Results
31 workflow templates, showing 1 to 24
Acceptance criteria sheet
Hand a developer or agency a story with its definition of done written down: testable expected behaviours, error cases and edge cases, each traced to a rule or design state, with the unclear terms and open questions listed for the product owner.
- Starts it
- Product owner
- Brings
- notes
- Gets
- 5 outputs
Assumption map
For a product owner whose plan rests on beliefs nobody has tested: each belief is written down, set against the evidence you hold, ranked by what it would do to the plan, and given a cheap test to choose from. You decide what to test; no evidence is invented.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 6 outputs
Business model assumptions review
Before you commit money to a new or revised business model, see it block by block with every claim marked evidenced or assumed, the riskiest assumptions ranked, and the cheapest test for each. You choose what to test; no projection or valuation is made.
- Starts it
- Founder
- Brings
- export, notes
- Gets
- 7 outputs
Component inventory audit
When patterns come up for review, the design-system owner gets an inventory built from the library export and its documentation: every component with its naming, token and state gaps, and the pairs that may overlap. Nothing is merged on appearance; the owner decides.
- Starts it
- Design-system owner
- Brings
- export, notes
- Gets
- 4 outputs
Contract amendment trace
Before a question about a signed contract goes to counsel, the contracts manager has one dated history of the provision that matters: every signed document in order, each version quoted with its document and section, every gap marked, and a list for the lawyer to confirm. It never says which wording controls.
- Starts it
- Contracts manager
- Brings
- export, notes, document
- Gets
- 6 outputs
Prepares work for a lawyer. Not legal advice.
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.
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 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
Discovery requests and commitments register
Through discovery, the litigation paralegal keeps one register for the handling attorney: each request and its response in the exact words served, the Bates ranges produced against it, every supplement promised in correspondence with its date as written, and the promises now overdue. The attorney decides what it means.
- Starts it
- Litigation paralegal
- Brings
- export, notes, document
- Gets
- 9 outputs
Prepares work for a lawyer. Not legal advice.
Document production index and summaries
From a production review counsel has cleared, the paralegal prepares a draft for that counsel: an index of every document by Bates range, a short summary of each, every statement cited to its Bates page, missing documents and differing passages listed, and anything matching counsel's screen list held by number only.
- Starts it
- Paralegal
- Brings
- export, notes, document
- Gets
- 9 outputs
Prepares work for a lawyer. Not legal advice.
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
Inbound demand or claim intake record
When a demand, claim or subpoena arrives, the company's lawyer gets one intake record the same day: who sent it, what it asks, every date it states, the facts and citations it relies on, related matters, where the records are, and a question on keeping them. It rates nothing and recommends nothing.
- Starts it
- Legal operations coordinator
- Brings
- export, notes, document
- Gets
- 2 outputs
Prepares work for a lawyer. Not legal advice.
Invention disclosure brief for patent counsel
Before the first call with patent counsel, the founder or engineering lead has one factual brief: the invention in the inventor's words, who contributed what and when, every outside demonstration, sale, talk or publication with its date and audience, and the records still missing. Counsel decides.
- Starts it
- Founder
- Brings
- export, notes, document
- Gets
- 7 outputs
Prepares work for a lawyer. Not legal advice.
IP ownership and licence question table
Before an agreement or statement of work is signed, IP counsel gets one table of the ownership, assignment, licence, background-IP and confidentiality clauses, each quoted with its section, set against the company's own IP positions and led by whether the assignment words counsel expects were found.
- Starts it
- Contracts manager
- Brings
- notes, document
- Gets
- 6 outputs
Prepares work for a lawyer. Not legal advice.
Journey accessibility findings
When a user journey is ready for accessibility review, the reviewer gets a finding list: each finding with its task impact and evidence, the manual checks still required and the limits of the review. The reviewer verifies every finding and agrees fixes with the design owner.
- Starts it
- Accessibility reviewer
- Brings
- export, notes
- Gets
- 5 outputs
Legal hold custodian tracker
Once counsel has issued a legal hold, your legal operations lead keeps one tracker for counsel: every custodian and system in counsel’s scope, who has acknowledged and who is overdue, who has left or changed role, the refresh date counsel set, and reminders copied from counsel’s own text for a person to send.
- Starts it
- Legal operations lead
- Brings
- export, notes, document
- Gets
- 3 outputs
Prepares work for a lawyer. Not legal advice.
NDA check against counsel's approved positions
Before anyone signs a proposed NDA, counsel gets every clause quoted with its section and set beside the positions counsel has approved: matching, departing or not covered. Any obligation beyond confidentiality sends the whole NDA to counsel. The check never says an NDA is ready to sign.
- Starts it
- Salesperson
- Brings
- notes, document
- Gets
- 6 outputs
Prepares work for a lawyer. Not legal advice.
Open-source licence inventory for counsel
Before a release ships or an acquirer asks, counsel and the engineering lead get every open-source package listed with its licence as found, the file and line where it was read, and the duties your own policy attaches to it. A missing, custom or conflicting licence is marked needs review, never cleared.
- Starts it
- Engineering lead
- Brings
- export, notes, document
- Gets
- 5 outputs
Prepares work for a lawyer. Not legal advice.
Outside-counsel invoice questions
When a law firm’s invoice arrives, legal operations has one worksheet ready: every line set against the agreed rates, the approved matter budget and the company’s own billing guidelines, each difference written as a neutral question for the firm. Nothing is sent, paid or rejected until people decide.
- Starts it
- Legal operations manager
- Brings
- export, document
- Gets
- 10 outputs
Prepares work for a lawyer. Not legal advice.
Product pricing options
A product owner weighing how to price or package a product gets one options brief: what each customer group uses, the willingness-to-pay evidence held with stated kept apart from observed, what each option would bill every account, the uncertainties and the tests. It recommends no price.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 6 outputs
Release notes draft
The product owner gets draft release notes for one shipped release, in words users recognize: what is new, changed, removed and fixed, the steps users must take, and the known limitations. Only what was supplied is described. The owner checks and publishes.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 8 outputs