Weekly Review Reflection Prompt

What this prompt does

Most "weekly reviews" end as a list of things you didn't get done. This prompt structures the review so it captures what actually happened, surfaces patterns (what kept going well, what kept getting derailed), and builds a specific plan for the next week — not just a task dump.

Good weekly reviews take 15 minutes and make Monday mornings noticeably less chaotic.

The prompt

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

How to use it

1. Don't clean up your input — paste raw notes. The messier and more honest your input, the more useful the reflection.
2. Be specific in "what got in the way" — "got busy" is noise. "Spent 3 unplanned hours in meetings on Tuesday" is a pattern worth noticing.
3. Use the pattern insight — if the AI flags a recurring theme (context switching, scope creep, underestimating tasks), write it down and carry it into next week's planning.
4. Commit to one priority for next week — not three. If you have three, you have zero.

Example output

Week summary:

• Shipped the new onboarding email sequence (3 variants) after 2 weeks of delays
• Closed one new client at a higher rate than last year's average
• Finished reviewing all 15 grant applications before the committee deadline

Pattern spotted: Three tasks that "almost" got done this week were all interrupted by unscheduled requests from the same person. Worth a direct conversation or boundary-setting next week.

Next week plan:

Top priority: Deliver the campaign brief to the design team — this is the bottleneck for everything else going live on schedule.

Important but not urgent:

• Prep for Thursday client call (review their recent campaign data)
• Write the July content calendar first draft
• Finish the quarterly OKR update

Tasks to schedule or batch:

• 4 emails sitting in draft (batch these Monday morning, 30 min)
• Update CRM records (block Tuesday, 45 min)
• Read the new brand guidelines doc

If the week gets hard, defer: July content calendar — important but not due until June 28.

Honest reflection: My "top priority" was "close the new client deal" last week too, but it kept getting pushed because reactive work filled the mornings. Protecting 9–11am as non-meeting time might be the lever here, not better task lists.

Variations

End of month (deeper review)

"Help me run a monthly review. I'll share what happened across four weeks. Focus on: what moved toward my main goals, what got deprioritized, any patterns that showed up consistently, and what to adjust for next month."

For teachers (end of week)

"Help me review my teaching week. I'll share: what lessons went well and why, what was harder than expected, student patterns I noticed, and what I want to adjust next week."

Common pitfalls

• Don't: Skip the weekly review when the week was bad. Reviewing a hard week is more useful than reviewing a good one — it surfaces what actually happened vs. what you hoped for.

• Try instead: Make a short version for hard weeks: just 3 bullets on what happened and 1 thing to change.

• Don't: Treat the next-week plan as final. Things will change. The point is to start Monday knowing your priority, not to predict every hour.

Who uses this prompt

• Freelancers: Managing client work, personal projects, and business development in parallel
• Small business owners: Keeping operational and strategic work in balance
• Teachers: End-of-week reflection on student engagement and lesson effectiveness
• Managers: Personal productivity and team oversight