A firm needs one matter-linked record for every settlement offer. That record should preserve the received terms, responsible lawyer’s review, client consultation, current authority, approved response, transmission evidence, and superseded history. Support staff can maintain the record and coordinate defined steps. Lawyers provide legal advice, valuation, and negotiation support. The client decides whether to settle.
Scope: This article provides an operations framework, not legal advice. ABA Model Rules are models, not controlling law. Each firm must apply its jurisdiction’s rules, engagement terms, court orders, and matter-specific requirements.
Why offer handling needs its own control
An offer may arrive by email, letter, portal, or call. The lawyer’s analysis may live elsewhere. Client instructions may arrive later by phone, text, or email. A response can then leave through another channel.
That fragmentation creates a basic operational question: which offer and which instructions are current?
Public paralegal discussions describe agreements communicated through calls and texts, later confusion about releases, and anxiety about saying the wrong thing to an adjuster. Another discussion questions whether advance authority should replace later client contact. Those accounts are not legal authority. They do reveal why a simple “settlement pending” task is too vague.
The ABA Model Rule 1.2 states that a lawyer shall abide by a client’s decision whether to settle. Model Rule 1.4 addresses communication needed for informed decisions. Model Rule 5.3 addresses lawyer responsibilities concerning nonlawyer assistance. Controlling rules and interpretations vary by jurisdiction.
The workflow should therefore prove more than completion. It should show what was received, who reviewed it, what the client decided, what the decision covered, and what was actually sent.
What belongs in the offer record
Create one offer record under the matter. Give every new or revised proposal its own version identifier.
Source and term fields
Record:
- received date and time;
- sender and delivery channel;
- source document or call note;
- offered amount and nonmonetary terms, as transcribed without interpretation;
- stated expiration or response date;
- parties, claims, and coverage implicated;
- attachments and referenced documents; and
- any missing, inconsistent, or unclear term.
Support staff should not decide what a term means. They should preserve the source and flag ambiguity.
Review and consultation fields
The responsible lawyer’s review record should identify:
- the offer version reviewed;
- legal or factual questions requiring attention;
- the consultation owner;
- approved communication materials;
- the consultation date and channel; and
- follow-up information requested by the client or lawyer.
ABA Model Rule 1.4 requires lawyers to keep clients reasonably informed and explain matters enough for informed decisions. Its comment specifically discusses communicating settlement offers. A firm should verify the controlling jurisdiction’s formulation.
Authority and response fields
Do not reduce authority to a permanent yes/no field. Connect it to:
- a named client or authorized decision-maker;
- the exact offer version;
- the decision recorded;
- any amount, term, time, or condition limiting that decision;
- the lawyer who confirmed the record;
- the approved outgoing response;
- the person authorized to transmit it; and
- delivery confirmation or other completion evidence.
A later counteroffer, revised release, changed allocation, or new condition may require a new decision. The responsible lawyer decides whether existing authority still applies.
How the workflow moves from receipt to response
1. Preserve the inbound offer
Attach the original message or document. For a phone call, use the firm’s approved call-note process. Keep the source separate from any summary.
2. Run an administrative completeness check
Confirm that basic fields can be populated. Flag missing attachments, unidentified parties, conflicting amounts, unclear deadlines, or a proposal that may involve multiple claims.
This is issue spotting for routing, not legal interpretation.
3. Assign the responsible lawyer
Route the intact source and exception list. Use a backup owner when the primary lawyer is unavailable. Do not let an internal task deadline become an independently calculated legal deadline.
4. Record lawyer review
The lawyer determines the meaning and significance of the offer. The lawyer also decides what advice, comparison, disclosure, or follow-up the client needs.
5. Coordinate client consultation
Support staff may schedule the conversation, assemble attorney-approved material, log contact attempts, and preserve the communication record. They should not value the claim, recommend acceptance, explain legal consequences independently, or negotiate.
6. Capture the client’s decision
Use the firm’s approved method. Tie the decision to the exact proposal and its limits. If instructions are unclear, conditional, inconsistent, or reported by someone other than the client, stop and escalate.
7. Lock the approved response
The lawyer should approve the response version and transmission channel. After approval, prevent silent editing. Any substantive change returns to lawyer review.
8. Transmit and reconcile
Send only through the approved route. Retain delivery evidence. Reconcile the sent response against the locked version, then record any reply as a new event.
9. Supersede without erasing
Mark an older proposal superseded, rejected, expired, withdrawn, or accepted only under the firm’s approved vocabulary. Preserve its history. Do not overwrite it with the newest number.
Workflow at a glance
- Preserve the source offer
- Check administrative completeness
- Route to responsible lawyer
- Record lawyer review
- Coordinate client consultation
- Capture scoped client decision
- Lock lawyer-approved response
- Transmit and reconcile
- Preserve superseded history
Who owns each decision
| Activity | Support staff | Responsible lawyer | Client |
|---|---|---|---|
| Save the inbound source | Perform under protocol | Supervise controls | — |
| Transcribe stated terms | Enter without interpretation | Resolve meaning or conflict | — |
| Identify missing fields | Flag exceptions | Decide significance | — |
| Explain legal consequences | Do not perform independently | Advise | Participate |
| Value the claim | Do not perform | Analyze and advise | Consider advice |
| Decide whether to settle | Do not decide | Communicate and confirm | Decide |
| Negotiate or counter | No independent authority | Direct and approve | Provide scoped authority |
| Send approved response | Only if expressly assigned | Approve version and channel | — |
| Close or supersede record | Update defined state | Confirm consequential status | — |
ABA Model Rule 5.3 places responsibilities on managers and supervising lawyers regarding nonlawyer work. Written roles, escalation rules, access limits, and review evidence make supervision observable.
How technology should support the record
The record may live in a case-management platform, document system, or configured workflow tool. The product matters less than the controls.
Require:
- matter and offer-version identifiers;
- source attachment retention;
- role-based access;
- required fields before state changes;
- separate source, summary, advice, decision, and response objects;
- timestamps and user attribution;
- approval locking and version history;
- exception alerts with backup ownership; and
- exportable audit history.
Avoid free-text status fields that silently become the only evidence. Avoid automation that converts a client message into “accepted” without lawyer confirmation. Avoid reminders that imply an independently determined legal deadline.
The firm should also apply its confidentiality, security, retention, and vendor-review requirements. This article does not verify any product or vendor.
Which measures reveal control problems
Metrics should diagnose the workflow, not become promises or universal benchmarks.
Measures to define
- Receipt-to-lawyer-routing time: Elapsed time from recorded receipt to assignment to the responsible lawyer
- Source-linked offer rate: Percentage of offer records retaining the original source or approved call note
- Authority exception age: Time unresolved authority questions remain in the exception queue
- Approved-response reconciliation rate: Percentage of sent responses reconciled against the lawyer-approved version
Set targets from the firm’s risk assessment, staffing model, jurisdiction, and baseline. Do not adopt illustrative labels as performance claims.
Review queue indicators
- unreviewed offer age
- missing source documents
- unclear or conflicting authority
- response version mismatch
- overdue lawyer escalation
Which exceptions require escalation
Route the record to the responsible lawyer when:
- the offer is oral, incomplete, revised, withdrawn, or disputed;
- the sender, client, claim, party, or covered interest is unclear;
- a client instruction conflicts with an earlier instruction;
- someone other than the client purports to decide;
- the client asks what the offer means or what to do;
- a response would require valuation, strategy, legal analysis, or negotiation;
- the proposal includes a release, confidentiality term, allocation, lien issue, or other consequential condition;
- multiple clients or claims may be affected;
- the client cannot be reached or appears not to understand;
- staff detect a deadline, technology, access, or transmission problem; or
- the sent response differs from the approved version.
The list routes questions. It does not answer them.
How to implement the workflow
Define the minimum record
Start with fields and evidence states. Agree on what “received,” “under lawyer review,” “client consultation pending,” “authority confirmed,” “approved to send,” and “sent” mean.
Separate administrative work from judgment
Document what support staff may transcribe, schedule, assemble, send, and reconcile. State which questions always return to a lawyer.
Configure permissions and backups
Limit access by role and matter. Assign a backup lawyer and backup coordinator. Test absence and urgent-escalation paths.
Pilot with closed examples
Use de-identified or appropriately controlled matters. Compare the source, lawyer review, client decision, response approval, and sent artifact. Repair gaps before scaling.
Audit state changes
Sample records for source linkage, authority scope, approval evidence, version integrity, and closeout. Review exceptions by age and cause.
Readers exploring broader personal injury operations resources can place this control beside intake, records, demand, mediation, and disbursement workflows without merging their distinct decisions.
Where this model fits
This model fits mid-size and large firms that receive many offers across teams, channels, offices, or systems. It is especially useful when several people coordinate client contact while a named lawyer retains responsibility.
It does not fit a firm seeking to delegate settlement decisions, valuation, advice, or unsupervised negotiation. It cannot repair unclear representation, disputed client identity, deficient legal analysis, or inadequate lawyer availability.
A provider of personal injury law firm support may help execute defined administrative steps. Broader virtual legal assistant services should operate within the same permissions, supervision, and evidence requirements. Outsourcing does not transfer the lawyer’s professional obligations.
Frequently asked questions
What should a settlement-offer record contain?
Preserve the source, stated terms, lawyer review, consultation record, scoped client decision, approved response, transmission evidence, and superseded history.
Can a virtual legal assistant tell a client whether to accept?
No. A support role should not provide legal advice, value the matter, recommend a decision, or exercise settlement judgment.
Can support staff relay an offer?
They may perform defined communications under lawyer direction where permitted. The lawyer remains responsible for required consultation, explanation, advice, and supervision.
What if the client gives instructions by text?
Preserve the message and route it through the firm’s approved lawyer-confirmation process. Do not assume an ambiguous or incomplete message authorizes a response.
Does earlier settlement authority cover a revised offer?
The responsible lawyer must decide. Authority should be tied to the identified proposal, conditions, and current client instructions.
When should staff escalate?
Escalate uncertainty about identity, terms, deadlines, authority, understanding, legal meaning, strategy, response language, or transmission integrity.
Sources and disclosures
- American Bar Association, Model Rule 1.2, allocation of authority between client and lawyer. Model guidance; accessed 2026-09-13.
- American Bar Association, Model Rule 1.4 and comment, client communication. Model guidance; accessed 2026-09-13.
- American Bar Association, Model Rule 5.3 and comment, responsibilities regarding nonlawyer assistance. Model guidance; accessed 2026-09-13.
- Public community discussions this workflow-SRC-001 through 003 informed the operational questions only. They are not proof of legal duties.
