Most people run two systems that overlap badly. Some things end up on the calendar, some on a list, and the rule for which goes where is whatever felt natural at the moment of writing it down.
The result is a calendar you have learned to half-trust and a list you have learned to half-read. Both failures come from the same place, and the fix is a single rule you can apply in about a second.
The rule
A calendar is for things that happen at a time whether or not you show up. A list is for things that need doing but do not have a slot.
That is it. The dentist happens at 3pm on Thursday whether you are there or not. "Renew the insurance" does not happen at any time; it needs to be done before a date, which is a different thing entirely.
The test, when something is ambiguous: if I am not there, does it still occur? Yes → calendar. No → list.
Why putting tasks on the calendar goes wrong
Blocking out 2pm to 3pm for "write the report" is the most common piece of productivity advice there is, and it fails for a specific, mechanical reason.
Tasks slide. The report does not get written at 2pm because a meeting overran, so it moves to 4pm, then to tomorrow. Each move is a small edit and a slightly larger lie: your calendar now shows something that did not happen and something else that will not.
Do that for two weeks and the calendar stops being a record of what is true. Once it is not reliably true, you stop reading it as though it were — and now the dentist appointment is in the same visual field as four blocks you already know are fiction. The appointment is what you lose.
The cost is not the moved block. It is the trust.
Why putting appointments on a list goes wrong
The opposite error is quieter and more expensive.
An appointment on a to-do list has no shape. Lists are read as things I could do next, scanned in priority order, and a 3pm meeting has no priority — it has a time. Put it in a list and it either gets done early, which is impossible, or it gets missed, which is the usual outcome.
An appointment needs to be somewhere that will interrupt you. A list will not interrupt you. That is a large part of what makes a list restful to look at.
The useful third category: a deadline
Most confusion lives here, and it dissolves once you notice that a deadline is two things.
A deadline is a point in time — the tax return is due on the 31st. The work is a block of effort with no natural home in the calendar, because it is not an event, it is a task you have to find hours for.
So: put the deadline on the calendar as an all-day marker, because it is genuinely a fact about the 31st. Put the work on the list with the 31st as its due date, so it rises as the date approaches. One thing, two records, each of them true.
What you should not do is block "do tax return" for Tuesday afternoon and treat that block as the plan. If Tuesday goes wrong you have lost both the plan and the record of the deadline.
Time-blocking, defended properly
Time-blocking works, but only under a condition people rarely state: the block has to be a commitment to be unavailable, not a prediction of what you will feel like doing.
"9 to 11, no meetings, deep work" is a real thing that really happens — you can protect that time, and it is true whether or not the report is what you end up writing in it. It behaves like an appointment because it constrains other people.
"2pm, write the report" is a wish. It constrains nobody, it is not verifiable, and it is the version that erodes the calendar.
If you want to time-block, block the availability, not the task. Then pull from the list when the block starts.
Recurring things, which are neither
There is a third bucket that people force into one of the first two and should not.
Water the plants. Twenty minutes of Spanish. Take the pills. Put these on a calendar and it fills with grey repeating events you stop seeing. Put them on a to-do list and they arrive as new tasks every single day, drowning the four things that are actually new.
These are habits, and they want a third kind of record: a grid where the question is not "what should I do today" but "how has this gone over the last month". Tracking habits without a separate app for it goes into that properly. The relevant point here is that misfiling them is what makes both of your other two systems noisy.
Similarly, a routine — the four things you do every Monday morning, in order — is a checklist you run, not four separate tasks and not a calendar event. Checklists for the things you do every week is the same idea.
What a good day looks like
With things filed correctly, the morning view answers one question — what is fixed today, and what is available — and it has four parts:
- What happens at a time. Two meetings, a call, a collection. Non-negotiable, in order, with the next one's time visible.
- What is due. Things whose deadline is today or close, risen from the list.
- What is outstanding. The habits not yet ticked, the routine not yet run.
- Everything else, which is a list you choose from in the gaps.
The point of the separation is that only the first is a constraint. The rest is choice, and being able to see the difference at a glance is most of what people want from a planner. Cyanote's Today page is built exactly on that split, which is not a coincidence — it came out of trying to plan a day I would actually follow.
A five-minute audit
Open your calendar for last week and look for anything that moved more than once. Each of those is a task pretending to be an event; take it off, put it on the list with a due date.
Then open your list and look for anything with a time in the text — "call Sam 3pm", "dentist Thursday". Those are events pretending to be tasks; put them on the calendar.
Most people find between three and ten items in the wrong place, and the immediate effect of moving them is that the calendar becomes true again. A true calendar is one you can read in a second and believe, which is the only version of a calendar that is any use at all.