Report Generator: the weekly report skeleton that takes 10 minutes
Four sections, fixed order, numbers first. Stop staring at a blank document every Friday afternoon.
Weekly reports are not graded for length — they are graded for signal. Managers want to know: what moved, what is stuck, what you will do next, and whether they need to help. The skeleton below forces those four answers out of you in order.
The skeleton (copy this every week)
| Section | What goes in it | Example line |
|---|---|---|
| 1. Done this week | 3 bullets, verb-first, numbers when you have them | Shipped the onboarding email sequence — 4 emails, open rate 38% |
| 2. Results / impact | The outcome, not the activity | Cut invoice-processing time from 2 days to 4 hours |
| 3. Next week | 3 priorities only | Launch the ticket triage queue; hire 1 agent; draft SOP v2 |
| 4. Help needed | Blockers + what you want from whom | Need finance to confirm the budget by Wednesday — holding Q3 plan |
Writing the summary for your manager
The first two lines are the whole report for most managers. Rule: outcome first, blocker second, ask last. Example: Onboarding sequence is live and beating target (38% open vs 25% plan). The Q3 budget sign-off is the one blocker — if it lands by Wednesday, the launch stays on track.
Two habits raise the value of every report: keep a running "win log" all week (one line per completed thing, written when it happens) so Friday is a copy-paste job, not a reconstruction; and attach the numbers even when they are ugly. A missed target reported early reads like control. A missed target discovered in the monthly review reads like a surprise nobody wanted.
When your boss forwards your report upward, they will read the first two lines and copy the numbers. Build those two lines for them — and your results travel further than the report does.
AI prompts to draft it
- Bullets to report.
Turn these rough notes into a weekly report: 3 achievement bullets with numbers, 2 blockers, 3 next-week priorities. Tone: direct, no fluff. Notes: [paste your week's bullets]. - Manager summary.
Write a 3-line executive summary for my manager: line 1 = biggest result with number, line 2 = the main blocker, line 3 = what I need from them. Facts: [paste report bullets].
How it works
- Before Friday, dump your week into rough bullet notes — no structure required.
- Run prompt #1 to turn them into the four-section skeleton.
- Add your manager summary on top, then send at the same time every week.
Under 250 words. Three achievement bullets with numbers, two blockers, three next-week priorities. Managers skim reports, so the first two lines have to carry the whole message.
Report the small things honestly: process cleanup, a recurring task you automated, documentation you finished. A quiet week reported honestly builds trust; a quiet week padded with fluff builds suspicion.
Never. Blockers reported early and paired with a proposed fix look like ownership. Blockers discovered late look like failure. The help-needed section exists precisely so you surface them early.
Bullets. Every bullet starts with a verb (shipped, cut, onboarded) and carries a number where possible. Prose paragraphs belong in the executive summary only.
Weekly, same time. Predictability matters more than length — a short report that arrives every Friday beats a long one that shows up when you remember.
Who this tool is for
This is for anyone with a recurring written update: the weekly report, the monthly summary, the client status note, the self-assessment that feeds a review. Team leads rolling up several people's work and remote employees reporting to another time zone get the same benefit.
Regulated documents are out of scope: statutory accounts, audit evidence, safety incidents and anything with an official template and a sign-off chain.
How to read your result
The result is four sections plus a short summary, under 250 words.
- Summary test. Line one is the biggest result with a number, line two the blocker, line three the ask and its date. Your manager should be able to forward those three lines unedited.
- Section one. Three bullets at most, each starting with a verb and carrying a number or a scope.
- Section two. Results, not activity. Running four workshops is activity; cutting approval time from five days to two is a result.
- Section three. Three priorities, not nine wishes.
- Section four. The blocker, the person, the date, and what happens if it lands or misses.
- Consistency. Numbers should line up with last week. If a metric moved, add one clause explaining why.
- Honesty. A quiet week is reported as a quiet week, with the small work named. Padding is easy to spot.
- Forwardability. If the report travels upward without you, the first two lines must still make sense.
Print the report and read only the first two lines. If the outcome is not visible there, the rest will not be read either. Keep last week's report open beside it, so any number that moved can be explained in one clause instead of a paragraph.
A worked example
Tom leads IT support at a company of 180 people. The week runs from 19 to 23 October 2026.
Win log: closed 41 of 47 tickets; wrote a password reset guide; laptop refresh 6 of 10 done, waiting on finance for 4; new starter setup 35 minutes, down from 50; one complaint about the queue; vendor call moved to Monday.
Summary: Open tickets fell to six from nineteen last Friday. The laptop refresh is blocked on finance approval for four units; sign-off by Wednesday 28 October keeps the November start dates.
Done: closed 41 of 47 tickets, six remain; published a one-page password reset guide in the help centre; set up three new starters at 35 minutes each, down from 50.
Results: average setup time fell by 15 minutes per starter; the queue complaint closed after adding a same-day callback slot on Tuesday and Thursday.
Next week: finish laptops for six of ten users; run the callback slot for two weeks and track volume; draft an asset-tracking sheet so devices stop living in email threads.
Help needed: finance approval for four laptops, from Priya, by Wednesday 28 October. Without it, two November starters wait.
The skeleton keeps the blocker near the top instead of burying it in week four, and every ask names a person and a date. The vendor's scheduling work stays out of Tom's achievements because it was not his.
Common mistakes
- An activity dump. Meetings attended and calls made are not outcomes.
- A blocker saved for the monthly review. By then it is a surprise.
- Nine priorities, which is none.
- Numbers that do not reconcile with last week. Readers notice before you do.
- Prose in the body. Bullets skim faster and survive forwarding.
- Need help with no name and no date. That is a complaint, not a request.
- Writing for the archive rather than the reader. The report is a decision tool.
- Claiming shared results alone. Use we where it is shared and state your own contribution.
- Pasting raw figures into an AI prompt. Client names, salaries, incident details and contract amounts stay out; anonymise or keep the report manual.