Skip to main content

Planning

Weekly Review Template

A weekly review is 45 minutes that stops small things from going stale: clear the inboxes, look back honestly, check every project has a next step, then choose three priorities for next week. Copy the template, or start from the weekly review example closest to your week.

Updated 2026-10-27

Copy and adapt

The template

Weekly reviewTemplate

Weekly review, week of {{date}}

Time box: 45 min. Week: [Mon date] to [Fri or Sun date]

Get clear (10 min)

  • Email, messages and paper inboxes to zero
  • Brain dump: everything on my mind that is not written down anywhere
    • [Loose item]
    • [Loose item]

Look back (10 min)

Done: [what finished, shipped or moved] Slipped: [what I planned and did not do] because [honest reason] Energy: [what gave energy, what drained it]

Get current (10 min)

  • Last week's calendar: [follow-ups I owe from meetings and calls]
  • Next two weeks: [deadlines, travel, anything that needs prep]
  • Projects: every active project has a next action
    • [[Project name]]: next action [verb + thing]
  • Waiting for: [what, from whom, since when, nudge or not]

So what (5 min)

  • Stop: [one thing]
  • Keep: [one thing]
  • Change next week: [one thing, small enough to actually do]

Next week (10 min)

  1. [Priority] @due(YYYY-MM-DD)
  2. [Priority] @due(YYYY-MM-DD)
  3. [Priority] @due(YYYY-MM-DD)

Not this week: [what I am deliberately parking, and until when]

5 examples

Examples for different situations

The same structure, filled in for the situations people actually bring to it. Copy the one closest to yours.

1.Product manager, the week a launch slipped

When it fits: Use this when something important missed its date and the review has to separate what went wrong from what simply needs a new date.

Product manager, the week a launch slippedExample 1

Weekly review, week of 2026-10-19

Time box: 45 min, Friday 16:00. Week: Oct 19 to Oct 23

Get clear

  • Inbox from 61 to 0. Three emails became tasks, the rest archived.
  • Brain dump: vendor contract renewal (Nov 30), Dad's birthday gift, the design review I promised Luca, passport renewal before March.

Look back

Done: pricing experiment write-up sent; onboarding screens 1 and 2 through QA; contract copywriter hired. Slipped: Android beta, planned for Thursday, because the payment SDK update broke sign-in on Android 12. Found Wednesday at 18:00. I scoped the release without asking for a run on older devices. Energy: Tuesday's customer calls gave energy. Three hours of status meetings on Wednesday took it.

Get current

  • Last week's calendar: I owe Mei the notes from Tuesday's calls.
  • Next two weeks: board update Nov 3 needs a launch date. I am out Oct 30.
  • Projects:
    • [[Android beta]]: next action, agree a new date with Ravi once the SDK fix is tested
    • [[Onboarding v2]]: next action, QA screens 3 and 4
  • Waiting for: legal on the vendor contract (since Oct 14, nudge Monday); Ravi's estimate for the fix.

So what

  • Stop: scoping releases without a device list.
  • Keep: customer calls on Tuesdays.
  • Change next week: skip Wednesday's status meeting and send a written update instead.

Next week

  1. New beta date agreed and in the board deck @due(2026-10-27)
  2. Device list added to the release checklist @due(2026-10-28)
  3. Call notes to Mei @due(2026-10-26)

Not this week: the Q1 roadmap draft. It waits until the beta ships.

2.Freelance illustrator chasing invoices

When it fits: Use this when you work for several clients, nobody else tracks your money or your scope, and the waiting-for list is where the real risk sits.

Freelance illustrator chasing invoicesExample 2

Weekly review, week of 2026-11-02

Time box: 40 min, Sunday 18:00. Week: Nov 2 to Nov 6

Get clear

  • Email and DMs to zero. Two new inquiries, both answered.
  • Brain dump: quarterly tax payment, new tablet nib, portfolio update, Hollis Coffee wants "one more small change".

