Weekly report writer — from Friday brain-dump to a 60-second read
Your notes are scattered across a notebook, two chats and a ticket queue. Paste all of it — fragments and all — and get the four sections managers actually read.
Why this beats a form
A weekly template asks you to remember what you did before you can write about it. This asks for the raw material — ticket IDs, names, numbers, half-sentences — and does the sorting. The four sections it returns are the ones that get read: what changed, what is moving, what will slip, what happens next.
Keep the risks section honest. A status update that never mentions a blocker is read as either lucky or uninformative, and the second one is worse for you.
Getting a better output
Dates beat relative words: “QA sign-off moved to Thu 12th” survives summarising, “sometime next week” does not. If your manager wants numbers, put the numbers in the notes — they will be carried over verbatim.
Need the structure itself? Three copy-and-paste weekly report templates — the five-line channel update, the manager email, and the at-risk escalation.
FAQ
Will it make up metrics?
No. It reuses only numbers in your notes; empty sections read “none this week” rather than being padded.
Do I have to write full sentences?
No. Fragments like “LM-402 fix shipped Tue, QA pending, blocked on vendor” are the intended input.
Which format does it use?
Highlights, in progress, risks and blockers, next week. Paste your company template into the notes and it will follow that shape instead.