Insurance Verification Form Template
Four documents and three sheets, with a dollar figure on every check so the skipped ones stop being invisible.
Free download · No account needed
Verification Record
One row per encounter, one column per check
The encounter reference is the join key. Without it the record is a form, and a form cannot tell you what any of its fields is worth.
| Encounter | Payer | Plan | Response date | Visit date | Planned code |
|---|---|---|---|---|---|
The seven checks
| Check | Done | Skipped | Not applicable | |
|---|---|---|---|---|
| 1 | Payer and plan captured from the response, not the card alone | |||
| 2 | Member id read back against the card, character by character | |||
| 3 | Plan effective and termination dates captured | |||
| 4 | Patient share and remaining deductible captured | |||
| 5 | Authorization requirement checked for the planned code | |||
| 6 | Other coverage asked about, in words | |||
| 7 | Referring provider identifiers captured, from the referral |
Three marks, and never a fourth
Done, skipped, or not applicable. Never blank. A blank cannot be told apart from not applicable, and the whole arithmetic downstream depends on the difference. Marking a check that did not apply as done inflates the denominator and makes it look safer than it is.
What this row is
A record of what a plan said on a date. It is not a coverage determination and not a prediction, and the script in the pack is written to keep it from becoming either one in front of a patient.
A verification form is easy to write and impossible to prioritize. Every field on it reads as equally mandatory, none of them carries a price, so the slow ones get skipped whenever the schedule is full. Four weeks later the denial report arrives with no way to connect the two halves. The plan's own answer is at least a defined artifact rather than whatever a portal chose to display. The eligibility inquiry and response pair is adopted in regulation, so what it said on the day is a recordable fact.
So this pack joins two records that never meet. One row per encounter says which of seven checks were performed. The remittance says which lines were denied and under which adjustment code. Joined on the encounter, they give dollars per skipped check, and that number is what reorders a front desk script. The ranking it produces is usually an inversion of the one a skip count produces.
At Alder Creek Pediatrics, 412 encounters carried 367 skipped checks and $27,480 of attributable denials. Asking about other coverage was skipped 147 times and cost $21.63 a skip. Checking the authorization requirement for the planned code was skipped 38 times and cost $332.63. The most-skipped item of all, remaining deductible at 88, caused no denials at all, because it never touches adjudication. It belongs with what the practice tells a patient about money, which is the financial policy pack, not with denial prevention.
What's in the pack
How the Failure Log Closes the Loop
The method: the join key, the code-to-check mapping written out, the conservative attribution rule, and both ratios with what each one answers.
Verification Record
One row per encounter, a column per check, three permitted marks and never a blank, because blank and not applicable cannot be told apart downstream.
Failure Log by Cause
Skips, skip rate, attributed denials, hit rate, denied charge and dollars per skip, ranked twice so the disagreement between the two rankings is on the page.
Denial Attribution
The claim-level evidence, each row carrying the alternative cause that was considered and a confidence mark, so a thin attribution stays visibly thin.
Verification Procedure
The seven checks in call order, when each visit type gets verified, and the re-run on the morning of the visit that catches a plan terminated since booking.
Patient Communication Script
Exact words, built around not turning the plan's statement into the practice's promise, plus what is never said at the desk and why.
Payer Response Quirks
Per payer: what the response omits, how termination is expressed, how stale the deductible figure is, and the honest residue that still needs a portal.
Where the loop continues
An authorization requirement that turns out to exist is a job for the prior authorization pack, and the denials this log cannot attribute get ranked by remittance and denial triage. A verification that comes back out of network goes to the single case agreement pack before the visit is booked.
How to use it
- 1
Open in River, or download it
Open the pack in River and let the agent build the join from your own data, or download the blank Word and CSV files instantly and run the seven checks by hand.
- 2
Send the checklist and the remittance
Your current form maps onto the seven checks. A month or a quarter of remittance with adjustment codes is the half that puts a dollar figure on each one.
- 3
Join them on the encounter
The mapping from adjustment code to check gets written down first, then attribution runs narrow, and every row records the alternative cause considered.
- 4
Rewrite the script by dollars, not by skips
Checks that need a second system move off the desk into a batch run. Checks that feel intrusive get exact words. Nothing gets added without something coming out.
Frequently asked questions
Is this template free?
Yes. The four documents and three sheets download as Word and CSV files with no signup and no card. "Edit with AI" is the optional path for practices that want the join run against their own encounters and remittance. The rest is in the template library.
What format are the downloaded files?
Word documents for the procedure, the patient script, the payer quirk note and the method note, plus CSV for the record, the failure log and the attribution sheet, zipped together. They open in Word, Pages, Google Docs, Excel, Numbers and Sheets.
Why seven checks and not the ninety-six fields on a typical form?
Because a row has to be fillable during the call, and because a check nobody completes is worse than one nobody wrote down. Seven is enough to be honest about the work and few enough that the skip marks mean something when they appear.
Does this tell us whether a service is covered?
No, and it is built to avoid implying it. An eligibility response is a statement a plan made on a date, recorded as exactly that. Plans do adjudicate against their own prior responses, so the script deliberately attributes every figure to the plan rather than to the practice.
How do you avoid blaming the front desk for payer behaviour?
The attribution rule. A denial counts against a check only when the adjustment code is one that check can cause and the check was marked skipped. An authorization that expired is not an unchecked authorization, and it sits at medium confidence with the alternative written on the row.
What if the most-skipped check turns out to cause nothing?
That is a finding, not an error, and it happened in the worked example. Remaining deductible was the second most-skipped item and produced no denials, because it never touches adjudication. It moves out of the denial-prevention section into the patient-financial one.
Do we need the remittance data to use this?
The record, the procedure and the script work without it. The dollar figure on each check does not, because it comes from joining the two. Without remittance you have a better form, which is genuinely useful and is not the reason this pack exists.
Find out what each verification step is worth
Send your current form and a quarter of remittance with the adjustment codes. The first thing back is dollars per skipped check, ranked against the skip counts.
Edit with AI