What client intake is for
Client intake collects, checks and organises the information a firm needs before it decides how to handle a new request. It is not the same as taking instructions, and it is not the same as opening a matter. It is the stage where a firm works out what it has been asked, whether it can help, and what still needs to be known.
A structured flow gives the firm consistent information for every enquiry and reduces the details that get lost when messages arrive across email, chat, handwritten notes and spreadsheets. For a small firm, the aim is not a long corporate procedure. It is a clear, repeatable first contact that any member of the team can follow on a busy afternoon. If you want the wider picture of how intake, review and client updates connect, the LexFlow walkthrough shows the same journey end to end.
The six steps of a repeatable intake workflow
1. Collect only what is initially needed
The first form should ask for enough to review the request, and nothing more. That usually means name and contact details; a short summary of the issue; key dates and any urgency; the other parties involved; a broad practice area; which documents the client already has; the preferred language for correspondence; and a privacy acknowledgement or consent where it is required.
Mark each field as required or optional, and say why anything sensitive is being asked for. A form that asks for a national identification number with no explanation invites the client to stop halfway. Explain the purpose in one line next to the field, and give the client a way to say 'I would rather discuss this'.
2. Classify and review
A submission should enter review, not automatically become an accepted matter. Between the two there are checks a firm cannot skip: whether there is a conflict of interest, whether the matter falls within the firm's jurisdiction and competence, whether a deadline makes the request urgent, whether the firm has the capacity to take it on, whether the client's identity needs verifying, and whether the service is a good fit for both sides.
Useful statuses for this stage include: new; conflict review; information required; lawyer review; consultation proposed; accepted; declined; and referred. The value of named statuses is that anyone in the firm can see where a request actually stands without asking the person who last touched it.
3. Assign responsibility
Every request needs a visible owner - one person responsible for the review and for the next action. Without an owner, a request can sit with no one aware that it is waiting. With one, the question 'who is dealing with this' has an answer in seconds.
A shared flow makes that ownership legible across roles. Assistants can see which requests are missing information and chase it. Lawyers can see what is waiting on a professional review. Owners can see where their own matters have stalled, rather than discovering it when the client calls.
4. Keep information attached
Connect emails, form submissions, internal notes, tasks and documents to a single matter record instead of leaving them distributed across inboxes and folders. When everything sits in one place, the next person to open the matter sees the whole history rather than a fragment of it, and nobody has to reconstruct the sequence from memory.
Attaching information does not change who may see it. Access must still reflect a person's role, the firm's confidentiality obligations and the security model the firm has approved. A shared record is a shared responsibility, not an open door.
5. Explain what follows
The confirmation a client receives should say three things: that the request was received, whether any information is still missing, and how and when the firm will make contact next. A vague 'we will be in touch' leaves the client calling to check whether the message arrived at all.
Be precise about what has not yet happened. Submitting a form does not by itself create a lawyer-client relationship, and it does not guarantee that the firm will take the matter on. Only approved terms can establish the relationship, so the confirmation should not imply otherwise.
6. Measure sensibly
Track the numbers that reveal where intake breaks down: how many requests are awaiting review, how long they sit unassigned, how often client information is missing, which practice areas generate suitable work, and how many clients abandon the form before finishing. Six honest measures are more useful than a dashboard of twenty.
Where automation and reviewable AI fit
Automation can acknowledge receipt, classify a request by practice area, create a follow-up task, remind staff that a review is outstanding, and ask a client for missing information. Each of those removes a manual step that carries no judgement, which is exactly where automation belongs.
Reviewable AI extraction can map text from a client's message into structured fields - so a date mentioned in a paragraph lands in the right field without someone retyping it. It must remain reviewable and must not make acceptance decisions, give legal advice, or expose sensitive information. A person always confirms what the system proposes. Elisa, the LexFlow intake assistant, gathers the first details of a request for exactly this kind of downstream review; Elisa does not give legal advice and does not replace a lawyer.
The intake flow at a glance
Reduced to its simplest form, the workflow runs like this:
- 1. A visitor submits an enquiry.
- 2. Elisa or a member of staff checks that it is complete.
- 3. A lawyer reviews suitability and conflicts.
- 4. The firm requests missing information or proposes a next step.
- 5. An accepted request becomes a matter.
- 6. The client receives approved access and updates.
The steps are short on purpose. A workflow that nobody follows is worse than no workflow, because it gives the firm the appearance of a process without the reliability. For the client-facing half of this journey, read how a client matter tracker reduces routine status calls.
Scope note
LexFlow is intended to connect intake, matter tracking, responsibility and client updates. Exact fields, integrations, retention periods and automation behaviour vary between firms and deployments, so verify the detail for your own setup rather than assuming a default. Where client information is concerned, we protect the privacy of our customers and their clients using recognised standards as a point of reference - ask us for the specifics that apply to your firm. Form submission does not by itself create a lawyer-client relationship, and Elisa does not give legal advice.
Curious how a structured intake flow would look in your firm? Request a walkthrough and demo, or see what each plan includes on the pricing page.
