The migraine tracker breaks when the headache never comes

The attack starts and there's nothing to press

The room starts to tilt while you're loading the dishwasher. Not spinning exactly, more like the floor decided to become a boat. Your eyes can't settle. There's the pull of nausea, the low static of brain fog rolling in, that familiar sensitivity to the overhead light. And no headache. Not a whisper of one.

So you open the tracker you've been keeping for your neurologist, the one you've been diligent about for months. The first field wants a headache intensity, 1 to 10. The start-time picker is labeled "when did the pain begin." You sit there, mid-attack, unable to focus your eyes, being asked to timestamp a pain that isn't happening. You either fake a number or you close the app. Most days you close the app.

The pain-onset anchor

Here's the thing almost nobody names: every migraine tracker built, ours included, was architected around a single assumption. Headache onset is the anchor. It's the canonical event, the timestamp that everything else hangs off. Aura logs relative to it. Medication timing logs relative to it. Postdrome, the after-phase, gets measured as hours-since-headache. The whole timeline is a clothesline, and the headache is the pole holding it up.

Call it the pain-onset anchor. It works beautifully for classic migraine with head pain. And it's a quiet structural failure for the meaningful slice of vestibular migraine patients whose attacks don't reliably produce a headache at all. The pole was never planted. Everything on the line is on the floor.

This isn't a symptom problem, it's a data-model problem

The usual correction you'll read is "vestibular migraine is more than dizziness." True, and beside the point. You already know that. You're the one living the vertigo, the disequilibrium, the visual dependence in the cereal aisle.

The failure sits one layer down, in the schema. A tracker that asks for headache intensity as the entry point isn't just missing a symptom field. It's declaring what counts as an event. When the app's definition of "an attack happened" requires head pain, a headache-absent episode doesn't get logged late or logged wrong. It structurally doesn't exist. Multiply that by months and the neurologist opens a record with suspicious gaps, right where your worst weeks were.

What the record actually costs

The community has been saying this out loud for a while. Across r/migraine and r/VestibularMigraines, the recurring plea isn't "what is VM," it's "how do I even log this when there's no headache to time it to." VEDA and the vestibular-ENT literature keep flagging the same diagnostic bottleneck: attacks that present as vertigo without pain get routed to inner-ear workups, not neurology, for years.

A documented case report puts a number on that detour. One headache-absent vestibular migraine patient went roughly a decade misdiagnosed before landing the right label. A tracking record that can't hold the episode is part of how a delay like that survives contact with a specialist.

Anchor to what actually fired first

So walk the alternative. The attack still has a first event, it's just not pain. For most headache-absent episodes it's one of three: vertigo onset (the room moves), a prodrome symptom (the fog, the yawning, the neck stiffness that shows up before everything), or disequilibrium onset (the unsteady, walking-on-a-trampoline drift that builds slower).

You pick whichever fired first and you make that your zero. That's your anchor. Aura, nausea, photophobia, the medication you took, the postdrome that drags on for two more days, all of it logs as relative-to-vertigo-onset instead of relative-to-a-headache-that-never-came. The timeline reads. Below, the same attack in a pain-anchored app versus one that lets you set a non-pain anchor.

What the neurologist can finally see

Change the anchor and the record stops lying by omission. Your specialist opens a timeline where the headache-free weeks are present, timed, and shaped like attacks, not blank stretches that read as "patient stopped tracking." Frequency counts are honest. The relationship between prodrome and vertigo is visible. Medication response is measurable against a real onset instead of a fictional one.

And the postdrome, which is the whole reason a lot of you started tracking, finally has something true to measure from. When the after-phase outlasts an attack that never had a headache, hours-since-vertigo is a number that means something. Hours-since-a-pain-that-didn't-happen is not.

A blank week in the log doesn't say "no attack." It says "the app couldn't hold the one you had."

Where Postdrome sits on this

We'll be straight about it: the pain-onset anchor was our assumption too, at the start. Building Postdrome for the after-phase meant building for the subset the after-phase hits hardest, and a chunk of that subset doesn't get a headache to hang the day on. So the anchor became something you set, not something we assume. Vertigo onset, a prodrome symptom, disequilibrium, or headache when there is one. Aura Mode exists because timestamping an event while your eyes won't hold still is its own problem, separate from the pain that isn't there.

That's the difference between a tracker that records what you actually experienced and one that records what its schema expected you to. For a headache-absent episode, only one of those hands your neurologist a usable timeline.

What we're still working out

The open question isn't whether a non-pain anchor reads better, it does. It's how to make picking the right anchor mid-attack effortless when your vision's gone and the nausea's up, so the log gets captured in the moment instead of reconstructed from memory two foggy days later. That's the next thing we're building against, and the thing we most want to hear from headache-absent patients about.