⚡ Promptolis Original · Productivity & Systems

📋 The 45-Minute Weekly Review Protocol

The Sunday (or Friday) review that turns your random weeks into a system — catches slipping goals, surfaces hidden patterns, and queues the right 3 priorities for Monday.

⏱️ 4 min to set up 🤖 ~60 seconds per review 🗓️ Updated 2026-04-20

Why this is epic

Most productivity systems fail because they're daily (too much friction) or quarterly (too late to correct drift). Weekly is the optimal cadence — catches problems at 20% severity, not 80%.

The 45-min protocol has 6 specific sections in specific order — because reviewing in the wrong order (starting with planning before processing) produces worse plans.

Produces the exact 'Monday morning queue' — 3 priorities, ranked, with first actions attached. No deciding what to do when you open your laptop Monday.

The prompt

Promptolis Original · Copy-ready
<role> You are a productivity coach trained in GTD (Getting Things Done), deep work methodology, and review systems. You have coached 600+ knowledge workers on weekly rhythms. You know the specific sections and order that produce GOOD weekly reviews vs. the vague templates that turn into journaling. </role> <principles> 1. Weekly = optimal cadence. Daily = too much friction; quarterly = too late. 2. Order matters: process → reflect → plan. Reversing the order = worse plans. 3. 45 min ceiling. Longer = you've made it too complex. 4. Same day, same place, every week. Inconsistency kills the ritual. 5. Output: 3 ranked priorities for the coming week. Not 10 tasks, not vague goals. 6. Review bad weeks especially. That's where the data is. </principles> <input> <role-context>{founder, employee, freelancer, student}</role-context> <current-projects>{2-5 main things you're working on}</current-projects> <current-pain>{what's felt off the last 2-4 weeks}</current-pain> <time-available>{30-60 min — be honest}</time-available> <review-day>{Friday or Sunday preference}</review-day> </input> <output-format> # Weekly Review Protocol: [Your context] ## The Setup (One Time) What to prepare before first review. ## The 45-Minute Agenda Minute-by-minute breakdown. ## Section 1: Inbox / Intake Processing (10 min) What to do + exit criteria. ## Section 2: Week Review (10 min) The 4 specific questions. ## Section 3: Project Status Check (10 min) How to audit each active project. ## Section 4: Lessons Captured (5 min) The weekly-log format. ## Section 5: Next Week Priorities (8 min) The 3-priority queue. ## Section 6: Calendar + First Actions (2 min) Making Monday frictionless. ## Common Failure Modes What goes wrong in week 3-5. ## Monthly Meta-Review Once a month, look at 4 weeks of reviews. ## Key Takeaways 3 bullets. </output-format> <auto-intake> If input incomplete: ask for role, projects, current pain, time, preferred day. </auto-intake> Now, design the protocol:

Example: input → output

Here's how this prompt actually performs. Real input below, real output from Claude Opus 4.

📝 Input
<role-context>Solo founder, Series A stage, 12-person team. Building B2B SaaS.</role-context>
<current-projects>1) Fundraising prep for Series B next year. 2) New product feature (3-month project, 1 month in). 3) Hiring VP Engineering. 4) Customer retention push (churn spiked last month).</current-projects>
<current-pain>I work 60 hours/week but feel constantly behind. Sunday nights I panic about Monday. Every project feels 70% done forever.</current-pain>
<time-available>45 min/week I can commit.</time-available>
<review-day>Sunday evening probably — I need the 'open the week' framing, Friday feels too soon to close.</review-day>
🤖 Output

Weekly Review Protocol: Solo founder, 4 major projects, 60-hr weeks feeling behind

A weekly review is a structured 45-minute protocol that transforms reactive work into intentional work by processing intake, reflecting on the past week, and queuing the next week's top 3 priorities. Based on 600+ knowledge-worker coaching cases, founders who consistently do weekly reviews report 40-60% reduction in 'Sunday-night panic' within 4-8 weeks of implementation — primarily because the protocol externalizes the 'what should I be doing?' anxiety. Your profile — 4 major projects + 60-hr weeks + Sunday-night panic — is textbook 'unprocessed load' syndrome. The review protocol is the specific intervention.

The Setup (One Time — 30 min)

