Define consultation readiness before a meeting is booked. Preserve each source, show missing or contradictory inputs, and assign every remediation task. Administrative support can collect approved facts and assemble the packet. A lawyer should decide whether the information is sufficient to proceed, whether legal analysis is needed, and whether the firm will accept the matter.
Scope: This is an operational framework, not legal advice. Each firm must adapt confidentiality, conflicts, communications, retention, supervision, and professional-conduct controls to its jurisdictions and systems.
Why a scheduled consultation can still be unready
A calendar invitation proves that time was reserved. It does not prove that the attorney has usable information.
The incident date may appear in a web form but differ from the voicemail. A party name may be abbreviated. A police-report number may be promised but absent. An uploaded document may exist in email without a link from the intake record. A caller may believe that sending a long narrative completed the intake.
Public law-firm discussions describe people arriving without completed intake forms or enough information to make meetings productive. A separate paralegal discussion describes needing more intake information before attorney review. These statements identify the operational pain; they do not establish a universal list of required facts.
The failure usually has four layers:
- The firm has not defined what “ready” means.
- Required inputs lack source provenance.
- Missing or contradictory items have no accepted owner.
- The calendar proceeds without an authorized release decision.
A longer questionnaire alone will not solve those control failures.
Define readiness without evaluating claim merit
Consultation readiness should answer an operational question: does the attorney have the firm-approved minimum packet, and are exceptions visible?
It should not answer whether the prospect has a viable claim. It should not value damages, calculate a legal deadline, resolve a conflict, or promise representation.
Build a versioned readiness matrix
The practice leader and supervising attorney should approve the matrix. It can identify:
- the consultation type;
- required and optional fields;
- the source expected for each input;
- permitted administrative validation;
- conditions requiring lawyer review;
- who can waive an operational requirement;
- whether the consultation may proceed with an exception; and
- the version and effective date.
Different consultation types may require different packets. The matrix should avoid collecting information merely because a system can store it.
Separate four states
Use precise states instead of a single “complete” checkbox:
- Present: an expected input exists.
- Source linked: the record points to the voicemail, form, message, or document.
- Administratively checked: an approved, nonlegal check was performed.
- Attorney reviewed: an authorized lawyer made the necessary judgment.
Those states prevent a generated summary or copied value from looking more authoritative than its source.
Build the consultation-readiness workflow
Workflow at a glance
- Preserve the original inquiry and assign its identifier
- Apply the attorney-approved readiness matrix
- Link each captured value to its source
- Flag missing, conflicting, illegible, or uncertain inputs
- Assign an accepted remediation owner and next action
- Reconcile returned information to the same record
- Present the packet and exceptions to the authorized lawyer
- Record proceed, proceed-with-exception, reschedule, or other approved instruction
- Reconcile the calendar and notify through approved language
- Audit reopened and overridden readiness decisions
1. Preserve the source
Retain the original voicemail, web form, referral notice, email, or message under firm policy. Give the inquiry one identifier. A structured summary may assist review, but it should link back to the source.
Record later corrections as corrections. Do not silently replace a reported date or party name.
2. Apply the correct matrix
Select the approved matrix for the consultation type and office. Record its version. Staff should not improvise new merit filters when a fact falls outside the form.
3. Classify observable exceptions
Useful administrative exception labels include missing, conflicting, illegible, inaccessible, wrong format, possible duplicate, prospect unavailable, language support needed, source not preserved, and lawyer question raised.
These labels describe record condition. They do not declare credibility, liability, urgency, or legal significance.
4. Require accepted remediation ownership
Each exception needs an owner, an approved next action, and a policy-based review time. Assignment is not acceptance. If the primary owner does not accept, the exception should move visibly to a backup or supervisor.
5. Reconcile new information
An email attachment or returned call should update the original record. Preserve the prior state, the new source, who reconciled it, and any remaining difference. Never mark a field complete merely because something was uploaded.
6. Use an attorney release gate
The authorized lawyer sees the packet, the sources, unresolved exceptions, and prior contacts. The lawyer decides whether to proceed, proceed with a documented exception, reschedule under firm policy, request another action, or make another authorized disposition.
Administrative support may implement that instruction. It should not substitute its own claim evaluation.
Assign responsibilities and decision boundaries
ABA Model Rule 1.18 addresses duties concerning information learned from a prospective client, including when no client-lawyer relationship follows. It is a model rule; each firm must analyze the rules and facts in its jurisdiction.
ABA Model Rule 5.3 addresses managerial and supervisory responsibility for nonlawyer assistance. Its official comment discusses nonlawyers inside and outside a firm. These model provisions do not create one universal intake process.
| Role | May own | Must not decide independently | Completion evidence |
|---|---|---|---|
| Practice leader | Matrix approval and exception policy | Delegation beyond applicable duties | Approved version and effective date |
| Intake manager | Queue design, training, staffing, quality review | Claim merit, legal deadlines, conflicts, representation | Training and audit record |
| Administrative support | Approved fact capture, source linking, missing-item follow-up | Legal advice, valuation, liability, acceptance or decline | Source-linked readiness packet |
| Supervising lawyer | Legal questions and release decisions | N/A within authorized role | Dated instruction and exceptions |
| Technology owner | Access, integration, alerts, logs | Legal or workflow judgment | Test results and incident record |
Control technology and source provenance
The system should expose uncertainty rather than hide it.
Before automating the workflow, document:
- the authoritative system for each field;
- where recordings, forms, and uploads remain accessible;
- how duplicate candidates enter review;
- how generated summaries are labeled;
- how contradictions and corrections remain visible;
- how failed transfers create exceptions;
- who can change a readiness state;
- how access is granted and removed; and
- how retention and deletion follow firm policy.
If transcription or extraction is used, test names, dates, negations, accents, noise, handwriting, truncated uploads, and multiple incidents. A confidence score should not silently become an attorney decision.
Related resources include personal injury practice resources, personal injury law firm support, and broader virtual legal assistant services.
Measure readiness without inventing benchmarks
Establish a baseline before setting targets. The following definitions are examples, not industry benchmarks.
Measures to define
- First-review completeness: Packets meeting the current matrix at first readiness review divided by packets reviewed
- Source-link coverage: Required captured inputs linked to an accessible source divided by required captured inputs
- Exception acceptance: Open exceptions with an accepted remediation owner divided by open exceptions
- Readiness override rate: Consultations proceeding with a documented exception divided by consultations released
Track exception age, reschedules caused by packet condition, repeated requests for the same item, failed uploads, reopened completeness states, and matrix-version errors. Segment results before drawing conclusions.
Review queue indicators
- source preservation
- required input state
- unresolved contradiction
- remediation ownership
- attorney release status
Handle exceptions
Common edge cases include a third party providing information, multiple incidents in one inquiry, uncertain party names, a prospect who cannot use the standard form, inaccessible attachments, language-access needs, possible duplicates, and a reported urgent event.
The workflow should route observable conditions. It should not let support staff conclude that a legal deadline exists or that the firm represents the person. Urgent-event language and destinations require attorney approval.
If the prospect cannot supply an item, preserve that fact. The lawyer can decide whether the meeting remains useful. “Missing” should not automatically mean “poor claim.”
Implement the control
- Map current inquiry sources and consultation types.
- Ask attorneys which inputs they need and which require judgment.
- Approve a minimal, versioned readiness matrix.
- Define exception labels and accepted ownership.
- Configure source links and an attorney release state.
- Test complete, incomplete, contradictory, duplicate, and inaccessible cases.
- Pilot with one team and review false-ready and false-blocked records.
- Train staff on role boundaries and escalation.
- Audit overrides, reopened states, and access.
Decide whether this support model fits
Supervised support can fit when the firm has approved inputs, stable systems, named owners, an attorney release path, and audit access. It may fit especially well when attorneys repeatedly spend consultation time reconstructing information already scattered across channels.
It does not fit when the firm expects a nonlawyer to decide claim merit, interpret law, calculate deadlines independently, clear conflicts, promise representation, or hide uncertainty behind a score. It also will not repair an intake strategy that attorneys have not defined.
Frequently asked questions
How can my personal injury law firm prevent incomplete intake information from wasting attorney consultation time?
Define a versioned readiness matrix, preserve sources, flag missing or conflicting inputs, assign remediation ownership, and require an attorney release decision. Measure packet condition separately from claim merit.
What should my personal injury law firm verify before an attorney consultation is placed on the calendar?
Verify the approved packet requirements, source links, unresolved exceptions, ownership, access needs, and release authority. The exact inputs must come from the firm’s attorneys and applicable obligations.
How do I route incomplete personal injury intakes without letting nonlawyers evaluate the claim?
Route observable record conditions such as missing, conflicting, or inaccessible information. Reserve legal significance, merit, deadlines, conflicts, and representation decisions for authorized lawyers.
What should I do when a prospect cannot provide a requested document?
Record the missing item and the reason without judging the claim. Send the exception to the approved owner and let the attorney decide whether to proceed or request another step.
How can Remote Legal Team LLC support consultation readiness?
Remote Legal Team LLC can discuss supervised administrative support for approved fact capture, source linking, missing-item follow-up, packet assembly, and queue reconciliation. The firm retains supervision and all legal decisions.
Sources and disclosure
- American Bar Association, Model Rule 1.18, accessed 2026-09-13.
- American Bar Association, Model Rule 5.3 and comment, accessed 2026-09-13.
- Public community discussions listed in the internal this workflow source capture were used for discovery, not authority.
