When VA writes “no in-service event” or “no nexus,” they are not saying your condition is fake. They are saying the file does not prove one of the required links. You are not here to guess. You are here to understand. In plain English, VA is looking for a clean chain: (1) you have a current disability, (2) something happened in service (event, injury, illness, exposure), and (3) medical logic connects the two (nexus). A denial for “no in-service event” usually means link #2 is not established. A denial for “no nexus” usually means link #3 is not established, even if #2 is conceded or partially supported. Before you pull documents, read your Rating Decision and the “Reasons for Decision” section like a checklist. Highlight the exact sentence VA used. That sentence is your work order.
Start with the minimum set that tells you what VA considered and what they ignored. No hype. No shortcuts. No confusion. Pull these three items first: 1) Your VA Rating Decision and denial letter: Specifically the “Reasons for Decision” and “Evidence” list. The “Evidence” list is critical because it tells you what was actually in the file when VA decided. 2) Your C&P exam report and DBQ (if an exam happened): If the examiner wrote “no evidence in STRs,” “veteran reports X but cannot be corroborated,” or gave a negative nexus opinion, that tells you what kind of evidence will be “new and relevant.” For how to get the DBQ, use the process outlined in our existing guide: /blog/how-to-get-your-va-cp-exam-dbq-results-and-what-to-do-if-va-wont-release-them. 3) Your service treatment records (STRs) and personnel records (OMPF): STRs are where sick call, injury notes, profiles, and line of duty notes live. Personnel records are where assignments, dates, duties, and sometimes incident related paperwork shows up. If VA says “no in-service event,” STRs and personnel records are the first place to confirm whether the event is missing or just buried.
If the denial is “no in-service event,” your job is to prove that something happened during service that could reasonably cause or aggravate the condition. We follow VA logic step by step. Pull evidence in this order because it usually produces the fastest clarity: A) STR pages tied to the date window: sick call notes, ER visits, imaging orders, physical therapy, profiles, duty restrictions, and separation health assessments. If you do not know the date, start with a 30 to 90 day window around when you remember it happening. B) Personnel and admin proof of the circumstances: orders, travel vouchers, deployment records, training records, qualification logs, mishap reports, disciplinary records (yes, sometimes), performance evals mentioning injury limitations, and any documentation that places you at the location or doing the duty when the event occurred. C) Unit records when the incident was operational, not medical: unit logs, after-action reports, situation reports, safety reports, deck logs, watch logs, flight logs, convoy logs, incident reports, or command chronologies. These are most useful when the event was real but never made it into your STRs because you “worked through it.” D) Contemporaneous civilian records: off-base ER or urgent care, chiropractic visits, employer injury reports (post-service but close in time), or insurance records. If the event happened in service but you were treated off base, those records can be the missing puzzle piece. E) Lay evidence that anchors the event: buddy statements and your personal statement. Lay evidence cannot diagnose you, but it can prove what was observed and when. That matters when the medical record is thin.
A “no nexus” denial usually means VA accepts you have a condition now, and may even accept something happened in service, but they do not see a medically persuasive bridge between the two. Here is what to pull for a nexus-focused Supplemental Claim: A) The negative nexus opinion itself: Identify the examiner’s stated reason. Common patterns include: “no chronicity,” “no treatment for years,” “more likely due to aging,” “post-service injury explains it,” or “insufficient evidence.” Your response evidence should target that stated reason directly. B) Treatment records showing continuity and pattern: primary care notes, specialty notes, physical therapy records, mental health notes, medication history, and symptom complaints repeated over time. VA adjudicators respond to consistency across years. C) Imaging and objective testing: X-rays, MRIs, sleep studies, audiograms, nerve conduction studies, labs, or any test that supports severity and chronicity. Objective data is not required for every claim, but when it exists, it strengthens the bridge. D) A medical opinion when the gap is medical, not factual: A nexus letter or Independent Medical Opinion can be “new and relevant” evidence if it uses the correct standard (“at least as likely as not”), shows the provider reviewed records, and explains the reasoning. A one-line opinion with no rationale often fails. Important limit: a buddy statement or your own statement can support symptoms and history, but it usually cannot replace a medical nexus when VA’s denial rests on medical causation. If the denial is truly medical, you need medical logic in the file.
This is where most veterans waste months: they submit the wrong kind of “new evidence.” Use this decision guide instead. Choose UNIT RECORDS when: the event was operational or documented at the unit level, not in your medical file. Examples include vehicle accidents, training incidents, shipboard mishaps, firefights, mass casualty events, exposure incidents, or anything that would show up in logs or reports. Unit records are strong because they are independent of your memory and often time-stamped. Choose a BUDDY STATEMENT when: someone else personally witnessed the event, the immediate aftermath, or your symptoms during service. Buddy statements are best for filling a missing STR entry, confirming you reported symptoms, confirming duty limitations, or describing a visible change. They are weaker when the buddy is guessing at a diagnosis or repeating what you told them years later. Choose a PERSONAL STATEMENT when: you need to give VA a coherent timeline that ties the event to symptoms to today, especially when records are scattered. Your statement is where you explain onset, progression, flare-ups, and functional impact in plain language. A good personal statement does not argue the law. It documents reality. Practical rule: if the question is “Did it happen?” unit records and buddy statements usually answer it better than your statement alone. If the question is “How has it affected you over time?” your personal statement and treatment records do the heavy lifting. If the question is “Is it medically connected?” a medical opinion and consistent medical records matter most.
Illustrative scenario: A veteran files for a back condition. VA denies: “No in-service event” and “no nexus.” The veteran assumes they need a stronger personal statement, so they write three pages describing pain since 2012. But the real problem is the file never proved the 2012 incident happened in the way described. STRs are silent because the veteran never went to sick call. The fix is not a longer story. The fix is a different category of evidence: a buddy statement from the person who drove them to medical, plus unit records showing the training incident occurred, plus a medical opinion that explains how that mechanism of injury can lead to the current diagnosis. Same truth every time: the winning move is the evidence that answers the exact reason VA gave, not the evidence that feels most personal.
A Supplemental Claim (VA Form 20-0995) lives or dies on “new and relevant evidence.” New means VA did not have it before. Relevant means it tends to prove or disprove a matter at issue, like the in-service event or the nexus. Use this pre-file checklist: 1) Match each denial reason to one piece of evidence: If the denial has two reasons, you need to address both, not just one. 2) Confirm it is actually new: If it is already listed under “Evidence” in the decision, resubmitting it usually does nothing unless you are highlighting a specific page with a new argument and supporting context. 3) Make the evidence easy to rate: label files clearly (Example: “STR 2012-05-14 Sick Call,” “Buddy Statement SGT Smith,” “Unit Safety Report,” “Nexus Opinion Dr Jones”). Disorganized uploads slow everything down. 4) Avoid common lay statement errors: no diagnosing, no exaggeration, no vague timelines. Observations, dates, and functional impact only. 5) Keep your effective date in mind: You generally have 1 year from the decision date to choose a review option and preserve the effective date. This is general information, not legal advice. Confirm your exact deadline on your decision letter. For official VA starting points on rates and benefits rules, use VA.gov (example compensation tables: https://www.va.gov/disability/compensation-rates/veteran-rates/). For this article, the key is process, not rate numbers.
If you are deciding between a buddy statement, a personal statement, and unit records, start by writing a one-page timeline for yourself: date window, location, unit, what happened, immediate symptoms, and how it progressed. That timeline tells you what kind of proof is missing. Then draft the statement type that fits the gap. If you need a clean structure for lay evidence, use our buddy statement tool to generate a proper observation-based format you can edit and sign: /buddy-statements. The goal is not volume. The goal is the right evidence for the exact denial reason.