Filing a flight plan: schedule a study week that holds

Most study weeks fail during planning, not during the week itself. The plan lists everything that should happen and ignores how many hours actually exist. An airline never builds a schedule that way, and that difference is worth copying.

Airlines plan capacity, not intentions

An airline does not start with the flights it would like to operate. It starts with what it has: aircraft, crews, turnaround times, maintenance windows, slots at the airport. The published schedule is whatever survives those constraints.

A study plan usually runs the other way around. It starts with the subjects that need attention, spreads them across seven days, and only afterwards discovers that Tuesday already held a lecture until six and a shift until ten. The result is a plan that was never physically possible. When it collapses on Wednesday, most people read that as a failure of discipline. It is more often a failure of arithmetic. A weekly plan is a claim about capacity, and the claim has to be true before motivation gets to matter.

First the fixed blocks, then an honest count

Write down what you do not control

Before anything about content, list the blocks you do not control this week. Lectures, seminars, labs, shifts, appointments, family obligations, the commute at both ends, and the standing Thursday thing you never think of as an obligation but always attend.

Be specific about the edges. A lecture that ends at 18:00 followed by a 40 minute ride home does not free up 18:00. It frees up 19:00, and probably not for demanding work. In aviation, the gap between landing and the next departure is turnaround time: not idle time, but the time required to be ready again. Your commute, your meal, and the twenty minutes it takes to stop being in lecture mode are turnaround.

Do this in a calendar grid rather than a list. A list hides collisions. A grid shows them immediately.

Count the hours you actually have

Now add up what remains, in half hour units, honestly. Most people are surprised twice: first by how few hours are left, then by how badly they are distributed. Fourteen usable hours arranged as five on Sunday and one on each weekday is a completely different week from fourteen spread evenly, and it needs a different plan.

Two rules keep the count usable.

Do not count fragments under 25 minutes as study hours. They are real and they are fine for flashcards or re-reading a summary, but they will not carry a difficult chapter, and including them inflates the total.

Do not count a slot at full value if experience says it produces little. If the hour before sleep reliably turns into scrolling, write it in at half or leave it out. Capacity you cannot access is not capacity.

Match sessions to the day you will actually have

Once the hours are counted, assign the work to the state you will be in, not to an idealised version of yourself. Airlines schedule long haul departures when crews are legally rested, not when a gate happens to be free.

New and difficult material belongs in the block where you are freshest, which for most people is the first working block of the day rather than a particular time on the clock. Practice problems and past papers tolerate moderate fatigue well. Review, organising notes and light repetition are what the tired blocks are for. If Tuesday evening is always the wreckage of a long day, do not put the hardest chapter there. Put the review there and accept that Tuesday is a short haul day.

Give each block a destination rather than a subject. “Statistics” is not a plan. “Work through exercises 4 to 9 and note which ones I cannot start” is a plan, and it tells you at the end whether you arrived.

Buffer is part of the plan, not a failure

An airline that scheduled every aircraft back to back with no slack would collapse on the first delay, because nothing is left to absorb it. Timetables carry deliberate padding for exactly that reason.

A study plan that assigns work to one hundred percent of the available hours has already failed. It only holds if nothing overruns, nothing turns out harder than expected, and nothing personal happens for seven days straight. Plan roughly 70 to 80 percent of your usable hours and leave the rest genuinely empty. Those empty blocks are not rewards and not laziness. They are where the overruns go.

If a week ends with unused buffer, that is a correct plan working as designed, not time you wasted.

A missed block gets rebooked, not cancelled

Blocks will be missed. What matters is the procedure that follows, and most people do not have one, so a single missed session quietly turns into an abandoned week.

The operational answer is simple. When a block is missed, move it into the nearest buffer. If no buffer is left, decide explicitly what gets dropped in its place. Something has to give, and choosing it consciously is the entire point. An airline does not pretend a cancelled flight never existed. It rebooks the passengers or announces the cancellation. Both are decisions. Silence is not.

One useful limit: rebook once. If a block has already been moved twice, it is not a scheduling problem. It is a sign that the task is too large, too vague, or not actually a priority. Split it or strike it.

Five minutes of plan against reality

Close the week by comparing what you planned with what happened. Planned hours, completed hours, the gap. That is enough, and it takes about five minutes.

Read the gap as data about your capacity assumption, not about your character. If you plan sixteen hours and reliably complete eight, the useful conclusion is that your capacity is eight, and next week should be planned at nine. No amount of discipline advice will fix a number that was wrong from the start. Chronic under delivery is almost always a measurement error rather than a motivation problem.

Whether you track this in a notebook, a spreadsheet, or a timer that logs each session as a flight, the mechanism matters far less than the honesty of the numbers. A plan you can hit two weeks in a row is worth more than an ambitious one you abandon every Wednesday.