The problem
Weekly status reports are a necessary overhead on every consulting engagement. The client needs visibility. Your project manager needs a paper trail. The steering committee needs a summary for their monthly pack.
But weekly status reports take time that you would rather spend on the actual work. The information exists in your head and in your meeting notes, but assembling it into a coherent, well-structured document every Friday afternoon is a grind. The temptation is to dash it off quickly, which means the report does not actually communicate as clearly as it should.
Poor status reports create problems beyond admin inefficiency. A report that fails to surface risks clearly, or that buries a red flag in paragraph three, is a governance failure. A report that only lists what happened without explaining what it means leaves the client without the context they need to make decisions.
This workflow makes status reports fast enough that you will actually write good ones every week.
The system
Step 1: Record your weekly update as a voice note (Otter.ai)
At the end of each week, spend five minutes talking through the status of the project as if you were briefing a colleague. Cover:
- What was accomplished this week
- What is in progress
- Any risks or issues that emerged
- Any decisions needed from the client
- What is planned for next week
Record this using Otter.ai, which will transcribe it automatically. You do not need to be polished or structured — just talk. The act of verbalising the update is faster than typing it and often more honest.
Step 2: Export the transcript
Otter.ai provides a text transcript within minutes of your recording. Copy the transcript.
Step 3: Generate the status report (Claude)
Paste the transcript into Claude:
"I have recorded a voice update on my consulting project. Below is the transcript. Please turn this into a structured weekly project status report for a client audience. The report should include:
- Project name and reporting period
- Executive summary (3 sentences: where we are, what changed, what needs attention)
- Accomplishments this week (bullet points)
- In progress (what is currently being worked on)
- Risks and issues (with a RAG status: Red/Amber/Green)
- Decisions required (any items needing client input)
- Next week's priorities
Make it professional and clear. If the transcript mentions something that sounds like a risk but is not flagged as one, flag it yourself. UK spelling, no em dashes.
Transcript: [paste here]"
Step 4: Add the metrics section
If your project has specific KPIs or milestones, add these to your report template and ask Claude to integrate them:
"Add a milestones section to this report. Here are the current milestone statuses: [paste your milestone tracker]. Highlight any milestones that are behind schedule and note the impact."
Review the final report, add any specifics that the voice note missed, and send.
The results
Before: 60 to 90 minutes every Friday writing the status report, often delayed because the writing felt laborious.
After: 5 minutes voice recording, 15 minutes reviewing and editing the Claude output. Total: 20 minutes.
The voice recording step is the key insight. Speaking is faster than typing, and when you are talking rather than writing, you tend to be more direct about what is actually going on. The transcript captures the unfiltered version; Claude turns it into professional language.
Several consultants using this workflow have found that their status reports improved in quality as well as speed. The executive summary in particular became sharper because Claude was extracting the key points from a more candid voice note rather than from carefully crafted sentences.