A running log that turns into your weekly status report
Add a line to one note whenever something moves. On Friday, a template and one prompt turn it into the report your reader expects, with nothing added and nothing softened.
If you write a weekly status report, you probably start it on Friday afternoon by digging through your calendar and sent folder to work out what happened on Tuesday. The writing goes quickly. Rebuilding five days from memory is what takes the time.
This post moves that work to the moment it costs least. All week, you add one line to a running log whenever something moves. On Friday, an AI assistant turns the log into the format your manager, client or funder expects, under rules that stop it from doing what it does worst with reports: making a thin week sound busy and a real problem sound small.
By the end of today, in under an hour, you’ll have a log running, a report template saved and this week’s report drafted from the log. The method works in Claude, ChatGPT, Gemini or Copilot, for anyone who reports to someone: a project manager to a sponsor, a store manager to a regional manager, an engineer to a team lead, a program manager to a funder, an executive assistant pulling together someone else’s week.
Why reports from memory are slow and miss things
Memory fails in predictable ways. Small finished items vanish because they took ten minutes. Problems shrink, because by Friday you’ve lived with them for days. Figures get rounded, or cost you a quarter of an hour of searching your inbox. Decisions you need from your reader come out vague, because you’re putting them into words for the first time at four on a Friday.
A log fixes most of this before any AI is involved. Each fact is written down while it’s fresh, with the real number, and what’s left for Friday is formatting.
One line whenever something moves
Each line has four parts, separated by a vertical bar:
DATE | PROJECT | WHAT HAPPENED | TAG
Here is a made-up week from a fictional team redesigning a website. The rest of the post uses it.
Mon Oct 12 | Website | Content audit finished: 52 pages reviewed, 14 to cut, 9 to rewrite | #done
Tue Oct 13 | Website | Staging server access requested from IT on Oct 12, still not granted; design can't test the new menu | #blocked
Tue Oct 13 | Website | Agreed with design to launch without the events calendar | #done
Wed Oct 14 | Website | Moving pages to the new templates: 25 of 38 moved so far |
Wed Oct 14 | Website | Need approval of the new home page copy by Oct 21 to keep the Oct 30 launch | #decision
Thu Oct 15 | Website | Photo agency can deliver 18 of 30 images by Oct 30. Options: our own photos for the other 12, or launch Nov 6 | #decision
Thu Oct 15 | Website | Accessibility check on the 3 new templates: 11 issues found, 4 fixed |
Fri Oct 16 | Website | Move the last 13 pages; fix the other 7 accessibility issues; test the menu with 5 staff | #next
The tags do most of the work on Friday:
#done: finished, meaning delivered, sent, approved or closed. Started doesn’t count.#blocked: stuck on something you can’t move yourself. Say who or what it’s waiting on, and since when.#decision: something you need your reader to decide, with the date you need it by. A decision already made goes in as#done.#next: planned for next week.- No tag: it moved but isn’t finished. These lines become “In progress”.
Put the number in the line, with what it counts: “25 of 38 pages”, never “most pages”. If an item moves twice in a week, add a second line instead of editing the first; the prompt merges them.
Nothing in the format is specific to websites. For example, made-up lines from a recruiter, an account manager, an events coordinator and a teacher:
Tue Oct 13 | Hiring | Interviewed 4 of 6 shortlisted candidates for the customer service role |
Wed Oct 14 | Renewals | Proposals sent to all 5 accounts that renew in November | #done
Wed Oct 14 | Trade fair | Need sign-off on the March booth by Oct 23 to keep the early booking price | #decision
Thu Oct 15 | Biology | Lab kits ordered Oct 6, supplier still hasn't confirmed delivery; the week 3 lab sessions depend on them | #blocked
Keep it where adding a line takes seconds
The log survives only if adding a line is quicker than deciding whether to bother. A single note in the notes app you already use, pinned and synced to your phone, works well. So does a plain text file on your desktop, if you work at one computer. Use one log for all your projects, add new lines at the bottom, and keep it outside the AI chat, so it stays yours and you can search it next year.
Add a line right after you send something that matters or leave a meeting. A two-minute pass before you stop for the day catches the rest.
If the log will hold client names or internal figures, use code names for projects from the first line, and check what your assistant’s plan allows before you paste it (Before you upload a client document lists the questions).
Backfill this week from your calendar and sent mail
You don’t have to wait until next Friday to see it work. Set aside 15 to 20 minutes:
- Open your calendar to Monday. For every meeting that produced a decision, a task, a number or a problem, write one line.
- Go through your sent folder for the same days. Add a line for anything you delivered, asked for or chased.
- If your team uses a chat or ticketing tool, look there for anything still missing.
- Tag every line. When you’re unsure whether something is done, it isn’t: leave it untagged.
If you’re reading this early in the week, backfill last week instead. Either way, put the log next to the last report you sent and see what the report from memory left out.
The template and the prompt
Save this template once. Whatever needs action from your reader goes at the top, because that’s the part a busy reader acts on. If your reader already has a format, use theirs.
WEEKLY STATUS | [Project or team] | Week of [date]
For: [reader's name and role]
Blocked
- [What is stuck, since when, what would unblock it]
Decisions needed from you
- [The decision, the options, the date you need it by]
Done this week
-
In progress
- [Item and where it stands, with a figure if there is one]
Next week
-
A short week doesn’t need the assistant. When the log has eight lines and your reader wants five bullets, copying them into the template is quicker than any prompt. The assistant pays off when the log runs long or covers several projects, and the rules below target the two habits that ruin AI-written reports: filling thin sections with progress that didn’t happen, and polishing problems into “minor delays”.
Below are my report template and this week's work log. Write this week's status report in the template's format for [my manager / the client / our funder].
Rules:
- Use only what is in the log. Add no work, results, causes, dates or plans.
- #done lines go under "Done this week"; untagged lines go under "In progress". Never call something finished, delivered or complete unless its line is tagged #done.
- #blocked lines go first. Say plainly what is stuck, since when, and what would unblock it. Do not soften them.
- #decision lines go under "Decisions needed from you", with the options and dates the log gives.
- #next lines go under "Next week".
- Copy every figure exactly. Do not round, add up or calculate.
- No adjectives about the quality of the work. Do not use: significant, great, excellent, successfully, smoothly, well underway, on track, minor, slight, just.
- If a section has nothing in the log, write "None this week."
- Merge lines about the same item. Keep bullets under 25 words and the whole report under 250 words.
- After the report, list any log lines you left out and why.
TEMPLATE:
[paste the template]
LOG:
[paste this week's lines]
Add your own reader’s least favorite words to the banned list as you find them.
What the example week produces
From the website log above, a report that follows the rules looks like this. Your assistant’s wording will vary; the structure and the facts shouldn’t.
WEEKLY STATUS | Website redesign | Week of Oct 12
For: Head of communications
Blocked
- Staging server access: requested from IT on Oct 12, still not granted. Design can't test the new menu until it is.
Decisions needed from you
- Approve the new home page copy by Oct 21 to keep the Oct 30 launch.
- Photos: the agency can deliver 18 of 30 images by Oct 30. Use our own photos for the other 12, or launch Nov 6?
Done this week
- Content audit: 52 pages reviewed, 14 to cut, 9 to rewrite.
- Agreed with design to launch without the events calendar.
In progress
- Moving pages to the new templates: 25 of 38 moved.
- Accessibility: 11 issues found on the 3 new templates, 4 fixed.
Next week
- Move the last 13 pages.
- Fix the other 7 accessibility issues.
- Test the menu with 5 staff.
Left out: none.
Without the rules, a draft of the same week can open like this:
Excellent progress this week on the website redesign. The content audit was successfully completed and the migration is well underway, with only minor delays on the staging environment.
“Well underway” is 25 of 38 pages. The “minor delays” are a blocked request that stops design from testing the menu. And the two decisions with deadlines are gone.
Check it as the person receiving it
First, check the draft against the log. Every bullet should point back to a log line, and the “left out” list shows what didn’t make it. Search the log for each figure: a number you can’t find there was invented or calculated. Nothing belongs under “Done this week” unless its line says #done.
Then read it as your reader. Could they act on the top two sections without writing back to ask? Is any problem worded more gently than it will look in two weeks, if it’s still there? Fix those by hand; small edits are faster than another round with the assistant. If your reader expects a red, amber or green status, add it yourself, because that judgment is yours to make.
Try it today
Before you start, jot down roughly how long your last report from memory took. Then:
- Create the note or file, pin it, and paste the line format at the top.
- Backfill Monday to today from your calendar and sent folder, and tag every line.
- Save the template and the prompt where you’ll find them next Friday: in your prompt collection (Keep your best prompts in one place) or in your assistant itself, if it lets you save instructions (Set up your AI assistant once).
- Paste the prompt, the template and this week’s lines into a new conversation, and check the draft against the log.
- Set a daily reminder for ten minutes before you usually stop work: “Log: what moved today?”
You’re done when this week’s report is drafted from the log and checked against it, and tomorrow’s reminder is set. Next Friday, time the report from opening the log to a checked draft and set it against the number you jotted down. That’s your own answer, in real minutes, to whether the log is worth keeping.
Where the log takes you next
Your #next lines are already the start of next week’s plan. Make next week fit in your calendar sets them, with the rest of your to-do list, against the hours you actually have, and ends with a list of what can wait. Do it right after the report goes out, and the report and the plan share one Friday block.
Two more pieces plug into the log. Take meeting notes in three letters leaves you a list of actions after every meeting, and yours go straight in. The #blocked lines that wait on someone else also belong in a six-column tracker, which highlights the day each one is due for a nudge.