Writing the weekly narrative

The weekly report has five numbers on it: dials and connects, live conversations, meetings set versus held, the acceptance rate. Below them sits a paragraph, and the paragraph is the part that takes judgment to write. The numbers say what happened. The narrative says what it means and what happens next, and a program that ships numbers without the paragraph is asking the reader to do the analysis the sender was paid to do.

Three sentences, three jobs

The narrative we write under every client funnel has a fixed shape. What changed. What we learned. What we adjust.

What changed names the one movement worth noticing, against last week. "Connects fell by a third while dials held steady." Not a recap of every number, the reader has the table. The discipline is picking the single movement that matters, which forces the writer to actually rank them.

What we learned is the interpretation, and it is where honesty lives or dies. Falling connects on steady dials points at the list or the calling windows, the diagnosis we walked through in the connect-rate post. Three prospects raising the same new objection is a message finding, the kind an objection map exists to accumulate. The learning sentence commits to a cause. A narrative that says "numbers were mixed this week" has learned nothing and is admitting it.

What we adjust converts the learning into one action with a date on it. Rebuild the stale list segment. Shift the afternoon calling window. Test the new response to the pricing objection. Next week's narrative then has to report what the adjustment did, and that obligation is the mechanism that keeps the loop honest. Anyone can write an insight. Publishing the follow-through is the hard part.

Why the paragraph is hard to fake

Dashboards are easy to generate and easy to ignore. The paragraph is neither. Writing it requires someone to have watched the week closely enough to rank what happened, and it leaves a public record of judgment that either holds up or does not. Read four consecutive narratives from any program and you know whether anyone is steering: either the adjustments connect week to week into an iteration, or the paragraph is weather commentary rewritten every Friday.

The narrative is also where bad weeks keep their dignity. A rough week reported as "conversations dipped, here is our read on the cause, here is the change we are making" builds more trust than a good week reported as a victory lap. In our experience clients do not leave over bad weeks. They leave over reports that go quiet when the numbers do.

The reader's side of the contract

A narrative earns a two-minute read and deserves a reply. The one-line response to "what we adjust" is where a client steers the program: confirm the change, veto it, or add the context the vendor cannot see from outside. The five numbers make outbound observable. The paragraph and the reply make it steerable, and steering is the entire reason weekly reporting beats monthly.

Every CommandVA weekly report carries this narrative, including the weeks it has to explain us. If your current report is a dashboard with no author, book a strategy call and we will show you four consecutive weeks of ours, adjustments and all.