The Weekly Report Prompt That Always Works — Even When You Don’t Know What To Write
A weekly report prompt changed everything for me. I have a confession — for three years, I dreaded Monday mornings.
Not because of meetings. Not because of deadlines. Because of weekly reports.
Staring at a blank document, trying to remember what I did last week, turning bullet points into sentences that didn’t sound like a robot wrote them. The whole process felt like performing surgery with a butter knife.
Then I discovered something that changed everything: a single weekly report prompt structure that turns scattered notes into polished reports in minutes.
Today, I’m breaking down this exact weekly report prompt using RCTF (Role, Context, Task, Format) — the framework that makes every prompt work.
The Problem With Most Weekly Report Prompts
Most people approach their weekly report prompt completely wrong. They dump their notes and say “make this better.”
The result? Generic corporate-speak that sounds like it came from a template factory.
Here’s what usually happens:
“Here are my notes from this week. Make them into a report.”
“This week, various tasks were completed across multiple projects. Progress was made on several initiatives. Meetings were attended and outcomes were positive.”
Useless. Your manager learns nothing. You sound like ChatGPT in 2022.
The RCTF Weekly Report Prompt (Copy-Paste Ready)
Here’s the exact prompt I use every Monday. Copy it, customize the bracketed sections, and watch your report quality transform overnight:
**Role:** Act as a senior [your job title] who writes clear, actionable weekly reports for [your manager’s role/team].
**Context:** This report goes to [specific person/team] who needs to understand my progress on [main projects/initiatives]. They care about [specific outcomes they track] and make decisions about [what they use these reports for].
**Task:** Convert my scattered notes into a structured weekly report that highlights key achievements, surfaces blockers clearly, and sets expectations for next week. Use my voice — professional but not robotic.
**Format:** – **This Week’s Wins** (3-5 bullets with specific outcomes) – **Blockers & Challenges** (honest about what’s stuck) – **Next Week’s Priorities** (3 max, with success criteria) – **Team/Manager Support Needed** (specific asks only)
My notes: [paste your messy notes here]
Let me show you exactly how this weekly report prompt works with a real example.
Before vs. After: Real Results
- Fixed bug in payment system – users were getting double charged
- Met with design team about new onboarding flow
- Code review for Sarah’s feature took longer than expected
- Customer support escalation about mobile app crashes
- Started working on Q2 roadmap planning
- Need approval for new testing framework
This week involved various development activities. Bug fixes were implemented, meetings were attended, and code reviews were conducted. Progress was made on roadmap planning and collaboration occurred with multiple teams.
This Week’s Wins
- Payment System Fix: Resolved critical double-charging bug affecting 12% of users — saved an estimated ₹2.3L in potential refunds
- Onboarding Flow Progress: Collaborated with design team to finalize user flow for new customer onboarding (reduces setup time by 40%)
- Team Development: Provided detailed code review for Sarah’s feature implementation — caught 3 potential security issues before production
Blockers & Challenges
- Mobile App Stability: Customer support escalated 15+ crash reports this week — needs investigation priority
- Testing Framework Delay: Still waiting on budget approval for automated testing tools (blocking Q2 velocity improvements)
Next Week’s Priorities
- 1. Complete mobile crash investigation and deploy fix (success: <5 crashes/day)
- 2. Finalize Q2 roadmap with stakeholder input (success: documented priorities by Friday)
- 3. Begin onboarding flow development (success: MVP wireframes ready)
Team/Manager Support Needed
- Budget approval for testing framework (₹45K annual cost, 30% efficiency gain)
- Mobile testing device access for crash reproduction
See the difference? This is what a well-crafted weekly report prompt produces. Your manager knows exactly what you accomplished, what’s blocking you, and how they can help.
Why This RCTF Structure Works So Well
**Role Sets the Voice**
“Act as a senior [job title]” immediately calibrates Claude’s tone and technical depth. A senior developer writes differently than a junior analyst.
**Context Creates Relevance**
Telling Claude who reads this report and why transforms everything. Reports for your direct manager focus on execution details. Reports for executive teams focus on business impact.
**Task Defines Success**
“Convert scattered notes into structured report” is specific. “Make this better” is not. The clearer your task, the better Claude’s output.
**Format Eliminates Guesswork**
The four-section structure works for 90% of teams. But customize it! Some teams want “Metrics” or “Learning.” Others need “Dependencies” or “Risks.”
Advanced Customizations That Make It Even Better
Include specific metrics (response times, error rates, user adoption) and link to dashboards where relevant.
Mention client names and specific outcomes they achieved. Use their language, not internal jargon.
Highlight collaboration efforts and async communication wins. Show how you’re staying connected.
Focus on learning and discovery rather than just delivery. What did we validate? What assumptions changed?
Pro Tips I Learned the Hard Way
After your weekly report prompt generates the report, save it. Next week, include this line:
“Here’s last week’s report for tone reference: [paste previous report]”
Consistency matters. By reusing the same weekly report prompt, your manager won’t have to decode a different writing style every week.
Claude can’t invent metrics, but it can present them powerfully. “Fixed 3 bugs” becomes “Resolved 3 critical bugs affecting 200+ daily users.”
The best reports don’t hide problems — they surface them constructively. “Stuck on X because of Y, need Z to move forward” is gold for managers.
For next week’s priorities, always include what success looks like. “Complete feature” is vague. “Complete feature with 95% test coverage and design approval” is actionable.
Your Weekly Report Homework
- 1. Copy the RCTF prompt above and customize the bracketed sections for your role
- 2. Use your actual messy notes from last week — don’t clean them up first
- 3. Run it through Claude and compare the output to your usual report style
- 4. Save the prompt in Claude Projects with your customizations
- 5. Set a Monday calendar reminder to use this prompt consistently
The goal isn’t to replace your thinking — it’s to amplify it. You still decide what matters, what to emphasize, and what needs follow-up. Claude just handles the heavy lifting of turning thoughts into professional communication.
Next Monday morning won’t feel the same. With this weekly report prompt, instead of staring at a blank document, you’ll have a system that works every single time.
