Workflows Directory
Find your team’s next superpower.
- Function: Business systems and integrations
- Function: Legal and contracts
- Industry: Professional services
- Clear all filters
Results
9 workflow templates
App data requirements
When the requirements for an internal app leave fields or actions unclear, the business systems analyst gets one data specification: entities, fields, who reads and writes each, and every unresolved name as a question. Nothing is built or changed.
- Starts it
- Business systems analyst
- Brings
- export, notes, document
- Gets
- 9 outputs
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.
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
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.
Record sharing access matrix
When an approved access policy has to reach the CRM, the system owner lays the current sharing setup beside the proposed one, by record type and by role, internal and external. Every change is a question for its owner; inherited and platform-fixed settings are marked unknown.
- Starts it
- System owner
- Brings
- export, notes
- Gets
- 6 outputs
Service inbox routing plan
When a new service inbox is being set up, the service owner gets a routing plan: each approved address, the queue it should reach and who owns it, checks to run before it goes live, and the wrong-address risks, loop risks and unconfirmed queue owners still open. Nothing is configured.
- Starts it
- Service owner
- Brings
- export, notes
- Gets
- 5 outputs
Workflow inventory
When the ownership and status of your automated workflows come up for review, the platform owner gets one inventory built from the exports supplied: environments, enabled states, last run, queued runs and owner gaps. Quiet workflows become questions, not removal lists.
- Starts it
- Platform owner
- Brings
- export, notes
- Gets
- 7 outputs