It is Friday afternoon at an agency. Someone opens three tools, exports the week's numbers, pastes them into last week's deck and writes a paragraph on what changed. By six it is sent. On Monday nobody mentions it.
Ask who owns that report and you get three answers. The account manager, because the client reads it. The analyst, because they build it. The director, because they asked for it. In practice, nobody owns the result. Someone owns the Friday afternoon.
Builders and readers
Most weekly reports have one builder and several readers. The builder knows where every number comes from but rarely decides what the report is for. The readers know what they need but never see how it is made.
So the report keeps its shape long after anyone needs that shape. A section is added for a client who left. A chart nobody reads survives because removing it means asking permission.
What breaks
- It is late when the builder is away. The process lives in one person's routine.
- Nobody questions the numbers. A paste into the wrong row can sit there for weeks.
- The writing is the first thing to go. When time is short, the paragraph on what changed becomes "see attached". That paragraph was the only part the client wanted.
Give the result an owner
The fix is not a better template. It is one name next to the result: the person who decides what the report says and checks it before it goes out. Usually that is whoever faces the client.
Then separate the building from the owning. The building is the same steps every week: pull the export, check it, total it, write what moved. That part can run as a process. The owning stays with the person.
Let code do the counting
If you hand this to AI, keep one rule: a language model should never write a number it has not been given. Totals should be computed from the data by code, and the written part should quote them, word for word.
Ask for the boring checks too. Which rows were outside the week? Which were duplicates? A report that says what it left out is easier to trust than one that looks perfect.
Keep the check, drop the rebuilding
The owner's job becomes ten minutes instead of an afternoon: read the totals, read what moved, fix a sentence, approve. The report is ready on time when someone is on holiday, because the steps no longer live in their head.
This is how we run it in AUGMTD: you hand it the week's export, the totals are computed by code, the report is written around them, and nothing reaches the client until the owner has checked it. But the idea works with any tool. Name the owner first.