The Quiet Tightening: How M-21-1 Updates After Spicer v. McDonough Raised the Bar on Secondary Service Connection Claims

When the veteran community learned about the Spicer v. McDonough ruling, many celebrated what appeared to be a meaningful victory for those pursuing secondary service connection claims based on aggravation. The case addressed long-standing questions about how the VA should evaluate claims under 38 CFR 3.310(b), and the outcome seemed to favor veterans. But buried within the M-21-1 adjudication manual updates that followed — the very updates meant to implement the court's ruling — lies a quieter, more troubling story. In updating Section 5.ii.2.D.1.a, the VA didn't just address the aggravation standard the court ruled on. It also tightened the evidentiary requirements for all secondary service connection claims, including direct secondary causation under 38 CFR 3.310(a), which had nothing to do with the Spicer case. The result? While veterans were celebrating a win on one front, the rules of the game were being rewritten on another — and not in their favor.

This is what some in the veteran advocacy community call the "pendulum effect." When courts rule favorably for veterans, the VA sometimes responds with subtle regulatory or procedural adjustments that swing the pendulum back in the other direction. It's not always dramatic. It's not always immediately obvious. But for the thousands of veterans who rely on secondary service connection claims to obtain the benefits they've earned, these changes could have profound consequences.

Understanding Secondary Service Connection

Before diving into the specifics of what changed, it's important to understand what secondary service connection is and why it matters so deeply to veterans and their families.

Secondary service connection is the legal pathway that allows a veteran to receive compensation for a disability that wasn't directly caused by military service but was instead caused or worsened by a condition that is already service-connected. The governing regulation, 38 CFR 3.310, establishes two distinct pathways for establishing this connection.

Under 38 CFR 3.310(a), a veteran can establish secondary service connection through direct causation. The regulation provides that any disability proximately due to or the result of a service-connected disease or injury shall itself be service connected. For example, a veteran with a service-connected knee injury might develop hip problems because of the altered gait they've adopted over the years. The knee injury caused the hip condition, making it eligible for secondary service connection.

Under 38 CFR 3.310(b), a veteran can establish secondary service connection through aggravation. The regulation covers any increase in severity of a non-service-connected disease or injury that is proximately due to a service-connected condition — and not due to the natural progression of the non-service-connected disease. However, the VA will not concede aggravation unless the baseline level of severity of the non-service-connected condition is established by medical evidence created before the onset of aggravation, or by the earliest medical evidence created at any time between the onset of aggravation and the receipt of medical evidence establishing the current level of severity. For instance, a veteran's service-connected PTSD might significantly worsen a pre-existing cardiovascular condition that existed before or independently of military service.

These two pathways are critically important because military service rarely damages the body in isolation. Conditions cascade. A back injury leads to nerve damage. Chronic pain leads to depression. Medication for one condition causes gastrointestinal problems. Secondary claims represent one of the most common and vital ways veterans receive the full scope of compensation they deserve. And the evidentiary standard applied to these claims — the level of proof required — directly determines how many veterans can successfully navigate this process.

What the Spicer v. McDonough Ruling Actually Addressed

The Spicer case involved a veteran whose service-connected leukemia required medications that lowered his hematocrit (red blood cell level) to a point that precluded him from undergoing knee replacement surgery — surgery that could have alleviated his bilateral leg disability. Mr. Spicer was told his hematocrit would never rise to a level that would permit surgery because he was expected to stay on his cancer medications for life.

The VA regional office denied his claim for secondary service connection, and the Board affirmed, concluding that his inability to undergo knee replacement surgery because of the effects of his service-connected leukemia did not fall within the meaning of secondary service connection under the applicable laws or regulations. Mr. Spicer appealed, arguing that 38 U.S.C. § 1110 establishes entitlement to service connection in his circumstances, notwithstanding any regulation.

The case ultimately focused on the scope of secondary service connection and the meaning of causation within the statutory and regulatory framework. The ruling was widely interpreted as a clarification favorable to veterans — a win that would make it easier to establish aggravation-based secondary claims.

When a significant court ruling like Spicer comes down, the VA updates its internal adjudication manual — the M-21-1 — to reflect the new legal landscape. The M-21-1 is essentially the operating manual for VA Rating Veterans Service Representatives (RVSRs), the staff members who review evidence and make decisions on veterans' claims. Whatever the manual says is how evidence gets evaluated, how medical examinations are interpreted, and ultimately, whether a claim gets granted or denied.

So when the VA updated Section 5.ii.2.D.1.a of the M-21-1, veterans and advocates expected changes to the 3.310(b) aggravation standard. What they didn't expect — and what many haven't yet fully grasped — is that the VA used this same update to fundamentally alter the 3.310(a) direct secondary causation standard as well.

What Actually Changed in the M-21-1 Manual

The cleanest way to understand what the VA did is to walk through Section 5.ii.2.D.1.a phrase by phrase, comparing the old language to the new.

The section is titled "Provisions for SC Under 38 CFR 3.310(a) and (b)" and it tells adjudicators when to award service connection. Under the old version, the manual instructed raters to award service connection for "disabilities that are proximately due to, or the result of … a service-connected condition." Under the new version, the words "proximately due to, or" have been struck out, and a new phrase has been inserted in their place: "or would not have occurred but for." The word "condition" was also replaced with "disability." So the operative bullet now reads: "disabilities that are the result of, or would not have occurred but for, a service-connected (SC) disability."

The aggravation bullet under 3.310(b) was rewritten even more aggressively. The original language read "the increase in severity of a non-service-connected (NSC) disability that is attributable to aggravation by an SC disability, and not to the natural progression of the NSC disability." The new version strikes "the increase in severity" and replaces it with "aggravation." It strikes "attributable to aggravation by" and replaces it with "the result of." It strikes the entire "natural progression" qualifier — which historically gave examiners the analytical room to weigh how much of the worsening was due to service versus the natural course of the disease — and replaces it with the word "including," followed by two new sub-bullets that define what aggravation now means in practice:

• "any increase in severity of an NSC disability that would not have occurred but for the SC disability, or"
• "where an NSC disability would have been less severe but for the SC disability, including where the SC disability has interfered with or impeded treatment for the NSC disability."

Reading the before-and-after side by side, the pattern is unmistakable. Three different phrases that allowed for reasonable inference and professional judgment — "proximately due to," "attributable to aggravation by," and "and not to the natural progression of the NSC disability" — were all removed. In their place, the manual now uses "but for" causation language in three separate spots. That phrase, "but for," is doing a tremendous amount of work, and it's worth examining carefully.

Changes to Direct Secondary Causation — 38 CFR 3.310(a)

Under the old standard, the M-21-1 manual directed adjudicators to evaluate whether disabilities were "proximately due to or the result of" a service-connected condition — language that mirrored the regulation itself. This phrasing provided two thresholds. The "proximately due to" component functioned as a lower threshold — closer to an "at least as likely as not" standard that allowed for some flexibility. If a medical examiner found a reasonable association between the service-connected condition and the claimed secondary disability, that was often sufficient. The benefit of the doubt could tip the scales in the veteran's favor. The "result of" component represented a stricter standard, requiring a more definitive causal link.

Under the new standard, the VA removed the "proximately due to" language from the manual's adjudication guidance. Now, the disability must be shown to be "the result of" the service-connected condition or it "would not have occurred but for" the service-connected disability.

Read those two options carefully. By eliminating the lower "proximately due to" threshold, the VA has made "the result of" the least demanding option available — and it was previously the more strict of the two alternatives. The new addition — "would not have occurred but for" — is an even more stringent test. It essentially requires proving exclusive causation: that the secondary condition would simply not exist if not for the service-connected disability.

Both of these remaining options represent a higher burden of proof than the "proximately due to" language they replaced. And here's the critical point that every veteran needs to understand: this change to the 3.310(a) adjudication guidance had nothing to do with Spicer v. McDonough. The court case addressed the scope of secondary service connection in the context of treatment interference and aggravation. The direct secondary causation standard under 3.310(a) was not at issue. Yet the VA changed it anyway, using the same manual update as the vehicle.

It's worth noting that the actual text of 38 CFR 3.310(a) itself still uses the phrase "proximately due to or the result of." The regulation hasn't been amended. What changed is how the M-21-1 manual instructs adjudicators to apply it — and that distinction matters enormously in practice.

Changes to Aggravation-Based Secondary Claims — 38 CFR 3.310(b)