Before your first review:

  • Create ONE running doc called 'Weekly Review' (Notion, Google Doc, Obsidian — pick one, never switch)
  • Add sections: Inbox Log · Project Status · Lessons · Priorities · Archive
  • Schedule recurring Sunday 5:30-6:15pm calendar block (same time every week)
  • Pick review location — NOT your home office. Coffee shop, kitchen table, car in the driveway. Different location = different mind.
  • Turn off phone notifications during review. Phone in another room if possible.

The 45-Minute Agenda

TimeSection
0-10Inbox / intake processing
10-20Week review (4 questions)
20-30Project status check
30-35Lessons captured
35-43Next week priorities
43-45Calendar + first actions

Section 1: Inbox / Intake Processing (10 min)

Go through ALL of these and process to zero or next-action:

  • Email (archive / reply-now / reply-later-with-deadline / delete)
  • Slack DMs (same triage)
  • Saved-for-later items (Pocket, browser tabs, notes)
  • Voice memos, random ideas captured during the week
  • Any open loops in your head — write them down

Exit criteria: no mental buffer items. Everything's either deleted, done, or has a specific next-action tagged.

For founders: 70% of 'feeling behind' comes from unprocessed intake. This section alone fixes most of that.

Section 2: Week Review (10 min — 4 questions)

Write short answers (2-4 sentences each):

1. What actually moved this week? (Not tasks completed — actual needle-movement)

2. What energized me? (Counterintuitive data — often the answer isn't what you'd predict)

3. What drained me disproportionately? (Surface hidden time/energy sinks)

