Do It Tomorrow and the Pythagorean Evening Review: One Ritual That Closes the Day

What each one is actually for

Do It Tomorrow

Do It Tomorrow is a response to a specific structural problem, which is that most task systems have no boundary. Work arrives continuously, it goes onto one growing list, and because the list has no edge you can never finish it, only stop. Forster's answer is to separate arrival from execution by a day. Everything that comes in today — emails, requests, ideas, the thing your colleague mentioned in the corridor — gets written onto tomorrow's page rather than acted on. Today you work only from the page written yesterday, which is closed: nothing can be added to it after the day begins. So the day has a defined end, and finishing is a state you can actually reach rather than a horizon. Two consequences follow that people usually only notice after trying it. First, you get a genuine measurement — if tomorrow's page is consistently longer than what you can clear in a day, you are taking on more than you can do, and the system shows you that as a number rather than as a feeling of being behind. Second, the reflexive urgency of incoming work gets tested: most things that felt like they had to be handled immediately turn out to survive a night perfectly well, and the ones that genuinely cannot wait become visible precisely because they are the exceptions.

Evening Review

The evening review in its Pythagorean form is three questions asked of the day just ended, done from memory, lying down, before sleep. The verses put it as not letting sleep close your eyes until you have gone back over each of the day's deeds three times: what did I do wrong, what did I do, and what did I fail to do that I ought to have done. It is a memory exercise as much as a moral one — you are reconstructing the day in sequence rather than recalling impressions of it, and the reconstruction is meant to be specific, an actual replay of what happened in what order. Seneca describes running his own version in the dark once the house is quiet, going over the whole day, hiding nothing from himself and excusing nothing, and he makes a point that the tone matters: he says he examines himself as a judge would, but without dread, because a review you are frightened of is one you will start avoiding. The purpose is not to feel bad accurately. It is that conduct you have looked at closely tonight is conduct you are more likely to catch yourself in tomorrow — the review is aimed forward, at the next day, not backward at settling accounts with this one.

What you get out of pairing them

The task system gets you an end to the day that is real rather than negotiated. If you have ever finished work and carried a low hum of unfinished business into the evening — not any specific task, just the sense that there is more — that hum is what an unbounded list produces, and it does not respond to working harder because working harder does not reduce an infinite quantity. A closed list makes finishing possible, and the difference between 'I stopped' and 'I finished' is not cosmetic; it is the difference between an evening you are present for and one you are still half at work in. The review gets you something the task system cannot supply at all, which is a look at the day that is not about output. Forster's page tells you what got done. It tells you nothing about how you were — that you cut someone off in the meeting because you were behind, that you did the easy items first for the third day running, that the thing you keep moving to tomorrow has been moving for eleven days and the reason is not scheduling. Those are the patterns that shape a working life and none of them appear on a task list, because a task list records completion and not conduct. Put together, you get a day that ends twice: once as work, when the list is closed, and once as behaviour, when you have looked at how you spent yourself and turned what you saw into a specific line on the page you will pick up in the morning.

What Do It Tomorrow rests on

• Implementation intention closes intention action gap randomised trials
  Pre-committing to a specific situational cue paired with a specific response lets the behavior fire automatically when the cue occurs, without depending on in-the-moment willpower.
• Closed lists reduce overwhelm practitioner report
  A fixed bounded list of tasks rather than an ever-growing open list reduces the felt overwhelm of an infinite to-do list.
• Deferred capture protects commitment practitioner report
  Writing newly arriving tasks onto tomorrow's list rather than acting on them immediately protects today's already-committed plan from being derailed by reactivity.

What Evening Review rests on

• Self distancing improves judgment randomised trials
  Evaluating a situation from a distanced, third-person vantage point instead of an immersed first-person one improves the quality of judgment about it.
• Retrieval strengthens memory randomised trials
  Being forced to actively retrieve information from memory, rather than passively re-encountering it, strengthens long-term recall.
• Reflection consolidates learning practitioner report
  Structured nightly reflection against a personal standard consolidates lessons from experience into future behavior change.

Where they actually meet

Both practices put a hard line at the end of the day and treat what falls after it as belonging to tomorrow — but they draw the line around different material and that is exactly why they fit. Forster draws it around work: once today's page is closed, no new task can reach today, and everything arriving after the line is tomorrow's business by definition. The Pythagorean review draws it around conduct: you go back over the day deliberately, once, at a fixed point, and then you are done with it and asleep, rather than reviewing it involuntarily at three in the morning in fragments. In both cases the boundary is what makes the practice work, and in both cases the boundary requires a deliberate act at a specific time rather than a gradual trailing-off. That is the join. They want the same moment. One arrives at it needing content — what should go on tomorrow's page? — and the other arrives at it producing content it has nowhere to put.

