Field notes: the week the revetments filled up and nobody said why

There's a particular kind of week every airbase watcher knows and dreads a little. Nothing's on the NOTAM board. No exercise serial's been announced. Twitter's quiet, the aviation forums are quiet, and then you pull the latest tile on a dispersal field you check out of habit more than expectation, and half the revetments that were empty on Tuesday have airframes tucked into them by Friday.
No press release. No open-source chatter to pin it to. Just hardstands filling up in a pattern that looks deliberate, because dispersal always looks deliberate, and a nagging sense that you're the only one who noticed, because you probably are.
I had one of these weeks recently on a field I keep half an eye on, the kind of secondary dispersal site that never makes anyone's top ten watchlist until it does something. The baseline was six aircraft on the apron, a couple more rotating through the revetment line on any given pass, nothing worth a note. Then over about five days the revetment count crept from four occupied to eleven, apron count dropped by half, and a stretch of hardstand that had been bare dirt in the spring imagery had what looked like fresh grading work going on at the edge of frame.
None of that proves anything on its own. Revetments fill and empty for reasons that have nothing to do with anything an analyst cares about: a rotation, a maintenance push, weather routing from a field two hundred kilometers away having a bad week. What's missing is a baseline, what that field normally looks like on that specific week of the year, not just what it looked like the day before yesterday if you happened to pull that tile, and what it looks like today.
That gap between "today" and "the last time I happened to look" is where most of the interesting movement gets lost. Not because the imagery isn't there. It usually is, sitting in an archive, waiting for someone to go back and page through it tile by tile to reconstruct a timeline that should have been obvious in real time. By the time you've done that reconstruction, the window where the answer mattered has usually closed.
What I ended up doing that week was the thing everyone does: build a crude personal log, screenshot by screenshot, timestamp by timestamp, trying to get the apron count and the revetment count into some kind of running tally I could compare against itself. It's slow, it's manual, and it's the kind of task that makes you resent the archive even as you're grateful it exists. A proper daily count, type by type, on apron and in the revetments, with the construction creeping in at the margins flagged the day it shows up rather than the week someone finally notices the grading scar in a wide shot, would have turned a week of vague unease into a dataset I could argue with myself over coffee.
That's the gap Airfield Activity is built to close: a running log of a named field, so the question isn't "did something change" but "how much, and since when."
I still don't know why that field filled up the way it did. I'd like a system that at least tells me the day it started.
If you're carrying a few fields like that in the back of your head, it's worth seeing what a daily log on one of them looks like.