Workflows Directory
Workflow templates for legal and contracts or product management
Results
38 workflow templates, showing 25 to 38
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.
Privilege log entry check
Before a draft privilege log goes to review counsel, the paralegal gets an entry-by-entry check against counsel’s approved format and role map, and a list of logged documents’ attachments with no entry. It checks metadata only: review counsel makes every privilege call and writes or approves every description.
- Starts it
- Paralegal
- Brings
- export, notes, document
- Gets
- 6 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
Product sample feedback revision list
After each round of samples, your product lead gets one revision list by sample version and feature: the changes people agree on, the feedback that conflicts, and drafted notes for the next supplier brief. The product owner decides.
- Starts it
- Product lead
- Brings
- export, notes, document
- Gets
- 7 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
Research plan for counsel
Before an associate or paralegal starts on a partner's research question, they hold a one-to-two-page plan: the question split into sub-questions, the stated facts against each, the firm's own notes to read first, where to search and with what terms, and the gaps. Leads, not authorities: nothing is named from memory.
- Starts it
- Associate
- Brings
- export, notes, document
- Gets
- 6 outputs
Prepares work for a lawyer. Not legal advice.
Roadmap tradeoff review
When a new priority arrives, the product owner sees what the roadmap would have to give up to hold it: the capacity gap by team, the work that could move, the commitments and dependencies that move with it, and the questions still open. The owner decides.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 8 outputs
Smallest useful release scope
A product owner or founder with more features than capacity gets one page: what is in the first release and what is deferred, all tied to one user outcome, with the reason for each cut. The owner decides the scope; no effort is estimated beyond what is supplied.
- Starts it
- Product owner
- Brings
- export, notes
- Gets
- 7 outputs
Technical demo plan
Before a technical discovery or demo meeting, the account executive and solutions engineer get an attendee brief, a demo sequence built around the buyer's stated workflow from approved scenarios, and open questions. Requests nobody has verified stay questions.
- Starts it
- Account executive
- Brings
- export, notes, pasted text
- Gets
- 7 outputs
Tracking event plan
Before analytics goes onto a website or app, the founder or product owner gets one plan: the events and properties worth collecting, when each fires, where it goes, what it is called and who owns it, each tied to a question the business needs answered. The owner approves what is collected.
- Starts it
- Founder
- Brings
- export, notes
- Gets
- 5 outputs
Usability test session plan
Before a prototype or a confusing flow goes in front of users, the research lead and product owner hold one plan: who to recruit, the tasks in plain words, the neutral prompts, a blank note sheet and how success is counted. Recording and data handling are listed as decisions.
- Starts it
- Product owner
- Brings
- notes, document
- Gets
- 9 outputs
User research plan
When a design decision needs user evidence, the research lead gets one study plan: what the team needs to know, what evidence already exists, method options with their hours, participant criteria, permissions needed, how answers will be read and what the study cannot establish.
- Starts it
- Research lead
- Brings
- export, notes
- Gets
- 9 outputs
Weekly status requests to outside counsel
Every Monday, in-house counsel has a draft status request for each outside firm that owes one: what has happened since the last update, the dates on record to confirm, decisions pending and spend against budget, plus the matters skipped and why. Counsel edits and sends each one.
- Starts it
- Legal operations manager
- Brings
- export, notes, document
- Gets
- 2 outputs
Prepares work for a lawyer. Not legal advice.