Write a weekly assistant report that ends with a decision
A weekly report that summarizes the outcomes, the blockers, and the one decision needed.
How to approach: Write a weekly assistant report that ends with a decision
A weekly assistant report should help the executive see what moved and what needs a choice. Start with the outcomes, the blockers, and the decision. A report that lists activity is not a report. Review the first few notes together before the process expands.
Keep the report to one page. The executive should be able to read it in a few minutes. Update the template when the same question appears twice. Name the owner in the same line as the action.
Summarize the outcomes
Write the outcomes that were completed and the evidence. A task that is marked done without the evidence is a claim. Keep the evidence with the record rather than in a separate log. A short note with four fields is easier to use than a long narrative.
Record the outcomes that slipped and the reason. A slip without the reason cannot be fixed. Update the template when the same question appears twice. A short note with four fields is easier to use than a long narrative.
Name the blockers and the decision
Record the blocker, the owner, and the date. A blocker without an owner will remain. Separate what was observed from what was assumed. Keep the evidence with the record rather than in a separate log.
Write the one decision needed and the deadline. A report that ends without a decision is only an update. Record the exception and the person who approved it. Keep the boundary visible in the place where the work is assigned.
Keep planning
Questions people ask
What should a weekly assistant report contain?
The outcomes, blockers, and one decision needed.
How long should the report be?
One page, read in a few minutes.
Reference notes
These links are a starting point for general context. They are not custom legal, tax, hiring, or cybersecurity advice.
- U.S. Small Business Administration: Public guidance consulted for general context.