What a Nexus Letter Actually Needs to Say (The Legal Standard)

A nexus letter has one job: to state, in writing, that a veteran’s current diagnosed condition is “at least as likely as not” connected to their military service, and to explain why. VA measures every claim against three elements under 38 C.F.R. § 3.303: a current diagnosed disability, an in-service event, injury, disease, or exposure, and a medical nexus linking the two. If the condition developed because of, or was made worse by, a condition VA already service-connects, 38 C.F.R. § 3.310 governs that secondary connection instead.

The “at least as likely as not” phrase isn’t a legal formality you can skip. It’s a direct reference to 38 C.F.R. § 3.102, the reasonable doubt regulation that gives veterans the benefit of the doubt when evidence sits at 50/50. A doctor who writes “probably related” or “may be connected” hasn’t cleared that bar. VA raters and the Board of Veterans’ Appeals (BVA) are trained to look for that specific probability language, and its absence is one of the most common reasons a medical opinion gets set aside.

Direct and secondary service connection require different framing in the letter, even though both rely on the same probability standard. The table below shows how the two paths differ and which condition types typically use each one.

Why Weak Nexus Letters Get Discounted (What VA and the Board Look For)

VA and the BVA weigh medical opinions using a probative value framework: a conclusion is only as strong as the reasoning behind it. VeteransAuthority, in its guide on nexus letters, notes that conclusory opinions without rationale are routinely discounted, regardless of the clinician’s credentials. A one-line letter that says “this is related to service” with no explanation carries almost no evidentiary weight.

Chisholm Chisholm & Kilpatrick (CCK Law) makes a related point in its guidance on nexus letters: the opinion should come from a licensed professional in the appropriate field, a psychiatrist or psychologist for PTSD, a neurologist for migraines or TBI, and it should be grounded in the veteran’s actual service records and post-service medical history, not general medical knowledge. A family doctor can write a valid nexus letter for a straightforward musculoskeletal claim, but a PTSD or TBI opinion carries more weight coming from someone whose specialty matches the diagnosis.

The pattern behind almost every rejected letter is the same: a strong-sounding conclusion sitting on top of a thin or missing rationale. Fix the rationale, and the conclusion holds up. That’s the single most important lesson in this article, and it drives the template in the next section.

The Nexus Letter Template: 4 Sections Every Winning Letter Includes

Every authoritative source on nexus letters, from Avard Law’s clinical checklist to Informed Veteran’s four-component breakdown, converges on the same basic structure. A winning letter contains four sections: clinician credentials, records reviewed, a direct opinion statement using VA probability language, and a rationale explaining the medical reasoning. Skip any one of these and the letter loses persuasive power.

1. Clinician identification and credentials. Full name, license number, specialty, and signature. Avard Law’s 2026 nexus letter guide lists this alongside the veteran’s name, date of birth, VA file number, and the date of the opinion as baseline identifying information VA expects to see on page one.
2. Records reviewed. Name the specific documents: service treatment records (STRs), DD-214, VA claims file, private treatment records, imaging or labs, and any prior Compensation and Pension (C&P) exam. Informed Veteran’s guide emphasizes naming actual documents and dates rather than a vague “medical history was reviewed.”
3. The opinion statement. One clear sentence using the exact standard: “It is my medical opinion that it is at least as likely as not (50% or greater probability) that [condition] is [directly related to / secondary to] [in-service event or service-connected condition].” The Veterans of Foreign Wars (VFW) fact sheet on medical nexus letters recommends this near-exact phrasing as an opening line.
4. The rationale. The medical reasoning connecting the diagnosis to the event, injury, or secondary condition. Hill & Ponton’s step-by-step guide to nexus letters frames this as explaining consistency between symptoms and diagnosis, and describing how the condition affects daily functioning, both of which reinforce the opinion.

Print this list. Hand it to your provider before the appointment where you ask for the letter. A doctor who has never written a VA nexus letter will often produce something close to useless without this structure in front of them, not because they don’t believe you, but because they don’t know VA’s language.

How to Prep Your Doctor (What to Send Before They Write Anything)

Doctors are busy, and most have never seen a Disability Benefits Questionnaire (DBQ) or a BVA decision. Informed Veteran’s guide recommends veterans build a short packet for the provider containing a chronology of the condition, key dates, and a plain request for the four components above. That packet turns a 20-minute favor into a defensible medical opinion.

Hill & Ponton also points out something worth taking seriously: using a doctor who already treats you, rather than a one-time opinion mill, increases the letter’s credibility because the provider can speak to your ongoing symptoms and clinical relationship, not just a records review. Before your appointment, gather and hand over:

• Your DD-214 and relevant service personnel/treatment records
• Any prior VA rating decisions or C&P exam reports
• A one-page timeline: when symptoms started, how they’ve progressed, and any events that connect them to service
• A copy of the four-part template from the section above
• The exact “at least as likely as not” phrasing so the doctor can quote it directly

