Define the report’s job

In this example, a marketing lead needs a weekly view of channel performance before a planning meeting. The report should make meaningful changes visible, identify data limitations and help the team choose what to investigate. It does not automatically reallocate budgets or claim to explain every movement.

Begin with the questions the meeting needs to answer. Which campaigns changed materially? Are the numbers complete enough to compare? What requires a channel owner’s attention? The reporting specification follows those questions, rather than collecting every metric an API happens to provide.

Agree what every number means

List the sources, reporting period, time zone, currency, account scope and calculation for each measure. Agree what a conversion means in each source. A conversion in an ad platform, an event in analytics and a qualified opportunity in the CRM are three different things. Adding them up under one label gives you a number that looks certain and is not.

Store definitions alongside the report. If a measure changes, record when the definition changed and whether historical comparisons remain valid. Keep attribution windows visible. A report should distinguish the platform’s reported results from outcomes verified elsewhere.

  • Source and account scope
  • Time zone, date range and comparison period
  • Metric formula and inclusion rules
  • Attribution window and known limitations
  • Owner of each definition

Collect, then check

On schedule, the system collects the agreed data into one reporting layer that nothing else writes to. It only has the access the job needs. This example can begin with read-only source permissions and a separate permission to write the reviewed report to its destination.

Before calculating a summary, check freshness, expected date coverage, missing accounts, duplicate records and required fields. A source returning no rows is not automatically evidence of zero activity. Compare the response with what the connector and reporting contract expect.

If a critical source is incomplete, hold the affected section and show the reason. Preserve the last successful output with its original timestamp. Do not silently present old numbers as the current period or fill the gap with a model’s estimate.

Calculate before asking for a narrative

Compute totals, rates and period comparisons using explicit formulas. For example, cost per lead needs an agreed spend field and lead count from compatible scopes. If there is nothing to divide by, show an explanation rather than an invented rate.

Only then hand the checked results and their definitions to the step that writes the summary. Ask it to separate observations, possible explanations and proposed investigations. A rise in reported cost per lead is an observation. Creative fatigue is a hypothesis until additional evidence supports it. Every numerical statement should be traceable to the calculation output.

Put review at the decision point

The reviewer receives the summary, source references, freshness indicators and unresolved checks together. They can correct the interpretation, request an investigation or approve the report for distribution. The workflow records the approved version and avoids sending multiple copies when a run is retried.

Budget changes, publishing and customer-facing claims remain separate actions with their own authority. A reporting system should not inherit those permissions just because it can suggest a next step.

  • What changed: validated observations
  • What might explain it: labelled hypotheses
  • What is uncertain: coverage and attribution limits
  • What happens next: action, owner and review date

Design recovery and ownership

Each run needs a record of the sources used, checks completed, output produced and delivery status. If a connector fails, the owner should see which part failed and whether a retry is safe. If delivery fails after approval, recovery should resend the approved output rather than rerun analysis without a reason.

The written guidance should cover expired permissions, changed source fields, corrected historical data and updated definitions. Agree who watches it and who responds when it breaks. A build does not imply round-the-clock support or an unchanging external API.

Evaluate whether the engine helps

Compare the new workflow with a baseline: preparation effort, data corrections, review time and how often the report supports a clear action. A faster report is not necessarily a better decision. Review whether the people using it understand its definitions and can challenge its conclusions.

To put this example into production, verify source access, agree definitions and test it in the team’s environment. Begin with one reporting decision and enough evidence to judge whether the workflow helps, then expand once running it has become routine.

Continue exploring

How to automate weekly social media reporting