Look back

Done: Hollis Coffee bag artwork, round 3 delivered. Fernwood Press cover sketches (4 options) sent Thursday. Slipped: portfolio update, again, because client work filled every slot I gave it. Third week in a row. Energy: the Fernwood sketches. Drained by Hollis, who is now asking for a fourth round on a contract that includes two.

Get current

  • Last week's calendar: I promised Fernwood a call to walk through the sketches. Not booked yet.
  • Next two weeks: Fernwood picks a direction by Nov 13. Estimated tax due Jan 15, but I want the number by Nov 20.
  • Projects:
    • [[Hollis Coffee]]: next action, send the change-order quote for round 4 ($350)
    • [[Fernwood Press]]: next action, book the walkthrough call
  • Waiting for: $4,200 across three invoices. Brightline Studio $1,800 is 47 days overdue (second reminder sent Oct 28, no reply). Hollis $1,600 due Nov 10. Fernwood deposit $800 due Nov 9.

So what

  • Stop: doing extra rounds before the change order is signed.
  • Keep: sending sketches on Thursday so clients reply before the weekend.
  • Change next week: the portfolio gets Monday 8:00 to 10:00, before email.

Next week

  1. Phone Brightline about the overdue invoice, not another email @due(2026-11-09)
  2. Change order to Hollis before any round 4 work @due(2026-11-09)
  3. Portfolio: add the Fernwood and Hollis pieces @due(2026-11-13)

Not this week: the new tablet. It waits until Brightline pays.

3.Nursing student with clinicals and a part-time job

When it fits: Use this when your week is set by someone else's schedule (shifts, classes, rotations) and the review is mostly about where study time actually fits.

Nursing student with clinicals and a part-time jobExample 3

Weekly review, week of 2026-11-02

Time box: 25 min, Sunday 20:00. Week: Nov 2 to Nov 8

Get clear

  • School email and the class group chat caught up.
  • Brain dump: care plan due Friday, pharmacology exam Nov 12, swap a pharmacy shift, scrubs need washing, call Grandma.

Look back

Done: two 12-hour clinical shifts (Tuesday, Thursday). Care plan draft for my patient with CHF. Three pharmacy shifts, 15 hours. Slipped: flashcards. Planned five sessions, did two, because I planned sessions on clinical evenings and I was asleep by 21:00 both nights. Energy: clinical Thursday, when my preceptor let me do the full med pass. Drained by the 40-minute bus ride twice a day.

Get current

  • Last week's calendar: I told Kayla I would send her my cardiac drug chart. Not sent.
  • Next two weeks: pharm exam Thursday Nov 12, 08:00. Care plan final Friday Nov 13.
  • Projects:
    • [[Pharmacology exam 3]]: next action, finish the anticoagulants deck
    • [[Care plan, CHF patient]]: next action, add the evaluation section
  • Waiting for: shift swap approval from Dev at the pharmacy (asked Friday).

So what

  • Stop: planning study on clinical days. It does not happen.
  • Keep: flashcards on the bus. That is where the two sessions came from.
  • Change next week: study blocks Monday, Wednesday and Saturday only, 90 minutes each.

Next week

  1. Two 90-minute pharm sessions (Monday, Wednesday), anticoagulants first @due(2026-11-11)
  2. Care plan final submitted @due(2026-11-13)
  3. Drug chart to Kayla @due(2026-11-09)

Not this week: the scholarship essay. Starts the day after the exam.

4.Backend engineer, a week that went fine

When it fits: Use this when nothing went wrong, the review feels pointless, and that is exactly when long-term work drifts without anyone noticing.

Backend engineer, a week that went fineExample 4

Weekly review, week of 2026-11-09

Time box: 30 min, Friday 15:30. Week: Nov 9 to Nov 13

Get clear

  • Inbox and PR notifications to zero.
  • Brain dump: nothing urgent. Conference talk proposal deadline Dec 1, renew the team's staging certificate.

