Over, but not down
The meeting's done. The call ended an hour ago. The hard thing is, by any reasonable measure, finished. And you're still humming. Still a little alert, a little fast, slow to settle, as if some part of you didn't get the memo that the threat has passed.
You could explain the whole episode calmly to someone right now. Even-toned, balanced, done. Which makes the leftover buzz confusing, because surely if you can talk about it that steadily, you've landed. You haven't. Talking about it and landing from it are two different things.
No all-clear was ever sent
The trigger ended; the processing didn't. Your system came up to meet a demand and then stayed up, still switched on well after, because nothing told it to stand down. The body doesn't take the end of the calendar event as the end of the threat. It waits for its own signal, and that signal often never comes.
So you sit at baseline-plus, humming along, and the explaining you can do so calmly turns out to be a head thing that the body didn't get copied on. Being able to narrate it isn't the same as having come down from it. The mind closed the file. The system kept the engine running.
Carrying the last one into the next
The real cost is in the stacking. You carry the last thing into the next thing, never quite back at baseline when the next demand arrives, so each one starts you a little higher than the one before. The buzz compounds. By evening you're activated by a day's worth of things that were each, individually, fine.
This is how a manageable day leaves you wrung out. Not one big stressor, but a string of small ones, none of which got a clean ending, all of them still half-running in the background.
What helps, what backfires
What helps is a clear closing ritual, something small and deliberate that tells the body an ending happened. Shut the laptop and say that's done. A short walk to mark the line. A few breaths, a change of room, anything that functions as a signal rather than just a thought. Endings need a closing gesture your body can actually read.
What backfires is assuming it's solved just because it can be explained. That's the specific trap of this pattern, mistaking a clear account for a settled system, and then loading the next thing on top while you're still up from the last.
What to watch
Track how long it takes to return to baseline after something ends. Not whether you can describe it, you can, that's not the question, but how long the humming runs once the trigger's gone. That return time is the real readout, and it's the thing a closing ritual is meant to shorten.
Give endings a closing ritual, so your body knows they ended. The mind hears the words. The body needs the gesture.