Slots: time blocking that survives a real student week

Open next week in your calendar and look at what is already written there. Lectures, a lab session, a shift, a dentist, somebody’s birthday. Every one of those entries was placed by another person, and almost all of them will happen as written. The hours where your own work has to go are the white space between them, and white space is not a plan.

The half empty calendar

A calendar is very good at recording promises you made to other people and very bad at recording promises you made to yourself. The lecture sits at ten because a timetable says so, and you will be there. The four hours of statistics you owe yourself this week exist only as an intention, which is why they give way first when a friend calls or a deadline moves.

That asymmetry is not a character flaw. An appointment with another person costs you something the moment you miss it, and the cost is visible at once. Skipping your own work costs nothing today and everything in six weeks, which is the worst shape for a human to react to. Writing the work into the calendar does not remove the asymmetry, but it moves your own work into the same column as everything else, where it can at least be seen and defended.

A slot is a window with a tolerance

At a busy airport you do not simply take off when you are ready. You are given a slot, a window of a few minutes in which your departure fits into everything else moving that day. Miss it and you do not get the same window an hour later. You go back into the queue and take whatever gap is left, which is usually worse and always later.

A study block runs on the same terms, and most block plans fail because they were written as if it did not. A block is a named piece of work in a named window: not “statistics”, which is a subject, and not “study in the afternoon”, which is a mood. It has a start, an end, one task, and a state the work should be in when it closes. If you cannot say what would count as having used the block, you have written a wish with a time on it.

Size before ambition

The first thing people get wrong is length. A Sunday plan built from three hour blocks looks serious and collapses by Wednesday, because a three hour block has to survive three hours of everything else, and one interruption is enough to turn it into a failure. Anything that has failed is easier to abandon than to repair, and the rest of the plan usually goes with it.

Sixty to ninety minutes holds up better. It is long enough to get past the first twenty minutes of settling in, short enough that most days can produce one, and small enough that a bad day costs you a block instead of a week. If a task genuinely needs four hours, that is not a block. It is three blocks with a defined stopping point in each, and the third one is allowed to be cancelled. Study Airlines keeps a record of every session you actually fly, and after two weeks that record tells you your real block length more honestly than any Sunday plan does.

The gap belongs to the plan

Blocks placed end to end make a schedule that only works if nothing takes longer than expected. The first overrun eats the start of the second block, the second ends late, and by mid afternoon you are running a plan that no longer matches the clock. At that point you abandon the clock, and that, not the overrun, is the actual failure.

Leave fifteen or twenty minutes between blocks and treat the gap as scheduled rather than spare. It absorbs the overrun, covers the walk between buildings, and holds the small things that would otherwise interrupt a block from the inside: eating, the message that genuinely has to be answered, the two minutes of standing up that separate one subject from the next. A plan with gaps in it can lose ten minutes without losing its shape.

Decide the displacement rule before you need it

A block will be missed. Whether the week survives depends on what happens next, and that question gets answered badly in the moment it arrives, when you are already late and mildly annoyed. So answer it in advance and keep the answer boring.

Three answers cover almost everything. The block is dropped, the work moves into the next scheduled block for that subject, and something there gets cut to make room. Or the block moves into a named replacement window that already exists somewhere in the week, never into a vague later. Or the block shrinks to thirty minutes on the one part of the task that cannot wait, and the rest goes. The move you never make is adding the lost hours to the next day on top of what is already there, because a doubled block on an ordinary day tends to fail and hands you two losses instead of one.

Rebuilding instead of rescuing

Two missed blocks in a week is normal noise. The same block missed three weeks running is information: that window does not exist in your life, whatever the calendar claims. Tuesday at eight in the morning is not a slot if you have never once used it.

At that point stop patching the plan and build a new one from what actually happened. Look at which blocks you completed over the last fortnight, at what time, after which activity, and put next week’s work there. A plan assembled from observed behaviour is less impressive than one built from intentions and worth considerably more, because it describes a week you have already lived through twice.

The part of the week that will not block

None of this spreads evenly across a life. Shift work, a small child, a parent who needs care, a lab that runs until the experiment finishes: these produce weeks where half the days cannot be planned at all, and pretending otherwise gives you a plan that is wrong by Monday morning. The honest version is a split. The stable part of the week gets real blocks with real tasks in them, and the unstable part gets a short list of work sorted by size, so an unexpected free hour has something to fall into without any deciding.

That is less satisfying to look at than a full grid, and it is the version that survives the week. A calendar describing twelve honest hours is worth more than one describing thirty hours you were never going to have.