The aggravation standard — the one Spicer actually addressed — was also modified in the manual, and not necessarily in the way veterans might have hoped.

Under the old M-21-1 framework, the manual directed adjudicators to evaluate whether there was an increase in severity of a non-service-connected disability that was "attributed to aggravation by a service-connected disability and not to the natural progression of the non-service-connected disability." This language tracked the regulation, which requires that the increase be proximately due to or the result of a service-connected disease or injury, and not due to the natural progress of the non-service-connected disease. In practical terms, you needed to demonstrate that your condition got worse and that the worsening could be reasonably attributed to your service-connected disability rather than to the natural course of the non-service-connected condition. It wasn't easy, but the language allowed for reasonable inference.

Under the new standard, the increase in severity must be shown to "would not have occurred but for the service-connected disability." Alternatively, the veteran can show that the non-service-connected disability "would have been less severe but for the service-connected disability, including where the service-connected disability has interfered with or impeded treatment for the non-service-connected disability."

The shift here is significant. The old framework required showing that the worsening was attributable to the service-connected condition. The new standard requires proving the worsening would not have happened at all without the service-connected condition — a "but for" causation test that demands a much higher degree of certainty. The treatment-interference caveat does provide a secondary pathway — one that directly reflects the Spicer fact pattern, where Mr. Spicer's service-connected leukemia medications prevented him from having knee surgery — but it comes with its own evidentiary burden: you have to specifically prove that the service-connected condition interfered with or impeded treatment for the non-service-connected disability.

Even the standard that Spicer was supposed to improve appears to have been tightened rather than loosened in practical application.

Why This Matters: Real-World Impact on Veterans' Claims

The Goalpost Problem

Here's what makes these changes so consequential. The legal standard for granting a VA disability claim hasn't technically changed — it's still "at least as likely as not," meaning a 50 percent or greater probability. But the M-21-1 manual language changes affect how examiners and raters frame and evaluate the evidence to reach that threshold. And framing matters enormously.

Consider this analogy: if you came upon the scene of a car accident, the words someone uses to describe what happened would fundamentally shape your understanding of the event. "Fender bender" conjures one image. "Totaled car" conjures another entirely. The underlying facts might be the same, but the language used to describe them changes how you perceive and evaluate the situation.

The same principle applies here. When a medical examiner is asked whether a condition is "proximately due to" a service-connected disability, they're operating within a framework that allows for reasonable association and professional judgment. When they're asked whether a condition is "the result of" or "would not have occurred but for" a service-connected disability, the framing demands a higher degree of certainty before they can offer a favorable opinion. The VA is effectively moving the goalpost on what level of evidence is needed to reach the "at least as likely as not" threshold — even though the threshold itself hasn't changed on paper.

Subjective Claims Face the Greatest Risk

Not all secondary claims will be equally affected by these changes. Claims involving well-established, medically obvious relationships will likely continue to be granted at similar rates. If a veteran has a service-connected lumbar spine condition and develops radiculopathy — a nerve condition that is a well-known, medically documented consequence of spinal problems — the causal link is clear enough that the new language probably won't create significant obstacles.

The claims that will bear the brunt of these changes are those involving more subjective or complex medical associations. Consider these common secondary claim scenarios:

• Erectile dysfunction secondary to PTSD — There is medical literature supporting this connection, but the relationship is complex and involves multiple potential contributing factors.
• Mental health conditions secondary to chronic physical disabilities — Depression secondary to chronic pain, for example, often involves multiple causative factors.
• Gastrointestinal conditions secondary to medication use for service-connected conditions — Establishing that GI problems "would not have occurred but for" the medication requires ruling out all other potential causes.

In each of these cases, the old "proximately due to" standard gave examiners room to acknowledge the connection even when other factors were present. The new standard demands more definitive proof of causation, which is inherently harder to establish for conditions with multifactorial origins.

The Examiner-Rater Conflict

Perhaps the most troubling practical consequence of these changes is the potential conflict they create between medical examiners and VA raters.

Medical examiners — whether VA staff or private practitioners — may continue to write opinions using the language they've always used. An examiner might write that a veteran's secondary condition is "at least as likely as not proximately due to" their service-connected disability. Under the old framework, that opinion would likely be sufficient to support a grant.

