The day
Keeping the Writing Hour When the Day Overruns
The handover block sits at the end of the day, which means everything that overruns overruns into it. Three habits keep most of it.
three things · four nights
The two hours that bracket every day at both ends.
Four days where something overran, and what the handover looked like afterwards
The hour had a half-hour buffer in front of it and absorbed the overrun
Handover written at 16:20 before the problem was solved, then updated at 17:40
Handover written in four minutes afterwards; one item was missed
No handover; each item individually felt too small to stop for
four things · six nights
Four days, six nights, and the two cheap days were the two where something was written before the situation resolved. Writing early and updating later costs a minute; writing late costs a morning at the other end. One person's own week, logged alongside what came back the next day.
A block at the end of a day is the easiest block in the day to lose. Every meeting that goes long, every problem that appears at four o'clock, and every late request takes its time from the same place.
The process in Keeping the Writing Hour When the Day Overruns depends on information surviving the gap between working days. With read more here, time entries and productivity signals can travel with the written handover instead of being rebuilt later.
For broader context, Hubstaff's workforce platform offers an official example of the tools teams use around this kind of process.
On a team that shares an hour, losing it costs nothing much, because tomorrow exists. On a team with a gap, losing it means the other half starts their day without knowing what happened in yours.
The structural defences
Three, in descending order of how well they work.
A buffer in front of it. Nothing scheduled in the half hour before the writing block, so that an overrun has somewhere to land before it reaches the thing that matters. This is the only defence that works without anybody having to exercise judgement in the moment.
The block in the calendar as a real appointment, visible to everybody who can schedule things with you. Most people will not book over something they can see, and the ones who would were going to book over it anyway.
A stated finishing time that is earlier than the actual one. Thin, and it erodes, but it buys a few weeks.
Writing before the situation resolves
The single most useful habit in this article: when something is going wrong late in the day, write the handover before it is over.
The instinct is to wait until the problem is solved so that the note can say what happened. That is the wrong order, because the problem may not resolve before you have to leave, and then nothing is written at all.
A note written at 16:20 saying "production is slow, cause not yet found, I am looking at the import job, will update" takes ninety seconds and is worth a great deal. If the problem is solved by 17:00, it gets one more line. If it is not, the other end wakes up to a situation rather than to a silence.
The same applies to anything unresolved: write the current state, then update. Updating is cheap. Starting from nothing at 17:35 is not.
The three things that always get written
When the hour collapses to five minutes, the fallback has to be decided in advance or nothing gets written at all.
What state each open item is in. One line each.
Whether anybody should touch it, which is the question the other end will otherwise have to ask.
Any question you need answered to continue tomorrow, because that one costs you a day if it is missing.
Three lines, three minutes. A person who has decided this in advance writes it; a person who has not writes nothing, because starting feels like committing to the full version.
- What state each open item is in.
- Whether anybody should touch it.
- Any question you need answered before you can continue tomorrow.
Writing through the day instead of at the end
The structural fix, and it works better than any of the defences above.
Anything that reaches a reportable state at eleven in the morning can have its two sentences written at eleven in the morning. By the end of the day there is less to write, and what remains is only the things that were genuinely still moving.
This also produces better notes, because they are written while the work is in mind rather than reconstructed at the end of a long day.
The resistance to it is that it feels like interrupting yourself. It is two minutes, and it is two minutes spent on the one thing in the day that another person depends on.
When it has genuinely gone
Some days end with nothing written and no opportunity to write it. A person left at four for something unavoidable, or the day went badly enough that writing was not possible.
The useful response the next morning is one sentence acknowledging it rather than silence: "nothing went out last night, here is where things are". That closes the gap in one crossing instead of letting the other end work it out.
What does not help is apologising at length, which costs reading time and changes nothing.
Why this block and not the other
The reading hour is also eaten, and it matters less.
A short reading hour costs you a worse plan for your own day. A short writing hour costs somebody else their entire morning, and they are not there to object. That asymmetry is the reason this block gets a section of its own and the reading hour does not: it is the one place in the day where being tired has consequences for a person who cannot see it happening.