Keep a cleared prospect in a controlled pending state until the lawyer-approved contingency agreement is complete. Verify the client, agreement version, required signatures, and unresolved exceptions. Then require an authorized activation decision, create the correct matter, reconcile downstream systems, and confirm the start state. Support staff may administer these steps; they should not decide whether representation exists.
Scope: This is an operations framework, not legal advice or a conclusion about when a lawyer-client relationship forms. Counsel must configure agreement content, authority, signature, acceptance, urgent-action, and jurisdiction-specific requirements.
Why “sent” and “signed” are not activation controls
An intake dashboard may show an agreement as sent or completed. That label does not prove the firm used the lawyer-approved version, named the correct client, captured every required signature, resolved edits, or opened the intended matter.
Personal injury intake adds urgency. A prospect may report a deadline, request immediate action, upload medical material, or assume the firm has begun work. Speed matters, but an administrative status should not silently answer a legal question.
ABA Model Rule 1.5 addresses fee communications. Paragraph (c) says a permitted contingent-fee agreement must be in writing, signed by the client, and state specified fee and expense information. This is an ABA model rule; the adopted rules and law in the governing jurisdiction control.
The operational solution is a visible state model:
- conflicts cleared, agreement not yet approved;
- approved agreement sent;
- signature incomplete or exception present;
- signed version verified;
- lawyer activation decision recorded;
- matter and downstream systems reconciled; or
- offer expired, withdrawn, or routed to another lawyer-controlled outcome.
No support worker should convert state four into state five merely because software reported completion.
Build one activation record
Use one record to connect the prospect, approved agreement, signature evidence, exceptions, decision, and activated matter.
Approved-version lock
Record the template identifier, generated version, document hash or comparable immutable identifier, approving lawyer, approval time, intended client, matter description, and approved delivery channel. If the document changes, create a new version and invalidate the prior signature request according to firm procedure.
ABA risk-management material on engagement letters emphasizes identifying the client and defining the engagement’s scope. It is educational material, not controlling authority.
Signature and identity reconciliation
Staff can compare administrative facts without deciding legal effect. Check whether:
- the signer matches the intended client or an authorized signer identified for lawyer review;
- every required signature field is complete;
- the signed file matches the locked version;
- edits, initials, attachments, or handwritten notes created an exception;
- completion evidence and timestamps were preserved; and
- accessibility or language-support requests require a different approved process.
Do not treat an email address, typed name, portal status, or uploaded scan as universally sufficient. Counsel decides acceptable methods under applicable law and firm policy.
Activation decision
The record should name the authorized lawyer, show the exact agreement version and exception packet reviewed, state the decision, and identify the released path. Support personnel preserve the decision; they do not infer it.
End-to-end workflow
1. Receive the conflict-clearance event
Link the recorded conflict decision from the intake record. Confirm it covers the current client and parties. A later party change returns to the approved recheck process.
2. Assemble the agreement inputs
Pull the confirmed client identity, matter description, lawyer-approved scope, fee terms, expense treatment, responsibilities, exclusions, and other required fields. Route gaps to the lawyer. Never fill a legal term from memory.
3. Generate and lock the approved version
Create the agreement from the authorized template. Preserve its version and approval. Keep drafts out of client-facing delivery queues.
4. Deliver through the approved channel
Record recipient, channel, time, and delivery state. A failed email, bounced text, inaccessible form, or wrong recipient becomes an owned exception.
5. Reconcile completion
Retrieve the completed file and platform evidence. Compare it to the locked version. Verify expected signers and required fields. Flag every change or ambiguity without interpreting its legal consequence.
6. Protect urgent facts
Keep a separate lawyer-owned urgency lane for any reported deadline, medical emergency, evidence loss, or other time-sensitive fact. Do not promise action or use urgency to bypass activation controls.
7. Obtain the lawyer activation decision
Send a compact packet: conflict state, approved agreement identifier, signer/completion results, exceptions, reported urgency, and proposed administrative setup. The lawyer records activate, hold, revise, decline, or another authorized state.
8. Create and reconcile the matter
After activation, create the matter number, responsible team, permissions, communication preferences, task template, document location, and approved calendar intake. Compare the client, parties, matter type, and assigned owner across systems.
9. Confirm the start state
Send only the lawyer-approved welcome or next-step communication. Make clear which team channel to use and what information remains outstanding. Do not promise a result, timetable, or substantive action that was not authorized.
10. Close the transition
Completion requires the activated matter identifier, responsible owner, reconciled systems, delivered confirmation, unresolved-exception owners, and preserved source record. A signed PDF sitting in an inbox is not closure.
Workflow at a glance
- Link conflict clearance
- Assemble lawyer-approved agreement inputs
- Lock the approved document version
- Deliver and track the signature request
- Reconcile signer, fields, version, and exceptions
- Record lawyer activation decision
- Create and reconcile the correct matter
- Confirm the approved start state
Responsibilities and controls
| Stage | Support role | Lawyer or authorized leader | Required evidence |
|---|---|---|---|
| Inputs | Assemble confirmed facts | Approve client, scope, fee terms, and template | Source-linked input record |
| Version | Generate and preserve document | Approve client-facing version | Immutable version identifier |
| Delivery | Send through approved channel | Set delivery and expiration policy | Recipient and delivery event |
| Completion | Reconcile fields and changes | Decide legal significance of exceptions | Signed file and exception list |
| Activation | Present readiness packet | Decide whether and how to activate | Named decision and timestamp |
| Setup | Create authorized records | Assign responsibility and substantive next step | Matter ID and owner acceptance |
| Confirmation | Send approved logistics | Control advice and commitments | Delivered start-state message |
ABA Model Rule 5.3 describes managerial and supervisory duties concerning nonlawyer assistance. A documented handoff supports supervision without representing that administration replaces lawyer judgment.
Technology and integration considerations
The workflow may touch intake, e-signature, document management, practice management, identity, calendar, and communication systems. Define the authoritative field for each item before automating.
Use role-based access, minimum-necessary visibility, audit events, retention rules, and tested exception queues. Avoid copying completed agreements into multiple uncontrolled folders. An integration failure should create a visible hold, not a false success.
Test duplicate prospects, two signers, changed names, mobile accessibility, corrected agreements, withdrawn offers, reopened inquiries, conflicting matter numbers, and unavailable systems.
KPIs and dashboard brief
Measures to define
- Approval-to-delivery time: Elapsed time from lawyer version approval to verified delivery event
- Signature exception age: Elapsed time an incomplete, changed, or ambiguous agreement awaits an owner
- Activation reconciliation completion: Share of activated matters with client, party, owner, and matter identifiers reconciled across designated systems
- Activation-to-welcome time: Elapsed time from lawyer activation decision to verified delivery of the approved start-state message
These are definitions, not benchmarks. Each firm must choose targets from verified internal baselines and risk tolerances.
Review queue indicators
- approved agreement version
- signer and field exceptions
- lawyer activation state
- reported urgency
- cross-system reconciliation
- responsible owner acceptance
An accessible dashboard should expose text labels, owner, age, and next action without relying on color. Tables must support keyboard navigation, readable contrast, and mobile stacking. Decorative motion should stop when reduced motion is requested.
Failure modes and jurisdictional limits
- Sent equals retained: delivery is mistaken for lawyer acceptance. Keep separate states.
- Any signature equals complete: the wrong signer or altered version bypasses review. Reconcile facts and route exceptions.
- Matter opens before authority: automation creates folders and tasks before a lawyer decision. Gate write actions.
- Urgency disappears: reported dates remain in intake notes. Route them immediately to a lawyer-owned lane.
- Duplicate setup: staff re-enter parties differently across tools. Reconcile authoritative identifiers.
- Welcome language overpromises: a template implies a result or immediate action. Require approved wording.
- One national rule is assumed: formation, fee, signature, and contingency requirements vary. Configure by jurisdiction.
Implementation checklist
- Define every pending, exception, activation, and closure state.
- Name who may approve agreement language and activate a matter.
- Lock approved versions and invalidate superseded requests.
- Separate administrative comparison from legal conclusions.
- Create a lawyer-owned urgency lane.
- Test every integration’s failure behavior.
- Require responsible-owner acceptance after activation.
- Pilot with a controlled matter set and review exception causes.
- Keep KPI values unverified until measured internally.
Fit and not-fit guidance
This workflow fits firms with enough intake volume or system handoffs that agreement status and matter setup can diverge. It can also help teams standardize coverage during absences.
It does not fit a firm seeking to outsource client selection, fee decisions, agreement drafting judgment, deadline analysis, or the decision that representation exists. Technology cannot make those choices safe by making them fast.
After the firm defines authority and controls, supervised personal injury law firm support may help administer approved packets, delivery tracking, exception queues, and reconciliation. Review broader personal injury operations resources or the boundaries of virtual legal assistant services before choosing a support model.
FAQs
What should staff verify before converting a personal injury prospect into an active matter?
Verify conflict status, approved agreement version, intended client, expected signers, required fields, preserved completion evidence, exceptions, reported urgency, and the authorized lawyer’s activation decision. Then reconcile the created matter across designated systems.
Can a virtual legal assistant decide that a signed agreement creates representation?
No. A support professional can compare administrative facts, preserve documents, and route exceptions. A lawyer must decide legal effect, acceptance, scope, fee terms, and activation under applicable law and firm policy.
How should a firm handle an edited or incomplete contingency agreement?
Keep the prospect in an exception state. Preserve the returned version, identify the changed or missing fields neutrally, and route the packet to the authorized lawyer. Do not repair the agreement silently or activate the matter automatically.
Does every personal injury firm need the same activation checklist?
No. The state model can be consistent, but counsel must configure agreement, signature, fee, client-identity, deadline, and acceptance requirements for each jurisdiction and matter type.
Sources and disclosures
- American Bar Association, Rule 1.5: Fees, updated April 14, 2020; accessed September 13, 2026.
- American Bar Association, Engagement Letters: Beginning a Beautiful Relationship; accessed September 13, 2026.
- American Bar Association, Rule 5.3: Responsibilities Regarding Nonlawyer Assistance; accessed September 13, 2026.
