How do you log a day when you worked a night shift?

You clock in at ten at night and clock out at six the next morning, and somewhere in between, the date changes underneath you without anything about the shift actually changing. The break at 2am, the drive home in the dark, the meal that is either a very late dinner or a very early breakfast depending on how you want to think about it — none of it noticed the date roll over. So when it comes to writing any of it down, the obvious question shows up first: which day does this belong to?

The calendar day was never built for you

A calendar day is a convenience for people whose lives happen to fit inside it — asleep by midnight, awake by morning, one continuous stretch of waking hours bounded neatly by two nights of sleep. Night-shift work does not fit that shape, and it is not supposed to. Your waking stretch straddles the midnight line the way a normal day straddles noon: it is just the middle of something, not an edge. The trouble only starts when you try to force a record of your night into a container that was designed for somebody else's day.

Most tools that ask you to log or track anything inherit this assumption without saying so — a day is a box from midnight to midnight, and whatever happened gets filed into one box or the other. For a night-shift worker that means every log either gets awkwardly split at the exact moment nothing meaningful happened, or gets crammed entirely into the wrong box just to avoid the split. Neither is really about you. Both are about a container that quietly assumed everyone sleeps at the same time.

A written line doesn't need to pick a side

The reason this turns out to matter less than it seems is that a log entry is not a block of duration that has to be sliced cleanly in two if it happens to straddle midnight. It is a moment: a line, a time, a category, written about whatever you were doing right then. There is no span being measured that midnight could cut through, so there is nothing to divide and nothing to reconcile afterward. An entry at 1:40am simply carries its own timestamp, sitting wherever it actually falls, and the fact that the shift around it also touched the evening before or the morning after is not a problem the entry has to solve.

This is one of the quieter advantages of writing down what you were doing instead of timing how long you did it for. A tracker built around elapsed duration genuinely does have to decide which day a block of hours belongs to, because the total has to land somewhere for the arithmetic to work. A log made of individual, timestamped moments never has that argument in the first place — there is no total being kept, so there is no dispute over which day gets credited with it. The shift simply exists as a run of entries that happen to cross midnight, the same way it existed as a run of hours that happened to cross midnight while you were living it.

What is actually worth writing down about a shift like this

Once the date question stops being the thing you have to solve first, what is left is the same question as any other day: what actually happened. For night work that tends to be a slightly different set of things than a daytime log would collect — the drive in while everyone else is driving home, the strange quiet of a building running on a skeleton crew, the meal eaten at an hour that has no normal name, the particular kind of tired that shows up around 4am and the second wind that sometimes follows it, the daylight hitting you on the way home like something almost unfamiliar. None of that needs a category invented specially for night shifts. It just needs to be written down as itself, at the time it actually happened, rather than reorganized to fit a day that never quite matches your hours anyway.

Your record is allowed to look different from everyone else's

A month of night-shift entries, read back later, will not line up the way a month of ordinary nine-to-five entries would — the dense clusters will fall in the middle of the night instead of the middle of the day, and the quiet stretches will fall in daylight. That is not a flaw in the record. It is simply what an honest account of your actual hours looks like, and it is far more useful than a version of the log that was quietly bent to resemble a day-shift schedule you don't keep. The point of writing any of this down was never to match anyone else's rhythm. It was to keep your own.

TimeMap does not ask a log entry to decide which day it belongs to before it lets you save it — a line just gets a time and a colour, and midnight passing in the middle of your shift is not an event the entry has to account for. A night worth remembering does not need to be split in half to fit somewhere it was never going to fit cleanly, and it does not need to be.