How to Build a Clean Secondary-Claim Evidence Packet (No Nexus Guessing)

Direct answer: what a “clean” secondary-claim packet does

A clean secondary-condition evidence packet does one job: it makes it easy for the VA rater to follow the evidence trail without you trying to play doctor. You are not here to guess. You are here to understand. For a secondary claim, the VA is looking for three pillars, in order: (1) an already service-connected primary condition, (2) a current diagnosis of the secondary condition, and (3) competent evidence that the secondary condition is caused or aggravated by the primary condition. That third pillar is the “nexus,” and it usually needs a medical opinion, not a veteran-written conclusion. So your packet should focus on what you can prove cleanly as a layperson: dates, symptoms, treatment, and functional impact. Then you either (a) let the VA order a C&P exam opinion, or (b) submit a medical opinion that uses the correct standard. No hype. No shortcuts. No confusion.

Step 1: Use VA logic step by step (secondary claim basics)

We follow VA logic step by step. A secondary claim is not “I have X and it feels connected to Y.” It is a structured argument with evidence types that carry different weight. Here is the clean framework you are building toward: 1) Primary condition is already service-connected: You prove this with the VA rating decision code sheet or award letter showing the service-connected disability and its evaluation. 2) Secondary condition exists now: You prove this with a diagnosis in VA or private records, a problem list entry, imaging, labs, or a completed DBQ. Symptoms alone are not the same as a diagnosis. 3) Link (causation or aggravation): This is where veterans accidentally hurt themselves. If you write “my PTSD caused my sleep apnea” or “my knee caused my hip arthritis,” that is a medical conclusion unless you are qualified and your statement is supported by medical rationale. Your job is to document observable facts and functional loss, and then let a clinician provide the nexus opinion if needed. Important distinction: “caused by” and “aggravated by” are different. Aggravation means the primary condition permanently worsened the secondary condition beyond natural progression. Many secondary claims are stronger under aggravation when there are other risk factors in the record.

Step 2: Build a timeline that is factual, not persuasive

A timeline is the backbone of your packet. It helps the examiner and the rater understand onset, progression, and why the secondary condition is not a random one-off. Keep the timeline factual and sourced. That means each line points to a record, a date, and a concrete event. Think like an investigator, not an advocate. Use this simple timeline format (one page is ideal): • Date: Primary condition event or flare (record source) • Date: First documented symptoms that relate to the secondary condition (record source) • Date: First treatment attempt (medication, PT, counseling, CPAP trial, etc.) (record source) • Date: Formal diagnosis of the secondary condition (record source) • Date: Worsening markers (ER visits, dose increases, missed work, assistive devices, new limitations) (record source) What counts as a “record source”: a clinic note, imaging report, lab result, discharge summary, medication list, physical therapy note, urgent care note, sleep study report, or an employer accommodation letter. If it is not documented, treat it as your personal report and label it that way. Illustrative scenario: A veteran is service-connected for a right knee condition. Two years later, gait changes are documented in PT notes. Six months after that, the veteran seeks care for low back pain, then later receives a radiculopathy diagnosis. The packet does not claim “knee caused radiculopathy.” It shows the sequence, the gait documentation, the onset, and the functional impact, then lets the medical opinion connect the dots.

Step 3: Document functional impact like the VA rates it (without exaggeration)

Secondary service connection gets you in the door. Severity and functional impact help determine the rating. Your packet should make functional loss easy to see over time. Functional impact is not “it’s bad.” It is: frequency, severity, duration, and what you cannot do on your worst days. This is aligned with how C&P exams and DBQs are written for adjudicators. Use a “functional impact snapshot” page for each secondary condition. Keep it plain English: • Daily life: walking, stairs, standing, sitting, driving, cooking, hygiene, sleep • Work: missed days, reduced hours, duty changes, accommodations, write-ups • Safety: falls, near-misses, inability to drive during episodes, supervision needed • Flare-ups: triggers, frequency, typical duration, what stops during a flare • Treatment burden: meds and side effects, PT frequency, devices (brace, cane, CPAP), appointments If you have logs, summarize them. Do not dump 90 pages of raw notes unless asked. For migraines, a headache log summary is often stronger than scattered portal messages. For musculoskeletal issues, PT progression notes and range-of-motion findings are usually more persuasive than general complaints. Do not minimize. Do not inflate. Describe your worst days, not just average days. That is C&P logic, and it keeps your statements consistent with later exam questions.

