The operating problem
Start with an approved client communication entering the matter inbox. A successful handoff produces an assigned response task with sensitivity and timing visible. Define the accountable owner before connecting systems. The workflow must not issue legal advice or disclose matter details in routing alerts. 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 communication
Capture the approved message reference, matter candidate, receipt time, and channel.
2. Resolve the relationship
Verify client and matter association; ambiguous or prospective contacts enter intake review.
3. Apply firm-defined priority rules
Route urgent indicators to a person without calculating legal consequences or inventing deadlines.
4. Assign a response owner
Create a task with the approved service target and backup contact.
5. Reconcile the response
Record the actual reviewed response reference and stop reminders when the owner confirms completion.
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 |
|---|---|---|
| message_id | message_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| matter_id | matter_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| response_owner | response_owner | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
| response_reference | response_reference | Resolve the stable source reference in the correct client, entity, and engagement. |
Acceptance checks
- An ambiguous sender cannot receive matter details.
- A receipt acknowledgement cannot count as a substantive response.
- 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.