How to Organize a Huge To-Do List Without Starting Over

To organize a huge to-do list you have to process it, not sort it. If yours has well over a hundred items, the problem is not that you need better categories. It is that the list has only ever been added to. Most advice either teaches you to build a good list from zero, which does not help with the one you already have, or tells you to declare to-do list bankruptcy and archive the lot.

That second option is real and it does work. It also throws away genuine commitments along with the debris, and if you have ever done it you will know the particular feeling of someone asking in March about the thing you bankrupted in February. So here is the other version: four passes, about 50 minutes total, nothing deleted that you still intend to do.

Set a timer for each pass. The timer matters more than it sounds, because the failure mode of this job is deliberating over item 6 of 150 and running out of will by item 30.

Pass one: separate the list from the backlog (15 minutes)

Your huge list is actually two lists that have been wearing one name.

A list is work you intend to do in the next week or two. A backlog is everything else you have not decided against: the ideas, the someday items, the things waiting on other people, the half-formed intentions. Both are legitimate. Keeping them in one view is what makes a hundred and fifty items feel like a hundred and fifty obligations.

So the first pass is a single binary question per item, answered fast: next two weeks, or not? Do not prioritise. Do not estimate. Do not fix anything. Just split.

The split itself is the first useful thing that happens. The large majority of a long-standing list normally lands in the backlog, and once it does the list stops being a hundred and fifty obligations. It becomes a short list of commitments and a long list of maybes. You have been carrying the weight of both, because they shared a screen.

Pass two: name the debris (15 minutes)

Now work only through the shorter list, and look for five specific kinds of item. These are what actually make a list unmanageable, and none of the standard advice addresses them.

Duplicates that do not look like duplicates

"Sort out the website copy" and "rewrite the about page" and "fix the pricing wording" are often one job you have written down three times on three bad days. Merge them, and keep the most specific wording.

Projects wearing a task's clothing

"Redo the onboarding" is not a task, it is a heading. The test is whether you can name a first physical action. If the honest first action is "work out what this involves", then that is the task, it takes twenty minutes, and the project goes to the backlog under its real name.

This substitution is the most valuable thing in the pass. An item with no identifiable first step is the one your attention snags on every time you read the list, and it is the usual source of what people call task paralysis. Not laziness, and not too much work, but an item that cannot be started as written.

Items with no owner

"Chase the supplier" when somebody else owns the supplier relationship. These are reminders to have a conversation, not tasks. Convert or drop.

Items that are really information

A URL, a phone number, a sentence you want to keep. A to-do list is a bad filing cabinet. Move them somewhere you would actually look.

Items whose deadline passed and nothing happened

This is the most informative category on the list. If an item was due three weeks ago and no consequence has arrived, you have learned something true: either it did not matter, or somebody else did it, or the deadline was invented. Ask which, then act on the answer.

What disappears here is mostly merges and misfiled information rather than real work, which is why it is safe to do quickly. You are not deciding what matters. You are removing things that were never tasks.

Pass three: put numbers on it (10 minutes)

Estimate each remaining item in fifteen-minute steps. Fast, rough, no agonising. A 30-minute task and a two-hour task are different in a way that matters; whether something is 45 or 60 minutes does not.

Then add the numbers up. This is the step that turns an organised list into a plan, and it is the step nearly every article on this subject leaves out. You will have a total, and it will be larger than you expect.

Now compare it against your real capacity. Not the hours in your working day, but what is left after meetings, email, messages and the gaps between things. For most people with a desk job and a meeting load that is three to four hours a day of actual task time, which is worth measuring for yourself rather than taking from an article.

Which brings up the question everyone asks: how many tasks per day is realistic? There is no general answer, and the common prescriptions give the game away by disagreeing with each other. Under twenty items. Two or three big ones. Three to five key tasks. The 1-3-5 rule, meaning one big, three medium and five small.

None of those is derived from anything. They are different people's days, generalised. A day is not a number of tasks, it is a quantity of minutes. Five ten-minute tasks and five ninety-minute tasks are both "five tasks", and only one of those days is possible.

It is also why organising a to-do list with categories, by project or context or area of life, helps less than people hope. Categories make a list easier to read. They do not make it smaller, and they never tell you whether tomorrow fits.

Pass four: schedule only what fits (10 minutes)

This is where organizing a huge to-do list turns into a day you can finish.

Take your capacity number for tomorrow and fill it, in order of what cannot wait, stopping when the minutes run out. Not when the list runs out. When the minutes run out.

Everything beyond that line gets a specific day or goes to the backlog. "Later this week" is not a day. Thursday is a day.

A worked example

These are the 16 items left after the first two passes, and tomorrow has 200 minutes of task capacity:

Tomorrow adds up to 170 minutes against 200 available, which leaves 30 minutes of slack for the overrun that estimates always produce. Seven things, all of which can actually be finished.

Five items went to the backlog, and notice that none of them was deleted. The CRM research, the shared drive, the offsite and the photo library are all things you may genuinely do. They are just not things you are doing this week, and saying so explicitly is what stops them sitting in your eyeline pretending to be today's problem.

The Q4 plan is the interesting one. At 180 minutes it cannot fit tomorrow and would not fit Thursday either, so what goes on Thursday is its first action, not the project. That is the "project wearing a task's clothing" fix from pass two, applied at the point of scheduling.

About deleting things

Most advice on huge lists urges you to delete ruthlessly and gives you no rule for deciding what dies, which is why people either delete nothing or declare bankruptcy and delete everything.

Here is a rule that holds up. An item should come off the list entirely when you can answer yes to both of these: nothing bad happens if it is never done, and you would not add it again today if it were not already there. That second question is the useful one. A huge list is mostly accumulated past intentions, and the question "would I write this down today?" filters them better than any judgement about importance.

Everything else goes to the backlog, which is not a graveyard. It is the place where an item stops being a daily obligation without being a decision you have to defend.

One caveat worth being honest about. If your list has items from years ago, triage alone will not settle them, because the problem is not organisation, it is that you have changed and the list has not. Years of unfinished to-do lists is a different job with a different rule.

Keeping it from rebuilding

A triaged list rebuilds within a month unless two habits change.

New items need one place to land, immediately, without being organised. If capturing something costs more than a few seconds, you will keep things in your head instead, and the next huge list is already forming. Capture first, sort later, and in batches.

And the end of the day needs a decision rather than a drift. For everything you planned and did not finish, choose: tomorrow with a real slot, a specific later day, back to the backlog, or off the list. The reason lists become huge is not that people add too much. It is that nothing is ever deliberately removed.

That is the part Todonado is built to do for you. Inbox is the one capture place, and nothing in it has to be organised to be safe. Projects and sections hold the backlog without it sharing a screen with today. Tasks carry effort estimates in minutes, and the Today view totals them against the capacity you set, so pass four is arithmetic you do not do by hand. Unfinished work comes back as that four-way decision instead of silently reappearing, and Week planning distributes overflow across the next seven days against each day's own capacity, so "Thursday" means a Thursday with room in it.

What it will not do is the triage. The four passes above are judgement, and nothing can make the "would I write this down today?" call for you. Todonado keeps a triaged list triaged; it cannot do the first pass.

Once the list is down to something real, the daily job is small: planning a realistic day is the same arithmetic as pass four, run every morning in about five minutes.