The Pre-Exam Doctrine: Build the Record Before the Room

Most veterans walk into a Compensation and Pension exam thinking it is where they will "make their case." Some have practiced what they will say. Some have written notes. A few bring printed records. Almost all of them — once the exam is over — feel a familiar uneasiness: did the examiner actually capture what matters?

That uneasiness is the right intuition. The exam is not where your case is decided. It is one input, generated by an examiner who has roughly thirty minutes to fill out a structured form. The decision happens afterward, by a rater you will never meet, sitting in a separate office, working from the document — the DBQ the examiner produced — plus everything else that has been filed into your eFolder. The rater does not hear what you said. The rater does not see what you handed across the desk. The rater reads what is in the file.

This is the foundational asymmetry of the VA disability system, and it produces a corollary so important it deserves to be stated as a doctrine:

Control the record, not the conversation.

This is the first piece in a series — the Pre-Exam Doctrine — about how to operationalize that principle in the highest-leverage window of any claim: the days and weeks between when your exam is scheduled and when it takes place.

The Pre-Exam Window Is Where the Game Is Won

The interval between exam notification and exam date is typically two to six weeks. During this window, you have three things almost no other point in the claims process gives you simultaneously: time, control over what you submit, and a defined target — the DBQ the examiner will use.

You will spend roughly thirty minutes in the exam room. You will spend zero minutes with the rater. But you can spend several hours during the pre-exam window building the artifact that lands on both desks. That artifact, done well, becomes the structural backbone of the file the rater reads.

The artifact has a name in this series: the DBQ Reference Document.

What the DBQ Reference Document Is

A DBQ Reference is a structured submission, prepared by you, that mirrors the exact Disability Benefits Questionnaire the examiner will use. It is written before the exam, uploaded to the eFolder as soon as the exam is scheduled, and brought to the exam in printed form as a backup.

It has two parts:

1. A Quick Exam Reference at the top — a one-page executive summary the examiner can scan in thirty seconds: diagnosis, key dates, current treatment, course, the most important objective findings, and the basis of the claim.
2. A DBQ-mirrored detail section below — your factual answer to each question the DBQ asks, in the form's order, with cross-references to supporting evidence already in your file.

It is:

• Form-aligned. Section I, Section II, Section III — same numbering, same structure as the actual DBQ.
• Factual, not argumentative. You are not making a legal argument. You are providing organized facts in the form's expected order.
• Professional in tone. This is going into the eFolder and will be read by a rater. It should look like a clinical/legal submission, not personal notes.
• One document per DBQ. Each condition has its own DBQ form, so each condition gets its own reference document.

It is not:

