Management reports that accept only approved figures

A management report can combine an ERP export, CRM data, a spreadsheet and manual adjustments. A number introduced during commentary may look as trustworthy as a sourced figure. The publication process should keep those two data types separate and reject unsupported values before the report reaches its audience.

The management newsroom uses a renderer that receives an approved figure set and a commentary draft. It keeps source references with the figures and checks the text against the allowed representations before publication.

Give every figure a meaning and an owner

A number is useful only with its definition. For each metric, record:

• business name and formula;
• period, currency and unit;
• source system or query;
• refresh and adjustment rules;
• owner responsible for reconciliation;
• permitted display forms and rounding.

Revenue, margin, active customer and plan attainment can be calculated correctly from different source selections and still mean different things. A metric dictionary gives the controller a contract to review before report assembly.

Reconcile sources before writing prose

Reconciliation should be an explicit function with a recorded result. Define matching keys, time period, rounding tolerance, currency conversion, source precedence and the owner of an unresolved difference.

Keep the disagreement visible when values exceed the rule. A report can annotate the issue with both source references and hold publication of the affected commentary. The process should never silently average or overwrite a value simply to make the page look complete.

Control the number vocabulary

The renderer can derive permitted representations from the approved figure set. For each value, include the configured formats for units, percentages, currency, rounding and ranges. Commentary containing a digit sequence outside the permitted set moves to review.

This check works for text written by a controller and text drafted with a model. A model may suggest explanations, but it does not approve a figure. The renderer also needs tests for dates, identifiers, abbreviations and numbers embedded in a sentence, because a digit can be valid in one context and misleading in another.

The number check cannot prove that a figure has the right label. Commentary should reference a metric identifier, and a controller should review whether the wording matches the metric definition.

Make publication a visible state

Use states such as draft, reconciled, review required, approved and published. Store the source snapshot, metric-definition version, reconciliation result, commentary version, reviewer and publication time.

If a source changes after approval, create a new report version. If commentary changes, rerun the number and source checks. An accepted report should be reproducible from the recorded inputs and rules.

Run the work in four operating steps

1. Inventory source systems, manual adjustments, metrics and report sections.
2. Define metric owners, formulas, tolerances, formats and escalation roles.
3. Control figure approval, commentary checks and publication state in code.
4. Compare the controlled report with the current report for several cycles.

The parallel run should record time from source close to publication, reconciliation effort, unresolved differences, rejected commentary and controller corrections. Keep a manual fallback for a source outage or an unavailable model.

Include the controller in the control design

The system can enforce data and number rules. A person still decides whether the metric definition is right, whether an unresolved source difference is acceptable and whether the report is ready for management review.

Give the controller a concise review surface:

• figure and metric identifier;
• source and query version;
• reconciliation result;
• commentary with linked figures;
• rejected values and reason;
• decision and reviewer.

The interface should make an unsupported number easy to correct and an unresolved source conflict impossible to overlook.

Price the reporting workflow

Syntalith lists reporting automation from €3,500 net. A quote depends on source connectors, metric preparation, reconciliation logic, output format, review roles, monitoring and support. Model usage is one cost line beside data preparation and controller time.

Use the organisation's current report to estimate the opportunity:

monthly value = preparation and review time saved
                + avoided correction or meeting delay
                - integration, model and operating cost

Replace the estimate with measured parallel-run data before expanding the workflow.

Publication readiness list

1. Does every figure have a definition, owner, period and source?
2. Are tolerances and source precedence explicit?
3. Does a conflict remain visible until an owner decides?
4. Are approved figures separate from commentary?
5. Can the renderer reject unsupported number forms?
6. Are labels checked against metric identifiers?
7. Are report, rule and source versions retained?
8. Can the controller approve, reject or request a new version?
9. Does the process have a manual fallback?

If a board report depends on manual copying and source questions delay review, bring one edition to a free process scan. The case page shows the control pattern.