Client report corrections: what to do when agency numbers change
A practical agency process for late reporting data: preserve the issued version, compare changed figures, decide whether to reissue and approve the correction.
When agency reporting numbers change after approval, preserve the approved report, compare the new figures with its source snapshot, and let the account lead decide whether the change needs a correction now or a note in the next report. Any replacement needs its own review and approval. An automated refresh should never quietly rewrite the report a client used to make a decision.
Separate a reporting mistake from later data
A report can change for different reasons. The agency may have selected the wrong account, copied an incorrect value or made an arithmetic error. Alternatively, the source may have reported additional activity after the original export. Record the observed difference before assigning a cause. A newer number alone does not tell you which explanation applies.
Google Analytics says processing can take 24–48 hours and report figures may change during that time. Those intervals describe processing behavior; they do not establish a universal point when every marketing metric becomes final. [1]
Google Ads also documents later metric adjustments, including late-arriving conversions and retrospective invalid-traffic removal. Those Google-specific behaviors justify checking extraction times and source context before calling every difference an agency mistake. Other platforms require their own checks. [2]
This guide covers the decision after a report has been approved or issued. For collecting inputs and reconciling different metric definitions before drafting, use our agency reporting workflow guide. The correction process below is Croissant’s recommended operating template, rather than a vendor feature.
Keep an issued snapshot and a separate freshness label
Give each report a stable reference such as CLIENT-A-2026-W44 and a revision such as v1. Keep its reporting window, governing time zone, metric definitions, source account references, extraction timestamps and approved output together. Store evidence in the team’s existing access-controlled system; avoid copying private client records into a general task board.
Record approval and distribution separately. A useful state sequence is draft, approved, issued and superseded. Alongside that, keep a data label such as provisional or reviewed at the agreed cutoff. An issued report may still contain clearly labeled provisional figures. Approval means someone accepted that version with its stated limitations; it cannot stop source data from changing.
Preserve the issued artifact and its approval record. Create a new candidate revision for later figures. If a live dashboard continues refreshing, retain the snapshot or export used for the client discussion and label the dashboard as current data. Otherwise two people can open the same link and discuss different numbers without realizing it.
Use a short delta record before asking AI to explain
For each changed metric, record the report reference, original value, new value, absolute difference, old and new extraction times, source reference and known explanation. Include a status: verified source revision, confirmed report error or unresolved. Check that account, period, filters, date basis and metric definition still match. A changed comparison basis belongs in the investigation queue.
Calculate derived measures from the accepted inputs using explicit arithmetic. Let AI draft a plain-language explanation from that record, but require it to preserve unresolved causes. “More conversions appeared in the later export” can be observed. “Our new creative caused the increase” needs separate evidence.
Assign one account lead to decide the business consequence and one reporting owner to check the data. In a small agency, one person may hold both roles. The record should still distinguish checking the figure from deciding what to tell the client.
Worked example: a revised conversion count changes the recommendation
This example is entirely synthetic. A fictional agency issues v1 of a weekly report showing USD 1,200 of spend and 20 attributed conversions. Its agreed cost-per-conversion calculation is 1,200 divided by 20, or USD 60. The report recommends that the account lead review the campaign because the client’s fictional review threshold is USD 55.
At the next agreed recheck, the same source, period and metric show 25 conversions and unchanged spend. The revised calculation is USD 48. The count rose by five, or 25%; the cost per conversion fell by USD 12, or 20%. These invented numbers illustrate arithmetic and a decision process, not campaign results or a suggested target.
The reporting owner verifies both exports and records that the source count changed. If the cause is still unknown, the correction keeps that uncertainty. The account lead sees that the earlier recommendation depended on USD 60 and approves a replacement report with the updated calculation and an explanation of the changed recommendation.
A proposed client note could read: “Revision v2 replaces v1 for this reporting period. The later source export shows 25 attributed conversions rather than 20; recorded spend remains USD 1,200. Cost per conversion is now USD 48. We have withdrawn the earlier threshold-based review recommendation while we assess the updated figures.” A person checks that wording and authorizes delivery. The reporting workflow does not change advertising budgets.
Agree when to reissue, annotate or investigate
Croissant recommends reissuing promptly through the agency’s approved process when a verified change alters a recommendation, affects a client commitment or corrects a misleading statement. Use the client’s reporting agreement and the account lead’s judgment to set materiality rules. A percentage threshold alone can miss an important change to a small count.
For a verified change that leaves the decision intact, the account lead may record it for the next scheduled report, with a clear comparison note. Agree that policy with the client before relying on it. Keep the original value and the revised value available so the next report does not silently compare a revised prior period with the originally issued figure.
Hold the affected conclusion when the account, definition or cause is uncertain. Assign an investigation owner and next check. Unaffected, independently verified sections may proceed if the account lead approves. Never fill missing data with zero or label an investigation complete because the narrative sounds plausible.
A tracking outage, wrong-client data or unauthorized distribution needs the appropriate incident process. A correction note alone does not resolve those problems. If the underlying automation needs repair or a new reporting rule, use the separate change request guide to scope and approve that work.
Approve the replacement and prove which version was delivered
Prepare the candidate revision with a short change note: what changed, why it changed if verified, which conclusions changed and which earlier revision it replaces. Recheck affected totals, charts and narrative together. Approval must identify this exact revision; approval of v1 does not automatically authorize v2.
Keep client delivery as a separate human-authorized action. Record the approved recipients, issued revision, delivery evidence and replacement reference. If delivery is uncertain, inspect the existing delivery record before considering another send. A reporting refresh should not trigger repeated correction messages.
Where the existing report system supports it, mark the old version as superseded and point to the replacement while preserving its history. If a PDF has already been downloaded, acknowledge that the old copy may remain in circulation. Clear replacement wording helps recipients identify the intended version; it cannot recall every copy.
For a first implementation, test this process with synthetic reports: unchanged figures, a verified late revision, an unexplained discrepancy and an uncertain delivery. Confirm that unchanged figures create no correction, unresolved causes stay unresolved and replacement delivery waits for approval. The reporting demo offers context for a scoped workflow discussion. Bring Croissant your report structure and correction rules through the contact form, using fictional data.
Implementation checklist
- Name the account lead, reporting owner and correction decision rules.
- Preserve the issued report, source snapshot, extraction times and exact approval.
- Keep report state separate from the data freshness label.
- Compare like-for-like metric definitions before calculating the difference.
- Record verified causes separately from unresolved explanations.
- Recheck affected calculations and recommendations in a new revision.
- Approve the exact replacement and authorize delivery separately.
- Record delivery evidence and link superseded versions to their replacement.
The sources behind the sauce.
Primary research and official documentation behind the cited points. The workflow examples and checklists are Croissant’s own guidance.