Already written when they ask.
Some documents should simply exist, current, without anyone rebuilding them. A standing report in Abstract is one living document with an agent on a schedule, not fifty-two stale copies.
The weekly update is the same document every week with different numbers and a slightly different story.
Rebuilding it costs someone their Monday morning; skipping it costs everyone context. And the version that finally goes out is stale by Thursday.
Write it once. It keeps itself current.
Write it once.
The report is a living document bound to its sources, with your structure and your voice rules.
Put it on a schedule.
Every Monday at 7am the agent reads what changed, applies the safe updates, and drafts the narrative shifts as proposals. In beta
Approve and it's out.
Review the two or three things that need your call. The document is the latest version; there is nothing to send around unless you want to export it.
The CEO stopped asking for the weekly report, because it stopped needing to be asked for. It updates Monday mornings; she reads it Monday lunchtime. When churn moved enough to change the story in week 31, the report didn't quietly smooth it over: the reframed paragraph sat waiting for the ops lead's approval, with the source movement attached.
The schedule automates the legwork, never the judgement.
Figures refresh silently, marked and reversible; the narrative waits for a human.
A week with nothing to say produces "no change recommended", not invented news.
Sources in, one living page out.
Sources: files and exports today; CRM and API feeds Coming. Distribution: a live published page In beta, or export on demand.
One honest line: this is a document with a pulse, not a dashboard with paragraphs. Dashboards show numbers; this tells whoever opens it what the numbers mean.
Questions
What if I want weekly snapshots too?
Keep the living document and export a dated copy whenever you like; or run a template that creates one per cycle. Both patterns work.
Can it email people?
Distribution beyond the published page is on the roadmap; today you share the page or export.
How is this different from the reporting use case?
Same trust mechanics, different rhythm: reporting is you producing a cycle deliverable; a standing report is a document that maintains itself between your approvals.