A Practical Playbook for Weekly Decisions

I once watched a director open a weekly report, scroll for four seconds, and close the tab. She'd asked for it. She'd waited for it. She just couldn't find the one thing she needed: what changed, and what she had to do about it.

That's the real problem with weekly reports. Not that people don't write them. It's that most of them are written as a diary of effort instead of a briefing on movement. A diary says "worked on X, had calls about Y, blocked on Z." A briefing says "X shipped, Y slipped two weeks because of Z, and I need a decision from you by Thursday."

If your weekly report gets skimmed and forgotten, the fix isn't more detail. It's a different structure. Here's the one I've used across three teams and two companies, plus the AI shortcuts that actually help without turning your update into beige mush.

Lead with the change, not the chronology

Most weekly reports start with Monday and walk forward. Readers don't care what happened first. They care what's different now compared to last Friday.

Open with a short "what moved" section. Three to five bullets, each one a change in state:

• Checkout error rate dropped from 2.1% to 0.4% after the retry fix shipped Tuesday.
• Onboarding redesign slipped from May 12 to May 26 — design review found a blocker in the permission flow.
• Hired a contractor to clear the support backlog; down to 40 open tickets from 210.

Notice each bullet has a number or a concrete state. "Made progress on onboarding" tells the reader nothing. "Slipped two weeks, here's why" tells them everything.

If nothing moved, say so. "No movement on the migration this week — the vendor hasn't returned the API keys." That's more useful than three paragraphs of activity that add up to zero.

Put the ask in the first screen

The single biggest failure of weekly reports is burying the request. People write six sections of context and then, in paragraph eleven, mention they need budget approval.

Flip it. After the "what moved" bullets, add a short "what I need from you" block. One to three items, each with an owner and a date:

• Need sign-off on the revised scope by Wednesday so engineering can start sprint planning Thursday. — Priya
• Need two hours from the data team to pull Q2 cohort numbers. — Marco

If you need nothing, write "No asks this week." That's a signal too. It tells the reader they can skim the rest.

This is the same principle behind a good status update email: the reader should know within ten seconds whether they need to act.

Keep a running "risks and blockers" list

Weekly reports that only describe completed work create a nasty surprise later. The launch looks fine for five weeks, then suddenly it isn't, and leadership feels ambushed.

Keep a persistent section — the same heading every week — for risks and blockers. Carry items forward until they're resolved. Mark each one with a status:

• Blocked: Payment provider sandbox is down. Escalated to their support Tuesday. Owner: me. Next check: Friday.
• Watching: QA capacity is tight for the last sprint. Mitigation: pulled one engineer from the backlog. Owner: Sam.

The carry-forward discipline is what makes this work. A risk that appears one week and vanishes the next without explanation reads as either solved or ignored. Neither builds trust.

Write it in the reader's language

Engineers write weekly reports for their manager, who writes one for a director, who writes one for a VP. By the time it reaches the top, "refactored the auth middleware" has become "made progress on platform work" — which means nothing to anyone.

Write your report for the person one level up, but include enough plain-language translation that it survives the next hop. "Refactored the auth middleware (the login system) — this cuts login failures by roughly half and unblocks the SSO feature for enterprise customers."

That parenthetical does more SEO for your career than any amount of jargon. It's the same reason a good project status update names the business impact, not just the deliverable.

Where AI helps — and where it flattens your voice

I use AI on weekly reports, but not to write them. Here's the split that works:

Let AI do:

• Summarize a pile of tickets, PRs, or Slack threads into a candidate list of "what moved" bullets. It's good at finding the signal in 80 items.
• Tighten a draft. Paste your bullets and ask it to cut anything that doesn't change state or name an owner.
• Turn a long thread into a first-draft risk list with owners and dates.
• Draft the "what I need from you" block from a messy paragraph of asks.

Keep doing yourself:

• Deciding what counts as movement. AI will happily call a status meeting "progress."
• The judgment call about what to escalate. Only you know which blocker is politically sensitive.
• The tone. AI-written weekly reports have a tell — everything is "on track," nothing is anyone's fault, and every risk is "being monitored."

The failure mode is real. Feed a chatbot a week of activity and it hands back a smooth, confident summary that omits the one thing your director needed to know. You have to read it like an editor, not a proofreader.

A quick prompt that works: "Here are my notes from the week. Give me three bullets describing what changed state, one bullet per risk with an owner, and a list of anything I need from someone else. Don't invent status."

Then rewrite the output in your own words. The structure is the value. The prose should sound like you.

A template you can steal

Here's the shell. It fits on one screen if you're disciplined.

## Week of [date]

### What moved
- [Change in state, with a number if possible]
- ...

### What I need from you
- [Ask] — [owner] — [date]
- (or "No asks this week.")

### Risks and blockers
- **[Status]:** [Risk] — [owner] — [next check]

### Next week
- [Top 1-3 priorities, not a task list]

Four sections. No preamble. No "hope everyone had a good weekend." The reader knows exactly where to look.

Two habits that make it stick

Send it at the same time every week. Predictability is half the battle. If your report lands Thursday at 4pm like clockwork, people build it into their week. If it shows up whenever you finish it, it competes with everything else.

Keep a scratch file all week. Don't try to reconstruct the week on Thursday afternoon. Jot one line each day — a number that changed, a decision made, a risk you spotted. By Thursday you have raw material instead of a blank page and a vague memory of being busy.

The weekly report isn't a performance of effort. It's a briefing. Write it like the reader has four seconds and one question: what do I need to know, and what do I need to do? Answer that in the first screen, and people will start reading to the bottom.