The operating problem
Start with a reviewed discovery request entering the matter. A successful handoff produces an owned response plan with source-linked tasks. Define the accountable owner before connecting systems. Deadlines, objections, scope, and response adequacy are professional decisions. 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. Register the request set
Preserve source document, service evidence, matter ID, and a lawyer-verified request identifier.
2. Create the task structure
Break requests into stable item IDs without rewriting their meaning.
3. Assign collection owners
Map responsive-data categories to authorized custodians and secure collection routes.
4. Review status and exceptions
A lawyer checks scope questions, missing evidence, objections, and reviewed due dates.
5. Control response release
Link the approved response version and delivery evidence to the request set.
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 |
|---|---|---|
| request_set_id | request_set_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| request_item_id | request_item_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| reviewed_due_date | reviewed_due_date | Validate the date, timezone, and approved reporting or review period. |
| response_version | response_version | Bind approval to this exact source version; changes require review. |
Acceptance checks
- A changed request set preserves item history.
- An unreviewed draft cannot be marked served.
- 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.