• A medical opinion (only a clinician can write one)
• A legal brief (only post-decision, in appeal)
• A symptom diary (that's a separate supporting document)
• A narrative essay about your service

Length discipline matters. The Quick Exam Reference fits on one page. The DBQ detail typically runs three to five pages. Anything longer reduces effective signal.

Why DBQ-Mirrored Matters

This is the structural insight that makes the document work: the DBQ is not just a clinical form — it is the rating decision in waiting. Each section maps directly to specific rating criteria in 38 CFR. Section 4 of the Headaches DBQ is the prostrating-attacks inquiry. Section 3 of the Esophageal Conditions DBQ is the symptom inventory. Section 2 of the Hypertension DBQ is the medication and treatment history.

Examiners pattern-match for the data points the form asks about, in the order it asks them. Raters scan for the same data points when reviewing the file. If your reference document is structured to mirror the DBQ, you are giving both readers exactly what they are looking for, in the order they expect to find it.

The alternative — a narrative summary, a generic symptom list, a personal letter — forces the examiner and rater to translate. That translation step is where information gets lost.

The Quick Exam Reference

The examiner has approximately thirty minutes. They will spend most of it filling out the form, not reading your materials. A four-page reference document, however well-structured, is more than they will engage with in that window.

The Quick Exam Reference solves this. It is one page, at the top of your document, that gives the examiner the punch line first:

• Diagnosis with ICD-10 code and date
• Current treatment regimen (medications, dosages, escalation history)
• The course (chronic, treatment-resistant, controlled, etc.)
• Key objective findings (representative test results with dates)
• Established nexus opinions of record (who, when)
• Basis of the claim (direct, secondary, presumptive — with the regulation cited)

The examiner gets a thirty-second briefing on the file. The DBQ-mirrored detail below is there for any section they want to dig into, and for the rater who will read the whole thing later.

The DBQ Detail Section

For each section of the DBQ the examiner will complete, write a corresponding entry that:

1. Restates the question briefly — the section number and the question itself
2. Provides your factual answer — in clean, professional prose
3. References supporting evidence — what document, what date, where in the file

The question types fall into a few categories, each calling for a slightly different technique:

Factual/clinical questions (diagnosis, dates, medications) get direct factual answers. No narrative needed.

Yes/no with frequency questions (4A — Yes/No, then "Greater than once per month," etc.) get a direct answer paired with the supporting evidence: "Yes. Frequency: greater than once per month. Supported by neurology treatment notes dated [X], [Y], [Z]."

Symptom narrative questions (what does it feel like, how does it interfere) are the right place for an anchor line — a clean verbal expression in your voice, paired with an evidence flag:

"I have to stop what I'm doing and lie down when an attack starts." → prostrating behavior; supported by symptom log dated [X]

Functional impact questions get a brief, specific narrative with concrete examples — what you can no longer do, what you have had to adapt around.

The anchor-line technique is one tool inside the DBQ-mirrored document, not the structural pattern of the whole document. Use it where the question calls for it.

Anticipating Known Challenges

Sophisticated DBQ References go beyond passive question-by-question answering. They anticipate the structural problems the rater will encounter in your file.

No untreated baseline. Many veterans have been on continuous medication since diagnosis. A DBQ may ask about diastolic predominantly ≥100 or systolic predominantly ≥160, and your current readings are medicated. Acknowledge this directly: "There is no documented untreated baseline because medication began at diagnosis and has continued without interruption. Across the medicated record, readings still include [examples]." That frames persistence under treatment as the rating-relevant fact, not whether you ever had untreated readings at threshold.

Examiner-evidence conflict. If a prior DBQ or examiner finding will look superficially unfavorable, address it in the relevant section with the contrary evidence already in the file.

Anchoring to favorable precedent. If the VA has already granted related conditions secondary to the same service-connected disability — particularly on the same regulatory basis — note that pattern explicitly with dates and rating decision references. The rater is cognitively constrained from contradicting their own prior favorable findings without explanation.

This is what separates a strong DBQ Reference from a competent one: it is not just answering the questions, it is shaping the framework the rater will use to read the answers.

Building Yours: The Process

The construction process is mechanical once you understand the architecture.

Step 1 — Pull the exact DBQ form. The VA publishes its current DBQ inventory at va.gov; your VSO or accredited representative can also provide them. You want the specific form number (e.g., VA Form 21-0960A-3 for Hypertension) that matches your exam.

Step 2 — Walk through each section, question by question. List every section and the questions within it.

Step 3 — Write your factual answer for each question. Use the technique that fits the question type. Reference supporting evidence by document and date.

Step 4 — Add the Quick Exam Reference at the top. Compress the most consequential facts into a one-page summary. The examiner reads this first.

Step 5 — Anticipate the structural challenges. Where the file has known problems, address them in the relevant section directly.

Step 6 — Anchor to favorable precedent. If prior rating decisions in your own file support the framework, cite them by date in the appropriate section.

Step 7 — Cross-reference exhibits. If you are submitting supporting documents (nexus opinions, symptom logs, treatment correspondence) as separate exhibits, reference them by exhibit name within your DBQ Reference.

A complete DBQ Reference for a single condition typically runs four to six pages including the Quick Exam Reference. One document per DBQ. Each condition gets its own.

The Submission

Once your DBQ Reference is built, it has two delivery channels.

Upload to the eFolder as soon as the exam is scheduled. Use VA.gov's claim portal or QuickSubmit. Filename matters: a clear, descriptive name like 2026-06_Hypertension_DBQ_Reference.pdf is more likely to be opened than Document1.pdf. Number your submissions in order if uploading multiple documents.

Bring a printed copy to the exam. Hand it across once, naturally: "I uploaded a reference summary to the file — printed copy here if useful." Some examiners will use it. Some will not. It does not matter; the eFolder copy is already where the rater will look.

The Strategic Logic

The reason this works is not that examiners are uniformly hostile or careless. They are not. The reason it works is that examiners are variable, and raters are not.

C&P examiners — VA staff or contract clinicians (QTC, LHI, VES) — operate with different levels of attention to outside materials. Some review the full eFolder before the exam. Some review only the prior DBQ. Some review nothing and ask the veteran to summarize. You do not know in advance which examiner you will draw.

What you do know is that the rater always reviews the file. A well-built DBQ Reference, sitting in the eFolder under a clear filename, lands in front of the person actually deciding the claim — regardless of how the exam itself unfolds.

This is the difference between controlling the conversation (low leverage, examiner-dependent, unpredictable) and controlling the record (high leverage, rater-dependent, consistent). Veterans who internalize this stop optimizing for the exam and start optimizing for the file.

A Note on Multi-Condition Claims

The framework above assumes a single condition with a single DBQ. Many claims involve multiple conditions, each with its own DBQ. The discipline is the same — one DBQ Reference per DBQ — and the result is a small set of structured documents, each focused on a single condition.

For early-stage claim development, before specific exams are scheduled, a broader cross-condition summary can be useful for your own preparation. That kind of document — multi-condition, narrative, organized around verbal anchors — is a personal preparation tool, not a submission artifact. Do not confuse the two. The DBQ Reference is what goes into the eFolder; the cross-condition summary, if you build one, stays with you.

Common Pushback

"Won't this make me look like I'm being coached?" No. Raters reward organized, clear submissions — they make the rater's job easier. Examiners are accustomed to seeing reference documents from sophisticated claimants.

"What if the examiner refuses to take the printed copy?" It doesn't change the outcome. The eFolder copy is already in the file.

"How long should it be?" Four to six pages per condition including the Quick Exam Reference. Anything longer reduces effective signal.

"What if I can't get the exact DBQ in advance?" The current DBQs for major conditions are publicly available. If you cannot locate the exact form, structure the reference around the rating criteria in 38 CFR for the relevant diagnostic code — those are what the DBQ implements.

"Should I include lay statements from family or coworkers?" Not inside the DBQ Reference itself. Those are separate evidence submissions filed alongside, referenced by exhibit name.

Bottom Line

The exam is one input. The file is the decision.

The DBQ Reference Document, built during the pre-exam window, is the single highest-leverage intervention available to a veteran filing or under review. It costs a few hours of disciplined work. It produces an artifact that survives the exam, lands in front of the rater, and structures the record around the facts that matter.

Control what is in the file. Everything else is downstream.

— Michael Barthlow

Next in the Pre-Exam Doctrine series: how the DBQ Reference Document evolves — a worked example using three iterations from my own claim.