Turn Your Notes into a Weekly Status Report

Friday afternoon status reports are one of those tasks that feel like they should take five minutes but somehow consume half an hour. You stare at the blank template, try to remember what you actually did on Monday, give up, and write something vague that does not reflect the week you actually had. Your manager reads it in thirty seconds and learns approximately nothing.

The fix is not more discipline. It is keeping notes throughout the week, then spending two minutes with Claude on Friday to turn those notes into something readable.

Getting the Input Ready

You do not need tidy notes. The messier the better, actually, because tidy notes suggest you spent time tidying that you could have spent doing actual work.

What works as input:

• A running bullet list you update throughout the week
• A dump of your completed tasks from a task manager
• Forwarded emails summarizing things you finished or unblocked
• A quick Friday brain-dump of everything you remember doing

The key is to capture specifics during the week rather than trying to reconstruct them on Friday. “Finished the Johnson proposal” is more useful than “worked on proposal.” Numbers are especially valuable: “reviewed 47 invoices,” “reduced ticket backlog from 32 to 11.” Paste those in and they will appear in the Metrics section of the report.

One habit that compounds over time: keep a plain text file open in the background all week. Every time you finish something or run into a blocker, add one line. By Friday you have everything you need without any extra effort.

The Prompt

You are a senior project manager writing a concise weekly status report.

Using the notes I provide below, write a professional weekly status report with these sections:

**Week of:** [insert week ending date]

**Executive Summary** (2-3 sentences: what was the overall theme of the week, are we on track?)

**Accomplishments This Week** (bullet list, 4-6 items, past tense, specific)

**In Progress** (bullet list: what is actively being worked on)

**Blockers & Risks** (bullet list: anything slowing progress or at risk; write "None" if there are none)

**Next Week's Priorities** (numbered list, 3-5 items in order of importance)

**Metrics / Key Numbers** (any numbers from my notes; skip this section if I provide none)

Rules:
- Keep the whole report under 350 words
- Use plain language -- no buzzwords
- Write in third person or first person, whichever reads more naturally
- Do not invent information not found in my notes

Here are my raw notes from this week:

[PASTE YOUR WEEK'S NOTES, EMAILS, OR BULLET POINTS HERE]

The rule “do not invent information not found in my notes” matters. Without it, Claude will sometimes fill in plausible-sounding accomplishments that you did not actually do. That is not what you want appearing in a report going to your manager.

What You Get

A structured, under-350-word status report you can review, adjust, and send. The Executive Summary section is the one most likely to need a quick read. Claude will infer a theme from your notes, and that inference is usually right, but sometimes the week had two distinct themes and the summary collapses them into one. Fix it in thirty seconds if so.

The Blockers and Risks section is where this workflow earns its keep. When you are writing from memory, blockers are easy to omit because you have already mentally moved past them. Claude picks them up from whatever you pasted, which means your manager actually learns what is getting in the way.

If you have no numbers to report, Claude skips the Metrics section automatically. No awkward “N/A” rows.

Calibrating the Output

A few tweaks worth keeping in your back pocket:

If your team uses a specific report template with different section names, describe those sections in the prompt instead of the ones above. Claude will match the structure.

If your manager prefers a shorter format, add “Keep the whole report under 200 words” to the rules. The report will get tighter. Everything important still makes it in.

If you write reports for multiple stakeholders with different contexts, run the prompt twice with a different audience instruction each time. The facts stay the same. The framing shifts. That takes about four minutes total, which is still faster than writing either version manually.

The goal is a weekly habit you can actually sustain. Thirty seconds of notes each day plus two minutes with Claude on Friday is a reasonable ask. A blank Friday template at 4:45 pm is not.