Step 4: Write lay statements that stay in your lane (what to say and what not to say)

Lay statements are powerful when they describe what you observed. They get weak when they try to prove medical causation. Use this rule: if it requires a medical explanation, do not state it as fact. State what happened, what changed, and what a clinician told you, with attribution. Safe language examples (clean, credible): • “After my knee pain worsened, I began limping daily. My spouse noticed I started avoiding stairs. I later sought care for hip pain.” • “I take medication X for my service-connected condition. After starting it, I began experiencing symptom Y. I reported this to my provider on [date].” • “My provider noted altered gait in PT on [date].” • “I was diagnosed with [secondary condition] on [date] at [clinic].” Risky language examples (avoid unless it is a quoted medical opinion): • “My knee caused my hip arthritis.” • “My PTSD definitely caused my sleep apnea.” • “The VA has to connect these.” • “This is scientifically proven in my case.” If you want to reference a clinician’s view, do it like this: “Dr. Smith told me on [date] that my altered gait may be contributing to my hip pain.” That is still not a nexus opinion, but it is an accurate report of what you were told. Buddy statements follow the same rule. They should describe observable changes: sleep disruptions, snoring and apneic episodes, limping, missed social events, irritability, panic episodes, falls, or needing reminders. They should not diagnose you or declare causation.

Step 5: Assemble the packet in an order a rater can scan in 5 minutes

Most evidence packets fail because they are technically “complete” but practically unreadable. Your goal is scanability. Recommended packet order (PDF or binder-style): 1) Cover page: Name, last four, claim type (secondary), list of documents included 2) One-page timeline (with exhibit numbers) 3) Proof of primary service connection: rating decision excerpt or code sheet 4) Secondary condition diagnosis evidence: key records only (diagnosis note, imaging, sleep study, specialist note) 5) Functional impact evidence: PT notes, work accommodations, symptom log summary, ER visits, assistive device prescriptions 6) Lay statement (you): one to two pages focused on timeline and impact 7) Buddy statement(s) if relevant 8) Optional: DBQ and or medical opinion (if you have it) How to keep it clean: • Highlight nothing. Let the structure do the work. • Use exhibit labels: “Exhibit A: Knee SC code sheet,” “Exhibit B: Hip X-ray,” etc. • Include only the pages that matter. If a record is 20 pages, include the relevant pages and note “excerpted for relevance.” • Avoid duplicate copies of the same note from different portals. If you submit private records, include the provider letterhead pages that show the clinic name and date. Undated screenshots create friction and credibility issues.

Step 6: Handle the nexus gap the right way (without making it worse)

If your packet clearly shows (1) SC primary condition and (2) current secondary diagnosis and (3) a reasonable indication they may be connected, the VA may order a C&P exam and obtain a medical opinion under its duty to assist. That is often the correct path when you do not already have a strong medical opinion. If you decide to submit a medical opinion (nexus letter or IMO), it should use VA’s standard: “at least as likely as not (50% or greater probability)” with rationale. A one-line letter that says “it is due to service” is usually weak. What you should not do is try to “write the nexus into existence” with confident wording in your personal statement. That can backfire if the examiner sees overreach or if your statement conflicts with medical risk factors in the record. A clean approach is to end your statement with a request, not a conclusion: “I am claiming [secondary condition] as secondary to my service-connected [primary condition]. I request VA consider causation and aggravation and obtain any necessary medical opinion.” This is not legal advice. It is evidence hygiene. Your packet should make it easier for the VA to do the right development, not give them reasons to doubt your credibility.

Next step: use the DBQ to self-audit what evidence you still need

Your next step is to pull the DBQ for your secondary condition and use it as a checklist. DBQs show exactly what the examiner must document, including functional impact. When you know what boxes exist, you stop guessing and start preparing. Go to our DBQ Library at /dbq-library, find the DBQ for your secondary condition, and compare it to your packet. If you cannot point to evidence for diagnosis, history, frequency, flare-ups, and functional loss, that is what you gather next. No hype. No shortcuts. No confusion.

  • All VA claims and benefits articles
  • DBQ Library
  • Buddy Statement Drafting Tool
  • Conditions Library
  • Secondary Conditions Finder