Intake is the operating system between a person asking for help and the firm deciding what happens next. It includes far more than answering: identifying the request, protecting information, routing uncertainty, scheduling appropriate conversations, following up, recording decisions, and handing signed work into the legal team.
When those steps live in individual memory, owners feel the consequences elsewhere. Lawyers are interrupted, callers repeat themselves, marketing receives vague “bad lead” feedback, staff chase work across inboxes, and signed matters reach the case team without a clean handoff.
A dependable law firm intake process gives every inquiry a defined stage, accepted owner, next action, and exception path. This guide shows how to build that system from the firm’s decisions outward.
Define the service before drawing the workflow
Write a short intake service definition with the practice leaders and the intake manager. It should answer:
- Which contact channels and hours does intake cover?
- Which practices, offices, jurisdictions, and languages have approved paths?
- How are existing clients, vendors, job seekers, referrals, and new prospective clients distinguished?
- What information may each role collect or explain?
- Which conditions require attorney or supervisor review?
- When does intake responsibility end, and how does the next team accept the work?
This is where legal and operational authority meet. ABA Model Rule 1.18 addresses duties concerning information learned from prospective clients, including people who do not become clients. It is a model rule. The firm’s lawyers should apply the rules and guidance governing their practice when setting questions, access, retention, conflicts procedures, and communications.
Build one stage map with named exits
The stage map should describe work, not optimism. A practical starting version is:
Scroll sideways to review every column.Each row is shown as a labeled card.
| Stage | Entry condition | Required next action | Exit evidence | Exception owner |
|---|---|---|---|---|
| Received | A distinct inquiry record exists | Acknowledge under the approved channel rule | Receipt and reconnection path recorded | Intake supervisor |
| Contact work | Human contact has not been established | Make the next reason-specific attempt | Contact established, person declines, or approved stop rule reached | Queue owner |
| Preliminary information | Contact established | Collect minimum approved routing/review facts | Required fields plus summary complete | Intake lead |
| Review | An attorney or supervisor decision is needed | Review by the appropriate role | Decision, reason, and next action recorded | Practice review owner |
| Consultation | An appropriate appointment is offered or set | Confirm, remind, and prepare the handoff | Held, rescheduled, canceled, or no-show recorded | Scheduling owner |
| Engagement decision | Firm and prospective client are deciding whether to proceed | Complete approved agreement and acceptance steps | Signed, declined, referred, or pending with reason | Authorized decision owner |
| Matter handoff | Firm has accepted the work under its procedure | Transfer the complete handoff packet | Receiving team accepts | Practice operations owner |
| Closed intake | No intake action remains | Preserve final disposition and required record | Closure rule met | Intake supervisor |
Use the firm’s actual terms. Keep unable to contact, service mismatch, pending review, capacity unavailable, and person declined separate. “Unqualified” is rarely specific enough to improve anything.
An eligible distinct inquiry should mean one deduplicated request included under a stated reporting rule. A preliminary qualified inquiry should not be treated as an attorney-reviewed opportunity. A signed agreement should not automatically be reported as an opened matter.
A script cannot fix an unclear decision boundary. Create an authority matrix before training.
Scroll sideways to review every column.Each row is shown as a labeled card.
| Decision | Intake specialist | Intake supervisor | Attorney/practice leader | Marketing/operations |
|---|---|---|---|---|
| Confirm contact details | Perform under procedure | Coach and audit | Approve boundaries | Specify reporting need |
| Collect preliminary facts | Perform approved questions | Resolve process exceptions | Approve questions and review triggers | Avoid requesting unnecessary data |
| Make a legal or merits judgment | Do not make | Route uncertainty | Decide under firm procedure | No role |
| Offer an appointment | Use approved slot/type | Resolve capacity exception | Approve appropriate appointment paths | Maintain campaign expectation |
| Change service-fit rule | Flag pattern | Propose change | Approve | Supply demand evidence |
| Change status definition | Use current version | Co-own implementation | Approve legal implications | Co-own reporting impact |
Write the “do not decide” boundary as clearly as the permitted tasks. Staff need a safe response when a person asks for a conclusion they cannot give.
Size the work from demand and handling time
Monthly volume hides peaks. Count distinct inquiries by channel, hour, day, practice, and language. Then sample the actual time spent on direct handling, follow-up, documentation, attorney coordination, quality review, and exceptions.
If a firm receives 300 inquiries and direct handling averages 12 minutes, that represents 3,600 minutes, or 60 hours, of direct handling. It does not mean 0.375 of a full-time employee can run intake. The calculation excludes uneven arrival, breaks, repeat attempts, meetings, training, supervision, scheduling, integration failures, and absence coverage.
Create three views:
- Base demand: ordinary volume and work mix.
- Peak demand: busy hours and campaign or seasonal surges.
- Resilience demand: absence, platform failure, and after-hours fallback.
Set coverage after seeing all three. Averages alone produce a team that is perpetually surprised by predictable peaks.
In a Juris Digital podcast conversation with Stewart Guss, Guss described a separate attorney-supervised intake department and the focus it created for the active-case team. He also distinguished that focus and productivity from immediate docket growth. Specialization is an operating choice whose result should be judged in the firm’s own context.
Design the conversation around the next decision
Build guidance in modules rather than one rigid script:
- opening, identity, and reconnection;
- immediate request and approved urgent/sensitive escalation;
- preliminary routing or review questions;
- accurate explanation of what happens next;
- appointment and follow-up modules; and
- approved closure or referral language.
The intake specialist should listen, summarize, and confirm. Required fields do not justify interrupting a person to complete a form in screen order. Ask only what the next responsible decision needs at that stage.
Use paired examples in training. A weak next step is “An attorney will call you.” A stronger version is “Your information is in attorney review. Morgan owns that step, and we expect to update you by 2 p.m. tomorrow.” The wording must match the firm’s real capacity and must not imply engagement before the firm’s process establishes it.
Treat response as a series of queues
Record at least receipt, automated acknowledgment, first human attempt, established contact, accepted review ownership, consultation, and engagement decision. Each interval has a different cause and owner.
Create reason-specific follow-up. A requested callback, missed first contact, pending documents, attorney review, and scheduled consultation should not receive the same message cadence. Define stop rules and protect communication preferences.
Manage the age of open work, not only averages. A queue can have an attractive median while a smaller group waits far too long. Supervisors need the oldest open items, unassigned items, failed transfers, and next actions due today.
JD-100, the companion article on faster intake, goes deeper on these clocks and delay budgets.
Route by appropriateness before availability
Write routing rules in order. A typical firm may first identify existing-client paths and attorney-defined escalation, then likely practice and review needs, then office/language handling, then eligible capacity. Unresolved records go to a named review queue.
Assignment must end in acceptance. A notification to five people is not five owners. Record who accepted, when, the next action, and the fallback when that person becomes unavailable.
Test ambiguous, duplicate, multilingual, after-hours, capacity-constrained, and failed-transfer scenarios. JD-103 provides a complete routing method for multi-office and multi-practice firms.
Create a minimum intake record
The record should contain enough to continue work and explain what happened:
- stable inquiry identifier and linked contact identifier;
- original source evidence and contact event history;
- contact details and communication preferences;
- requested service in the person’s language plus standardized category;
- current stage, disposition reason, owner, next action, and timestamps;
- review and appointment events;
- signed-agreement and opened-matter links where applicable; and
- definition version and material corrections.
Limit access by role and purpose. Preserve the original value when standardizing a reporting field. Do not overwrite “what was received” with a marketer’s later category.
JD-101 provides the companion data-contract and integration design.
Supervise the work through samples and exceptions
A dashboard cannot hear whether a caller understood the next step. Use a balanced sample across staff, shifts, outcomes, channels, languages, and practices. Review listening, accuracy, approved questioning, documentation, escalation, next-step clarity, and follow-through.
Pair that sample with exception counts:
- open inquiries without an accepted owner;
- overdue next actions;
- records stuck in attorney review;
- repeated or failed transfers;
- consultations without a recorded outcome;
- signed agreements without an accepted matter handoff; and
- reconciliation differences between systems.
Coach behaviors and repair the process. If five people make the same mistake, the source may be an unclear rule or impossible workload. If one route fails only after hours, the coverage design may be the problem.
Hand engagement into the case team deliberately
Signing is not the end of intake. Define a handoff packet and require acceptance by the receiving team. It may include the agreement status, approved summary, contact preferences, relevant deadlines flagged under the firm’s procedure, documents received, commitments already made, and outstanding tasks.
The case team should be able to reject an incomplete packet back to a named owner without losing the matter in a general queue. Record the handoff time and acceptance. Keep signed agreement, conflict clearance if applicable, matter opening, and first case-team contact as distinct events.
Run the operation with three review rhythms
Daily control: unassigned records, overdue actions, urgent exceptions, capacity, and failed transfers.
Weekly quality: sampled conversations, coaching actions, routing corrections, inquiry mix, and mature near-term outcomes.
Monthly business review: cohort progression, signed agreements, opened matters, acquisition cost, collected economics when available, staffing, campaign feedback, and process changes.
Counts require definitions and denominators. Show pending and unknown outcomes. Expected fee value, gross fees, collected fees, direct costs, and contribution answer different questions and should remain separate.
A 30-day implementation sequence
Days 1–5: sample recent inquiries, map the current path, define units, and list failures without redesigning everything.
Days 6–10: approve stages, authority, minimum fields, routing order, and exception owners.
Days 11–15: configure one bounded path and write modular guidance. Build test cases before launch.
Days 16–20: train with examples, run controlled records, and correct failed handoffs.
Days 21–30: pilot live work in one channel, office, or practice. Review daily exceptions and a balanced quality sample. Decide what to keep, repair, or expand.
Do not judge long-cycle revenue from an immature 30-day cohort. The first implementation should prove control: records remain intact, owners accept work, staff follow approved boundaries, and exceptions surface.
The operating test
Choose a recent inquiry and ask five questions:
- What did the person ask for?
- What did the firm know, and what remained uncertain?
- Who accepted the next action?
- Did the person receive an accurate expectation?
- Can the firm explain the final status without reconstructing it from inboxes?
If those answers require a cross-functional rebuild, bring the stage map, authority matrix, demand sample, five anonymized paths, and exception report to a JurisOS conversation. Juris Digital can help map how marketing, intake, tracking, and reporting should connect and define the work in a specific proposal. The firm’s lawyers retain the legal decisions; the proposal should define systems, roles, fees, and delivery commitments.
Last updated:
