Duty-to-Assist Errors

VA claims are not adversarial in the way a lawsuit is. Congress built the system so that VA has an affirmative obligation to help you gather the evidence your claim needs. That obligation is the duty to assist, and when VA skips part of it, the resulting denial rests on an incomplete record. That is not just unfair — it is a specific, named, correctable error with its own procedural remedy.

What VA is required to do

The duty is set out in statute at 38 U.S.C. §5103A and implemented in regulation at 38 CFR §3.159. Broken down, VA must:

• Obtain your service treatment and service personnel records. These are federal records. Under §3.159(c)(2), VA must keep trying until it obtains them or concludes they do not exist or further efforts would be futile — and it must tell you in writing when it makes that conclusion.
• Obtain your VA treatment records. Records from any VA medical facility are constructively in VA's possession. You should not have to produce them, and VA must get them for the relevant period.
• Make reasonable efforts to obtain private records you identify. Under §3.159(c)(1), once you identify a private provider and give VA an authorisation, VA must make an initial request and at least one follow-up unless the first response makes further efforts futile. If VA cannot get them, it must notify you so you can obtain them yourself.
• Obtain records held by other federal agencies. Social Security Administration disability files, National Personnel Records Center holdings, Department of Defense records, service department records. §3.159(c)(2) applies the same continuing-efforts standard to all of them.
• Provide a medical examination or obtain a medical opinion when one is necessary to decide the claim, under §3.159(c)(4).

When VA owes you an examination — the McLendon factors

The most litigated part of §3.159(c)(4) is when an examination is owed. The standard comes from McLendon v. Nicholson, 20 Vet. App. 79 (2006). VA must provide an examination or obtain an opinion when all four of these are present:

1. Competent evidence of a current disability, or of persistent or recurrent symptoms of a disability.
2. Evidence establishing an in-service event, injury or disease, or a presumptive disease manifesting in an applicable period.
3. An indication that the current disability may be associated with service.
4. Insufficient competent medical evidence in the file for VA to decide the claim.

The third factor is where denials usually go wrong. McLendon describes it as a low threshold. It does not require a medical opinion — that is the very thing the examination is supposed to produce. Your own competent lay statement about continuity of symptoms since service can satisfy it. When VA denies because "there is no evidence linking the condition to service" and no examination was ever provided, that reasoning is often circular: VA declined to develop the evidence it then held against you.

The failures that come up most often

1. A records set you identified was never obtained

You listed a private provider on the claim form or in a VA Form 21-4142 authorisation, and the claims file contains no request, no response, and no notification that VA gave up. Under §3.159(c)(1) and (e), VA had to make an initial request, at least one follow-up, and if it failed, to notify you. Silence on all three is a duty-to-assist error.

2. No examination was scheduled when one was owed

The McLendon factors were met on the face of the file and no examination appears anywhere in it. This is common in claims for conditions with a strong lay-evidence component — tinnitus, joint pain, sleep disturbance, mental health — and in secondary service connection claims where VA examined the primary condition but never developed the secondary one.

3. An examination was provided but was inadequate

This is the largest category. An examination that does not answer the question asked does not discharge the duty. Recurring defects:

• The examiner gave a conclusion with no rationale at all.
• The examiner relied on a fact that is contradicted by the record — most often "the service treatment records are silent", when they are not.
• The examiner reasoned solely from the absence of in-service treatment, which the Court has repeatedly held is not by itself an adequate basis.
• The examiner declined to opine "without resort to mere speculation" without explaining why, contrary to Jones v. Shinseki.
• The examination did not test what the rating criteria require — for example, range of motion without pain-on-motion and weight-bearing testing, which Correia v. McDonald requires.
• The examiner never addressed flare-ups or functional loss during flare-ups, as DeLuca v. Brown and §4.40 and §4.45 require.

The detail is set out in when the C&P exam was inadequate, and DBQs explains how to read the completed form against the criteria. ACE examinations — done from records without seeing you — deserve particular scrutiny, because an ACE review is only appropriate where the existing record is sufficient.

4. Federal records from another agency were never requested

Two come up constantly:

• Social Security Administration records. Where you have told VA you receive SSA disability benefits, the underlying medical file is frequently relevant — especially to TDIU. VA must request it where it is relevant.
• National Personnel Records Center holdings. Where service records are incomplete, or were affected by the 1973 NPRC fire, VA must make continuing efforts and consider alternative record sources rather than simply noting the records are unavailable. A single unanswered request is not the end of the duty.

5. No unit-records or JSRRC development for a claimed stressor

In PTSD and other stressor-based claims, where you have provided a stressor description with a location and a date range of roughly 60 days, VA is required to attempt corroboration through unit records, morning reports, and the records repository that succeeded the Joint Services Records Research Center. A denial for "unverified stressor" where no research request was ever submitted is a duty-to-assist failure, not an evidentiary finding.

6. Development ordered but never completed

A prior decision, remand or deferral instructed that something be obtained, and the file shows it never was. This one is easy to prove because VA documented the requirement itself.

Why this matters procedurally

A duty-to-assist error is not just a complaint. It is one of the two grounds a Higher-Level Review exists to address, the other being a difference of opinion on the same record.

Under 38 CFR §3.2601, where the higher-level reviewer identifies a duty-to-assist error, the claim may be returned for correction of that error. In practice that can mean VA goes and obtains the records it should have obtained, or orders the examination it should have ordered, or orders a corrected examination — and then decides the claim on the completed record.

Note the limit that follows from HLR's design: no new evidence may be submitted in a Higher-Level Review. The duty-to-assist argument therefore has to be built entirely from what is already in the file. That is usually possible, because the error is an absence in the file — and an absence is visible from the file itself.

How to find one in your C-file

Request your claims file, then work through it methodically. What you are looking for is the gap between what VA said it did and what the documents show it did.

1. List every record source you identified. Go through your claim forms, every 21-4142 authorisation, and every statement you filed. Write down each provider and facility.
2. For each one, find the request in the file. Is there an outgoing request? A response? A follow-up? A notification to you that VA could not obtain it? Any missing step is a potential error.
3. Check the "evidence considered" list in the decision. Compare it against your list. Anything on your list that is not on VA's list is a candidate.
4. Check the VA treatment record date range. If VA pulled records through 2021 and decided the claim in 2024, three years of your own VA treatment were never considered.
5. Check whether an examination happened at all, and if not, work the four McLendon factors against the file.
6. If there was an examination, read it against the question asked. Compare the examination request to the opinion returned. An opinion that answers a different question than the one posed is inadequate.
7. Read every deferred rating and prior remand instruction and confirm each instruction was carried out.
8. For a stressor claim, look for the research request and its response.

How to raise it in a Higher-Level Review

Vagueness is what sinks these arguments. "VA didn't help me" gets nowhere. A duty-to-assist argument should be specific enough that the reviewer can verify it from the file in a couple of minutes.

1. Name the missing evidence exactly. Provider or agency, facility, and the date range.
2. Show you identified it. Cite the form or statement, with its date, where you told VA about it.
3. Show VA did not obtain it. Point to the absence of the request in the file, or to the absence of the notification §3.159(e) required.
4. Cite the provision. §3.159(c)(1) for private records, (c)(2) for federal records, (c)(4) and McLendon for examinations, (e) for the notification failure.
5. Say why it matters. Connect the missing evidence to the specific element VA said was unproven. An error VA considers harmless goes nowhere; explain what the missing evidence would have gone to.
6. File on VA Form 20-0996, identify the issue precisely, and tick the box requesting an informal conference.

Using the informal conference

The informal conference is a telephone call with the higher-level reviewer, and it is the only opportunity in the HLR process to speak to the decision-maker directly. You get one per review, so it is worth using well.

You cannot submit evidence on the call. What you can do is:

• Point the reviewer to specific documents already in the file, by date and description.
• State the duty-to-assist error in one or two sentences and identify the regulation.
• Identify the favourable findings in the prior decision that are binding under §3.104(c) and narrow what remains in dispute — see the denial letter decoder.
• Ask what the reviewer sees as the remaining obstacle to a grant.

Prepare a written outline before the call: the error, the regulation, the document references, and the relief you are asking for. Reviewers handle many files; a clear, specific, verifiable point is far more use to them than a long narrative.

When a Supplemental Claim is the better lane

Duty-to-assist arguments belong in HLR. But if the honest answer is that the evidence your claim needs simply does not exist yet — no diagnosis on the record, no medical opinion linking the condition to service — then no amount of procedural argument fills the hole. In that case you need to add evidence, which means a Supplemental Claim, and a Supplemental Claim triggers a fresh duty to assist in its own right.

There is a strategy point here. Where a claim has both problems — a procedural error and a missing piece of evidence — filing the Supplemental Claim with a well-reasoned nexus opinion is often faster than winning a return for correction. The decision rule is set out in HLR vs Supplemental Claim.

Both lanes have to be filed within one year of the decision to preserve the effective date under the continuous-pursuit rule. Whichever route fits, the deadline is what governs — identify the error, pick the lane, and file inside the year.