Look back

Done: rate limiter shipped Tuesday, zero incidents. Reviewed 9 PRs. On-call quiet, one page at 03:10 that was a false alarm. Slipped: nothing planned slipped. But the caching RFC, my one quarterly goal, has had no work for three weeks. Not because of a blocker. Every week had something more urgent and smaller. Energy: good week. Finishing the rate limiter felt like closing a door.

Get current

  • Last week's calendar: nothing owed.
  • Next two weeks: quarter ends Dec 31; the RFC needs review time from two other teams, so a draft by Nov 27 at the latest.
  • Projects:
    • [[Caching RFC]]: next action, write the problem statement (one page)
    • [[On-call alert tuning]]: next action, raise the threshold on the 03:10 alert
  • Waiting for: nothing.

So what

  • Stop: treating a calm week as a week with nothing to decide.
  • Keep: the Friday review even when it is short.
  • Change next week: the RFC gets the first two hours of Monday and Wednesday, calendar blocked.

Next week

  1. RFC problem statement shared with Ana for a first read @due(2026-11-18)
  2. Fix the 03:10 alert threshold @due(2026-11-17)
  3. Talk proposal outline @due(2026-11-20)

Not this week: refactoring the test fixtures. Nice, not needed.

5.Quarterly review for a small bakery

When it fits: Use this when you scale the weekly review up to a quarter: the same sections, plus numbers against targets and one project you decide to drop.

Quarterly review for a small bakeryExample 5

Quarterly review, Q3 2026 (Jul to Sep)

Time box: 2 hours, Saturday Oct 3 after close. Written by: Rosa

Get clear

  • Supplier invoices filed, Q3 sales tax return ready for the accountant.
  • Brain dump: holiday preorder form, oven service contract, a third wholesale café asked for a quote, Jamal's raise.

Look back

Numbers: revenue $86,400 against an $80,000 target. Wholesale now 22 percent of sales (2 cafés). Food cost 31 percent, up from 28. Done: second wholesale account (Pine & Pour) running since July. Weekend hours extended to 15:00. Slipped: online preorders, planned for August, because Lucia left in August and I covered her shifts for five weeks. The oven repair ($3,100) also ate the budget for the preorder system. Energy: wholesale mornings run calmly. Saturdays at 11:00 are chaos.

Get current

  • Q3 goals scored: revenue target hit; preorders not started; hire one baker, done in September (Jamal).
  • Next quarter: holiday orders start Nov 15. Butter contract renews Dec 1.
  • Projects:
    • [[Holiday preorders]]: next action, a paper and email form, not the full system
    • [[Wholesale]]: next action, quote the third café
  • Waiting for: butter supplier's new price (asked Sep 28).

So what

  • Stop: the Tuesday market stall. $310 average revenue for 6 hours of my time.
  • Keep: wholesale. It pays on time and smooths the week.
  • Change next quarter: food cost reviewed monthly, not quarterly.

Next quarter

  1. Holiday preorder form live @due(2026-11-10)
  2. Third wholesale café signed or declined @due(2026-10-31)
  3. Food cost back under 29 percent by December @due(2026-12-31)

Not this quarter: the online preorder system. Revisit in the Q4 review.

What a weekly review is for

Lists go stale. A task written on Monday is half true by Thursday, a project with no next action quietly stops, and a promise made in a hallway is gone by the weekend. A weekly review is the block of time where you put the system back in line with reality, before small drift becomes a missed deadline.

David Allen's Getting Things Done made the habit popular and named its three parts: get clear (empty the inboxes and your head), get current (walk the calendar, projects and waiting-for lists) and get creative (decide what comes next). The template above keeps that order and adds two sections most checklists skip: an honest look back with reasons, and a "so what" step.

How long each part takes

