How Can a Personal Injury Firm Build a Supervised Intake Workflow?

Scope: This is operational information, not legal advice. ABA Model Rules are models, not automatically controlling law. Each firm should check its jurisdictions, matters, contracts, technology, and professional obligations.

Why intake breaks under volume

Intake is not one task. It is a chain of receipts, questions, records, checks, decisions, and follow-ups.

Public practitioner discussions show why ownership matters. Some firms use reception for initial details. Others rely on dedicated intake teams, paralegals, or rotating backups. Another discussion describes the handoff into the firm’s system as harder than answering the first call.

Those comments are not proof of an industry benchmark. They do identify useful design questions:

• Who acknowledges an inquiry?
• Where does the original submission live?
• Who checks whether required fields are complete?
• Which issues immediately reach an attorney?
• Who records the attorney’s decision?
• Who follows up when the prospective client does not respond?
• What happens when the primary owner is absent?

A vague answer to any question creates a queue that may exist only in someone’s inbox.

Define the authority boundary first

The workflow should separate administrative intake support from professional judgment.

The ABA’s discussion of Formal Opinion 506 says trained and supervised nonlawyers may assist with specified prospective-client intake tasks. It also explains that whether a question requires an attorney depends on the question and the applicable jurisdiction.

ABA Model Rule 5.3 addresses managerial and supervisory responsibilities for nonlawyer assistance. Its official commentary also discusses outside providers, instructions, information protection, and jurisdictional context.

For workflow design, support staff can use an attorney-approved script to collect facts and prepare a review packet. They should not independently:

• tell someone whether a valid claim exists;
• decide a conflict;
• calculate or set a legal deadline;
• interpret an agreement or negotiate a fee;
• accept or decline representation;
• promise an outcome; or
• imply that completing intake created an attorney-client relationship.

The firm’s written rules should identify who may make each decision. Labels alone are insufficient without training, review, and escalation.

Use an end-to-end intake workflow

1. Capture the original inquiry

Receive the call, form, email, referral, or message in an approved business channel. Preserve the original submission. Create a unique intake record instead of copying fragments into personal notes.

The acknowledgment should state what happened next without making a representation promise. It can confirm receipt, identify the staff role, and explain that attorney review may be required.

2. Collect approved fields

Use an attorney-approved question set. Collect only information required for routing, conflict screening, and review. Mark unknown values as unknown. Do not fill gaps with assumptions.

3. Normalize without changing the source

Prepare a concise intake packet while retaining the source material. A summary should link to the original call note, form, email, or document. The reviewer should be able to verify important details.

4. Route conflict data

Send names and related parties through the firm’s approved process. A possible match, missing name, or ambiguous entity belongs in an exception queue. Staff may record the output, but the authorized decision-maker resolves it.

5. Route urgency and legal questions

Use predefined escalation triggers. Examples include an asserted deadline, an imminent proceeding, safety concerns, unclear jurisdiction, a request for legal advice, or incomplete party information.

Support staff should not calculate a deadline or assess the claim. They should preserve what the person said and alert the designated attorney.

6. Complete attorney review

Give the reviewing attorney the intake packet, source links, conflict status, open questions, and urgency flags. The attorney records the decision and any approved next communication.

7. Communicate and close the loop

Send only an approved communication through an approved channel. Record the send, delivery status, response, next owner, and next review time. If the firm does not accept the matter, use the firm’s jurisdiction-appropriate process.

8. Transfer accepted matters deliberately

After the authorized acceptance steps are complete, open the matter through the approved workflow. Transfer the source packet, decision record, responsible attorney, support owner, and outstanding tasks. Do not treat an intake record as an active matter prematurely.

Workflow at a glance

1. Capture original inquiry
2. Acknowledge without promising representation
3. Collect approved fields
4. Preserve sources and prepare packet
5. Run supervised conflict process
6. Escalate urgency and legal questions
7. Obtain attorney decision
8. Communicate and record outcome
9. Transfer accepted matter

Assign responsibilities and controls

The table is a design template. Firms must adjust it to their rules and staffing.

Design technology around the workflow

A system should expose ownership, status, sources, and exceptions. It should not obscure them behind automation.

Useful configuration questions include:

