Weekly Schedule Templates
Three filled-in weeks to copy, and the decisions behind them.
Templates are starting points, not answers
Every filled-in week below leaves at least one block empty on purpose. Copy the structure, not the contents: the blocks that matter are the fixed ones and the protected ones; the rest is replaceable.
Template 1: a student week
Built around classes that start on the hour, with study blocks placed where they are most likely to happen — right after the class they follow, not late at night.
| Block | Monday to Friday | Weekend |
|---|---|---|
| 07:00 | Wake, breakfast, commute | Wake later, no alarm |
| 08:00 | Classes | Revision, 90 minutes |
| 12:00 | Lunch, then a 20-minute walk | Free |
| 13:00 | Classes or lab | Assignment work, 2 hours |
| 15:30 | Study block: review today's notes | Free |
| 18:00 | Dinner, sport or society | Dinner with friends |
| 20:00 | Reading, then stop at 21:30 | Plan the coming week |
The study block sits at 15:30 because reviewing notes within a few hours of the lecture is cheaper than re-reading them the night before an exam. The weekend revision block is fixed; the rest of the weekend is not.
Template 2: a rotating shift week
Shift work breaks the idea of a "normal" day, so the schedule is organised around sleep anchors rather than around meals. The example is a three-week rotation: early, late, night.
| Week | Shift | Protected sleep | Anchor that does not move |
|---|---|---|---|
| 1 | 06:00–14:00 | 21:30–05:00 | Breakfast at 05:15, gym at 15:30 |
| 2 | 14:00–22:00 | 23:30–07:30 | Gym at 10:00, dinner at 23:00 |
| 3 | 22:00–06:00 | 07:00–14:00 | Meal at 17:00, walk before the shift |
Two rules make this survivable. First, the sleep window is planned with the same seriousness as the shift, including the commute home. Second, one habit keeps its time across all three weeks, which gives the body a fixed signal when everything else moves.
Template 3: a family week
The constraint here is not hours but handovers: who collects whom, and what happens when a meeting overruns. The week is built around two fixed points and one fallback.
| Time | Weekday | Weekend |
|---|---|---|
| 07:00 | School run, breakfast | Slow breakfast |
| 09:00 | Deep work, no meetings | Family activity |
| 12:00 | Lunch, admin and errands | Lunch out |
| 13:30 | Meetings and calls | Free |
| 15:30 | School pickup, handover | Free |
| 17:00 | Dinner, homework | Dinner |
| 20:00 | Fallback hour: catch up or rest | Plan the week |
The 09:00 deep-work block has no meetings in it. The 20:00 hour is deliberately unassigned: it absorbs the day that went wrong, and on a good day it is free time rather than a debt.
Four rules behind all three
- Fixed before flexible. Commitments that cannot move go in first; otherwise the plan is built on sand.
- Protect one block per day. One defended hour is worth more than five hopeful ones.
- Plan the transition, not just the event. Commutes, handovers and setup take time; a grid without them is fiction.
- Leave a fifth empty. The empty rows are what make the other rows survive a bad Tuesday.
Make your own: the weekly schedule maker builds the same seven-day grid with the hours and row length you choose, then prints it or exports a CSV.
Questions
Should the template start at 7 a.m.?
Only if your day does. A night shift or a 5 a.m. start needs a different window; the grid is a rectangle, not a rule. Start where your day starts.
How much detail belongs in a weekly plan?
Enough to decide, not enough to become a second job. Blocks of one to two hours with a named outcome work better than fifteen-minute fragments, because they survive interruptions.
What if the same thing happens every week?
Keep last week's grid and edit it rather than starting blank. Repetition is the point of a template — the fixed blocks rarely change, and rebuilding them each week is wasted effort.