Your tracker asks the most the moment you can give the least.
The postdrome hours are when logging matters most and when your brain can least do it. A field guide to capturing an attack you can barely see.
Four hours past the worst of it, and the number won't come
The form wants a number from zero to ten. You're maybe four hours past the worst of it, the light through the blinds still lands like a needle behind one eye, and the number will not come. Seven? Five? The scale means nothing right now. So you put the phone down. You'll log it later, once your head clears. It doesn't clear for two days, and by the time it does, the shape of the attack is already gone.
The capacity-demand inversion
Every tracker we've tested asks for its most detailed input at the exact hour your brain can supply the least of it. Peak symptom load sits right on top of minimum data-entry capacity, and the form was built for neither. We call it the capacity-demand inversion, and once you see it you can't unsee it. The zero-to-ten slider, the twelve-field trigger list, the duration picker: all of it presumes a clear head. You don't have one. That's the whole reason you're logging.
The 'log every day' advice quietly assumes a working brain
Most tracking guidance comes down to one instruction: log every day without fail, and the pattern reveals itself. Fine in theory. But that advice treats the good days and the wrecked days as interchangeable, and they are not. The days you most need in your data are precisely the days you're least equipped to enter it. So the record skews. Your clean, well-logged entries are the mild days and the recovered days, and your severe attacks show up as gaps or as guesses typed in 48 hours later. A dataset built that way doesn't just have holes. It's biased toward the days that mattered least.
What the after-phase actually looks like when you try to log through it
Spend an evening in r/migraine or r/VestibularMigraines and the same admission surfaces over and over: people abandon their tracker during the postdrome stretch, then feel guilty for the gap. Residual photophobia, the neck stiffness that lingers, the flat mood, the fog that makes a paragraph slide off the page. These are the symptoms most worth a timestamp, and they're the first ones people drop, because reading a form is itself a trigger. The fix isn't more discipline. It's lowering the cost of a single capture until it fits inside what a fogged brain can actually do. There's a rough hierarchy to that, and it's worth knowing before your next attack, not during it.
Capture method
Effort in the moment
What survives to the timeline
One-tap symptom marker
Lowest
Timestamp plus a single symptom flag
Ten-second voice note to yourself
Low
Real detail, but it needs transcribing later
Photo of the room or your meds
Low
Context you'd forget: light level, the dose you took
Full structured form (0-10, triggers, duration)
Highest
Rich data, only if you can finish it
Next-day retroactive entry
Deferred
A rough shape, with the precision already lost
Capture methods ranked by cognitive cost in the moment. The lower the effort, the more likely the attack gets recorded at all.
One tap now, the details when you surface
Picture the next bad one. The aura starts, or the pain spikes, and instead of opening a form you hit a single marker: attack, now, timestamped. That's it. Two hours later, still flattened but able to speak, you leave a ten-second voice note: took the second dose, light still bad, neck tight. The next morning, head half-clear, you open the entry and it's already anchored in time with two breadcrumbs waiting. You add what you remember and leave blank what you don't. What you never do is sit down cold two days later and invent a number. The attack got recorded as it happened, in the currency your brain had at the time.
Coarse, honest data beats precise, invented data
Change one belief and the whole practice gets easier: a rough entry made in the moment is worth more than a detailed one reconstructed after the fact. Clinicians don't need your pain graphed to the decimal. They need frequency, duration, what you took and when, and whether the after-phase is stretching longer over time. All of that survives low-effort capture. None of it survives a two-day gap filled with guesses. So stop treating a blank field as failure. A gap you didn't fabricate is clean data. A confident wrong seven is noise you'll be reading back to your neurologist a year from now.
Don't backfill a number you don't have
If you can't remember whether the pain was a 6 or an 8, log 'moderate to severe' or leave it blank. A confident wrong number distorts the trend more than a gap does, and it's the trend your clinician reads.
A gap in the data is honest. A guessed number is noise.
Why we built the capture to survive your worst hour
This is the constraint Postdrome was designed around, not bolted onto. Aura Mode strips the interface down to what a light-sensitive, fogged brain can operate: high contrast, minimal fields, one-tap capture that timestamps the moment and lets you fill in the rest whenever you resurface. The timeline doesn't stop when the headache does. It keeps running through the 24 to 72 hours after, so the fatigue, the residual photophobia, and the mood dip land on the same continuous record as the attack itself. Everything stays on your device. There's no subscription and no per-insight paywall: you pay once, and the data is yours to export whenever you want it.
What we're working on next
The open problem we keep circling is voice. Talking is often the last input channel still working when reading and typing have failed, and a clean way to drop a spoken note straight onto the timeline, transcribed later, would close most of the remaining gap. That's the next piece we're building toward.
Try the one-tap capture and the after-phase timeline for yourself. Pay once, keep your data on your device, and export it anytime.
We built Postdrome after watching the people we love give up on trackers that quit at the headache and demanded the most exactly when they could give the least. The after-phase is the point here, not an afterthought, and the capture is built to hold up when reading a form is itself a trigger.