What actually matters to the client
- What got finished this week, concretely.
- What's coming next week.
- Any blocker that needs their decision, clearly flagged.
What you can leave out
Internal technical details, team discussions with no impact on the client, or minor tasks that change nothing from their perspective. A report isn't a full work journal, it's a useful summary.
How to generate it without extra effort
If projects and tasks are already updated daily, the weekly report is just a pull of what changed, not separate work written from scratch every Friday.
Bottom line
The best report is the one the client actually reads to the end. Short, concrete, and directly tied to the decisions they need to make.