The operating problem
Start with a first-contact form submission. A successful handoff produces an assigned intake task without premature collection of confidential facts. Define the accountable owner before connecting systems. A receipt acknowledgement must not imply acceptance of representation. 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. Collect minimal details
Ask for contact, broad matter category, location, and party names only as the firm approves.
2. Preserve the inquiry record
Store the original submitted values with access restricted to the intake team.
3. Check scope and urgency flags
Route firm-defined urgency indicators for prompt human review without calculating legal deadlines.
4. Assign an intake owner
Create an acknowledgement target and backup owner for unclaimed inquiries.
5. Send approved next steps
Use neutral wording about the review process and what the prospect should avoid submitting.
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 |
|---|---|---|
| inquiry_id | inquiry_id | Resolve the stable source reference in the correct client, entity, and engagement. |
| matter_category | matter_category | Resolve the stable source reference in the correct client, entity, and engagement. |
| intake_owner | intake_owner | Use the authorized owner or reviewed decision; unknown values stop the handoff. |
| acknowledgement_due | acknowledgement_due | Validate the date, timezone, and approved reporting or review period. |
Acceptance checks
- An acknowledgement contains no acceptance language.
- An urgency flag creates an owned review task.
- 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.