• Does every channel create one traceable record?
• Can staff see the original submission beside a summary?
• Are permissions limited by role?
• Are conflict flags separated from conflict decisions?
• Can staff stop automation and reach an attorney?
• Does the audit trail show edits, decisions, and sends?
• What happens when an integration fails?
• How are retention, deletion, and vendor access governed?

An automated classification is not a legal conclusion. A generated summary is not a verified source. A scheduled message is not proof of delivery.

Measure control, not promises

The firm should define measures before a pilot. Do not borrow vendor benchmarks without verification.

Measures to define

• Receipt-to-acknowledgment time: Elapsed time from recorded receipt to approved acknowledgment
• Complete-packet rate: Percentage of attorney reviews receiving required fields or documented exceptions
• Attorney-review age: Time an intake packet waits for the designated attorney decision
• Unowned-intake count: Open intake records without a named current owner
• Escalation-resolution time: Elapsed time from an exception flag to documented disposition

Counts need definitions. For example, decide whether the acknowledgment clock pauses outside coverage hours. Document exclusions and system outages. Review trends by channel and workflow stage without presenting internal targets as legal requirements.

Review queue indicators

• current owner
• attorney-review age
• conflict exception status
• urgency flag
• delivery failure
• backup coverage

The accessible dashboard should offer text labels, sortable tables, keyboard navigation, readable contrast, and mobile stacking. Color must not be the only risk indicator.

Handle exceptions and jurisdictional differences

The ordinary path is only half the design. Test these cases:

• the person asks whether they have a case;
• a relative submits information for an injured person;
• key party names are missing;
• a potential conflict appears;
• the person reports an urgent date;
• sensitive documents arrive through an unapproved channel;
• the intake owner is absent;
• the reviewing attorney does not respond;
• the acknowledgment or follow-up fails delivery;
• two records appear to describe the same inquiry;
• the firm serves several jurisdictions with different rules.

Create an owner and response path for each. Do not convert jurisdictional uncertainty into a universal answer.

Implement the workflow

1. Inventory every intake channel and current owner.
2. Map the current path using real, de-identified examples.
3. Separate administrative steps from attorney decisions.
4. Approve scripts, fields, access, retention, and escalation triggers.
5. Configure one system of record and test integration failures.
6. Train the primary owner, backup, reviewer, and policy owner.
7. Pilot one bounded channel or team.
8. Sample packets against original submissions.
9. Review exceptions and update the playbook.
10. Expand only after ownership and attorney review remain visible.

Decide whether this model fits

This model may fit a firm with recurring intake volume, defined attorney reviewers, and a willingness to document authority. It may also help teams separating intake coordination from higher-value paralegal case work.

It is not a fit when the firm expects a nonlawyer or tool to make unsupervised legal decisions. It also fails without a real attorney-review path, approved systems, backup coverage, and jurisdiction-specific governance.

After the workflow is defined, firms evaluating supervised virtual legal support for personal injury firms can compare proposed roles against the same responsibility and control map. The broader personal injury law firm support resources provide the practice context.

Frequently asked questions

Which prospective-client intake steps can trained support staff perform?

Under the ABA Model Rules framework discussed above, trained and supervised staff may support specified information-gathering and process steps. The exact boundary depends on the task, jurisdiction, and arrangement. Attorneys should define and supervise the work.

Can intake staff tell someone whether the firm will take the case?

Only through the firm’s authorized process and approved communication. Support staff should not independently evaluate a claim, resolve a conflict, negotiate fees, or imply representation.

What should a personal injury intake dashboard measure?

Measure workflow control: acknowledgment time, packet completeness, attorney-review age, unowned records, unresolved exceptions, delivery failures, and backup coverage. Values and targets should be firm-defined.

Can a virtual legal assistant support this workflow?

A virtual legal assistant may support documented administrative steps within approved access, training, supervision, and review controls. The assistant should not give legal advice, exercise attorney judgment, or independently accept a matter.

Sources and disclosure

• American Bar Association, Rule 5.3 and official commentary, accessed 2026-09-13.
• American Bar Association Litigation Section, “ABA Ethics Opinion Offers Clarity on Use of Nonlawyers,” discussing Formal Opinion 506, accessed 2026-09-13.
• Public community sources informed operational questions only; they were not used as legal authority or performance evidence.

Last updated: 2026-09-13.