Short Article Description
Legal client intake is more than collecting a name, email address, and case description. It is the operating process that moves a prospective client from first contact through information collection, conflict review, attorney decision, engagement, payment, and matter creation.
A well-designed intake system reduces repeated data entry, clarifies when attorney judgment is required, and helps information move consistently from one stage to the next. Firm in Motion approaches intake as part of a connected law-firm operating system rather than an isolated form or CRM task. Pasted markdown
Quick Answer
Legal client intake is the structured process a law firm uses to move a prospective client from initial inquiry to an accepted and opened matter.
A complete intake process may include:
Inquiry → structured intake → conflict review → attorney approve or decline → engagement agreement → signature → payment → matter creation → initial client communication
Not every firm will use exactly the same sequence. The important point is that each transition should have a defined condition.
The system should know what information is required, what happens next, where it must wait, and which decisions belong to an attorney.
In This Guide
This guide explains:
- what legal client intake includes
- where intake workflows commonly break
- the difference between an inquiry, prospective client, and open matter in the operating process
- what information should be structured early
- where conflict review fits
- why attorney approval should be an explicit gate
- how engagement, signature, and payment connect to intake
- how information should move into the matter-management system
- what intake automation can and cannot do
- how to design an intake process step by step
- how to evaluate whether your current intake system is working
What Is Legal Client Intake?
Legal client intake is the process of collecting, reviewing, routing, and acting on information from a prospective client before the matter becomes active.
The first inquiry may arrive through:
- a website form
- phone call
- referral
- scheduling system
- another approved contact channel
That inquiry is only the beginning.
A working intake system still needs to determine what information is required, whether the matter fits the firm’s process, whether a conflict issue needs review, whether an attorney approves representation, what documents must be signed, whether a required payment has occurred, and when a matter should be created.
Firm in Motion’s law-firm operations work includes intake, conflict review, attorney approve or decline gates, retainer generation, payment-triggered progression, matter creation, client notifications, and synchronization across connected systems. Pasted markdown
The intake form is therefore not the intake system.
It is one entry point into that system.
Why Intake Breaks Between the Steps
Many intake problems do not begin with bad software.
They begin in the handoffs.
A prospective client submits a form. Someone reads the email. Another person copies the details into a spreadsheet or practice-management platform. Conflict information is sent to an attorney. The approval comes back through email or chat. Staff prepare an agreement, send a payment link, and later create the matter.
Every step may work individually.
The problem is that the transitions depend on people remembering what happens next.
Common signs of intake friction include:
- the same client information being entered in several places
- incomplete intake forms requiring repeated follow-up
- conflict review occurring outside the main workflow
- attorneys approving or declining matters through unstructured messages
- agreements being prepared manually after approval
- payment status being checked manually
- matter creation happening long after the required conditions are complete
- staff not knowing the current intake status
- prospects receiving inconsistent follow-up
- different systems containing different versions of the same information
The operating question is not simply:
“How can we make the intake form faster?”
A better question is:
“How should a prospect move from first inquiry to an open matter?”
That question forces the firm to design the process between the tools.
The Core Stages of a Legal Client Intake Workflow
A useful intake model can be broken into defined stages.
1. First Inquiry
The first inquiry creates the initial record.
At this point, the firm may have only basic information:
- name
- contact details
- referral source
- broad matter type
- brief description
- relevant parties
- requested service
The goal is not necessarily to collect every fact immediately.
The goal is to capture enough structured information to determine the next appropriate step.
2. Structured Intake
If the inquiry should continue, the firm may request more detailed information.
Structured intake means collecting information in defined fields rather than relying only on free-text emails or notes.
That makes the data easier to reuse later.
For example:
Prospect enters address once → intake record stores address → approved engagement document can reuse it → matter record can receive the same value
The exact fields depend on the firm’s practice area and process.
The architectural principle is simple: information that will be needed downstream should not have to be repeatedly re-entered.
3. Conflict Review
Conflict review should be part of the intake process, not an invisible side conversation.
The workflow should define:
- what information is required before review
- who performs the review
- what status means “pending”
- what happens if additional information is needed
- what happens if the matter cannot continue
- what event allows the intake to proceed
The system does not need to make the legal judgment.
It needs to route the information to the right person and wait for the decision.
4. Attorney Approval or Decline
This is one of the most important control points.
A submitted form should not automatically cause every downstream action to begin.
The workflow should include an explicit attorney-controlled decision such as:
Approve → continue
Decline → stop the acceptance path
Need more information → request information and wait
Firm in Motion’s intake implementations specifically include attorney approve and decline gates. Pasted markdown
That separation protects the difference between automated coordination and professional judgment.
5. Engagement Documents
Once the matter is approved, the system may prepare the appropriate engagement documents.
Information already collected during intake can be reused rather than entered again.
The workflow can then track whether the document is:
- generated
- sent
- signed
- awaiting correction
- complete
The important point is not merely generating the agreement.
The system needs to know what the agreement’s status means for the next step.
6. Payment
Some firms require payment or another financial condition before the matter progresses.
If payment is part of the intake path, the workflow should define exactly when it matters.
For example:
Attorney approval → agreement signed → required payment received → matter can open
Another firm may use a different order.
Automation should represent the firm’s actual operating rules rather than force every practice into the same sequence.
Firm in Motion’s implementation patterns include dynamic payment calculation and payment-triggered progression as part of connected law-firm workflows. Pasted markdown
7. Matter Creation
Matter creation should occur at the point the firm’s required conditions have been satisfied.
At that stage, relevant intake information can move into the firm’s matter-management system.
This may include:
- client information
- matter type
- responsible attorney
- key dates
- contact information
- approved fields
- related parties
- initial workflow status
The objective is to avoid rebuilding the matter manually from information that the firm already collected.
8. Initial Client Workflow
Opening the matter is not the end of intake.
It is the transition into service delivery.
The system may then initiate the firm’s next approved actions, such as:
- welcome communication
- scheduling
- document requests
- evidence collection
- initial tasks
- matter-specific workflow steps
Client intake works best when the end of one system state becomes the clear beginning of the next.
Inquiry, Approval, and Open Matter Are Different States
One of the simplest ways to improve intake is to stop treating every prospect record as though it represents the same thing.
These states are different:
| Intake state | What it means |
| Inquiry received | A person has contacted the firm |
| Intake in progress | Required information is still being collected |
| Conflict review | The matter is awaiting review |
| Attorney review | A decision is required |
| Approved | The matter may continue through the acceptance process |
| Declined | The intake stops or follows the firm’s decline procedure |
| Engagement pending | Required documents are not yet complete |
| Payment pending | A required financial condition has not yet been met |
| Ready to open | Required acceptance conditions are satisfied |
| Open matter | The matter has entered the firm’s service workflow |
Clear states make automation safer because every next action is tied to a defined condition.
Without states, automation becomes a series of disconnected triggers.
What Should Be Automated in Client Intake?
Intake contains both repetitive handling and human decisions.
Those should not be confused.
| Good automation candidates | Keep human-controlled where appropriate |
| Creating intake records | Deciding whether to accept representation |
| Sending intake forms | Resolving substantive conflict questions |
| Reusing structured contact data | Evaluating unusual facts |
| Routing information for review | Giving legal advice |
| Creating predefined follow-up tasks | Making legal strategy decisions |
| Generating approved engagement documents | Approving exceptions |
| Tracking signatures | Authorizing consequential actions |
| Updating matter fields | Final substantive review |
| Sending approved status communications | Handling sensitive client situations |
A useful rule is:
Automate coordination. Preserve judgment.
Firm in Motion’s systems-first approach is built around the same principle: repetitive work can move automatically while attorney judgment remains at the appropriate control points. Pasted markdown
How to Design a Better Intake System
A strong intake process should be mapped before it is automated.
Step 1: Map the Current Intake Path
Document what happens today.
Start with the first contact and continue until the matter opens.
Ask:
- Where do inquiries arrive?
- Who sees them first?
- What information gets collected?
- What is entered more than once?
- When does conflict review occur?
- Who approves the matter?
- When is the engagement agreement created?
- When is payment required?
- Who creates the matter?
- Which system owns the final record?
Do not design from assumptions.
Map the process staff actually follow.
Step 2: Define Intake States
Give each meaningful stage a clear status.
Avoid vague labels such as “working on it.”
The team should be able to look at the record and understand what the intake is waiting for.
Step 3: Identify the Source of Truth
Decide which system owns key information.
For example:
- Which system owns prospect contact information?
- Where should matter status live?
- Where should the final client record live?
- Which data should synchronize into other systems?
A connected intake workflow needs one clear answer for each important record.
Step 4: Identify Required Attorney Gates
Mark every point where automation must stop for attorney judgment.
At minimum, this may include acceptance or decline.
Some practices may require other approval points.
Build those decisions into the workflow rather than treating them as interruptions to it.
Step 5: Define Transition Rules
Write every important transition in plain language.
For example:
If required intake information is complete, route the record to conflict review.
If the attorney approves the matter, continue to the approved engagement process.
If required payment has not been received, do not open the matter.
These rules become the operating logic behind the automation.
Step 6: Design for Missing Information
A production intake system needs to know what happens when the ideal path does not occur.
Examples include:
- incomplete form
- duplicate inquiry
- missing opposing-party information
- attorney requests more facts
- agreement needs correction
- signature never arrives
- payment fails
- prospect stops responding
Firm in Motion’s implementation experience emphasizes that the difficult part is often not connecting applications. It is controlling when a workflow should continue, stop, wait, loop, reject, or require attorney judgment. Pasted markdown
Step 7: Test the Full Path
Do not test only:
Inquiry → approved → signed → paid → open
Also test:
Inquiry → incomplete
Conflict review → more information required
Attorney review → decline
Agreement → correction
Payment → failed
Approved matter → duplicate record
A real intake system must handle the branches as well as the ideal path.
Example Intake Process Map
A simplified legal client intake workflow could look like this:
First inquiry
↓
Create prospect record
↓
Collect structured intake information
↓
Check required information
- Complete → continue
- Incomplete → request missing information and wait
↓
Conflict review
- Clear for attorney review → continue
- More information required → request and wait
- Cannot proceed → stop according to firm process
↓
Attorney decision
- Approve → continue
- Decline → stop acceptance workflow
- More information → return to intake
↓
Generate engagement documents
↓
Signature complete?
- No → wait or follow up
- Yes → continue
↓
Required payment complete?
- No → wait
- Yes → continue
↓
Create or update matter
↓
Trigger initial client and matter workflow
This is much more useful than simply saying, “automate intake,” because it defines the states, conditions, and decisions.
Firm in Motion Field Note: Intake Is Part of the Operating System
Firm in Motion has implemented attorney-controlled workflows that connect Gavel, Clio Manage, Make.com, Stripe, Gmail, and Google Calendar. The implementation patterns include intake, conflict review, attorney approval gates, retainer generation, payment-triggered progression, matter creation, client notifications, and data synchronization. Pasted markdown
The main lesson is that intake should not be designed as one isolated form.
The inquiry data needs somewhere to go. Conflict review needs a state. Attorney approval needs a control point. Engagement and payment need defined conditions. Matter creation needs to occur at the correct stage.
When these steps are treated as one operating path, the firm can reduce unnecessary manual coordination without removing attorney control.
That is the systems difference.
Legal Client Intake Readiness Checklist
Before redesigning or automating intake, answer these questions:
- Where can a new inquiry enter the firm?
- What information must be collected first?
- Which information gets entered more than once today?
- What information is required before conflict review?
- Who owns the conflict-review decision?
- What happens when more information is required?
- Who approves or declines representation?
- What event allows the engagement process to begin?
- When does the agreement need to be signed?
- Is payment required before matter creation?
- Which system should become the system of record?
- What data should move into the open matter automatically?
- What happens when a prospect stops responding?
- What happens when a payment or signature fails?
- Who owns intake exceptions?
- How will the firm know that an intake is stuck?
If the answers are unclear, the first priority is process design.
Automation should come after the firm understands how the intake is supposed to move.
How to Evaluate Your Current Intake Process
A better intake process should make the firm’s operating state easier to understand.
Useful questions include:
- Can staff tell where every active intake is waiting?
- Is the same client information being entered repeatedly?
- Are attorney decisions clearly recorded?
- Can the firm distinguish an inquiry from an accepted matter?
- Are engagement and payment states visible?
- Does matter creation depend on someone remembering to do it?
- Are intake records synchronized with the system of record?
- Are exceptions handled through a defined process?
- Does the firm know when an intake has stalled?
These questions are more useful than simply counting how many automated actions exist.
The purpose of intake automation is not to maximize automation.
It is to create a reliable transition from first inquiry to active representation.
Frequently Asked Questions
What is legal client intake?
Legal client intake is the structured process used to collect prospect information, review the potential matter, route required decisions, complete engagement requirements, and move an approved client into an open matter.
Is a website intake form the same as a client intake system?
No. The form only collects information. A complete system also needs workflow states, conflict review, attorney decisions, engagement steps, payment conditions where applicable, matter creation, and downstream communication.
Should conflict review be automated?
The routing, status tracking, and information collection around conflict review can often be automated. The substantive decision should remain with the appropriate attorney or firm personnel according to the firm’s process.
When should a matter be created?
The firm should define the exact conditions that make an intake ready for matter creation. Those conditions may include attorney approval, signed engagement documents, payment, or other firm-specific requirements.
Can intake information be reused after the matter opens?
Yes. One of the strongest reasons to use structured intake is that approved information can move downstream into matter records, documents, communications, and other workflows instead of being entered again.
Should every intake process be identical?
No. Practice areas and firms have different acceptance requirements. The goal is to standardize the repeatable core while creating clear paths for exceptions and attorney judgment.
Conclusion
Legal client intake should function as a controlled transition, not a collection of disconnected administrative tasks.
The first inquiry creates the opportunity. Structured intake organizes the information. Conflict review and attorney approval protect the decision points. Engagement, signature, and payment establish the conditions for the relationship to move forward. Matter creation then transfers approved information into the firm’s active operating system.
The strongest intake systems make these transitions explicit.
They tell the team what state the prospect is in, what the process is waiting for, which information should carry forward, and when an attorney needs to act.
That is the difference between having an intake form and having an intake system.
For more practical guidance on designing reliable law-firm workflows, explore the Firm in Motion Legal Systems Library or review Law-Firm Operations. The Firm in Motion content framework specifically uses these resources to help law firms understand where workflows break, what can be automated, what must remain human-controlled, and how connected legal systems should be designed.