Under the new manual language, however, the RVSR reviewing that opinion may be directed to find it insufficient. The manual now instructs raters to evaluate whether the evidence shows the condition is "the result of" or "would not have occurred but for" the service-connected disability. If the examiner's opinion doesn't use that specific framing, the rater may be compelled to push back — requesting a new opinion, seeking clarification, or potentially denying the claim even when the examiner intended to support it.

This creates a frustrating gap where the medical professional supports the veteran's claim, but the adjudicator's updated instructions require a higher standard of proof. Veterans caught in this gap face unnecessary delays, denials, and the burden of navigating the appeals process.

How VeteranAI Researches Counter-Evidence to Strengthen Your Nexus Letter

This is precisely the kind of evidentiary tightening that VeteranAI was built to help veterans navigate. When a claim depends on a higher burden of proof — a "result of" or "but for" standard — a generic nexus letter is no longer enough. The letter needs to anticipate the rater's skepticism and address it head-on. That means going beyond simply asserting a connection; it means proactively identifying and rebutting the counter-conditions and alternative explanations a rater is most likely to point to when denying a claim.

Here's how the VeteranAI nexus letter generator approaches this differently than a template:

Searching the medical literature for both sides of the argument. Our AI doesn't just look for studies that support your claim — it actively searches for alternative causes, comorbidities, and competing diagnoses that a VA rater might cite as a reason to deny. If the literature shows a counter-condition exists, the letter addresses it directly rather than ignoring it. A rater can't easily dismiss a nexus opinion that has already acknowledged and rebutted the obvious counter-argument.

Aligning the language with current adjudication standards. Because the M-21-1 framework now demands "result of" or "but for" causation language, our nexus letter output is structured to use the precise causation phrasing the rater is trained to look for. Vague phrases like "may be related to" or "there appears to be an association" are exactly the kind of hedging that triggers a denial under the new standard.

Cross-referencing your C-File for supporting evidence the rater can verify. A nexus opinion is much harder to dismiss when it's grounded in evidence already in the veteran's own records. The C-File Analyzer reads through your claims file and service treatment records to surface in-service events, diagnoses, and treatment history that establish the foundation for a strong secondary claim — including baseline severity evidence, which is required for aggravation claims under 38 CFR 3.310(b).

Flagging when the evidence isn't strong enough. This is important: VeteranAI will not generate a nexus letter if the medical research and your individual evidence don't actually support the connection. Submitting a weak letter does more harm than good. We'd rather tell a veteran their claim needs more evidence than help them file something that's likely to be denied and damage their credibility on appeal.

The goal is straightforward — give the veteran the strongest possible draft to bring to a treating provider for review and signature, with the counter-arguments already addressed and the language already aligned with how the VA actually evaluates claims today.

Adapting Your Medical Evidence Strategy

Given these changes, every veteran who is obtaining a private Disability Benefits Questionnaire (DBQ) or independent medical opinion (IMO) needs to be acutely aware of the new language requirements. Medical providers filling out these documents must now use specific causation language that aligns with the updated manual framework.

For claims under 3.310(a), the medical opinion should clearly state that the secondary condition is "the result of" the service-connected disability, or that it "would not have occurred but for" the service-connected disability. Generic statements about association or probability may no longer be sufficient.

For claims under 3.310(b), the opinion should state that the worsening of the non-service-connected condition "would not have occurred but for" the service-connected disability, or that the condition "would have been less severe but for" the service-connected disability. Where applicable, the opinion should include specific evidence of how the service-connected condition interfered with or impeded treatment for the non-service-connected disability. Additionally, remember that the VA requires the baseline level of severity of the non-service-connected condition to be established by medical evidence — either created before the onset of aggravation or by the earliest evidence created between the onset of aggravation and the current medical evidence.

Vague or hedging language that may have been acceptable under the old framework — statements like "it is possible that" or "there appears to be some association" — will almost certainly be inadequate under the new standards. Precision in language has always mattered in VA claims, but with these changes, the margin for error has gotten considerably smaller.

The Pendulum Effect: A Pattern Worth Recognizing

What happened with the M-21-1 updates following Spicer v. McDonough is not an isolated incident. It reflects a pattern that veterans and their advocates should recognize and watch for.

