You wake up with a headache that wasn't there when you went to bed. By 10 a.m. it's gone. By 3 p.m., after two hours in a café with strong Wi-Fi and a table full of phones, your ears are ringing and your chest feels tight. Was it the coffee? The noise? The router two meters from your head?
You don't know. And that's the actual problem with electrosensitivity—the symptoms show up with a delay that makes the cause nearly invisible. A useful electrosensitivity symptom tracking journal template isn't the same thing as a generic pain diary. It has to capture exposure, not just feeling. Source type. Distance. Duration. Shielding. Time of onset. Time symptoms faded.
Most of the free templates floating around don't do any of that. I've downloaded maybe twenty of them. Here's what I built instead, and why the standard columns kept failing me.
Key Takeaways
- A generic symptom tracker records what you felt. An EHS journal records what you were exposed to, and when.
- You need at least three exposure columns: source type (low-frequency vs radiofrequency), distance in meters, and duration in minutes.
- Log symptoms twice a day minimum—once at exposure, once 2–6 hours later. The latency window is where the pattern hides.
- Shielding and device-off periods belong in the log too. Otherwise you can't tell whether a bad day was exposure or something else entirely.
- A spreadsheet beats paper for spotting correlation. But paper beats a spreadsheet you never open.
Before the columns, though, there's a question worth answering honestly.
Why a generic symptom tracker fails for EHS
Chronic illness trackers are built around a simple assumption: the trigger and the symptom are close in time. You eat something, your gut reacts within the hour. You take a medication, side effects show up. The journal just needs to record both.
Electrosensitivity doesn't work that way. Symptoms attributed to electromagnetic fields—headaches, tinnitus, insomnia, heart palpitations, skin sensations, brain fog—can appear minutes after exposure, or hours later, or the following morning. And the exposure itself is often invisible. You don't notice the neighbor's router through the wall. You don't notice the low-frequency hum from the building's wiring until you've been sitting in it for forty minutes.
The latency problem
This is the single biggest gap in every printable symptom tracker I've tested. None of them ask when the exposure started relative to when the symptom started. Without that gap, you can't tell whether your 4 p.m. headache came from the morning train ride or the afternoon video call.
In my own log, I started measuring the delay. Headaches appeared between 20 minutes and 4 hours after I marked "high-RF environment." Once I had that window, I stopped blaming the wrong things.
What the standard columns miss
Go download a chronic illness symptom tracker PDF—any of them. You'll find date, symptom, severity 1–5, mood, sleep, notes. Fine for a rheumatology diary. Useless for this. What's missing:
- Source type (power lines and appliances vs Wi-Fi, cell towers, phones)
- Distance to the nearest known emitter
- Duration of exposure
- Whether shielding or airplane mode was active
- Onset time and resolution time, separately
That's five columns a general tracker won't give you. You have to add them yourself.
The columns your journal actually needs
Here's the structure I landed on after a year of tinkering. I'm not going to pretend it's perfect—I rebuilt it three times because the first two versions were too complicated to fill in on a bad day.
Exposure log (fill in when you notice, or at fixed checkpoints)
This side of the sheet is about the environment, not you.
| Column | What to record | Example |
|---|---|---|
| Time | Clock time you entered or noticed the environment | 14:20 |
| Location | Where, specifically | Office, 3rd floor, near server room |
| Source type | Low-frequency (wiring, appliances, transport) or RF (Wi-Fi, phones, masts) | RF |
| Estimated distance | Rough distance to nearest known emitter, in meters | ~2 m to router |
| Duration | Minutes spent in that environment | 95 min |
| Mitigation | Shielding, airplane mode, moved seats, nothing | Airplane mode on phone |
Symptom log (fill in at onset, not later)
This is the part people skip, and it's the part that makes the whole journal worth keeping. Record symptoms as they appear, even if you only scribble two words.
- Symptom name — keep a fixed vocabulary. "Headache," "tinnitus," "palpitations," "brain fog," "skin tingling." Don't invent new labels every day or you'll never see a pattern.
- Severity 0–10 — 0–5 is too coarse. I moved to a 10-point scale after realizing half my days were being flattened into "3."
- Body location — left temple, both ears, chest, forearms. Location matters more than people expect.
- Onset time — the exact minute you noticed it.
- Resolution time — when it faded, and how (moved rooms, went outside, sat in the car).
Two sentences of notes beat a paragraph of prose. Write "left temple, sharp, faded 30 min after leaving building" and move on.
Paper, PDF, or spreadsheet?
Honest answer: it depends on how bad your worst days are. On a good day I can type into a Google Sheet. On a bad day I can barely look at a screen, which is a problem when the screen itself might be part of what's making it a bad day.
That's not a hypothetical. That's why I keep both.
When paper wins
A printed A5 sheet and a pen by the bed. No screen, no battery, no backlight. If your symptoms flare around screens, this is the only format that doesn't contaminate your own log. I print a week at a time and keep them clipped to a folder.
When a spreadsheet wins
For finding patterns, nothing beats a spreadsheet. Sort by source type, filter by duration above 60 minutes, and count headache days. I ran that filter across four months and found something I'd completely missed: my worst symptom clusters lined up with evening exposure windows, not morning ones. I'd been assuming the opposite.
You can do this in Google Sheets with nothing more than the free FILTER and COUNTIF functions. No paid tools, no plugins.
A quick comparison
| Format | Best for | Weakness |
|---|---|---|
| Printable PDF (A5) | Flare days, screen-avoidance, bedside use | Manual analysis; you have to tally by hand |
| Excel / Google Sheets | Sorting, filtering, finding delayed patterns | Requires screen time; sync can expose you to the same triggers |
| Fillable PDF | Laptop-friendly, keeps fixed columns | Still a screen; awkward to fill on a phone |
| Notes app on phone | Quick capture when you're out | The phone is often the emitter—bad idea mid-exposure |
That last row is the one people don't think about. If you're logging a suspected phone-related symptom, don't log it on the phone. It seems obvious written down. It took me embarrassingly long to realize it in practice.
How to actually use it without burning out
A journal you abandon after nine days tells you nothing. Here's what kept mine alive.
- Log at fixed checkpoints. Morning, after lunch, evening. Three entries a day, minimum. Trying to log "whenever" fails within a week.
- Capture the environment even on good days. If you only record exposure when you feel bad, you have no baseline. The good days are data too.
- Wait before drawing conclusions. Two weeks of entries is noise. Six to eight weeks is where patterns start showing up reliably.
- Bring it to your doctor, but read it first. Clinicians respond to a summary, not a stack of raw sheets. Highlight the three worst days and what preceded them.
On that last point—and this needs saying clearly—a symptom journal is not a diagnosis. Electrosensitivity is not recognized as a distinct medical condition by major health bodies, and self-tracking won't change that. What a well-kept journal can do is give you and your doctor something concrete to work with: a record of when symptoms occur, what surrounds them, and what doesn't correlate at all. That's real value, and it's honest about what the tool can and can't prove.
I've had entries that pointed clearly at something—and entries that pointed nowhere. Both were useful. The ones that pointed nowhere saved me from chasing a trigger that wasn't there.
Should I track mood, sleep, and diet too?
Yes, but keep them at the edge of the sheet, not the center. Sleep hours and caffeine intake can absolutely affect the same symptoms you're attributing to fields. Track them lightly—one column each—so you can rule them out rather than accidentally rule them in.
How long before the journal shows anything useful?
Roughly six weeks of consistent entries. Shorter than that, you're mostly looking at ordinary day-to-day variation. I noticed my first clear pattern around week seven.
What if my symptoms never correlate with exposure?
Then that's a finding, and a genuinely informative one. It tells you to look elsewhere—sleep, stress, diet, an underlying condition worth investigating with a clinician. A negative result from an honest journal is not a failure. It's direction.
The template matters less than the habit of writing down two things you'd otherwise forget: what you were exposed to, and when the symptom started. Everything else is detail. Get those two columns right and the rest of the journal builds itself around them.
And if you take nothing else from this: start with three columns. A date, an exposure, a symptom. Add complexity only after the simple version stops being enough.