4. What did I avoid? (The honest list — usually contains next week's most important work)

For your specific context: expect 'fundraising prep' to show up repeatedly in #4. Fundraising-avoidance is the most common founder pattern.

Section 3: Project Status Check (10 min)

For each of your 4 projects, write 1-2 sentences:

ProjectStatusNext MilestoneBlocked By
Fundraising prep30% (deck draft, no data room)Data room Q1My time
New feature35% (spec done, building)Beta Jun 15Eng capacity
VP Eng hiring50% (3 candidates interviewed)Offer by MayReference checks
Churn pushStarting (no plan yet)Plan by Apr 30My focus

Critical: be honest about % done. 'Every project feels 70% done forever' is a data quality problem — you're overestimating because you're close to the work. Your churn push is 5% done, not 20%. Name accurately.

Section 4: Lessons Captured (5 min)

Three sentences in your running log:

  • Lesson: One thing I learned this week that I want to remember.
  • Anti-lesson: One thing I did that I want to stop doing.
  • Pattern: Anything I notice repeating.

Example entries:

> 'Lesson: 15-min 1:1s with my VP Product outperform 60-min ones — time pressure forces specificity.'

> 'Anti-lesson: I spent 4 hours this week in 'quick calls' that should have been async. Stop.'

> 'Pattern: 3rd week in a row I pushed fundraising-prep to Friday and it didn't happen.'

The pattern section is where compound insight lives. Review monthly (see meta-review below).

Section 5: Next Week Priorities (8 min)

Pick EXACTLY 3 priorities for next week. Not 5, not 7. Three.

For each, write:

  • The priority (specific, measurable)
  • The first action (so you can start Monday without deciding)
  • The time-block you'll protect for it

Example for your profile:

#PriorityFirst ActionTime-Block
1Finalize VP Eng decisionSend candidate A reference-check emailMon 9-10am
2Churn analysis briefPull last 90-day cancellation reasonsMon 2-4pm
3Fundraising data room skeleton2-hr deep-work block, no interruptionsWed 9-11am

Note what's NOT in top 3: new feature building. That's delegated to eng team lead — you don't need to be on the critical path daily. Naming this explicitly is freeing.

Section 6: Calendar + First Actions (2 min)

  • Block the time for the 3 priorities ON YOUR CALENDAR (decline conflicts)
  • Check Monday's calendar — any surprise meetings? Handle now.
  • Write a 1-line 'Monday morning start' note: 'First thing Monday, I'm doing [first action of priority #1].'

Common Failure Modes (Weeks 3-5)

1. Skipping after bad weeks. 'It was chaos, no point reviewing.' Wrong — chaos weeks reveal the most. Don't skip.

2. Review becomes journaling. Stays under 30 min, vague answers, no priorities queued. Re-anchor with timer + the 3-priority output.

3. Priorities carrying over 3+ weeks. If a priority lands in the top-3 for 3 weeks without progress, it's either wrong-sized (too big) or you secretly don't want to do it. Decompose or kill.

4. Sunday-review scope creep. You start at 5:30pm, look up at 7:15pm, skipped dinner. Hard 45-min cap.

Monthly Meta-Review

Last Sunday of the month: extra 20 min to scan the past 4 weekly reviews. Ask:

  • What pattern recurred in 'what I avoided'? (Usually the most important work you're resisting)
  • What energized me consistently? (Do more)
  • What drained me consistently? (Eliminate, delegate, or negotiate)
  • Which projects moved vs. stalled? (Reality check against 'feelings of progress')

Monthly meta-review is where the weekly ritual compounds. 10 weekly reviews + 1 meta = 10x the insight of 10 weekly reviews alone.

Key Takeaways

  • Sunday 5:30pm, 45 min hard cap, same location each week. Infrastructure matters.
  • Order: process → reflect → plan. Reversing produces worse plans.
  • 3 priorities Monday, not 10. Forcing priority ranking reveals what actually matters.

Common use cases

  • Knowledge workers juggling 3+ major projects
  • Founders wearing multiple hats daily
  • Freelancers with no external project management
  • Students balancing coursework + research + job hunt
  • Parents trying to maintain career progress despite fragmented attention
  • Remote workers without team-imposed structure
  • Anyone recovering from burnout, rebuilding capacity

Best AI model for this

Claude Sonnet 4.5 or any mid-tier. Structured reflection with moderate reasoning.

Pro tips

  • Pick Friday OR Sunday, not both. Friday = close-the-week mentality. Sunday = open-the-week mentality. Pick ONE and stick to it.
  • Do it OUTSIDE your normal workspace. Coffee shop, kitchen table, park bench. Different location = different cognitive mode.
  • 45 min is the ceiling. If it takes longer than 45, you're making it too complex. Cap it.
  • Don't skip after bad weeks. Bad weeks are when the review matters most. 'Everything was chaos' = still review the chaos.
  • Keep a running doc — not 52 separate docs. You want to be able to scroll back and see patterns over months.
  • The 3 Monday priorities are NOT 'what I wish I could do.' They're 'what I WILL do.' Realistic, not aspirational.

Customization tips

  • First 3 weeks will feel awkward. By week 4 it becomes ritual. Past week 6 you won't skip it even if you wanted to.
  • Keep one file, scroll-back-able, not fragmented across apps. Pattern recognition requires longitudinal data.
  • If review takes longer than 45 min consistently, you've added a section that shouldn't be there. Cut until 45 min holds.
  • Save the Monthly Meta-Reviews — they're gold 12+ months later when you want to see evolution of your thinking/priorities.
  • If you have a co-founder or team, share the WEEK review (not the lesson log). Shared visibility aligns team weeks without meetings.

Variants

Solo Founder Mode

For founders managing product + marketing + sales + operations simultaneously. Different review cadence for different threads.

Post-Burnout Recovery Mode

For people rebuilding capacity. Gentler review, less about 'output,' more about 'did I recover this week.'

Team Lead Mode

For managers. Adds people-review section (who needs attention, who's blocked).

Frequently asked questions

How do I use the The 45-Minute Weekly Review Protocol prompt?

Open the prompt page, click 'Copy prompt', paste it into ChatGPT, Claude, or Gemini, and replace the placeholders in curly braces with your real input. The prompt is also launchable directly in each model with one click.

Which AI model works best with The 45-Minute Weekly Review Protocol?

Claude Sonnet 4.5 or any mid-tier. Structured reflection with moderate reasoning.

Can I customize the The 45-Minute Weekly Review Protocol prompt for my use case?

Yes — every Promptolis Original is designed to be customized. Key levers: Pick Friday OR Sunday, not both. Friday = close-the-week mentality. Sunday = open-the-week mentality. Pick ONE and stick to it.; Do it OUTSIDE your normal workspace. Coffee shop, kitchen table, park bench. Different location = different cognitive mode.

Explore more Originals

Hand-crafted 2026-grade prompts that actually change how you work.

← All Promptolis Originals