The intake handoff is the moment a prospective client becomes someone the firm must serve. It is also where information is most likely to be incomplete, duplicated, or trapped in an inbox. A reliable handoff gives the next person enough context to act without asking the client to repeat the story. It protects the attorney calendar, makes follow up visible, and creates a clear record of what happens next.
Define the stages in client language
Name the stages the client and the team can understand. A simple path might be inquiry, screening, consultation, conflict review, engagement sent, engagement received, and matter opened. Use the firm's actual decisions. Do not create ten statuses because the software offers them. A stage should answer what has happened, what is waiting, and who owns the next action.
Write an entry and exit rule for every stage. “Consultation scheduled” is an entry rule. “The consultation occurred and the next step is recorded” is an exit rule. If a lead can remain in a stage indefinitely, add a date, owner, or follow up rule. The team should see stale inquiries before a prospective client has to ask for an update.
Collect only what the next decision needs
Intake forms become harder to complete when they collect every fact the firm may want later. Start with the information needed to screen the inquiry, identify potential conflicts, schedule the next conversation, and communicate expectations. Add a clear place for unknown information. A blank field should not look like a completed answer. Explain why a required field matters when the client may not know the firm's internal term.
Separate facts from decisions. A form can capture names, dates, opposing parties, contact details, and a plain language description. A trained person or attorney decides whether the inquiry fits the practice, whether a conflict review is needed, and what advice can be given. This separation reduces the risk that a form response is mistaken for legal analysis.
- Prospective client name and safe contact method
- Opposing parties or related organizations for conflict review
- Matter type and key dates as the person understands them
- Requested service and urgency
- Consent and communication expectations required by the firm
Make ownership visible at every handoff
A handoff is not complete when someone forwards an email. It is complete when the receiver accepts the work, sees the required information, and knows the deadline. Use one owner for the next action and one person who can answer a question. If both people are “responsible,” nobody is clearly accountable. Record the acceptance in the intake system or task queue.
Set a response promise the firm can keep. It may be a same day acknowledgement, a scheduled call, or a written update after screening. Use a template that states what the client should do and what the firm will do. Never imply that a consultation is legal advice or that an inquiry has been accepted as representation before the firm has made that decision.
Preserve context when a lead becomes a matter
The handoff from an intake platform to a matter system should carry the contact record, notes, completed forms, communication history, and open questions. Reentering the same facts creates errors and makes the staff member who performs the copy feel responsible for a system problem. If the tools cannot transfer a field, label the gap and assign someone to reconcile it before the matter is active.
Use a conversion checklist. Confirm that the client name is correct, the responsible attorney is assigned, the matter type is accurate, conflict review is recorded, the engagement status is visible, and the first task has a date. Ask another person to review the checklist for high risk matters. The checklist should be short enough to use every time.
Design follow up as a process, not a memory test
Every open inquiry should have a next action, owner, and date. A follow up queue is safer than a personal notebook because the firm can see coverage and aging. Use a simple reason code when an inquiry is waiting: client documents, attorney decision, scheduled consultation, conflict review, or firm response. The reason tells the next person what action is appropriate.
Review the queue at a predictable time. Look for inquiries with no next action, overdue tasks, repeated attempts to reach someone, and inquiries that are close to a stated deadline. Keep the review separate from the attorney's deep work when possible. A support person can prepare the queue, while the attorney handles the decisions that need legal judgment.
Automate the predictable parts with a pause for judgment
Automation can send an acknowledgement, create a task, request a missing document, or schedule a reminder. It should not decide whether the firm can represent a person, give legal advice, or approve an exception without the firm's chosen review. Build a pause into the workflow. The person approving the next step should see the facts that led to it and the source of any generated text.
Clio's workflow guidance describes a trigger, ordered steps, human approval, a skill or firm instruction, and a run record. That model is useful even when a firm uses another platform. Start with a manual checklist, test the sequence, then automate one stable step. Keep a record of failed or cancelled runs so the team can correct the process rather than silently repeat the error.
Measure the handoff from both sides
Measure how long a qualified inquiry takes to reach the next meaningful action. Also measure incomplete forms, duplicate entry, unanswered messages, conversion errors, and client questions about what happens next. A faster handoff that increases confusion is not a successful design. Ask the receiving staff member whether the record was complete and ask the client whether the next step was clear.
Review a small sample each month. Compare the records with the process definition and update the required fields when the same question appears repeatedly. Keep the audit notes separate from client records. A short monthly review protects the process from drift as staff, practice areas, and tools change.
Use support when the queue needs an owner
Some firms have a good intake design but no consistent person to run it. A fractional paralegal or intake specialist can own follow up, prepare summaries, and keep the queue current when the scope and supervision are explicit. The attorney still decides matters that require legal judgment. The support role should have a written escalation path and a secure system for client information.
Woven Legal publishes client intake and legal support as part of its workflow approach. If you speak with the team, bring a stage list, a sample handoff with identifying information removed, and the follow up queue age. Those details make the conversation about the actual process instead of a generic software demo.
Make the change stick
Before you change the intake handoff, write down the current path in enough detail that another person can explain it. Record the trigger, the first owner, the handoffs, the waits, the review points, and the finished result. Use a safe sample when the process touches client information. The sample should include one ordinary case and one case that needs clarification. This baseline prevents the team from comparing a polished example with a messy real one. It also gives the person leading the change a way to answer questions without relying on memory.
,During the first cycle, make the new behavior easy to see. Keep one queue, one status vocabulary, and one place for the next action. Ask the owner to note a blocked item instead of working around it in a private message. The purpose is to learn where a lead that waits without a next action appears. If a person solves the issue with an unrecorded shortcut, capture the shortcut and decide whether it belongs in the standard process. A visible exception is a design input. A hidden exception becomes a surprise later.
,Use a small review sample rather than waiting for a complaint. Check stage age, missing fields, and client questions and compare the record with the definition of done. Look for missing inputs, duplicate entry, unclear ownership, and work that appears complete but still needs a decision. Ask the person who receives the work whether it was usable without another explanation. That question often finds a quality issue sooner than a manager reviewing the dashboard. Keep client facts out of general notes and keep the review tied to the approved matter system.
,If the first result is mixed, keep the useful part and change one variable. You might clarify a required field, move the review earlier, change the queue owner, or shorten the template. Do not add three new tools to compensate for one unclear rule. A process becomes harder to learn each time the team creates a special path. Write the change, the reason, and the date. The next review should test whether the next meaningful action is now easier to complete and easier to check.
,Teach the revised process to a second person before you call it stable. Ask that person to follow the instructions with a safe example and to explain what they would do when a conflict or representation question appears. Notice where the person pauses, asks for a missing decision, or chooses the wrong record. Those moments show where the instructions need a clearer rule. Teaching is also a capacity test. If only the original owner can perform the work, the firm has documented a dependency, not created resilience.
,At the review date, decide whether to keep, revise, or stop the change. Keep the evidence with the process owner and record the next check. A good operating decision can be modest. The firm may decide that the new path saves review time but needs a better intake field, or that a support role should own the queue while the attorney keeps approval. The important result is a shared decision based on the handoff sample and client clarity. That record makes the next improvement faster and prevents the team from reopening the same debate.
,Keep the final decision visible to the people who perform the work. A short note in the queue or process page is enough when it names the owner, effective date, and next review. Visibility turns a one time project into a shared operating habit.
Use this worksheet with your team
Swipe or scroll to see all columns →
| Question | Evidence to collect | Decision |
|---|---|---|
| What stage is this? | Entry and exit rule | Use a status the client can understand |
| What does the receiver need? | Required fields and open questions | Remove duplicate entry and label gaps |
| Who acts next? | Owner, reviewer, date | Assign one next action |
| What can automation do? | Predictable step and approval point | Automate only after manual proof |
Seven checks before you change the process
- Name the stages and their exit rules.
- Collect only what the next decision needs.
- Record an owner and next action for every open inquiry.
- Carry context across systems or record the reconciliation step.
- Keep legal judgment and representation decisions with the responsible attorney.
- Measure completeness, aging, and client clarity.
- Review a sample and update the process each month.
Choose the next practical step
Bring your current intake stages and one anonymized handoff to a Woven Legal strategy call. The goal is to see where information or ownership is lost before you add another tool.
Keep the operating language consistent as you improve the process. Start with workflow, then define the handoff in client intake or delegation. Record the repeatable method in a standard operating procedure. When extra capacity is the answer, compare a fractional paralegal model. Add a quality assurance check, then use document automation and capacity planning only where they reduce work without hiding responsibility.