The Veterans Authority Statement Reviews (VASRD) criteria for your specific condition aren’t the doctor’s job to research, but if you already know your likely rating category, mentioning it briefly can help the provider understand what functional limitations matter to include.

Example 1: PTSD Nexus Letter

This example shows a direct service connection opinion from a licensed psychologist, built on a documented in-service stressor and a current DSM-5 diagnosis, following the four-part structure above.

Re: Nexus Opinion for [Veteran Name], DOB [date], VA File Number [number]

I am a licensed clinical psychologist (License #[number]), specializing in trauma-related disorders, and I have treated [Veteran Name] since [date]. In preparing this opinion, I reviewed the veteran’s service treatment records, DD-214, VA claims file, and my own clinical notes from [number] treatment sessions.

[Veteran Name] meets the DSM-5 diagnostic criteria for Post-Traumatic Stress Disorder (PTSD), with symptoms including intrusive memories, hypervigilance, and avoidance behavior consistent with the stressor documented in service.

It is my medical opinion that it is at least as likely as not (50% or greater probability) that [Veteran Name]’s PTSD is directly related to the in-service stressor event of [brief description], documented in the service record dated [date].

Rationale: The onset of symptoms occurred within the timeframe following the identified stressor and has remained clinically consistent through ongoing treatment. The nature, severity, and duration of these symptoms are typical of trauma-related psychiatric injury and are not better explained by any pre-service or post-service factor identified in the records reviewed.

[Signature, credentials, date]

Example 2: TBI-Related Migraines Nexus Letter

This example demonstrates secondary service connection, where a neurologist links chronic migraines to an already service-connected traumatic brain injury (TBI) rather than to a separate in-service event.

Re: Secondary Nexus Opinion for [Veteran Name], VA File Number [number]

I am a board-certified neurologist (License #[number]) and have treated [Veteran Name] for headache disorder since [date]. I reviewed the veteran’s VA rating decision confirming service connection for traumatic brain injury (TBI) rated [percentage], service treatment records documenting the [date] head injury, private neurology notes, and imaging reports.

[Veteran Name] carries a diagnosis of chronic post-traumatic migraine, occurring [frequency] and consistent with post-concussive headache syndrome.

It is my medical opinion that it is at least as likely as not (50% or greater probability) that [Veteran Name]’s migraine disorder is secondary to, and aggravated by, the service-connected TBI.

Rationale: Post-traumatic headache is a well-documented sequela of traumatic brain injury, with onset and pattern in this case consistent with the veteran’s documented head injury and subsequent neurological history. No competing etiology, such as a pre-service headache disorder, is present in the records reviewed.

[Signature, credentials, date]

Example 3: Lumbar Spine Condition with Radiculopathy Nexus Letter

This example covers a musculoskeletal claim where an orthopedic specialist connects radiculopathy, nerve symptoms radiating into the leg, to an already service-connected lumbar spine condition, another secondary connection under 38 C.F.R. § 3.310.

Re: Secondary Nexus Opinion for [Veteran Name], VA File Number [number]

I am a board-certified orthopedic specialist (License #[number]) and have treated [Veteran Name] for lumbar spine and lower extremity symptoms since [date]. I reviewed the veteran’s VA rating decision confirming service connection for lumbar strain rated [percentage], electromyography (EMG) results dated [date], MRI imaging, and treatment notes spanning [timeframe].

[Veteran Name] presents with radiculopathy of the [left/right] lower extremity, confirmed by EMG findings consistent with nerve root involvement at the [level] level.

It is my medical opinion that it is at least as likely as not (50% or greater probability) that [Veteran Name]’s lumbar radiculopathy is secondary to the service-connected lumbar spine condition.

Rationale: Radiculopathy is a recognized and common complication of degenerative or traumatic lumbar spine disease. The nerve distribution and EMG findings in this case directly correspond to the anatomical level of the service-connected spine condition, and no independent cause for the radiculopathy is documented in the records reviewed.

[Signature, credentials, date]

Common Mistakes That Sink a Nexus Letter (Quick Checklist)

The mistakes below account for most of the nexus letters VA and the BVA discount or reject outright. Each one is easy to fix before the letter ever gets submitted.

• Using hedging language (“may be,” “could be,” “possibly”) instead of the exact “at least as likely as not” standard
• Missing or vague records review, no specific documents or dates named
• No rationale, just a bare conclusion with nothing explaining the medical reasoning
• A specialist mismatch, a general practitioner opining on a complex psychiatric or neurological diagnosis with no supporting explanation for why they’re qualified to do so
• Failing to distinguish direct versus secondary connection, citing the wrong regulation or none at all
• No credentials, license number, or signature, leaving VA unable to verify who wrote the opinion

If your letter has even one of these problems, it’s worth going back to the provider with a revision request before you file. A rejected nexus letter doesn’t just fail, it can also color how the rest of your evidence gets weighed.