Controlled client intake

Immigration Client Intake Automation With Attorney Review

A structured intake workflow that collects client facts and documents, exposes conflicts, and prepares an attorney review brief without offering legal advice.

By WhichAI. Published 2026-07-12. Updated 2026-07-12.

Methodology: Editorial synthesis of workflow design patterns and implementation constraints. Public control references provide context, not proof of a deployment or legal advice. Where a versioned evidence pack appears, its evidence class, method, and limitations govern what the artifact can support. Read the full method. Report a correction.

Built for

Immigration attorneys, intake coordinators, paralegals, and firm operations managers

The decision

Decide which intake steps can be standardized while legal issue spotting and advice remain with an attorney.

Answer first

Use structured intake to collect facts, preserve the client's wording, identify missing records, and surface contradictions. Route a sourced intake brief to an attorney before anyone communicates a legal conclusion.

Self-serve workflow planner

Start with this article's task

For Immigration attorneys, intake coordinators, paralegals, and firm operations managers. Start a brief for this task: Decide which intake steps can be standardized while legal issue spotting and advice remain with an attorney.

Start this brief

The capacity leak

What the team is doing before anyone calls it a systems problem

Headcount pressure rarely starts with one giant task. It starts when ordinary work is split across inboxes, tabs, handoffs, and undocumented judgment calls. These are the signals to map first.

SIGNAL 01

Prospective clients repeat the same facts across forms, calls, emails, and document uploads.

SIGNAL 02

Intake staff translate free-form answers into case notes without preserving every original source.

SIGNAL 03

Contradictory dates, names, status histories, and family relationships are discovered during attorney consultation.

SIGNAL 04

The firm cannot distinguish client delay from internal intake delay because milestones are not recorded consistently.

The implementation

The system should prepare the decision, not pretend the decision disappeared

A complete implementation connects the intake, context, transformation, review, and record. The output of one stage becomes the controlled input to the next. A human owns the exceptions and the final consequence.

StageCurrent dragSystem responsibilityHuman responsibilityEvidence kept
1. Consent and scopeIntake begins before the client understands what information is being collected.Present the intake purpose, channel, required fields, and document-handling notice before collection.Approve the intake language and decide which matters the channel can accept.Consent response, notice version, timestamp, and intake scope.
2. Structured factsFacts arrive in narrative messages that must be re-keyed.Collect names, dates, relationships, history, and matter objectives in a structured record.Clarify ambiguous answers and avoid recasting client facts as legal conclusions.Original response, normalized field, editor, and change history.
3. Document intakeFiles arrive across inboxes and text threads without a common inventory.Route uploads into a matter-specific inventory and flag missing, duplicate, or unreadable items.Resolve identity mismatches and decide whether additional records should be requested.File checksum, uploader, category, receipt time, and disposition.
4. Conflict reviewContradictions remain buried in notes until the consultation.Compare structured facts and document fields to produce a conflict and missing-information queue.Determine which conflicts matter and ask the client appropriate follow-up questions.Compared fields, source links, conflict status, and reviewer notes.
5. Attorney briefAttorneys enter consultations without one reliable intake summary.Assemble a source-linked brief that separates client statements, document facts, and unresolved questions.Conduct legal issue spotting, give advice, and approve the next step.Brief version, source map, attorney disposition, and consultation outcome.

What the human keeps

The goal is not zero humans. It is zero avoidable preparation around the judgment only a responsible owner should make.

  • Attorneys interpret facts, identify legal issues, provide advice, and decide whether the firm accepts the matter.
  • Intake staff clarify ambiguous responses and resolve identity, translation, and document exceptions.
  • The client confirms material facts before the attorney relies on the prepared intake brief.

Controls before volume

A workflow is not ready because the happy path worked once. It is ready when access, review, fallback, and evidence are explicit.

  • Preserve original client answers alongside every normalized intake field.
  • Keep each prospective client's files in a separate access-controlled matter space.
  • Label generated summaries as preparation material pending attorney review.
  • Require an attorney disposition before the workflow produces any legal next-step communication.

The scorecard

Measure capacity, not activity

A system can produce more messages and still make the operation worse. Measure movement through the workflow, the quality of review, and the load that still reaches a person.

Intake completion time

Elapsed time from consent to an attorney-review-ready fact and document record.

Consultation gap rate

Share of consultations delayed by facts or documents the intake workflow should have requested.

Conflict discovery timing

Share of material conflicts surfaced before, rather than during, attorney consultation.

Source fidelity

Share of brief statements linked to an original client answer or submitted document.

What a fake implementation looks like here

These patterns create an AI demo while leaving the labor, risk, and accountability in the same place.

  • Presenting automated intake guidance as legal advice or a prediction about the matter.
  • Overwriting the client's original answer with a normalized interpretation that changes its meaning.
  • Combining records from people with similar names without an identity exception.
  • Sending a legal next step before an attorney reviews the complete intake record.

Two ways to act

Use the path that matches the decision

Questions

What operators ask before they build

Can an automated intake tell a client what filing path to use?

The workflow should collect and organize facts, not choose a legal path or advise the client. That decision belongs in attorney review.

What belongs in the attorney intake brief?

Include client-stated facts, document-derived facts, source links, missing items, contradictions, and open questions. Keep legal analysis in the attorney's own review.

How do we avoid losing nuance during normalization?

Store the original response beside the normalized field, record every edit, and route ambiguous language to a person instead of forcing it into a fixed category.

Primary references

Controls should come from the specific operating environment

These are broad public control references, not article-specific evidence, vendor endorsements, or legal advice. Validate the current rules, contracts, system configuration, and organization-specific risk before deployment.

Keep mapping

Related implementation guides