Fixing Reporting Workflows with Better Forward

The forward is the whole game.

You write a weekly update, hit send, and 40 minutes later your VP forwards it to the CEO with one line: "See below." That forward is the only performance review your writing will ever get. Not the polish, not the word count, not the clever subject line. Whether a busy executive reads it once and knows what's happening — that's the bar.

Most weekly updates fail that bar for a boring reason: they report activity instead of movement. "Met with design, reviewed the spec, aligned on scope" tells your reader what you did with your calendar. It doesn't tell them whether the thing they care about — the launch, the revenue, the risk — moved this week. A VP can't forward a list of meetings. They can forward a sentence that says the launch is two weeks out and one dependency is at risk.

Here's the format that survives the forward test, and the reasoning behind each piece so you can adapt it rather than copy it.

Lead with the one thing that changed

If your reader only reads one line, make it the line that matters. Not "status: on track." Something with a noun and a number in it.

Weak: "Continued progress on the onboarding revamp."

Forwardable: "Onboarding revamp is 80% built; we're on track for the June 3 launch, with one open risk (below)."

The second version answers the three questions an executive actually has: what is it, how far along, and is it going to land. Write that sentence first, before anything else, even if you have to draft the rest of the update to figure out what the sentence should say. The lead is a conclusion, not a summary of your week.

Separate "what moved" from "what's stuck"

Two short sections, clearly labeled. This is the single highest-leverage structural choice in the whole document, because it maps to how your reader will act on it.

What moved this week gets three to five bullets, each one a completed change, not an activity. "Shipped the new signup flow to 10% of traffic" beats "worked on signup flow." Past tense, done, measurable.

What's stuck gets the blockers, each with an owner and a date. Not "waiting on legal" — "Legal review of the data-processing addendum, owner: Priya, needed by May 20 or the June 3 date slips." A blocker without an owner and a date is just a complaint. Your VP can't forward a complaint; they can forward an escalation.

Keep both sections ruthlessly short. If "what moved" runs to nine bullets, you're listing tasks, not outcomes. Cut to the ones a stranger would recognize as progress.

Give the numbers their own line

Whatever your team measures — activation rate, tickets closed, revenue booked, latency — put the current number and the direction of travel in one place. "Activation: 41% (up from 38% last week, target 45%)." Three data points, one line.

The temptation is to bury metrics in prose or skip them because they're unflattering. Don't. A flat or falling number stated plainly, with a sentence on what you're doing about it, builds more trust than a vague "making good progress." Executives have seen enough updates to smell a number that's been hidden. Put it where they can find it.

Name the decision you need, if any

Most weekly updates don't need a decision, and saying "no decisions needed this week" is fine. But when you do need one, make it impossible to miss: a bolded line, the decision framed as a choice, and a default if no one answers.

"Decision needed by Friday: Do we hold the June 3 date with the current scope, or cut the reporting tab and ship June 3? Default if no reply: we hold the date and cut the tab."

That default is the part people forget. It converts your update from a question into a plan the reader can veto. Busy people forward plans. They ignore open questions.

What to leave out

The forward test is also a subtraction test. Three things reliably kill an update's chances of being read:

• The play-by-play. Nobody needs the sequence of meetings that produced the outcome. They need the outcome.
• Hedging language. "We're cautiously optimistic that we may be able to potentially..." A VP can't forward a sentence they can't parse. Pick the verb. "We expect to ship June 3."
• Anything the reader already knows. If it was in last week's update and nothing changed, it doesn't belong in this one. Repetition reads as padding, and padding is what makes people stop opening the email.

A template you can paste

Here's the whole thing in a shape you can reuse every week. It takes about 15 minutes to fill in once you've internalized the sections.

Weekly update — [Team] — week of [date]

Bottom line: [One sentence: what's the headline, on track or not, and the date.]

What moved:

• [Completed outcome, measurable]
• [Completed outcome]
• [Completed outcome]

What's stuck:

• [Blocker] — owner: [name], needed by [date], consequence: [what slips]

Numbers: [Metric]: [value] ([direction vs. last week], target [X])

Decision needed: [The choice, the deadline, the default.] (or "None this week.")

That's it. No appendix, no status color-coding, no RAG dashboard. If a reader wants more depth, they'll ask, and you'll have the detail ready because you did the work.

The habit that makes it fast

The reason weekly updates take two hours is that people write them from memory on Friday afternoon, reconstructing a week they've already half-forgotten. Keep a running note all week — a single doc where you drop one line each time something ships, slips, or a number moves. By Friday you're assembling, not remembering. The update writes itself in the time it takes to cut the list down to the three things that matter.

One more thing: send it at the same time every week. Predictability is half of why an update gets read. When your VP knows the Friday 3pm note is coming, they stop asking for status in side channels, and the forward becomes a habit instead of an accident.