Your headache diary answers the wrong question at the neurology appointment

The question the export can't answer

Fifteen minutes into the appointment, the neurologist looks up and asks how long the postdrome usually runs. Two days? Three? Is it worse after the attacks you treat late?

You have four years of data on your phone. You open the export anyway, already knowing what's in it, and there it is: a date, a pain score, a checkbox for nausea, a timestamp labeled headache resolved. Nothing after that timestamp. The app's model of the attack ended when the pain did, so the file has no field where the answer could live.

So you estimate out loud. The neurologist writes down what you said, and now that estimate is the clinical record: patient reports postdrome lasting roughly one to two days. Four years of diligent tracking produced a guess.

The false floor

Bring a headache diary is the most repeated instruction in migraine care. American Migraine Foundation guidance says it. Practice handouts say it. It's the standing reply in r/migraine whenever someone posts about a first specialist appointment, and as far as it goes, it's good advice.

The false floor is what happens after you follow it. You bring the diary. The instruction has been satisfied, visibly, in the room, and the presence of a diary reads as preparedness to everyone including you. Nobody audits whether the file contains the variables the clinician is about to query. So the gap never gets named as a gap. It surfaces instead as a scatter of small verbal estimates across a twenty-minute appointment, each one entering the chart with the same weight as the tracked data sitting next to it.

Diaries were built for a question you already answered

Headache diaries were designed to establish frequency. How many days a month, how severe, does the pattern hold across three months. That's a diagnostic question, and by the time someone is sitting in a headache specialist's office it's largely settled. The referral itself answered it.

The questions in that room are different in kind. They're about sequence and response. When in the attack did you treat. What happened after the pain went. How long does the aura last, and does it always come first. Every one of those is a question about the shape of an attack over time.

And most trackers model an attack as a single row carrying a severity value, because that's the shape a pain scale takes. Everything that isn't pain becomes a tag hanging off the row, and the row closes when the pain does. The schema is pain-primary. Once it is, no amount of careful logging yields phase-level data, because there is nowhere to put it.

The three variables a specialist actually queries

Three variables carry most of the weight in that appointment, and pain-primary exports drop all three.

Postdrome duration and character. How long the impairment ran past the pain, and what it consisted of. This is the number that turns fifteen headache days into a considerably larger count of impaired days, and impaired-day counts are what functional-impairment documentation runs on.

Medication timing relative to onset. Prior-authorization criteria for CGRP monoclonals typically require documented monthly migraine day counts plus dated trials of prior preventives Blue Cross Blue Shield Mississippi medical policy requires prior authorization for CGRP monoclonal antibodies when patients have more than four migraine days per month ([source](https://www.bcbsms.com/policy-search/medical/policy-detail/monoclonal-antibody-therapies-for-migraine-prevention)). The prescribing conversation needs more than the count, though. A triptan taken forty minutes into an attack and a triptan taken four hours in are two different data points about the same drug, and only one of them supports a fair conclusion about whether it works.

Aura type and duration. A checkbox marked aura tells a neurologist very little. Visual versus sensory versus speech, gradual spread or abrupt onset, five minutes or fifty: those distinctions are diagnostic, and they bear directly on which acute options are appropriate.

What it looks like when the file answers back

Take a plausible case, numbers invented for illustration. Eighteen headache days last month, a triptan on eleven of them, two preventives tried and stopped. A pain-primary export hands the neurologist those three facts and then stops talking.

A phase-aware export hands over the same three facts plus the shape underneath them. Eleven triptan days. Median time from onset to dose of two hours and ten minutes. The four attacks treated inside the first hour ran a postdrome of under twelve hours; the seven treated later ran past a day.

That's a testable read sitting on the table: the drug may be fine and the timing may be the failure. It's a different appointment. It might produce a rescue-plan change before it produces a prescribing change, and either way the eventual preventive request arrives with a documented history behind it instead of an assertion.

The prep happened in March

None of this is reconstructable. You can't go back and add onset-to-dose times to attacks you logged as dates. You can't recover how long June's postdrome ran from a file that closed the entry the moment the pain stopped. The prep that matters isn't the night before the appointment. It happened in March, when the schema either had those fields or it didn't.

Which makes appointment preparation a data-structure decision taken months upstream, and makes the choice of tracker something closer to a clinical decision than a preference about interface. That framing is uncomfortable on purpose. It means a tracker someone has been filling in faithfully for two years may have been quietly guaranteeing a thin export the entire time. Better to learn that now than in the chair.

Building the export backwards from the question

We built Postdrome around the after-phase because that's the part the schema kept dropping. The timeline doesn't close when the pain resolves. Fatigue, brain fog, residual photophobia, neck stiffness, mood: each carries its own start and end, so postdrome duration is a measured value in the export rather than a recollection produced under pressure in an exam room. Medication entries record clock time, so onset-to-dose falls out of the data instead of being estimated. Aura logs carry type and duration, not a checkbox.

The export is a file you own, held on a device you control, and the price is paid once. A document your neurologist reads shouldn't sit behind a renewal.

What we're watching next is payer policy language. If functional-impairment documentation starts carrying real weight in appeal outcomes, postdrome duration stops being a clinical courtesy and becomes the variable the whole export exists to produce.