2026-06-29
Don't let weekly reports be a burden: build the weekly review from accumulated daily reports
Writing a weekly report from scratch is double work. Smooth your daily reports by the week and the weekly report becomes 'just a summary.' How to build a weekly review from daily reports and connect it to 1-on-1s and evaluation.
Weekly reports hurt because they're double work
Writing a weekly report from scratch separately from the daily one you already write — this double work makes the weekly report a burden and lets it go stale. Feel made to write the same thing twice and content thins and doesn't last. When you try to recall the week at its end, the small events are forgotten, and you tend to end up writing only from the impression of the last few days.
Smooth daily reports by the week
Look across a week of P, D, C and A and the weekly report becomes not something to recall and write anew but just a summary of what accumulated. With the daily facts in place, the weekly report is built from records, not memory. Concretely, pick up the flow of aims from the row of Ps, the words that keep recurring from the row of Cs, and the improvements actually tried from the row of As, and sum each up in one sentence.
The week is the unit for seeing trends
What a single day can't show, a week reveals: trends in stumbling, consistency between plan and execution, issues left unaddressed. Such trends are best grasped at the unit of a week, a natural break for thinking about improvement. For example, if the same kind of waiting time appears in C again and again, it may be a sign that the way of working needs review rather than individual effort. Conversely, if what was decided in A continues into the next week, it can be recognized as a sign of taking hold.
The week becomes the start of 1-on-1s and evaluation
The weekly summary can be used directly as the agenda for a 1-on-1 and the basis for evaluation. When the once-double-work weekly report doubles as prep for the meeting and the appraisal, a burdensome task turns into a worthwhile bit of effort. In the meeting, a good guide is to start from the summary and draw out the person's own words: 'this is what caught my eye in this week's C; how did you feel about it?' In evaluation too, the accumulated weekly summaries back up concrete examples.
Common stumbles and how to avoid them
A common one is the manager making the weekly summary alone, leaving the person uninvolved. Adding a field where the person sums up their own week in a line makes it their own and easier to sustain. Also, too many summary items bring back the double work, so keeping to about three points — trend, insight and next week's move — is safe. Even if some days are missing from the daily reports, looking at them as they are without forcing them to be filled can bring the circumstances of the gap into the conversation.
The smallest first step to try
This Friday, read back through the daily reports from the top and mark words that caught your attention. From those marks, write just one sentence on 'this week's trend,' and that is your first weekly summary. Bring that sentence up at the next meeting, and the weekly habit starts in an unforced way.
Related articles
The feature that fits this article's topic: PDCA history →
A tool for a culture of improvement and fair evaluation that implements these ideas.