Most weekly review guides say "about 30 minutes" and stop there. Here is where the time actually goes once the habit is running:

  • Get clear, 10 minutes. Inboxes to zero means every item is either done, deleted, or turned into a task. The brain dump is the part people skip and the part that matters most: anything still in your head is not in the system.
  • Look back, 10 minutes. Write what got done and what slipped, each slip with a reason. One line each. This is a reflection, not a report.
  • Get current, 10 minutes. Last week's calendar for follow-ups you owe, the next two weeks for anything that needs preparation, and every active project checked for a next action. Waiting-for items get a date and a decision: nudge or wait.
  • So what, 5 minutes. One thing to stop, keep and change.
  • Next week, 10 minutes. Three priorities with dates, plus a line for what you are deliberately not doing.

The first review takes longer, often 90 minutes, because everything has piled up. By the fourth week the inboxes are smaller and the review settles under 45 minutes.

Turning observations into next week

This is the gap in most weekly review templates: they collect observations and then ask you to "adjust". Adjust what, exactly?

Use the so what step as a filter. Read the Slipped and Energy lines and ask which single change would have prevented the worst of it. Then make that change small enough to happen next week: not "study more", but "study blocks on Monday, Wednesday and Saturday only", as the nursing student example shows. One change per week, checked in the next review, compounds faster than five resolutions.

Then pick the top three. If something on the list has been in the top three for three weeks without moving, it is not a priority; it is a project that needs a smaller next action, or a decision to drop it.

Monthly and quarterly reviews

A monthly review template is the weekly one with two additions: a Numbers line (whatever you track, from revenue to runs) and a short check against the month's goals. Read the four weekly reviews before you start. The useful part of a monthly review is the pattern across them: the same slip, the same drained evening.

A quarterly review template adds one more thing: score every goal as hit, missed or dropped, and stop one project. The bakery example above stops a market stall that earned $310 for six hours of the owner's time. Quarterly is the right altitude for that decision; weekly is too close, yearly is too late.

Common mistakes

  • Reviewing only tasks. The calendar and the waiting-for list hide most of the dropped promises.
  • No reasons on slips. Without a because, the review repeats the same week.
  • Ten priorities. Three is a choice. Ten is a list.
  • Skipping the review in a good week. Calm weeks are when long-term goals drift, as the fourth example shows.
  • Starting fresh every week. Open last week's review first and check its top three. A review that never looks at the previous one is a diary, not a system.

When to use a different template

If you only want to lay out next week's days and hours, the weekly planner template is the tool; run this review first and feed it the top three. If the week is chaos and you cannot see straight, start with the brain dump template and come back. For goals that span a quarter or more, write them in the goal setting template so the weekly review has something to measure against.

Customization tips

  • Give it a fixed slot

    Friday at 15:30 or Sunday at 18:00, the same time every week. A review that floats gets skipped the first busy week, and the second skipped week makes the third one feel too big to start.

  • Keep a 15-minute version for bad weeks

    When the week was chaotic, do only Get clear and Next week. A short review that happens is worth more than a full one you postpone to Monday, and the habit survives.

  • Write the reason next to every slip

    "Slipped" without a because is a guilt list. With a reason, three weeks of reviews show the pattern: the same meeting, the same kind of task, the same evening that never works.

  • Turn it into a monthly review

    Once a month, add a Numbers line (money, hours, workouts, whatever you track) and score the month against the goals you set. Read the four weekly reviews first; the monthly review is mostly what they have in common.

  • Turn it into a quarterly review

    Each quarter, score every goal as hit, missed or dropped, and choose one project to stop. The last example above shows the shape. A quarterly review that only adds work is a wish list.

  • One review for work and life, unless it gets long

    Most people need one review with both. If it runs past an hour, split it: a work review on Friday afternoon and a personal one on Sunday, each with its own top three.

In the app

