The operating problem
Start with a settlement-related communication being registered. A successful handoff produces a source-linked review task with the responsible lawyer notified. Define the accountable owner before connecting systems. The workflow must not accept, reject, characterize authority, or negotiate an offer. A source event is a request to evaluate the current state; it is not permission to make an irreversible change.
Use your own working copy
The free workbook for this process opens in a browser and works offline after download. It includes editable checks and notes, a text export, and a print view. It is a planning resource: it does not send messages, read account data, or run actions in business systems. No vendor account is needed to use the workbook.
Map the process
1. Preserve the communication
Store the original in the approved matter system and record receipt time and source.
2. Extract candidate logistics
Identify stated dates, parties, and referenced documents with source citations and uncertainty flags.
3. Restrict access
Apply the matter’s approved permissions and exclude terms from shared alert channels.
4. Notify the responsible lawyer
Create an owned review task; a professional determines duties, timing, and client communication.
5. Record the reviewed next step
Link the lawyer-approved action without letting the workflow communicate acceptance.
Information to check
These reference fields describe the process. Use invented values while planning. Keep real records in an appropriate private system; the public website does not need them.
| Reference field | Working record | Check before progressing |
|---|---|---|
| offer_reference | offer_reference | Resolve the stable source reference in the correct client, entity, and engagement. |
| received_at | received_at | Validate the date, timezone, and approved reporting or review period. |
| source_page | source_page | Resolve the stable source reference in the correct client, entity, and engagement. |
| lawyer_task_id | lawyer_task_id | Resolve the stable source reference in the correct client, entity, and engagement. |
Acceptance checks
- An extracted date requires lawyer verification.
- No automated reply can accept terms.
- A repeated source event creates only one current review task.
- A changed source version invalidates an earlier approval.
Walk through a successful example, a duplicate, a missing item, an incorrect match, and an interrupted handoff with synthetic records. Record the expected result, observed result, owner, and recovery action. Checklists record your work; checking a box does not establish that an external action happened.
Ownership and review
Name the person responsible for the process and the person who can resolve an exception. Define which decisions require qualified professional review. Use stable references, limit access to private records, and document when work must stop. Educational material does not establish legal, accounting, tax, security, or regulatory compliance.
Run a measured pilot
Choose a small, reversible sample. Measure handling time, waiting time, review, rework, and errors before changing the process. Include the effort of maintaining the new method. Expand only when the observed result meets your acceptance criteria; a longer checklist is not proof of improved performance.
Use the free workflow planner to define your next step, or compare the assumptions in the opportunity calculator.