When courts rule in veterans' favor, the VA sometimes responds by tightening other regulatory or procedural mechanisms — not necessarily the specific provision the court addressed, but adjacent ones that affect the same population of claimants. The Spicer changes provided both the procedural vehicle and the political cover to simultaneously revise the unrelated 3.310(a) standard. The veteran community's attention was focused on understanding and celebrating the aggravation-related changes, while the direct secondary causation standard was quietly tightened with little public discussion or fanfare.

This is why it's essential for veterans, advocates, and Veterans Service Organizations (VSOs) to scrutinize the full text of every M-21-1 update — not just the sections that appear to be directly tied to a specific court ruling. Wins in one area can be offset, or even outweighed, by quiet tightening in others. The details matter, and they matter enormously.

What Veterans Should Do Now

If you're a veteran with a secondary service connection claim — whether pending, recently filed, or being contemplated — these changes demand your attention and, in many cases, your action.

Review your pending claims. If you have a secondary claim in the pipeline, evaluate whether your existing medical evidence meets the new "result of" or "but for" threshold. Evidence that was strong enough under the old standard may need to be supplemented or updated. Running your records through the C-File Analyzer can help surface secondary connections and supporting evidence you may have missed.

Strengthen your medical evidence. Work with your medical provider to ensure that nexus opinions use the specific causation language now required by the updated manual. Don't leave room for ambiguity. The opinion should clearly articulate the causal relationship in terms that satisfy the new framework — and ideally, address the counter-conditions a rater might cite as alternative explanations. For aggravation claims, include specific evidence of how the service-connected condition worsened the non-service-connected disability beyond its natural progression, document any treatment interference where applicable, and establish baseline severity with appropriate medical evidence. The VeteranAI nexus letter generator was designed specifically to handle this kind of evidence-backed, counter-argument-aware drafting.

Consult a knowledgeable advocate. These changes are nuanced, and their implications for claim strategy are significant. Veterans should discuss the M-21-1 updates with accredited Veterans Service Organizations (VSOs), claims agents, or attorneys who understand the distinction between the old and new standards. Many county and state VSOs now use VeteranAI's seat-based licensing to give the veterans they serve direct access to AI-assisted documentation tools, which can be a force multiplier on cases involving subjective conditions or complex medical relationships.

Understand the appeals process. If a secondary claim is denied under the new standard, carefully review the denial letter to determine whether the updated evidentiary threshold was applied. Understanding whether a denial was based on insufficient evidence under the new framework versus a legitimate medical determination is critical for crafting an effective appeal. The specific language used in the denial can tell you a great deal about which standard was applied and where your evidence fell short.

Staying Informed, Staying Vigilant

The Spicer v. McDonough ruling itself may well represent genuine progress for veterans pursuing aggravation-based secondary claims. That progress should be acknowledged. But the accompanying M-21-1 manual changes represent a net tightening of secondary service connection standards that could affect thousands of veterans across both the 3.310(a) and 3.310(b) pathways.

The removal of the "proximately due to" language from the manual's adjudication guidance is not a minor editorial change — particularly when the regulation itself, 38 CFR 3.310(a), still uses that exact phrase. It represents a fundamental shift in how VA adjudicators are instructed to evaluate the evidence in secondary claims. The replacement language — "the result of" and "would not have occurred but for" — demands stronger, more definitive proof of causation. For veterans with straightforward, medically obvious secondary conditions, the impact may be minimal. For those with more complex or subjective claims, the path to service connection just got harder.

The VA claims process has always rewarded preparation and precision. It has always demanded that veterans present their cases with clear evidence, specific language, and thorough documentation. With these M-21-1 changes, those demands have intensified. The margin for error is smaller. The language in your medical opinions matters more than ever. And the need for informed, evidence-based advocacy has never been greater.

Veterans earned their benefits through service and sacrifice. The system that adjudicates those benefits should not be quietly shifting the rules in ways that make it harder for deserving claims to be granted. Stay informed. Review the changes. Update your evidence. And make sure the people — and the tools — helping you with your claims understand exactly what the new standards require, including how to anticipate and rebut the counter-conditions a rater is most likely to cite. The details in the M-21-1 manual are where your claim lives or dies.

---

VeteranAI is a self-service AI platform used by 30,000+ veterans to independently prepare VA disability claim documentation. Start free — no credit card required.