The principle underneath both

A day that is not deliberately ended does not end. It carries on in the background as unfinished work you cannot name and unexamined conduct you will repeat, and both of those keep drawing on you at a low level for as long as they stay unresolved. Closing it on purpose — stepping outside it while the detail is still recoverable, seeing what happened, and converting what you find into something specific enough to act on tomorrow — is what stops the day from following you. Held this way, a list and a nightly examination are two halves of one closing act rather than two separate disciplines.

What that makes the real goal

What you want at eleven o'clock is for nothing about today to still be running. Not resolved in the sense of everything having been done, but resolved in the sense that everything outstanding, whether it is a task or something you did that you would rather have done differently, is written somewhere specific enough that your mind can stop holding it. Put that way the goal is independent of both traditions: it is about converting open loops into named next actions before sleep, and there is a body of experimental work on exactly that conversion which neither Forster nor the Golden Verses had access to.

Other practices that serve the same goal

The most directly relevant modern research here concerns what happens when an unfinished intention gets a specific plan attached to it. Experiments by Masicampo and Baumeister found that unfulfilled goals intrude on attention and impair performance on unrelated tasks — but that simply making a concrete plan for the goal, without doing anything about it, released the intrusion. That finding is the mechanism a closed tomorrow-list is quietly relying on, and it is stronger evidence for the practice than Forster's own case material. Closely related is the sleep literature on constructive worry, where writing down the concerns that would otherwise circulate at bedtime, along with the next step for each, has been examined in insomnia work and appears to shorten how long it takes to fall asleep; a small trial found writing a specific to-do list before bed beat writing about completed tasks on that measure. On the reflective half, the Ignatian examen and the structured after-action review used in military and clinical settings both pursue the same end by different routes — the after-action review in particular is notable because it is deliberately done as a group and out loud, which supplies an external check that a private nightly replay cannot. And if the thing you specifically want is better judgment about a difficult moment from the day, the self-distancing research offers a very small intervention with real experimental support: reviewing the episode in the second or third person, using your own name, rather than reliving it from inside.

A tradition that already does this

The Ignatian examen, formalised by Ignatius of Loyola in the sixteenth century and still practised daily in Jesuit life, already fuses the two halves described here. It runs five steps at a fixed point each evening — become still, review the day's events in sequence, notice where you fell short, respond to what you found, and then, in the final step, form a concrete resolve for the day coming. That last step is the part that matters for this pairing: the tradition worked out independently that a nightly review which stops at noticing tends to produce repetition rather than change, and built the forward commitment into the ritual rather than leaving it to the practitioner. Ignatius was not building a task system and the examen's resolve is a single intention rather than a page of items, so the fit is instructive rather than exact. But it establishes that joining a structured evening replay to a specific commitment for tomorrow is a move a lineage arrived at through five centuries of daily use, not something assembled here for the sake of an argument.

Using tomorrow's closed list to give the evening review somewhere to land

The oldest complaint about a nightly examination is that it turns into a nightly bad mood. You replay the day, you find the place where you were short with your partner or dodged the difficult email for the fourth time, you feel the weight of it accurately, and then you go to sleep and nothing about tomorrow is different — so the same item surfaces again in a week, with a bit more weight on it. The fix is to insist that anything the review turns up leaves the review as writing on tomorrow's page, and to be strict about the form. A finding about a task becomes a task: 'the thing I keep not doing' becomes the actual first line of tomorrow's list, positioned first specifically because eleven days of evidence say it will not survive being third. A finding about conduct becomes a situation-and-response pair, which is a more useful shape than a resolution: not 'be more patient in the standup' but 'when Priya starts the update, I put the pen down and do not speak until she has finished.' The difference matters — a resolution names a quality you are trying to have, and a situation-and-response names a moment and what you will do in it, which is the form that has actually been shown to make intentions turn into behaviour. Cap it at one of each. Three findings converted into three lines is a review producing an admin backlog, and the point is that tomorrow's page absorbs the review, not that it becomes its output.

Using the Pythagorean questions to decide what goes on tomorrow's page

Forster tells you to write tomorrow's list. He does not tell you what should be on it, and in practice most people fill it with whatever arrived — the day's inbox, transcribed. That produces a list that is complete and entirely reactive, which is a subtle failure because the system looks like it is working. Use the three questions as the filter before you close the page, in their order, and give it four minutes. First: what did I actually do today? Go through it in sequence rather than by impression — morning, midday, afternoon — because sequence is what makes you notice the ninety minutes that are missing from your account of the day. Second: what did I do badly? Not morally; operationally is enough. Did I open the easy items first again? Did I let something interrupt a block I had committed? Third, and this is the question doing the work the other two can't: what did I leave undone that I should have done? That question is the one that finds the item which has been silently rolling from page to page for a week and a half, because rolling it forward is invisible in a system where moving things to tomorrow is the normal operation. Write what it turns up onto tomorrow's page before you write anything from the inbox. Then close the page. The list you end up with has one thing on it that came from looking at the day rather than from the day happening to you, which over a month is a substantially different list.

