There's a specific kind of low-grade mental cost that comes from waiting on something.
It isn't loud. It surfaces at odd moments — in the shower, at three in the morning, in the middle of an unrelated meeting — as a small unresolved has that come back yet? And because there's no answer available in the moment, it gets set down and picked up again a few days later, indefinitely.
That cost is entirely avoidable, and the fix is one written sentence.
Why an unwritten blocker keeps returning
Because your attention can't close a loop it hasn't got the information to close.
The question has the surveyor sent it is unanswerable without checking, so it can't be resolved and dismissed. It stays open. And an open loop gets re-raised periodically, which is exactly what you're experiencing when the thought arrives unbidden on a Sunday.
There's a second reason it lingers. Without a written form, you don't actually know whether it's reasonable. Is nineteen days a long time? It depends on what was agreed, and if what was agreed exists only as a vague memory of a conversation, then the question has no answer and will keep being asked.
The form that closes it
Four elements, and all four are needed.
What you're waiting for, specifically. Not the survey but the valuation report.
Who owes it. A name. The organisation isn't enough — the council can't be chased, a person can.
When you asked, and what was said. Requested 3 August, said about a week. This is the element people skip and it's the one that makes everything else work.
What you'll do, and when. Chase on the 14th. Different surveyor on the 28th.
Put together: Waiting on Chris at Harding's for the valuation report. Requested 3 August, said about a week. Chase on the 14th, different surveyor on the 28th.
Twenty-five words. The loop is now closed, because every version of the question has an answer sitting on the page.
The closing is the point, and it's worth noticing that nothing about the situation changed. The report still hasn't arrived. What changed is that the uncertainty has been converted into a fact with a date attached, and facts don't wake people up in the way uncertainties do.
The specific thing stops the blocker expanding. Vague blockers absorb adjacent work — waiting on the survey quietly becomes a reason not to do three other things that don't depend on it.
The name makes it chaseable and, occasionally, reveals that there isn't one. A surprising number of blockers turn out to be things nobody has ever been asked for.
The date and the agreement tell you whether it's late. This is the element that answers the three-in-the-morning question directly: nine days past what was promised is late, and week three of a statutory eight-week process is not.
The action and the date convert waiting into a scheduled task. That's the difference between a decision you'll have to make in a moment of social discomfort and one already made by a calmer version of you.
The test that catches false blockers
Try writing the sentence and see whether it completes.
Waiting on Chris for the report, asked 3 August completes cleanly.
Waiting on... myself... to have read enough about the framework doesn't. Nor does waiting on it to be ready to show anyone, or waiting for a proper block of time.
Those are conditions you invented, and they've been operating with all the authority of a real dependency because nobody ever asked them to identify who owed what. The sentence is the audit, and it takes four seconds.
Where the discipline is excessive
The counter, because not everything needs twenty-five words.
For short waits with obvious answers, this is overhead. If you asked a colleague this morning for something they'll send this afternoon, writing a formal blocker is ceremony, and ceremony is what makes people abandon systems.
The threshold is roughly: anything you'd still be waiting on in a week, or anything with more than one person involved. Below that, remember it.
There's also a relational limit. A blocker written about a favour — a friend reading a draft, a colleague doing something outside their job — with a chase date attached, can turn goodwill into a schedule. Note which kind you're dealing with when you write it. No date agreed, don't chase before October is a perfectly good blocker and prescribes doing nothing.
Nineteen days, three in the morning
The flat sale has been silent nineteen days and it wakes him up twice.
What's actually in his head is an undifferentiated worry: something is stuck, it might be his fault, it might be late, he isn't sure who he asked or when.
Writing it takes ninety seconds and produces: Waiting on Chris at Harding's for the valuation report. Requested 3 August, said about a week. Chase on Thursday, different surveyor by the 28th.
Three things happen. He discovers, in the writing, that it's nine days past what was promised — which he hadn't been sure of. The three-in-the-morning question now has an answer available without checking anything. And Thursday is a task rather than a decision, so the awkward email gets sent by someone who isn't feeling awkward about it.
The report arrives on Friday, having sat in a drafts folder since the 8th.
What the app does with it
Marking a goal blocked in goaldrift asks what you're waiting on, and that prompt is the whole feature.
It isn't record-keeping. It's the sentence that separates a real dependency from an invented one, tells you whether the wait is reasonable, and turns I should chase that into something with a date on it.
The counter carries on regardless, which is right — nineteen days is nineteen days. What changes is that the number now sits above an explanation, and an explained number costs nothing to look at.
That's the pattern throughout, and it's most of what the practice consists of. Not making the numbers smaller, but making sure each one has a sentence underneath it that you wrote at the time and can still believe in November.
Related: When you're waiting on somebody else · How to chase without being a nuisance · When the blocker is you
Share: