Weekly Review Template
Weekly review template: start here
A weekly review template closes the loops your week leaves open: process the inbox down to zero, reflect on what actually shipped (and what didn’t, and why), then set next week’s priorities and block time for them. Thirty to forty-five minutes, once a week, at the same time every week. That consistency is what makes it work.
Copy the template below, fill it in, and adjust it until it fits how you actually work.
—
The template
Here’s the exact structure I’ve settled on after more than a decade of working fully remote. The left column is what goes in each section. The right column shows a filled-in example so you can see what “done” looks like — the entries are illustrative, not from any real project, so adapt the substance to your own work.
| Section | What to fill in | Example (filled in) | |—|—|—| | 1. Clear the decks | Inbox processed to empty — every message gets deleted, delegated, done now, or turned into a task. Calendar checked for next week: stale meetings declined, duplicate holds removed. | Inbox: 22 → 0. Flagged two emails that need answers from other people. Declined a Thursday status meeting I don’t need to attend. Removed the placeholder block from last Tuesday that never got used. | | 2. Review the week that was | Three quick lists: what shipped (finished or meaningfully moved forward), what slipped (and the actual blocker, not just “didn’t get to it”), and how your energy ran (when you were sharp, when you were fog). | Shipped: sent the Q3 report draft, closed all support tickets, onboarded the new tool. Slipped: didn’t start the vendor comparison — brief was still vague, kept deferring it. Energy: sharpest before noon; Thursday afternoons were a write-off. | | 3. Current projects scan | One line per active project: where it stands, what’s the next physical action, is anything stuck. This is where you catch the project you haven’t touched in two weeks. | Q3 report: draft sent, awaiting feedback, next step is revisions when comments land. Vendor comparison: stuck — blocked on a clear brief, need to ask the requester for scope. Team onboarding: done, remove from active list. | | 4. Next week’s plan | Top 3 priorities (no more), calendar blocks that protect time for each one, and a risk lookahead — which day is already overloaded, what you’re quietly assuming will “figure itself out.” | Top 3: finish vendor comparison, revise Q3 report, prep the client call deck. Blocks: two 9–11am deep work blocks, Tuesday and Wednesday. Risk: Thursday has three meetings stacked — move any overflow to Friday morning, don’t let it eat the deck prep. |
Two things worth noting about this structure. First, “clear the decks” comes first for a reason: it’s nearly impossible to reflect on your week while unread email is nagging at the back of your brain. Second, the projects scan is the section most people skip, and it’s the one that catches the most problems — the stuck project that’s been stuck for a month doesn’t announce itself any other way.
If you want to see what a full, real-feeling review looks like written out in prose rather than table form, the flagship post on this site walks through a 7-part weekly review with filled-in work review examples — it covers some angles this template compresses, like quality checks and choosing a single behavioral adjustment for next week.
—
How to run the review (step by step)
The template tells you what to fill in. This is the part that determines whether you actually do it.
Pick your slot: Friday afternoon vs. Monday morning
Both work. They produce different reviews.
Friday afternoon is the classic, and it has a real advantage: the week is fresh. You remember what slipped on Wednesday and why. The downside is that by 3pm on a Friday, most of us are done. If you schedule it then anyway, you’ll either rush it or skip it — and skipped reviews compound into the habit quietly dying by week four.
Monday morning catches you rested, and the plan you build is right next to the week it applies to. But there’s a cost: you’ve lost the details. By Monday, “why didn’t I start the vendor comparison” has blurred into “eh, busy week,” and vague causes produce vague fixes. Monday reviews also compete with the week’s actual work — there’s always something urgent-looking that can bump them.
My honest take: try Friday first, earlier than feels natural — right after lunch, not end of day. If Friday genuinely doesn’t hold, Sunday evening works for a lot of people who like a quiet reset before the week starts. The specific slot matters far less than it being the same slot. A review that moves around every week is a review that stops happening.
Set the environment
One place to write — a single doc, a notebook, whatever you’ll actually open next week. Phone face down, Slack closed. Thirty to forty-five minutes is the realistic budget for the full version; you’re not writing a performance appraisal, you’re closing loops.
The 10/15/15 split
I break the session into three chunks that map to the template’s halves:
- Minutes 1–10: Clear the decks. Inbox to zero, calendar cleanup, nothing analytical. This is the mechanical warm-up. It earns its slot because it removes the background noise the rest of the review has to fight through.
- Minutes 11–25: Look back. Review the week that was — shipped, slipped, energy — and scan every active project one line at a time. This is the reflective half. Name actual blockers. “Didn’t get to it” is not a cause; “meetings filled every morning” is.
- Minutes 26–40: Look forward. Top 3 priorities, calendar blocks for each, risk lookahead. Then close the doc and don’t reopen it until next week.
If you’re running long, it’s almost always the middle section. Trim the projects scan to one line per project rather than trimming the forward-looking part — the plan is what pays next week’s rent.
If your calendar keeps collapsing under whatever you plan into it, the review pairs naturally with the time blocking tips on this site — the “calendar blocks” row in the template is where the two systems connect, and that post covers how to make blocks that bend instead of snap.
—
Adaptations
The full version is worth doing, but not every week is a full-version week. Three variants that keep the habit alive when the full session doesn’t fit.
The 15-minute version
When the week has gone sideways and forty minutes isn’t happening, run the compressed loop: clear the inbox (5 minutes), jot one line each for shipped and slipped (5 minutes), pick your single top priority for next week and block time for it (5 minutes). That’s it. No projects scan, no energy notes. It’s a third of the value of the full review for a quarter of the time, which is still a good trade — and a kept lightweight habit beats a lapsed thorough one. I’d argue this is the version to start with if you’ve never done weekly reviews at all; expand once the slot is protected.
The solo-worker version
If you work fully alone — freelancer, solo operator — two adjustments help. First, the “clear the decks” section matters less and the “review the week that was” section matters more, because nobody else is tracking your progress but you; the shipped/slipped lists are your only source of evidence against the story in your head (“busy week” usually dissolves under five minutes of actual listing). Second, add one question to the projects scan: what am I avoiding? Solo workers don’t have a manager noticing the stalled project, so the review has to do that job explicitly. Client-based solo workers should also check next week’s calendar against promised delivery dates during the risk lookahead — that’s the single most common silent failure I’ve seen in that setup.
The team-lead version
If you lead people, add a people-scan to section 3: one line per direct report — who’s waiting on something from you, who had a rough week, where did communication lag. Then a second pass on section 4: which of your top 3 priorities depends on someone else, and did you actually ask them, in writing? The most common lead-specific failure is planning the week as if your team will automatically be available and aligned — the risk lookahead should include the asks that need to happen Monday morning for any of the priorities to be realistic. Keep the review private; it’s your preparation, not a status report anyone sees.
—
Common failure modes and fixes
Three ways this habit typically dies, and what to do about each.
Skipping it when you’re busy
This is the big one, and it’s precisely backwards. When the week is chaotic is exactly when the review pays most — that’s when loops are open, priorities are undefined, and next week is about to inherit the mess. A calm, controlled week barely needs reviewing. Fix: pre-commit the slot as a recurring calendar block with a notification, and make the 15-minute version the official fallback rather than a reason to skip. The rule I use: it’s never “no review,” it’s either full or 15 minutes. That’s the whole decision tree.
Turning it into status theater
This one is subtle, and it mostly shows up once your review starts feeling polished. Symptoms: writing entries in language you’d be comfortable if a manager read, padding the shipped list with things you merely touched, spending twenty minutes formatting instead of two minutes thinking. A review that performs productivity isn’t reviewing anything. Fix: keep it in a private doc nobody sees, write the slipped list first if you notice yourself inflating the wins, and check whether any sentence in your review would survive being read aloud to a colleague. If you’re choosing words for their optics, delete and restart blunter.
Over-planning
The template asks for a top 3. The failure mode is a top 11, plus sub-items, plus a new productivity system you redesign mid-review. Over-planning feels like diligence, but a plan for a week with no slack in it is just next week’s disappointment, pre-scheduled. Fix: hard rule of three priorities, and the risk lookahead has to be honest — if Thursday is already full, the plan must account for that, not assume a heroic week. Anything beyond the top 3 goes on a someday list, not into the week. If this keeps happening, the time management hub on this site covers the underlying capacity question — weekly reviews surface it, but the fix is structural, not motivational.
—
Related comparisons and reviews
If you’re deciding how this fits alongside the other systems on the site:
- The weekly review walkthrough is the deeper companion to this template — same philosophy, more worked examples, including the quality-check and one-adjustment steps this page compresses.
- The time blocking tips post handles the daily half of the equation: the review sets the weekly plan, blocks protect it day to day.
- For the broader context on where a weekly review sits among planning and focus systems, start at the time management hub, and the main site at The Remote Innovator has the full library of remote-work systems.
—
Check before you buy
The GTD weekly review is the original practice this template adapts.
Frequently asked questions
What should I know about weekly reviews?
A weekly review is a short, recurring session — usually 30–45 minutes — where you process loose ends, reflect on what actually got done, and set the coming week’s priorities. It’s not a performance appraisal and nobody sees it. The two things that make it work are consistency (same slot every week) and honesty (naming real blockers, not
How do I choose the right weekly review template?
Pick the one whose sections map to your actual failure points. If your problem is dropped commitments, you need a projects-scan section. If your problem is chaotic mornings, you need the calendar-blocks section. Avoid templates with more than five or six sections — you won’t sustain them. The test isn’t whether a template looks thorough on day one; it’s whether you’re still filling it in after a month. Choose simple, run it four weeks, then add or cut sections based on what your reviews keep telling you.
What are the common mistakes with weekly reviews?
The three most common: skipping the review during busy weeks (exactly when it’s most valuable), turning it into status theater — polished, flattering entries instead of honest reflection — and over-planning, where a “top 3” quietly becomes eleven priorities plus a redesigned productivity system. Underneath all three is the same root: treating the review as a performance of organization rather than a tool for it. Keep it private, keep it blunt, keep it short, and let the plan fit the week you actually have.