How to do this in Scribelet

  1. Open Desk Settings, then Templates, tap Add Template, paste the template above and set the category to Planning. Keep {{date}} in the title so each review is dated for you.

  2. For Get current, open the Tasks view. It lists open tasks across all your notes, so you see every checkbox you wrote this week in meeting notes and daily notes, not just the ones you remember.

  3. Write next week's top three as - [ ] Task @due(2026-11-18). They appear on each day's daily note until you tick them, and @remind(2026-11-18 09:00) sends a push reminder in your local time.

  4. Link projects with [[Caching RFC]]. The project note's backlinks panel then lists every weekly review that mentioned it, which shows at a glance how many weeks it has been drifting.

  5. Ask the AI chat "what did I list as slipped in my last six weekly reviews?" It answers from your notes with citations, which makes the monthly review a reading task instead of a memory test.

  6. On Pro, the weekly insights email and the stale checker (which flags notes that need review) are useful inputs for the Get current step.

Templates, template variables and AI generation are documented in Note templates.

Frequently asked questions

What is a weekly review?

A weekly review is a fixed block of time, usually 30 to 60 minutes, to clear loose ends, look back at the week and plan the next one. The idea comes from David Allen's Getting Things Done, which splits it into Get Clear, Get Current and Get Creative. The template above keeps those three and adds a step that turns what you find into one concrete change.

What questions should I ask in a weekly review?

Four do most of the work: what got done, what slipped and why, does every project have a next action, and what are the three things that matter next week. Add "what drained my energy?" if you are tired, and "what am I waiting on from other people?" if your work depends on others.

How long should a weekly review take?

Plan for 45 minutes. The first one can take 90, because the inboxes and the brain dump are full. After a month most people settle between 25 and 45 minutes, and the 15-minute version in the tips above covers bad weeks.

What day should I do my weekly review?

Friday afternoon if the review is mostly work: the week is fresh and you can still send the follow-ups. Sunday evening if it is mostly personal or you want a clean start on Monday. The best day is the one you will not cancel.

What is the difference between a weekly review and a weekly planner?

A weekly review looks back first, then chooses priorities. A weekly planner lays those priorities out across the days and hours. Run the review, then fill in the weekly planner template with its top three.

Can I use the same template for a monthly or quarterly review?

Yes, with two additions: a Numbers line against your targets, and a goals check that scores each goal as hit, missed or dropped. The bakery example above is a quarterly review built from the same sections. For the end of the year, the year in review template adds a month-by-month pass.

A weekly review that remembers last week

Save this template in Scribelet, see every open task from the week in one Tasks view, and ask your notes what has slipped three weeks running. Encrypted, free to start.

Free plan, no credit card. See pricing

Planning

Weekly Planner Template

One page for the week: what carried over, three outcomes, the dates that cannot move, a short plan per day and a ten-minute review on Friday. It is plain Markdown, so it pastes into any notes app or document and prints from there.

Planning

Goal Setting Template

Most goal templates are a page you fill in once in January. This one is a chain: a few life goals, three for the year, one milestone each per quarter, and three weekly goals that move them. Copy it whole, or use only the level you need today.

Journals

Year in Review Template

A personal year in review is built from evidence, not memory: read the year back month by month, then write what went well, what did not, who mattered and what changes next year. Copy the template, or start from the example closest to the year you had.

Planning

Brain Dump Template

A brain dump only helps if the list goes somewhere afterwards. This template is two parts: fifteen minutes of writing everything down without order, then a sort that sends each item to a task, a decision, a project, someday, or the bin. Copy it, or start from the example closest to your week.

Work

OKR Examples and Template

An OKR is one qualitative objective and three to five key results with a baseline and a target. Most examples stop at the first day of the quarter. These five go further: weekly check-ins, a personal OKR, and a quarter scored honestly at the end. The template keeps all of it in one note.

Journals

Daily Journal Template

Seven minutes a day: two in the morning to name what matters, five in the evening to write what happened and what you noticed. Copy the daily journal template, or read the five entries below to see it filled in on very different days.

We use cookies for analytics to improve your experience. Learn more