Build a Weekly Review Template You Will Still Be Using in Three Months
For the review you designed carefully and then skipped almost every week. Sizes it to a 25 minute slot with a minute count per section, caps it at seven questions, and hands you a 10 minute version for the weeks that went badly. Opens with three questions, sweeps only the places that genuinely pile up for you, and repeats two identical pattern fields so the habit you keep repeating shows up in writing. Reads like a reset, not a report card, with a rule for the weeks you skip: there is no review backlog. If the review keeps surfacing the same stalled goal, revisit it with our SMART goal builder instead of letting it sit. Whatever the review flags as unprotected time, block it properly next week with our deep work session planner.

You are a personal systems designer. Your job is to build ONE weekly review template I will still be running in three months, and then hand it to me as something I can paste straight into my notes app or copy onto paper. WHO YOU ARE TALKING TO: I have built a weekly review before. It was thorough, it looked great, and on most weeks I would just skip it. The problem was not laziness. Whenever I thought about my weekly review I pictured it taking ages and being no fun at all, so I found something else to do instead. Then I felt guilty about skipping it, which made opening it the next week even less likely. No matter how perfect the system looks in theory, if I am not using it at all then it is useless. Two other things you need to handle: - I am slightly afraid of the review. If I look honestly at where my attention went last week I expect to be disappointed. A template that reads like a performance report written by a manager I do not like will get skipped. - A quick glance over the week does not work either. I have done that, and I just kept repeating the same bad habits, because nothing was ever written down long enough for me to spot a pattern. HARD RULES: - The finished review must fit the time I give you. If I do not give you a number, assume 25 minutes. Put the timebox at the top of the template and a rough minute count on every section. If the sections do not add up to the timebox, cut a section rather than shaving the estimates. - Maximum 7 questions or fields in the whole weekly template. A long questionnaire is exactly what killed my last one. - No open-ended journalling prompts. Nothing like reflect on your growth or describe your ideal week. Every question must be answerable in one line or a few bullets, either from memory or from something I can look at, like a calendar or a task list. - One-touch: if a section makes me open something, I deal with what is in there once and never come back to it later in the same review. - This is a week, not a life review. Anything that genuinely needs an hour of introspection goes into a short monthly or quarterly add-on at the end, or gets cut. - Never invent statistics, studies, or claims about what percentage of people run reviews. No productivity quotes and no motivational closing paragraph. - Ask me questions five at a time at most, then stop and wait for my answers. STEP 0 - ASK BEFORE YOU BUILD ANYTHING: Ask up to five short questions, then stop. Aim them at: - Where the review will live, and what format I need it in: markdown for a notes app, plain text, or short enough to write by hand in a planner. - What I actually want out of it: catching dropped balls, planning next week, spotting repeated patterns, or just feeling less out of control. Make me name a first priority, because these build different templates. - Which places stuff piles up for me that a review could sweep: calendar, task list, inbox, notes inbox, downloads or desktop, open loops waiting on other people. - Whether this covers work, personal life, or both, and whether I have ever actually managed to sustain the personal side. - What killed my last attempt, and which day and time I could realistically sit down. STEP 1 - NAME THE FAILURE MODE, THEN SIZE THE REVIEW TO IT: In three lines, tell me which failure mode I am describing: too long to face, too vague to answer, too exposing to open, or no fixed slot in the week. Then set the size: - MINIMUM, about 10 minutes, the version for a bad week. - STANDARD, the timebox I gave you, the default you build. Build STANDARD in full, and always give me the MINIMUM version too, because that is the one I will actually run when the week has gone badly. Do not offer a third longer version. STEP 2 - THE CORE THREE, ALWAYS FIRST: The template opens with three questions in bullets and nothing else: what went right, what went wrong, what happens next. Word them in my language, not in coaching language. State in the template that if I only ever fill in this part, the review still counted. STEP 3 - THE SWEEP, AS A TABLE: Give me the sweep as one table, maximum five rows: Where I look | What I am looking for | The one action allowed | Minutes Rules you obey: - Only places I told you actually pile up. No row for a system I do not use. - Exactly one allowed action per row, written as a verb I can finish in seconds: file it, delete it, write it into next week, or send one message. No row may allow open-ended reading or reorganising. - If a place has no clear single action, drop the row instead of inventing one. - Put the minute cost on each row and keep the table total under half the timebox. STEP 4 - CARRY-OVER AND THE WEEK AHEAD: Four short fields at most: what is still hanging over from last week, anything due in the next 14 days, what I am waiting on from someone else, and next week's commitments capped at three. If I name more than three commitments, the template tells me to pick three and park the rest rather than carrying a list of ten into Monday. STEP 5 - THE PATTERN LINE: This is the part a mental skim cannot do, so it matters. Pick at most two fields whose only purpose is to be compared across weeks, chosen from: biggest time-waster, what took longer than I expected, best day and why, the unplanned thing I ended up doing, what is not working in my system, or a 1 to 5 rating of the week with one line on why. Keep the wording identical every week so the entries stack into a readable column. Then add the read-back instruction: every fourth review, read only the last four pattern lines and write one sentence naming the repeat you see. Make clear I am looking for the habit, not scoring myself. STEP 6 - PERMISSION WORDING, INSIDE THE TEMPLATE: Write four lines maximum that live in the template itself, so they are there every time I open it. They should make it safe to look: this is a reset, not a report card. Nobody else reads this. A bad week is information, not a verdict. Noticing where my attention went is the entire point, and I do not owe anyone a justification for it. Plain sentences. No therapy language, no exclamation marks, no praise for showing up. STEP 7 - THE SKIPPED WEEK RULE: Write the rule for when I miss one week, or three. It must say plainly that I never catch up on missed reviews, that there is no such thing as a review backlog, and that a gap does not reset anything I already set up. The recovery move is to open this week's review, run the MINIMUM version, and stop. One short paragraph in the template, not a lecture. STEP 8 - MAKE IT A REAL APPOINTMENT: Based on the day and time I gave you, propose one specific fixed slot, deliberately small, so it stops feeling heavy. Name the day, the start time and the end time. Tell me what to do if I miss the slot: same day later if possible, otherwise it becomes the minimum version, and never a rescheduled two hour session. Then give me the exact thing to do in the next two minutes to book the first one. STEP 9 - HAND ME THE TEMPLATE: Output the final template as one clean copy-paste block in the format I asked for, in the order I will fill it, with the timebox at the top, the minute count on each section, headings and blank fields only, and no explanations inside the block. Put the MINIMUM version underneath it as a second short block. Then, outside the blocks, at most six lines: what to do in the first 60 seconds of the first review, and which section to delete first if the whole thing starts feeling heavy again. Then stop. No summary, no encouragement, no offer to build me a tracker. MY INPUTS Where the review will live and the format I need: [E.G. NOTION, OBSIDIAN, APPLE NOTES, PAPER PLANNER] Minutes I will realistically give it: [NUMBER, OR WRITE 25] What I mainly want out of it: [DROPPED BALLS / PLANNING NEXT WEEK / SPOTTING PATTERNS / FEELING LESS OUT OF CONTROL] Places stuff piles up for me: [CALENDAR / TASKS / INBOX / NOTES INBOX / DESKTOP / WAITING ON PEOPLE] Work, personal, or both: [WORK / PERSONAL / BOTH] What killed my last review habit: [DESCRIBE OR WRITE NEVER HAD ONE] Day and rough time I could sit down: [E.G. FRIDAY LATE AFTERNOON, SUNDAY MORNING] Anything I do not want to be asked about: [DESCRIBE OR WRITE NOTHING] Start at Step 0. Ask your questions, then stop.
How to use this chat prompt
Paste it directly into a new chat, replace anything in [BRACKETS] with your context, and send. Re-use it whenever the task comes up, or save it as a text-expander snippet.
Example output
Obsidian in markdown, 25 minutes on Friday afternoon, work and personal, after a previous 20 question review that got skipped most weeks.
Weekly Review Template: 1. Review goals 2. Review calendar 3. Process all inboxes 4. Review project list 5. Review someday/maybe list 6. Reflect on wins 7. Reflect on lessons learned 8. Plan next week.
Ask yourself: what did I accomplish? What did I learn? Where do I want to grow? What kind of person am I becoming?
Block out time in a quiet place each week and be honest with yourself about the answers.
FAILURE MODE: too long to face, and no fixed slot. Sized to 25 min, Friday 16:00 to 16:25.
THE CORE THREE (8 min), bullets only: what went right / what went wrong / what happens next. Fill only this and the review still counted.
THE SWEEP (10 min): Where I look | What I am looking for | The one action allowed | Min
Calendar, last 7 and next 14 days | missed things and due dates | write it into Next Week or drop it | 4
Obsidian inbox | unfiled notes | file or delete, no reading | 3
PATTERN LINE (4 min, same wording every week): biggest time-waster was ___ / week rated 1 to 5 because ___. Every fourth review, read the last four lines and name the repeat.
STANDING RULES: this is a reset, not a report card. Nobody else reads this. A bad week is information, not a verdict.
SKIPPED A WEEK: open this week's, run the 10 minute version. There is no review backlog.
FAQ
Frequently asked questions
I have built a weekly review before and skipped it most weeks. Why would this one be different?
Because skipping is treated as a design fault, not a discipline problem. The template is sized to a fixed timebox with minute counts per section, capped at seven questions, and it ships with a 10 minute minimum version for the weeks you cannot face the full one. A review you run badly beats a perfect one you never open.
How long should a weekly review actually take?
It defaults to 25 minutes and refuses to overflow: if the sections do not add up, it cuts a section instead of pretending each one takes less time. Give it any number you like, but it builds toward a small fixed slot rather than an open-ended Sunday session, because the heavy version is the one that gets skipped.
What if I am honestly a bit afraid of looking at where my week went?
That gets handled in the template itself rather than ignored. Step 6 writes four standing lines into the top of the review, saying plainly that this is a reset and not a report card, that nobody else reads it, and that a bad week is information rather than a verdict. There is also an input for anything you do not want to be asked about.
I already glance back over my week. Why write any of it down?
A mental skim tends to repeat the same bad habits, because nothing sits still long enough to become a pattern. The pattern line fields are worded identically every week on purpose, so after four reviews you can read that one column and name the thing that keeps happening.
What do I do if I miss a week, or three?
You never catch up. The skipped week rule says there is no review backlog, a gap does not reset anything you already set up, and the recovery move is to open this week's review, run the minimum version, and stop.
Should the review also set next week's priorities?
Yes, but capped at three commitments so Monday does not inherit a list of ten. If you want those commitments tied to something longer running, turn a vague goal into a SMART goal with milestones first and let the review check progress against it instead of reinventing the plan every Friday.
Keep going
What's next
Guide
Building Sustainable AI-Driven Workflows
Most AI fatigue isn't caused by AI. It's caused by too many tools and no boundaries around any of them. Here's how to consolidate the stack, schedule the usage, and keep the thinking that's yours.
Prompt
Turn a Vague Goal Into a SMART Goal and Milestones You Can Start in 15 Minutes
For goals that are either too fuzzy to plan from or so big they read like a mountain with no top. Translates 'be happier at work' into something you could actually point at, sets the measure as a minimum, target and stretch band so 9 out of 10 counts as 9 rather than failure, caps the plan at five milestones, and ends with one first step small enough to do today. Includes a renegotiation clause for when a reorg or a crisis makes the plan stale. Once the milestones exist, our weekly review template is where you actually check progress against them. If the milestone list is fighting your whole task pile for attention, sort the pile first with our Eisenhower matrix prompt.
Article
The AI Productivity Paradox Is Mostly a Prompting Problem
Studies keep finding AI adds work instead of saving it. A surprising share of that hidden tax isn't the model's fault - it's how we prompt.