I do not think most people need another calendar. I also do not think most people need another infinite to-do list.
The calendar is for things that happen at a time: meetings, flights, appointments, the dentist, the client call that starts at 14:00 because other people have made the unfortunate decision to exist in time too. A to-do list is for things you intend to do: send the note, fix the invoice title, read the document, call the person, remember the thing before it escapes and becomes a vague discomfort during dinner.
Both tools are useful. Neither one quite fits the way my week actually works.
Most of my work sits between those two tools. It matters, but it does not always have an hour attached. Some tasks belong this week, but not at 10:30 on Wednesday. Some ideas have value before they can become tasks. Some work has edges. Some work is still uncut material.
Slate is built for that gap.
Calendars are good at time
A calendar has one job: time. It knows when the train leaves, when the call starts, and when the appointment ends. It is very good at fixed commitments.
The problem starts when a calendar is asked to hold work that does not behave like an appointment. If I put “write proposal” from 9:00 to 10:30 on Tuesday, the calendar believes me. It draws a rectangle. The future looks handled. Tuesday arrives, the call before it runs over, a new message changes what the proposal needs, and the rectangle stops describing the day.
The work did not change. The drawing did.
This is why I stopped trying to make my calendar carry ordinary work. A calendar is excellent at external commitments. It is worse at holding the half-defined, flexible, human mess of a week.
To-do lists are good at intent
A to-do list has the opposite strength. It accepts almost anything: “follow up with Mira,” “fix onboarding note,” “maybe revisit pricing page,” “think about Mark.” The list does not ask many questions. That is useful when the thought is still current. Capture matters. If the app makes me explain too much too early, the task is gone.
But after a while, the list becomes a drawer with no bottom. Today, someday, later, important, waiting, personal, work, ideas, admin, errands, tax, maybe, next. A to-do list is good at keeping intentions alive. It is less good at deciding which ones deserve the week.
The list accepts everything and decides nothing, so people add dates.
Most task dates are guesses wearing formal clothes
A date field looks responsible. It looks organized. It looks like the adult in the room. But most dates I put on tasks were not deadlines. They were guesses.
“Wednesday” often meant: I hope the week has room for this by then. The app treated that hope like a promise. Then Wednesday arrived, the task was still undone, and now the app had a word for me: overdue.
That word is too heavy for what happened. I was not late for a flight. I did not miss a tax filing. I guessed wrong about my own week, which is one of the most ordinary human things a person can do.
A planning tool should know the difference between an external deadline and a private estimate.
Placement is the plan
Slate takes a simpler position: if a task belongs on Wednesday, put it on Wednesday. Not as a fake deadline. Not as an event. Not as a block of time unless it truly needs one. Just put it where you intend to meet it.
That is the weekly slate.
The week is laid out as days. Work that is ready goes into the day where it has the best chance of happening. The day carries the commitment. There is no second date hiding in a database field. There is no theatrical overdue state waiting to scold you.
If Wednesday changes, move the task. That movement is not task hygiene. It is planning.
Not everything deserves a day yet
The other half of Slate is the Idea Quarry. I built it because I kept needing a place for work that mattered before it was ready.
Corporate work has a lot of this. Some tasks are perfectly clear: send the follow-up, review the deck, book the appointment. Others are not: “figure out the client feedback,” “think through the proposal angle,” “do something about the onboarding notes.” These things matter, but they are not yet clean tasks. Forcing them into Tuesday does not make them clearer. It only makes Tuesday worse.
The Idea Quarry is where those items can wait without disappearing. It can hold a phrase, a rough task, a named list, a fragment, a possible errand, a decision you are not ready to make. Used honestly, it is not a junk drawer. It is the uncut pile beside the workbench.
Some items are ready for the week. Others need more cutting first.
Planning is not scheduling
This is the distinction Slate is built around. Scheduling is what you do when the constraints are known. Planning is what you do while the constraints are still arriving.
Most of my week is not fully knowable on Monday. A client will clarify the wrong thing. A small task will expose three hidden dependencies. A meeting will generate work while pretending to resolve it. The item that looked important on Friday may look faintly ridiculous by Tuesday afternoon.
A good planning surface should allow that. It should let work move from rough material to weekly commitment. It should let a task sit in the quarry until it earns a day. It should let Wednesday change without turning the whole system into an apology.
That is why Slate is not a calendar. It is also not a to-do list. It is a workbench for the week.