How to Prove Migraines Are “Prostrating” to the VA (Headache Log Guide)

The VA question you are really answering

You are not here to guess. You are here to understand. When the VA evaluates migraines, they are not just asking, “Do you get headaches?” They are asking whether you have characteristic prostrating attacks, how often they happen, how long they last, and whether they disrupt work and life. In plain English, “prostrating” is VA shorthand for an attack that knocks you down. Not “I had pain but pushed through.” More like “I had to stop, isolate, lie down, and I could not function.” Your goal is to document that pattern in a way a C&P examiner and rater can trust. This is general education, not medical or legal advice. Ratings depend on the full record, including treatment notes and the C&P exam. But a clean headache log can be the difference between “vague symptoms” and “credible, rateable evidence.” Official starting point for current VA compensation tables (for pay amounts, not criteria): https://www.va.gov/disability/compensation-rates/veteran-rates/. The migraine rating criteria live in VA’s rating schedule (38 CFR Part 4).

Illustrative scenario: “The log that finally made sense”

Illustrative scenario: A veteran we will call Alex is trying to explain migraines at a C&P exam. He says, “They hit me a few times a week. I take meds. Sometimes I miss work.” The examiner asks, “How often are they prostrating?” Alex freezes. He says, “Uh, most of them.” The examiner writes something that sounds harmless but is deadly to clarity: “Veteran reports frequent headaches. Prostrating frequency unclear.” The rater now has a documentation problem. Not because Alex is lying, but because the record cannot reliably convert his experience into the VA’s language. So Alex starts a headache log. Not a diary. Not a venting journal. A log built for VA logic. Two months later, his entries show a consistent pattern: specific start times, duration, whether he had to lie down, what he could not do, and what medication did or did not do. Now, when asked “prostrating?” he can answer without guessing. That is the whole point. No hype. No shortcuts. No confusion.

What “prostrating” looks like in a log (interactive self-check)

Use this quick self-check. For each migraine episode, ask yourself: 1) Did I have to stop what I was doing? If you kept working normally, driving normally, or doing normal chores without interruption, it is harder to call it prostrating. 2) Did I need to lie down or isolate? Many veterans describe needing a dark room, silence, no screens, no movement. That is functional impact the VA can understand. 3) Was I unable to perform ordinary activities? Examples: could not drive safely, could not work, could not care for kids, could not complete basic tasks. 4) How long did that “knocked down” period last? Minutes versus hours matters. Now pause and do a quick tally for the last 30 days: How many headaches happened total, and how many forced you into shutdown mode (lie down, dark room, unable to function)? That second number is usually the “prostrating” count your examiner is trying to capture. Important: some headaches are painful but not prostrating. A credible log distinguishes them. That separation often increases trust, even if it feels like you are “downplaying.” You are not. You are documenting accurately.

What a strong VA headache log looks like (copy-ready template + examples)

A strong log is consistent and boring in the best way. Same fields each time. Same definitions. Same level of detail. If you only write on the worst days and go silent for weeks, it looks like memory based reconstruction instead of tracking. Use these fields for every entry (you can do this in Notes app, a spreadsheet, or paper): A) Date and start time B) End time or total duration C) Severity (0 to 10) and whether it escalated D) Symptoms (nausea, vomiting, light sensitivity, sound sensitivity, aura, dizziness, visual changes, numbness, etc.) E) Prostrating? (Yes or No) with a one line reason F) Functional impact (what you stopped doing, what you could not do) G) Treatment taken (med name, dose if known, and whether it helped) H) Recovery time (how long until you were back to baseline) I) Work impact (missed hours, left early, called out, reduced productivity, mistakes, accommodations needed) Example 1 (prostrating): “Mon 07 Apr. Start 0915. Pain 8/10 within 20 min. Symptoms: photophobia, nausea, sound sensitivity. Prostrating: YES. Had to stop work, closed office door, lay down in dark room. Could not tolerate screen or conversation. Took sumatriptan at 0940, partial relief by 1130. Total duration 4 hrs. Recovery: felt ‘hungover’ and slow remainder of day. Work impact: missed 3.5 hrs productive time, rescheduled meeting.” Example 2 (non-prostrating but still real): “Thu 10 Apr. Start 1730. Pain 5/10. Symptoms: mild light sensitivity. Prostrating: NO. Able to complete dinner and basic chores but moved slowly and avoided TV. Took ibuprofen 1800, improved to 2/10 by 2000. Total duration 2.5 hrs. No missed work.” Example 3 (prostrating with safety impact): “Sat 12 Apr. Start 1345 while driving. Pain 7/10 with visual aura. Prostrating: YES. Pulled over, called spouse to pick me up. Lay down in dark room 2 hrs. Took prescribed med 1410. Total duration 6 hrs. Recovery: next day fatigue and neck soreness.” Notice the pattern: specific, grounded, and focused on function. Not just pain. That is what turns “I get migraines” into “here is how they disable me.”

