POTS and Activity Crashes: What to Record After Post-Exertional Symptoms

You did the grocery run on Tuesday. One store, twenty minutes, one flight of stairs with the bags. Nothing that should have mattered. By Wednesday afternoon you were flat on the couch, heart pounding for no reason, and Thursday you still hadn't caught up. When your doctor asked what changed before you crashed, the honest answer was nothing — and that is exactly the problem you cannot explain from memory alone.

If you have POTS and keep noticing a delayed crash after ordinary activity, the fields worth logging are what the activity actually was, your heart rate around it if you track that, how you felt at the time, and — separately — when the crash started, what it felt like, and how long it took to pass. Two short logs, one for the activity day and one for the days after, are what turn a vague pattern into something you can show a doctor.

This article is for educational and organizational purposes only. It is not medical advice.

The Push-Crash Pattern in POTS

People with POTS often describe the same shape: an activity that looks and feels manageable in the moment, followed by a drop that arrives hours later or the next day. It does not always look connected. The grocery run was not extreme, so the crash gets attributed to somewhere else — a bad night's sleep, a bug going around, stress at work. Without a written record, there is no way to actually test that assumption.

This delayed-crash shape is sometimes called post-exertional symptom worsening. People with ME/CFS and long COVID describe something similar under the name post-exertional malaise, and many people with POTS report a version of it too — activity that feels fine while it is happening, followed by a decline that lands later rather than during the activity itself.

Why the Delay Makes This Hard to Describe

Ask someone with POTS what triggered a bad week and most people start with the day they felt worst — not the day before, when the actual activity happened. Memory naturally centers on symptoms, not on the ordinary errand two days earlier that did not feel like anything at the time.

This is not something you can fix by trying to remember harder. It is a timing problem. The information that would show the pattern needs to be written down close to when it happens, on both ends — the activity day itself, and the days that follow it.

What to Record on Activity Days

You do not need a detailed log. A short note taken close to the activity captures far more than trying to reconstruct it two days later.

• What the activity was. Type, rough duration, and whether it involved standing or being upright for an extended stretch.
• Heart rate, if you track it. Resting beforehand, and during or right after the activity if you have a way to check.
• How you felt at the time. Dizziness, chest tightness, shakiness, or nothing unusual at all — "felt fine" is still a useful entry.
• Hydration and salt intake that day. Whether you kept up your usual routine or fell behind on it.
• Sleep the night before. Hours and rough quality, since a poor night can lower how much buffer you have before you even start.

What to Record in the Days After

The crash window is where the pattern actually becomes visible, but it is also when you feel least like writing anything down. Keep this part short on purpose.

• When symptoms started. Same day, next morning, or two days later — the timing itself is the pattern you are trying to catch.
• What the crash felt like. Fatigue that sleep did not fix, a heart rate that felt elevated at rest, brain fog, or being unable to stand as long as usual.
• How long it lasted before you felt back to your baseline. A day, a few days, more than a week.
• What you could and could not do. Concrete tasks — showering, cooking, sitting upright for an hour — compare more cleanly across crashes than a general "bad day" rating.

Reading the Pattern Across Several Crashes

One crash tells you very little. Three or four logged the same way start to show something — maybe the delay is consistently around a day, maybe stairs specifically show up every time, maybe hydration the day before measurably changes how bad the crash gets.

This is where a short, consistent log across several weeks does more than a detailed log of a single day. Consistency in what you record matters more than depth.

Keeping the Log Manageable

A log you abandon after four days is not useful. The version that actually works is usually the shortest one — a few fields per activity day, a few fields per crash day, filled in while you remember rather than reconstructed later from a hazy sense of "this week was rough."

A structured daily log helps more than a blank page here, because the same fields show up every time. You are not deciding what to write from scratch on a day when deciding anything already feels hard.

What This Looks Like at an Appointment

A logged pattern changes the conversation. Instead of "I get tired sometimes," you can point to three specific instances: activity on a Tuesday, a crash starting around 24 hours later, lasting two to three days each time. There is a separate piece on why POTS is so often misdiagnosed that covers how vague symptom descriptions contribute to that delay — a dated, specific log is one of the more direct ways to work against it.

If you already keep notes before appointments, the same structure used in how to track POTS symptoms before your next doctor appointment pairs well with an activity-crash log — one covers your daily baseline, the other covers what happens around specific activities.

Some people also find it useful to separate cognitive crash symptoms from physical ones, since brain fog after activity does not always follow the same timeline as fatigue or heart rate. The POTS and brain fog tracking guide covers that side in more detail if cognitive symptoms are part of what crashes for you.

Written by Yonatan Gabriel, MBBS. CareLog creates condition-specific health tracking templates for Google Sheets and Excel. Last updated: July 2026.