Eleven-fifteen, the light off, and the email you have moved for nine days

You are lying down and the day is behind you. Tomorrow's page is written and on the kitchen table — you did that at six, closed it, and the fact that it is closed is why you are not mentally reshuffling it now. You start the replay at the morning: coffee, the standup, the two hours on the report, which were good. Lunch. And then the afternoon comes back in less detail than it should, which is itself the finding — somewhere between two and four you did a lot of small things and you cannot reconstruct what they were. Then the third question, and it arrives with the specific email attached: the one to the supplier, the one where you have to say the deadline slipped and it was your fault. It has been on the list nine days. You have moved it nine times and each move took two seconds and cost nothing, which is exactly why it has survived nine days. Lying there you can feel the actual shape of it — it is not a scheduling problem, there has been time every one of those days, it is that writing the sentence 'this was on me' has a cost you have been declining to pay each morning. So you get up, which is the only part of this that takes effort, and you do two things to tomorrow's closed page. You write the email as the first line, above everything, and you write underneath it: 'when I sit down with coffee, before I open the inbox, I write that one sentence and send it.' Then back to bed. What has changed is small and specific. The item is no longer competing with a page of easier things at eight in the morning, and the version of you who wrote that line had seen why it kept failing, which the version of you at eight will not have.

When this is worth reaching for

The same item keeps rolling forward, and at some point it stops registering as rolling at all. Deferral systems have that specific blind spot: because moving a task to tomorrow is the standard operation rather than an exception, an item can migrate for a fortnight without ever being noticed as stuck, and only a review that asks directly what was left undone will catch it. That alone is reason to add the review, and the same fixed closing point matters again when days are ending badly — when work finishes and the evening does not feel like it belongs to anyone, or when two a.m. is spent running through fragments of the day. That pattern usually means the day was never closed in either sense, and a fixed closing point does more for it than better daytime scheduling will. It also fits well in the first month of adopting a deferral system, because the review question about what went badly is what surfaces the honest calibration problem early: most people load tomorrow's page with roughly twice what a day holds, and they discover this either through a nightly count or through three weeks of quiet failure.

Where this does not apply

Be careful about the timing, because these two want different physical conditions and forcing them into the same minute can spoil both. The Pythagorean review is done lying down, in the dark, from memory — a deliberately unproductive state — and moving it to a desk with a notebook at nine-thirty in order to make it feed the task list turns a settling practice into an administrative one and can leave you more activated at bedtime rather than less. If you find that happening, split them: close the list at the end of the working day, do the review in bed, and get up only for something that genuinely will not survive the night, which is rarer than it feels. For anyone prone to rumination or to nightly self-criticism, this needs real caution. A structured review at bedtime can become a scheduled hour of self-prosecution, and Seneca's own caveat — examine yourself as a judge would, but without dread — is the operative instruction; if you cannot run it without dread, run it in the morning about the previous day instead, or leave it. The pairing also does not suit work with genuinely unpredictable inbound demand, where a same-day emergency is routine rather than exceptional; the deferral rule assumes most arriving things can wait a night, and in an on-call week they cannot.

What the evidence does and does not support

It is worth separating what is supported from what is inherited here, because these two sit at opposite ends of that range. The strongest experimental footing under either of them is not something Forster or the Pythagoreans claimed. It is the finding that an unfinished intention keeps intruding on attention until a specific plan is made for it, and that making the plan — without doing the task — is enough to release the intrusion. That result, from experiments by Masicampo and Baumeister, is a much better argument for closing tomorrow's page before sleep than the practitioner case reports the task system rests on, and there is separate small-trial work in sleep research suggesting that writing a specific to-do list before bed shortens sleep onset compared with writing about what you finished. The evening review's own support is of a different character entirely: two and a half thousand years of continuous use across Pythagorean, Stoic and later Christian practice, which is testimony at scale rather than measurement, though two components of it do have modern experimental backing — that actively retrieving material from memory strengthens it more than passively reviewing, and that reflecting on a difficult episode from a distanced vantage rather than reliving it from inside produces better judgment. What is entirely unstudied is the specific proposition on this page: that routing the review's output onto a closed next-day list produces more behaviour change than the review alone. Testing it would be straightforward — same nightly review in both arms, one converting findings into a written next-day line and one not, with the outcome being whether the identified behaviour actually changed within a fortnight. No such trial appears to exist.