A medical-records request tracker should show what was requested, from whom, for which period, what actually arrived and who acts next. Separate a provider's reported delivery from receipt and review. The template below can be adapted to an approved spreadsheet or case system without treating every received PDF as a completed request.
Choose what one row represents
For a small PI firm, one row can represent one provider, one requested date range and one document type. If records and bills go to different departments, use separate rows linked to the same matter. This makes a partial response easier to describe than a single case-level status called waiting on medicals.
In a January 2026 paralegal discussion, a new PI paralegal described missing documents and incomplete responses; another participant suggested a tracking matrix. That is a useful design prompt, not proof that a spreadsheet solves every retrieval problem. The tracker needs an owner and a review routine to remain reliable.
Copy these columns into your approved system
Download the Excel request tracker for a fictional example and blank editable rows. This starter tracker covers the core queue; add submission route and reference, contact history, reviewer, coverage and priority fields in your approved system as needed. Start with the columns below. Use the firm's matter reference rather than repeating sensitive details across an unnecessarily broad worksheet. Store original documents in approved storage and link to them with appropriate access. The template is an operational outline; your firm's privacy, retention and access requirements determine where it belongs and who can use it.
Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.
| Column group | Suggested columns | Why it matters |
|---|---|---|
| Scope | Matter reference; provider; document type; date range | Defines the request being tracked |
| Submission | Request date; approved route; reference; request link | Shows what was actually submitted |
| Provider response | Last contact; reported status; response source | Keeps a reported update distinct from receipt |
| Receipt and review | File link; received date; coverage; reviewer; exceptions | Shows what arrived and what remains missing |
| Next action | Owner; action; follow-up date; counsel priority | Makes unfinished work actionable |
Keep a simple event history alongside the current row. A new response should update the next action while preserving the earlier request date and evidence. Without that history, a status change from pending to received can conceal that only one part of a packet arrived or that a later request covered a different period.
Use statuses that describe evidence
Define each status in plain language. Requested means the request was submitted through an approved route. The 'provider reports sent' status records what the provider said. Received means the actual file is present and linked. Reviewed means a person compared the response with the request and recorded whether anything remains unresolved. None of these states should be inferred from silence.
Use the records follow-up guide to decide what to ask on the next contact. For bills, the itemized-bill comparison helps specify the missing document. For imaging, the images-and-reports checklist separates the written report from the actual images so one arrival does not close both tasks.
A fictional request with a partial response
Fictional example: a request seeks clinic records for March through June. The provider reports sending them on October 20. On October 22, the team receives a packet covering March through May. The row records the actual receipt and the missing June period; it does not become complete merely because a file was delivered.
The reviewer assigns a follow-up asking whether June records exist within the approved scope and where the remaining response stands. A later no-records response is retained as evidence for review, rather than used to invent a clinical conclusion. The team keeps the original packet, the question and the later response connected.
Review actions, age and exceptions
Review the action queue at a cadence that fits the firm's workload. Prioritize counsel-assigned needs, unresolved identity or scope questions and actions whose agreed follow-up date has arrived. Track elapsed time from the original request separately from time since the last contact. Repeated contact should not make an old unresolved request look new.
- Which requests have no confirmed submission evidence?
- Which files arrived but have not been checked against the request?
- Which provider updates have no matching receipt?
- Which exceptions lack an owner or next action?
- Which completed rows need reopening because the scope changed?
An April 2026 discussion from a small plaintiff firm asks how to make records requests manageable. Its reported workload is an anecdote, not a staffing benchmark. Measure your own request volume and staff handling time, using the hold-time measurement guide to distinguish waiting from review, reconciliation and other work that remains with the team.
Know when the tracker needs a different home
If ownership, access controls or simultaneous edits become difficult, move the same definitions into the firm's approved case workflow. VerifyMD can connect scoped provider calls with received-file review after setup and owner activation for live calls. Book a workflow demo with a fictional partial-response example to evaluate how its evidence and exceptions fit your tracker.
Explore provider follow-up and source review for your firm. Live calls require agreed setup and activation.
Book a demo