Weekly Schedule Maker
A grid for the hours you actually have. Pick a start and end time, type into the cells, print it or take the CSV.
What this grid is for
A week has 168 hours and most of them are already spoken for. The useful question is not "what should I do" but "where is the space". A grid answers that in one look: sleep, work, commute and meals become blocks, and what is left is the time you can actually plan.
This page makes the grid, not the plan. It does not know your priorities and does not rearrange your week.
Build it in four steps
- Set the hours you care about. Most people do not need 00:00–24:00; 07:00–22:00 covers a normal day and prints on one page.
- Pick a row length. 60 minutes is enough for planning a week; 30 minutes helps when classes or shifts start on the half hour; 15 minutes is for detailed days and produces a long printout.
- Type into the cells. Click a cell and write. Tab moves to the next day, Enter moves down the same day, Shift+Enter starts a new line inside the cell.
- Print or export. Printing uses the browser dialog with a landscape page. The CSV opens in Excel, Numbers or Google Sheets.
Press Build grid after changing the hours or the row length: the grid is rebuilt and any text that still lands on the same day and time is kept. Reloading the page clears everything.
Fill it in this order
- Fixed commitments. Work, classes, shifts, school run, appointments. These are not negotiable, so they go in first.
- Sleep and meals. They are the blocks most often sacrificed and the ones that break the rest of the week when they go.
- Two or three protected blocks. The work that needs uninterrupted attention. Two hours twice a week beats ten half-hours scattered across the grid.
- One buffer block per day. Deliberately empty. It absorbs the delay that always happens.
- Everything else. Errands, admin, exercise, social. If it does not fit, the answer is that it does not fit this week.
A full grid is a failed plan. If every row has something in it, the first delay pushes the whole week. Aim to leave roughly a fifth of the waking hours empty, and treat that emptiness as part of the schedule rather than as slack to be filled.
Why a grid instead of a to-do list
A to-do list has no capacity limit: it grows until it is a record of guilt. A grid has 168 cells, so it forces the trade-off into the open — adding an hour somewhere removes an hour somewhere else. That constraint is the useful part. It is also why the tool refuses to invent priorities for you.
Questions
Does the page save my schedule?
No. The text lives in the page until you reload or close it. Print it or download the CSV before you leave. Nothing is sent to the server and nothing is written to local storage.
Can I print a blank week?
Yes. Build the grid, leave the cells empty and press print. The controls, headings and navigation are hidden in the printed version, leaving the table on a landscape page.
Can I import the CSV into Google Calendar?
Not directly. Calendar import expects iCalendar (.ics) files with start and end times; this export is a plain grid of text. The CSV is for spreadsheets, records and printing from another program.
Why does the printed grid show fewer rows than the screen?
Because the browser splits long tables across pages and the print stylesheet keeps each row intact. Very short rows over a long day can run to several pages; 30- or 60-minute rows usually fit on one.
Does it handle time zones or recurring events?
No. The grid is literal wall-clock time with no zone attached, and it describes one week. Repeat the exercise next week, or keep the printed sheet as a template.