- A copy-ready five-step end-of-day checklist
- Carry-forward rules that stop unfinished work from piling up invisibly
- When to run the review and what tools it needs (almost none)
- How daily reviews roll up into a cleaner weekly plan
This page is the practical half of a pair. The Daily Review Method explains why a daily review works and the three questions at its core. Here you get the implementation: the exact checklist, the rules for handling unfinished work, and the routine that makes it survive busy days. Read the method for understanding; use this page to actually run the practice tomorrow.
System overview
The system has three moving parts. Keep all three lightweight — the whole point is a routine so small it never gets skipped.
- A fixed checklist you run in the same order every day.
- Carry-forward rules that decide, in advance, what happens to unfinished tasks.
- A weekly roll-up that turns five daily reviews into planning material.
The end-of-day checklist
Run these five steps, in order, in whatever task tool you already use. The order matters: you close today before you open tomorrow.
Carry-forward rules
The hardest part of any review isn't logging progress — it's deciding what to do with what you didn't finish. Left to daily judgment, unfinished tasks quietly pile up and rot at the bottom of the list. Carry-forward rules make the decision once, in advance:
| Situation | Carry-forward rule |
|---|---|
| Task carried 1–2 days | Reschedule it to a specific day; that's normal slippage. |
| Task carried 3+ days | Force a decision: reschedule with a real slot, shrink it, delegate it, or drop it. |
| Task keeps getting deprioritized | It probably isn't important. Delete it honestly instead of guiltily re-listing it. |
| Waiting on someone else | Move to a separate "waiting" list with a follow-up date, so it stops cluttering today. |
A task you've rewritten onto your list five times isn't a productivity problem — it's a decision you keep avoiding. The carry-forward rule for 3+ days exists to force that decision instead of letting it haunt you indefinitely.
Timing and tools
- Timing: the last ten minutes of your workday, anchored to a shutdown cue so it becomes automatic.
- Tools: your existing task manager or a plain notes file. Keep a persistent "waiting" list and a place for tomorrow's anchor. Nothing specialized required.
- Friction: if any step feels heavy, cut it. A five-minute review you always do beats a fifteen-minute one you abandon in week two.
Rolling up to weekly planning
Because each daily review already recorded what moved and what stalled, your weekly reset has honest data instead of hazy memory. On your weekly planning day, skim the week's reviews and look for signals: which anchors got done, which tasks kept slipping, where blockers recurred. Feed those into the weekly planning system so the next week corrects for what actually happened.
A filled-in example
Here's one engineer's actual review, to show how brief it is:
- Moved: shipped the auth bugfix; unblocked the API review.
- Open: migration script half-written; docs update owed.
- Blocked: deploy pipeline — waiting on infra team (pinged, follow up Thu).
- Tomorrow's anchor: finish and test the migration script (9:00 block).
- Reset: inbox to zero, branches pushed, desk cleared.
Six lines, about seven minutes. But the migration now has a protected slot, the infra dependency is tracked instead of forgotten, and the evening is genuinely free because nothing is left silently running.
Common mistakes to avoid
- No carry-forward rules. Without them, stale tasks accumulate until the list is untrustworthy.
- Skipping the reset step. Leaving a messy inbox and open tabs blurs the boundary between work and rest.
- Over-engineering the tooling. A fancy review template you dread is worse than five plain lines you'll actually write.
- Re-planning the week nightly. That's the weekly system's job. Keep the daily review to closing today and anchoring tomorrow.
- Run a fixed five-step checklist: log what moved, capture loops, flag blockers, set tomorrow's anchor, reset the space.
- Decide carry-forward rules in advance so unfinished work never piles up silently.
- Keep it under ten minutes with tools you already use.
- Roll the week's reviews into your weekly plan for decisions based on reality, not memory.
Frequently asked questions
What should a daily review checklist include?
A practical daily review checklist has five steps: record what you moved forward, capture open and waiting-on items, note anything you're blocked on, decide tomorrow's single anchor task, and clear your workspace and inbox to a defined state. Keeping it to five steps means it fits in under ten minutes and actually gets done every day.
What is a carry-forward rule?
A carry-forward rule is a predefined decision about what happens to unfinished tasks at the end of the day, so you don't re-litigate each one. For example: a task carried more than three days must be rescheduled, delegated, shrunk, or dropped. Carry-forward rules stop stale tasks from silently accumulating and keep your list honest.
How long should the daily review system take?
Between five and ten minutes once it's a habit. The checklist is deliberately short and the carry-forward rules are decided in advance precisely so the review stays fast. If yours regularly runs longer, you are probably re-planning your week inside a daily review, which is a sign the two horizons have blurred.
Do I need special software for a daily review system?
No. The system works in any task manager or a plain notes file, and simpler is usually more durable. What matters is that the checklist and your carry-forward list live somewhere you already trust and open every day, not that the tool has special review features. Use what you already have.