How to Track a Migraine When You Have Brain Fog

Article ยท 3 min read

Log the migraine when brain fog won't let you read the screen.

Postdrome brain fog hits exactly when logging gets hardest. Voice memos, single-tap capture, and a screen you can actually stand to look at.

The part the tracker was supposed to help with

The pain has finally backed off. You are upright again, technically. But the log screen is a wall of tiny gray text, the medication field wants to know whether the sumatriptan was this morning or last night, and your brain hands back nothing.

This is the after-phase, the 24 to 72 hours the headache leaves behind: the residual photophobia, the neck that still will not turn, the thoughts sitting somewhere behind glass. It is also the stretch of data most worth having. And it is the exact stretch where opening an app, reading a form, and typing a coherent entry is a task your cognition cannot complete.

The fog-tracking paradox

Call it the fog-tracking paradox. The postdrome hours when your data would be most useful are the same hours your cognition can least produce it.

Word-finding trouble. Reading that runs at half speed. The sense that a simple three-step task has too many steps. Cognitive symptoms are a defining feature of the after-phase, sitting right alongside fatigue and light sensitivity. So the standard tracker asks the impossible: navigate three screens, type a symptom, remember a timestamp, spell the drug name, all while the fog is thickest. Most people just do not log it. The record skips the recovery entirely, and the recovery is where the pattern lives.

Why "just log it when it happens" fails here

The advice you get is some version of log it in the moment, log it consistently. That advice was written for a body that can read and type in the moment.

Fog does not respect consistency. It punishes menu depth (every tap is a decision you cannot make), it punishes free-text fields (you cannot find the word for the symptom you are having), and it punishes recall (asking what time did it start of a brain that has lost the last few hours). A logging flow built for a clear head is not a smaller version of a fog-proof one. It is a different thing that happens to look the same on a good day.

What the after-phase actually does to logging

This is not a fringe experience. In a prospective electronic-diary study of migraine attacks, patients reported at least one postdrome symptom after the large majority of attacks, with tiredness and difficulty concentrating among the most common. In plain terms: the cognitive drag is not the exception, it is the rule of the recovery phase.

Which means a tracker that only captures clean, well-typed entries is systematically blind to the fog hours. It records the attacks you felt well enough to log and misses the ones that flattened you. The data skews toward your better days and hides your worst ones, which is the opposite of what you need when you sit down across from a neurologist.

The recovery phase is the rule, not the exception

A prospective electronic-diary study found postdrome symptoms after roughly 81% of migraine attacks, with fatigue and trouble concentrating among the most reported. Source: Giffin et al. 2016, an electronic diary study of the migraine postdrome. A tracker that only captures typed entries misses most of these hours.

The low-cognition logging ladder

You do not need to log well during the fog. You need to log rough now and clean it up later. Match the method to how much brain you have:

  1. Talk, do not type. A ten-second voice memo ("still fogged, light hurts, neck stiff, took the second dose around noon-ish") captures more than you would ever type, and it captures it in your own voice with a real timestamp attached. 2. One tap, no menus. A single capture that just marks I am in postdrome right now beats a perfect entry you never make. Presence first, detail later. 3. Pre-set the answers. Load your usual meds and triggers once, on a good day, so logging becomes tapping a name you recognize instead of spelling one you cannot recall. 4. Turn the screen down. Drop the brightness and switch to high contrast before you try to read anything. If the interface glows, you will close it. 5. Backfill when the fog lifts. Come back a day later and turn the rough marks into real entries while you can still read them. The timestamp is already correct; you are only adding words.
How much fogWhat you can realistically doThe logging method that survives it
Mild, slow but readableRead short text, tap a few timesPre-set med and trigger pickers, one-tap symptom markers
Moderate, words won't comeSpeak, not read or spellVoice memo capture, single presence tap
Heavy, screen hurts to look atAlmost nothingOne-tap marker in a dimmed high-contrast view; backfill later
Match the logging method to the fog, not the other way around.

Aura Mode is a usability requirement, not a feature

Once you accept the fog-tracking paradox, a low-brightness, high-contrast, tap-and-talk capture mode stops being a nice extra. It becomes the only version of logging that works on the days you most need logged.

That is the reasoning behind Aura Mode in Postdrome: a stripped, dimmed, single-tap capture surface for the exact hours when reading a normal screen is not on the table. Voice memos instead of typing. Presence markers instead of forms. Your saved meds and triggers as one-tap options. The full timeline, including the 24-to-72-hour recovery most apps forget, fills in from rough captures you can clean up later. It is built for the head you actually have during postdrome, not the one you have on a clear afternoon.

You do not need to log well during the fog. You need to log rough now and clean it up later.

Open Postdrome, tap once, or talk it out. The timeline fills itself in while your head clears.

Postdrome captures the whole arc, prodrome through the 24-to-72-hour after-phase, on-device, with a one-time price and no subscription. The fog-hour captures are the ones it was built to catch.