EMF sensitivity symptom diary template: how to build one that actually holds up
Most symptom diaries fall apart within a week. Not because people are lazy, but because the template asks the wrong things. A blank column labeled "trigger" tells you nothing when your headache starts at 14:20 and the only thing that changed was a neighbor's Wi-Fi router powering back on after a two-hour outage.
If you're trying to track what you suspect is electromagnetic hypersensitivity (EHS), a generic chronic-illness tracker won't cut it. You need a structure that captures exposure source, estimated intensity, distance, and the lag between exposure and symptoms. That last part is where almost every free template I've seen fails.
Below is a practical EMF sensitivity symptom diary template you can copy into a spreadsheet or print, plus the methodology that makes the data worth showing to a doctor.
Key Takeaways
- A usable EMF diary needs five core columns: timestamp, symptom, severity, suspected source, and estimated distance/intensity.
- Log exposure events before symptoms appear, not after—this is what lets you test correlation.
- Record the lag time between exposure and onset. It's often minutes, sometimes hours, and it's the single most useful pattern in the whole log.
- EHS is not recognized as a medical diagnosis by the WHO or most national health authorities. The diary is a documentation tool, not a diagnostic one.
- Simple blind testing—someone else toggling a device while you don't know the state—turns a diary into actual evidence.
- Paper works fine. A spreadsheet is better only because sorting by source is instant.
Why generic symptom trackers miss the point
Symptom tracking templates are everywhere. Printable PDFs, Excel sheets, Notion dashboards. They're built for migraines, IBS, fibromyalgia, mental health flare-ups. They assume your trigger is something you did—ate, drank, stressed about.
EMF exposure isn't like that. It's ambient. It's on when you're asleep. It comes through walls from equipment you don't own.
The column that changes everything
A standard tracker has a "trigger" field. That's too vague here. You need your trigger field to specify source type (Wi-Fi router, mobile mast, power line, smart meter, household appliance, phone in pocket), estimated distance, and if you have a meter, a rough reading in µT (microtesla) for magnetic fields or V/m (volts per meter) for electric fields.
Here's what I mean. "Headache, 6/10, 2pm" is useless. "Headache, 6/10, started 12 minutes after sitting 1m from active router, ~0.4 µT reading, resolved 40 min after moving to far room" is a data point.
The catch? You probably don't have a meter yet. That's fine—start with distance estimates in plain language ("same room," "adjacent room," "2m"). Add instrument readings later once you know what you're measuring.
The core template structure
Here's the layout I'd hand to someone starting today. Twelve columns sounds like a lot. You'll use six of them constantly and the rest maybe twice a week.
| Column | What to enter | Example |
|---|---|---|
| Date & Time | When the symptom started, not when you noticed it | 2026-03-14, 14:08 |
| Symptom | Plain description, your own words | Pressure behind left eye, tinnitus rising |
| Severity | 0–10 scale, define anchors once and stick to them | 6/10 |
| Suspected source | What was active nearby | Neighbor's Wi-Fi (2.4 GHz), phone on desk |
| Distance / intensity | Meters if known, meter reading if available | ~1.5 m, no meter |
| Duration | Minutes from onset to resolution | ~45 min |
| Lag time | Time between exposure start and symptom start | ~12 min |
| Exposure event log | Anything that switched on/off nearby | Router rebooted at 13:55 after outage |
| Sleep quality (prior night) | Hours + subjective rating | 6h, poor |
| Other variables | Caffeine, stress, weather, menstrual cycle | 2 coffees, deadline stress |
| Confounder check | Could something else explain it? | Possible—skipped lunch |
| Notes | Anything that doesn't fit a column | Tinnitus faded first, eye pressure last |
Your severity scale has to be yours
Anchors matter more than the numbers. A 6 means nothing across two people. Define it once, in writing, and never shift it. Mine looked like: 1 = barely detectable, 4 = distracting but functional, 7 = had to stop what I was doing, 10 = couldn't think or speak clearly. That definition stayed fixed for eleven weeks. When you change the scale mid-log, you've thrown away the dataset.
Logging exposure and symptoms in the right order
Here's the mistake almost everyone makes. They log the symptom, then try to remember what was happening beforehand.
Reverse it.
Log exposure events as they happen—a router powering on, sitting next to a running microwave, a train ride under high-voltage lines. Timestamp each one. Then, when symptoms appear, you're comparing against a record you already have, not a memory you're reconstructing under discomfort.
The lag time question nobody addresses
Delayed onset is the most under-documented aspect. Symptoms don't always arrive with the exposure. In a stretch of my own logging, roughly a third of entries showed a 10–30 minute gap between a source switching on and the first symptom. Another cluster showed almost immediate onset within two minutes.
If you only log symptoms, you'll never see this. The lag column is the whole point.
Cumulative load over 24 hours
Add one running tally at the bottom of each day: total exposure minutes and total symptom minutes. Some people find their threshold isn't about any single source but about how much accumulated across the day. A 40-minute train ride at 8am might not trigger anything. The same ride at 6pm, after a full day of indoor Wi-Fi, might.
How to run a simple blind provocation test
The honest problem with self-reported diaries is expectation bias. You know the router is on. You expect a headache. The headache arrives. Was it the router or the expectation?
A basic single-blind test cuts through this without needing lab equipment.
- Ask someone you trust to control a specific device—a router, a cordless phone base, an LED lamp.
- They randomly turn it on or off during set blocks (say, 20-minute windows), writing down the true state.
- You log symptoms without knowing the device state.
- Compare at the end of the week.
It's not perfect. You might hear a router's fan or see a status LED. But even this crude version surfaces patterns that raw self-logging can't. In my own rough version—a friend toggling a router behind a closed door—the correlation was weaker than I expected. Honest result. That's the value of doing it.
Paper PDF, spreadsheet, or Notion?
All three work. Each has a cost.
- Printable PDF: fastest to start, zero friction, but no sorting. Best for the first two weeks when you're building the habit.
- Spreadsheet (Excel, Google Sheets, LibreOffice): the only format where you can sort by source, average lag times, and graph exposure minutes against symptom minutes. Once you have 200 entries, this becomes the format that saves you hours.
- Notion or a similar app: good if you want photo attachments (rashes, meter displays) and mobile entry. The trap is spending three evenings designing the dashboard instead of logging.
Start on paper, then migrate
Seriously. Print a two-week grid. Fill it by hand. If the habit sticks—and for most people it doesn't, which is worth knowing early—copy the data into a spreadsheet and structure it properly from there. Don't let the tool become the project.
Medical context: what this diary is and isn't
EHS is not recognized as a diagnosis by the WHO or by most national health agencies. That's the factual starting point, and skipping past it doesn't help anyone. This doesn't mean your symptoms aren't real—it means the mechanism isn't medically established, and no clinician can hand you a diagnosis code for it.
So what is the diary for? Two things.
First, it rules things out. Constant headaches, tinnitus, sleep disruption, tingling, skin redness—these have long differential lists. A detailed log gives a physician something concrete to work against when ordering tests.
Second, it gives you structure for your own decisions. You may not get a diagnosis, but you can still learn which environments make things worse and adjust accordingly.
A diary that shows patterns is worth ten that shows complaints. If you're going to hand it to a doctor, print a two-page summary—frequency by symptom, most common sources, average lag time—not the raw 60 pages.
The template is just a grid. What makes it useful is that you filled it in before you knew what you'd find.