Common log entries that quietly weaken credibility (and how to fix them)

Most credibility problems are not fraud problems. They are documentation problems. Here are the entries that commonly backfire, and what to do instead. 1) “Every headache is a 10/10 and prostrating.” Why it hurts: perfect extremes read like exaggeration, even when you are suffering. Also, it conflicts with normal human variability. Fix: separate headache days from migraine days, and separate prostrating from non-prostrating. Real patterns have range. 2) Vague frequency: “Happens all the time.” Why it hurts: the VA rates by frequency over “last several months.” “All the time” cannot be converted to a number. Fix: count it. “12 migraine days this month, 6 prostrating.” 3) Missing duration and recovery time. Why it hurts: a 45 minute episode and a 12 hour episode are not the same functional problem. Recovery matters too. Many migraines have a postdrome that ruins the day. Fix: log both “attack duration” and “back to baseline.” 4) Contradictions inside the same entry. Example: “Prostrating, but I finished my shift, went to the gym, and cleaned the garage.” Why it hurts: it reads like the word “prostrating” is being used as a label, not a description. Fix: write what happened. If you pushed through, say that. If you pushed through but performance collapsed, document that: mistakes, extra breaks, leaving early, unsafe driving, etc. 5) Copy-paste entries that look identical for weeks. Why it hurts: it looks manufactured. Fix: keep the same fields, but write the actual details of that day. Consistent structure is good. Identical narratives are not. 6) Medical conclusions instead of observations. Example: “This migraine is caused by my service-connected condition and meets 50% criteria.” Why it hurts: that is argument, not evidence. Your log should be facts. Let the claim and medical opinion do the arguing. Fix: document observable symptoms and impact. “Could not tolerate light, vomited, needed dark room, missed work.” 7) No link to real-world impact. Why it hurts: the VA is rating occupational and functional impairment. Pain alone is not the whole story. Fix: document what you could not do: driving, screens, lifting, childcare, meetings, cooking, errands, sleep. 8) Only logging after you decide to file. Why it hurts: it can look like a sudden new problem rather than an ongoing one. Fix: start now, keep going, and also pull older corroboration: appointment notes, urgent care visits, medication history, employer leave records, and lay statements. A log is strongest when it matches the rest of the record.

How to use your log in a C&P exam without sabotaging yourself

We follow VA logic step by step. The C&P exam is not treatment. It is documentation for rating. Your log is a tool to keep you precise under pressure. Before the exam, summarize your last 2 to 3 months on one page: - Total headache days per month - Total migraine days per month - Total prostrating migraine attacks per month - Typical duration and typical recovery time - Work impact: days missed, left early, reduced productivity - Current treatments tried and response During the exam: - Answer the question asked, then support it with your log. “In the last 30 days I had 8 migraine attacks. 4 were prostrating. Here are two examples.” - Describe your worst days, not your best day in the exam chair. - Do not minimize and do not exaggerate. If some attacks are not prostrating, say so. That honesty often increases trust. After the exam: - Keep logging. Claims take time, and consistency matters if you need an appeal or an increase later.

One next step: start a 30-day log you can actually maintain

Your next step is simple: start a 30-day headache log today using the template above, and do not change your definitions halfway through. If you already have a log, audit it for the credibility traps listed earlier and tighten it up. If you want a structured place to pull the right language for symptoms and functional impact, use our Conditions Library migraine reference and then match your log fields to what the VA is actually looking for: /conditions. No hype. No shortcuts. No confusion.

  • All VA claims and benefits articles
  • Conditions Library
  • DBQ Library