Track every requested document as a separate control item. Connect each arrival to its request, preserve receipt evidence, record whether the file is usable, and acknowledge what was accepted. Reconcile open items before sending another request. A file in an inbox is not received operationally until the firm can identify it, match it, review its condition, and assign its next step.
Scope: This is an operations framework, not legal advice. Firm counsel must set jurisdiction-specific confidentiality, prospective-client, consent, retention, conflict, deadline, and engagement rules. Support staff must not evaluate a claim, give advice, calculate a legal deadline independently, or promise representation.
Why the resend cycle develops
A prospect attaches one file to an email, sends another through a form, and photographs a third. An intake coordinator sees the email but cannot find the original request. Another coordinator later reviews the checklist, sees an empty field, and asks for everything again.
Both people may be acting carefully. The system still failed.
The common defect is a missing connection between the request and the receipt. A checklist says what the firm wants. A mailbox says what arrived. Neither proves which requested item the firm accepted.
Public legal-work discussions describe incomplete intake, partial delivery, unreadable pages, and frustrated responses that documents were already sent. Those accounts do not establish a universal rate. They do reveal a practical vocabulary for designing exception states.
The prospect should not have to serve as the firm’s reconciliation system.
Define a controlled receipt
Write one test that everyone can apply:
A requested intake document is controlled when its arrival evidence links to the correct inquiry and request item, its condition is recorded, an authorized person accepts or rejects it, and its next action is visible.
That definition separates several events teams often collapse.
- Delivered means a channel accepted data.
- Detected means the firm observed the arrival.
- Matched means staff linked it to an inquiry and request item.
- Reviewed means an authorized person checked its relevant condition.
- Accepted means it satisfies the administrative request under firm policy.
- Complete means no unresolved request line remains.
An automated “upload successful” notice proves delivery, not acceptance. Conversely, an unreadable file can be received correctly while leaving the request open.
Build the receipt-reconciliation workflow
1. Create one request-item ledger
Give the request set a stable identifier. Create one line for every item instead of asking for “all documents.”
Each line should identify the document category, who requested it, request date, approved receipt methods, current state, owner, and next action. Firm counsel decides whether particular information should be requested at this stage.
Use plain descriptions a prospect can recognize. Internal labels can be more precise, but the prospect-facing request should avoid unexplained codes.
2. Record arrival evidence
When something arrives, preserve the source event identifier, channel, timestamp, sender identifier available to authorized staff, filename or physical description, and linked inquiry.
Avoid putting sensitive content on broad operational dashboards. The control view generally needs identifiers and states. Authorized users can open the source through the firm’s protected system.
3. Apply the approved file-safety path
Receipt reconciliation does not replace technical screening. A file can be present but unsafe to open. Keep its request line in a visible screening state until the separate attachment-control process clears it.
Physical documents also need a chain of custody appropriate to firm policy. Record who accepted them and where the controlled copy or original went.
4. Match the arrival to one request item
Match using more than a filename. Confirm the inquiry, sender context, request identifier, document category, and relevant date or subject.
Do not silently merge uncertain identities. Place ambiguity in an exception queue for authorized review.
One arrival may satisfy several request lines only when firm policy permits that conclusion. Preserve the one-to-many link instead of copying the file and losing its provenance.
5. Record condition and acceptance
Use states that describe reality:
- received, review pending;
- accepted;
- unreadable;
- incomplete pages;
- wrong period or document;
- duplicate of accepted item;
- possible duplicate, review required;
- unable to match;
- technical screening hold; or
- attorney review required.
Free-text notes can explain an exception. They should not replace a state that reporting can reconcile.
6. Acknowledge the result
Tell the prospect which item the firm received and whether further action is required. Use lawyer-approved templates. An acknowledgment must not imply that the firm accepted representation or reached a legal conclusion.
If the file is unreadable or incomplete, identify the affected request line and the needed correction. Do not resend the entire checklist unless the entire request truly remains open.
7. Reconcile before another reminder
Before staff or automation sends a reminder, compare open request lines with all unmatched and review-pending arrivals.
Suppress the reminder when:
- a possible match awaits review;
- technical screening is still running;
- another worker accepted the item;
- a replacement arrived through a different channel; or
- attorney direction changed the request.
The system should surface the reason, not silently discard the reminder.
Workflow at a glance
- Create a request set and item-level ledger
- Record arrival evidence
- Apply approved file-safety controls
- Match the arrival to the inquiry and request item
- Review condition and record acceptance
- Acknowledge the exact result
- Reconcile open items before reminders
- Close exceptions with evidence
Assign responsibility and judgment
The ABA Model Rule 1.18 page addresses information learned from qualifying prospective clients. It is a model rule; firm counsel must determine the controlling jurisdiction and facts.
ABA Model Rule 5.3 describes managerial and direct-supervision responsibilities for nonlawyer assistance. Administrative delegation does not transfer a lawyer’s professional duties.
| Activity | Intake support | Intake manager | Supervising attorney |
|---|---|---|---|
| Create request lines from approved templates | Perform | Maintain templates | Approve legal boundaries |
| Record arrivals and match obvious items | Perform | Review exceptions | Decide sensitive ambiguity |
| Mark legibility and page presence | Perform under policy | Sample and correct | Set escalation rules |
| Decide legal sufficiency or claim merit | No | No | Lawyer only |
| Change a legal deadline or request scope | No | Route the request | Lawyer-controlled |
| Promise representation | No | No | Authorized lawyer only |
| Reconcile open administrative items | Perform | Own control results | Review material exceptions |
Document permissions should enforce these boundaries.
Configure technology around document states
Preserve provenance
Keep the request identifier, source event, intake record, and accepted document record connected. Renaming a file should not erase where it came from.
Make repeated delivery safe
Repeated delivery should create a possible-duplicate state, not overwrite an accepted item or generate several missing-item reminders. A person should resolve uncertain matches.
Separate status from content
For information within its scope, ABA Model Rule 1.6(c) addresses reasonable efforts against unauthorized access or disclosure. Counsel should apply the firm’s jurisdictional duties. Limit dashboards to the least content needed for operational control.
Test failures deliberately
Test a broken upload, repeated email, unreadable photograph, missing page, wrong inquiry, disabled integration, delayed virus scan, and physical drop-off. Every test should create an observable state with an owner.
Measure the workflow
Targets should come from firm policy and a measured baseline. No external benchmark is asserted.
Measures to define
- Request-item reconciliation rate: Request items accepted or closed with an approved reason divided by request items due for review
- Unmatched arrival age: Elapsed time from detected arrival until match or documented exception
- Repeat-request defect count: Reminders sent after a responsive item had already arrived but before reconciliation
- Unreadable-item resolution time: Elapsed time from unreadable classification until replacement, waiver, or approved closure
Review queue indicators
- open request items by owner
- unmatched arrivals by age
- unreadable or incomplete items
- possible duplicates awaiting review
- reminders suppressed for reconciliation
Handle exceptions
A prospect says the file was already sent
Search arrival evidence across approved channels before asking again. Confirm the address, portal, approximate time, sender, and filename without requesting unnecessary sensitive content. Create an unmatched-arrival investigation when needed.
One file contains several items
Link the source once and associate it with the applicable request lines. Do not split or alter the original unless approved procedure preserves provenance.
The file is readable but substantively insufficient
Administrative staff may record the observable condition. A lawyer or authorized reviewer must decide legal sufficiency when judgment is required.
The sender is not yet a client
Keep acknowledgment language precise. Receipt is not engagement. Preserve the firm’s approved prospective-client and conflict processes.
A request may implicate urgency
Support staff should preserve the sender’s exact statement and escalate through the approved attorney-review lane. They should not calculate or promise a deadline response independently.
Implement the control
- Inventory document requests used during intake.
- Replace bundled requests with item-level lines where useful.
- Define receipt, condition, acceptance, and exception states.
- Map each approved channel to arrival evidence.
- Assign primary and backup owners.
- Approve acknowledgment and correction templates.
- Add reminder suppression until reconciliation runs.
- Test negative paths and manual fallback.
- Review aging and repeat-request defects.
- Adjust access, retention, and escalation with counsel.
Decide whether this approach fits
This control fits firms receiving many intake documents through several channels or across multiple teams. It is especially useful when automated reminders operate separately from inboxes or portals.
It is not a substitute for technical file screening, conflict analysis, legal evaluation, deadline control, records management, or engagement decisions. A simple low-volume practice may use a smaller ledger, but every requested item still needs an observable owner and state.
After the workflow is defined, personal injury law firm support can help execute approved administrative steps under firm supervision. Firms comparing roles can review supervised virtual legal assistant services. Related educational material belongs with the personal injury operations resources.
Frequently asked questions
How can my personal injury law firm stop asking prospective clients to resend intake documents?
Use one item-level request ledger, connect every arrival to its request, record condition and acceptance, and reconcile review-pending arrivals before sending reminders.
What should my intake team record when a prospective client sends a requested document?
Record the request item, source event, channel, time, inquiry match, observable condition, review state, accepted owner, and next action. Restrict sensitive content according to firm policy.
How do I reconcile requested, received, unreadable, and missing intake documents?
Compare every open request line with accepted, unmatched, screening-held, and review-pending arrivals. Resolve each difference through a named exception owner before another reminder runs.
How does Remote Legal Team LLC support this workflow?
Remote Legal Team LLC can support firm-defined administrative tracking, acknowledgments, exception routing, and reconciliation under lawyer supervision. The firm retains legal judgment, professional responsibility, system governance, and final decisions.
Sources and disclosure
- American Bar Association, Model Rule 1.18, accessed 2026-09-13.
- American Bar Association, Model Rule 5.3, accessed 2026-09-13.
- American Bar Association, Model Rule 1.6, accessed 2026-09-13.
- Public-community sources informed pain-language discovery only and appear in the internal source log.
