Client Reporting Reconciliation Gate (QA)

Client Reporting Reconciliation Gate (QA)

1. 01

   Map every metric in the dashboard to its source definition

   Confirm that each KPI shown to the client traces back to a documented source field, so a change in platform naming does not silently alter the number reported.

2. 02

   Pull the underlying data from each connected source and verify that the dashboard aggregates match the platform's own reporting interface within a tolerance you define, typically 1% or less.

3. 03

   Check data freshness timestamps on every tile

   Stale data erodes trust faster than a wrong number. Confirm the last refresh time is visible and within the agreed SLA for each source.

4. 04

   Validate that white-label branding is applied consistently

   A client-facing report with a vendor logo or default color scheme undermines the agency's positioning. Review the header, footer, and export templates before sending.

5. 05

   Test the narrative layer for accuracy and tone

   If the platform auto-generates insights or commentary, read every line for factual claims and client-appropriate language. Replace any generic or misleading phrasing with a specific, actionable note.

6. 06

   Confirm that the report reaches the right stakeholders with the right access

   Verify the distribution list and permission levels, ensuring that internal staff see the full data while client users see only their approved view.

7. 07

   Document any reconciliation exceptions and the resolution path

   When a discrepancy appears, log the cause, the fix applied, and the date, so the same issue does not resurface in the next cycle.