Production workflow · from source close to delivery evidence
Automate the recurring work without automating away accountability.
A reliable monthly board-report workflow is not one prompt that produces a deck. It is a controlled sequence connecting approved definitions, live evidence, a stable document, human review, preflight, audience policy, delivery, and an attributable run history.
The recurring calendarp. 2
Seven checkpoints in one report definition.
- Before closeLock metric definitions, owners, audience, schedule, and the approved page system.
- Source closeRefresh governed datasets and record source time, schema, and reconciliation state.
- Draft runPopulate bound elements, draft commentary, and surface missing or inconsistent evidence.
- Owner reviewResolve exceptions, verify narrative, approve decisions, and retain attributable changes.
- PreflightCheck overflow, broken bindings, stale data, required sections, access, and delivery configuration.
- PublishBuild the approved audience editions and send them through their configured targets.
- After deliveryKeep run status, delivery receipts, decisions, actions, and next-cycle changes together.
Failure is part of the workflowp. 4
Design the stop conditions before the schedule starts.
A source changes shape
Stop the affected binding, expose schema drift, and require an explicit mapping decision.
A number does not reconcile
Flag it for an owner; do not let generated narrative smooth over an unresolved difference.
The design overflows
Fail preflight or require review instead of silently shrinking, clipping, or dropping evidence.
An audience should not see a section
Use a governed variant and access policy rather than making an uncontrolled file copy.
Delivery fails
Keep an attributable failure state and retry policy rather than treating document generation as delivery.
The meeting moves
Run on demand against the same report definition without rebuilding the pack from scratch.
In Rahoto
The report is the operating surface.
Sources, bindings, pages, editable charts, schedules, variants, delivery targets, access policies, preflight, and run history are first-class parts of the same runnable document. People can review it in the editor; authorised systems can operate it through the publishing API.
Implementation path
- Connect and validate the source.
- Compose and bind the report.
- Configure variants, access, schedule, and delivery.
- Operate approved publications through the API.
AI can assist with analysis and composition, but the source, claim, access, and delivery controls remain explicit. See AI assistance and theTrust Center.
Start with the report that comes back next month.
Define one production cycle, reconcile it, then schedule the approved runtime.