A recurring report is best run as a repeatable workflow rather than a project. The content changes every cycle; the stages do not. When the workflow is fixed, the report stops depending on whoever is producing it and starts depending on the process – which is what makes it reliable.
This guide sets out the six stages of report production, what happens in each, and where the control points sit. It is the companion to How to Produce Recurring Reports on Schedule.
The workflow is the report’s production line. Fix the line, and the report comes out the same way every cycle.
The six stages
Every recurring report runs through the same six stages, whether it is a board pack or a compliance filing.
| Stage | What happens | Control |
|---|---|---|
| 1. Intake | Inputs and data are requested and collected | Intake template, named contributors, deadline |
| 2. Freeze | The data is locked from the source of truth | Data freeze, version recorded |
| 3. Draft | The narrative and exhibits are assembled | Standard template, prior-cycle baseline |
| 4. Verify | Figures and claims are checked against source | Traceability, reconciliation |
| 5. Review | Accuracy, consistency and compliance are checked | Checklist, independent reviewer |
| 6. Approve and distribute | The report is signed off, issued and archived | Approval gate, version control |
Two stages decide whether the cycle holds: intake, because if inputs are late everything is late, and verify, because if a figure is wrong the report is worse than late.
Stage 1 and 2: intake and freeze
These two stages are where most recurring reports are won or lost.
Intake requests specific inputs against a template, names who supplies each, and sets a deadline ahead of the freeze. Sending the same request each cycle teaches contributors the shape, so inputs improve over time.
Freeze locks the data. It is the point after which a change requires an explicit decision rather than happening silently. Without a freeze, the target keeps moving and drafting becomes rework.
Together they create the stable base the rest of the workflow builds on. See Intake & Briefing.
Stage 3: draft
Drafting is assembly, not invention. The report owner and contributors build the narrative and exhibits against the standard template, starting from the previous cycle.
- Reuse structure, not content. The template carries the shape; the analysis is this period’s.
- Draft against the frozen data. Drafting a moving target guarantees rework.
- Mark AI-assisted content as unverified until it is checked. See Using AI to Draft Reports.
- Keep one owner per section so accountability is clear.
A draft produced against a frozen data set and a standard template is most of the way to a finished report.
Stage 4 and 5: verify and review
Verification and review are different tasks, and both matter.
- Verify checks every figure and claim against source. It is mechanical and traceable: figure, source, who checked.
- Review checks accuracy, consistency and compliance, against a checklist, ideally by someone who did not draft it.
Verification asks “is this number right?” Review asks “is this report right?” A report can pass one and fail the other, which is why both exist.
Stage 6: approve, distribute and archive
The final stage makes the report authoritative.
- Approve: a named approver signs off, and the approval is recorded.
- Distribute: the right version reaches the right audience, through a controlled list.
- Archive: the report and its data snapshot are stored, so the cycle can be reconstructed later.
Skipping the archive is common and costly. Without it, “which number did we send last month?” has no reliable answer. See Report Approval & Sign-off.
Why a fixed workflow beats a heroic one
Teams often pride themselves on producing a good report under pressure. That is a symptom, not a strength: it means the process depends on heroics, and heroics do not scale or repeat.
A fixed workflow produces three things a heroic process cannot:
- Consistency – the same report, produced the same way, every cycle.
- Resilience – a report that continues when the usual person is unavailable.
- Improvement – a stable process that can be measured and improved, rather than reinventing each cycle.
The workflow is the asset. Protect it.
What makes the workflow repeatable
A workflow is repeatable only if its inputs, roles and controls are fixed, even as the content changes.
- Fixed inputs: the same intake template, the same sources.
- Fixed roles: the same owner, contributors, reviewer and approver each cycle.
- Fixed controls: the freeze, the verification and the approval gate happen every time.
- Fixed structure: the template governs shape; only the analysis changes.
When these are fixed, the workflow stops depending on memory and starts producing the same result under different people and different pressures.
Adapting the workflow to report size
The six stages apply to every report, but their weight varies with size.
| Report size | What stays firm | What scales down |
|---|---|---|
| Small internal | Freeze, verify, approve | Formal review, multiple contributors |
| Standard management | All six stages | Depth of review |
| Large or regulated | All six stages, formal records | Nothing – the controls are the point |
The mistake is to scale down the controls rather than the effort. Verification and approval should survive every size; what changes is how much ceremony surrounds them.
Roles and controls in each stage
Each stage has an owner and a control, and keeping them paired is what makes the workflow accountable.
| Stage | Owner | Control that must happen |
|---|---|---|
| Intake | Report owner | Inputs requested against the template by the deadline |
| Freeze | Report owner | Data locked and version recorded |
| Draft | Section owners | Draft produced against the frozen data |
| Verify | Verifier | Every figure traced to source |
| Review | Reviewer | Checklist completed, independent of the author |
| Approve and distribute | Approver | Sign-off recorded; approved version issued |
When a cycle slips, the table usually shows which pairing broke – a stage ran with no owner, or an owner skipped the control. That is a more useful diagnosis than “we ran out of time.”
Common mistakes
- Starting with drafting. Without intake and freeze, drafting chases a moving target.
- No data freeze. Late changes cascade into rework and errors.
- Verification after review. Accuracy should be confirmed before the formal review, not discovered within it.
- No archive. Each cycle cannot reconstruct or learn from the last.
- Improvising the workflow each cycle. The process never stabilizes or improves.
Frequently asked questions
What is the report production workflow?
Six stages: intake, freeze, draft, verify, review, then approve and distribute. The content changes each cycle; the stages do not.
Which stage is most important?
Intake and verification. Intake determines whether the cycle has what it needs on time; verification determines whether what goes out is true. The other stages can be recovered from if they slip.
Should you freeze the data before or after drafting?
Before. Freezing first stops the target moving mid-draft, which prevents rework and the errors that creep in when numbers change late.
What is the difference between verification and review?
Verification checks every figure against source – a mechanical, traceable task. Review checks accuracy, consistency and compliance against a checklist, ideally by someone independent of the drafting.
Do you need to archive every cycle?
Yes. Archiving the report and its data snapshot is what lets you reconstruct what was sent, reconcile future disputes, and learn from the cycle.
Can a small team run the full six-stage workflow?
Yes. The stages stay; what scales down is ceremony, not control. A small team still freezes the data, verifies the figures and has a named approver – it just does less of the surrounding machinery.
How long does the workflow take?
That depends on the report, but the workflow reduces the time over cycles because it removes rework and chasing. The first cycle is the slowest; each subsequent cycle reuses the structure and the process.
What is the single most important control in the workflow?
The data freeze. Everything downstream depends on a stable target, and a moving data set makes verification impossible and drafting rework inevitable.
Who runs each stage of the workflow?
The report owner runs intake, freeze, and approve; section owners draft; a verifier checks the figures; a reviewer completes the checklist; the approver signs off. Keeping a named owner per stage is what makes the workflow accountable.
Can stages run in parallel?
Yes, where dependencies allow. Drafting independent sections can run together, but verification and review should follow the freeze, not race it. Sequencing mistakes cost more time than they save.
What is the most common workflow failure?
Starting with drafting. Without intake and freeze, the report is built on inputs that arrive late and data that changes, which guarantees rework and, often, an error.
Should the workflow be the same for every report?
The six stages are, but the ceremony around them scales with the report. A small internal report still freezes, verifies and approves; it just does less of the surrounding machinery.
How do you introduce the workflow without disrupting the team?
Run one existing report through the six stages, measure what changed, and use the result to justify the rest. A workflow imposed without evidence is resisted; one that visibly reduces rework spreads on its own.
How does the workflow handle a report with no prior cycle?
The first cycle is fuller: it defines the audience, the structure and the definitions. After that, each cycle is a delta on the last – which is why the first cycle is the slowest and the most important to document.
What is the fastest way to see the workflow’s value?
Run it on your most painful recurring report for one cycle, then compare the effort and the errors to the previous cycle. The contrast is usually obvious enough to justify extending it to the others.
Does the workflow need to be documented?
Yes, briefly. A one-page description of the six stages, their owners and their controls is enough, and it is what lets a new contributor run a report without being taught from scratch. Keep it with the templates, not in someone’s head. Documentation is what turns the workflow into a team asset rather than one person’s habit or memory alone, and it is the first thing to write.
Next step
Run your next report through the six stages deliberately, and note where it slips. The workflow is the foundation of reliable recurring reporting. See How to Produce Recurring Reports on Schedule for the full method, and book a reporting pilot to have a cycle run for you.
Sources
- APMP, Body of Knowledge: end-to-end proposal process, reviews and production management, applied to recurring report production.
- Intuit Enterprise Suite, Future of Finance 2026 Report (2,000 finance leaders, May 2026): the volume of manual work in recurring reporting.
Good-practice claims are cited from their sources; no statistic in this article is invented.