Reconciliation Gate Before Client Delivery (QA)

Reconciliation Gate Before Client Delivery (QA)

1. 01

   Map every metric in the report to its source system and definition

   Document which platform or database each number comes from, including the exact metric name and date range. This prevents mixing apples and oranges when the client asks for a breakdown.

2. 02

   Compare platform-reported conversions against backend order data for one client account

   Pull the sum of conversions claimed by ad platforms and analytics tools for a recent period, then compare it to actual orders or leads in the CRM or backend. Quantify the gap so you know how much to trust the dashboard.

3. 03

   Verify that attribution settings match the client's accepted model

   Confirm whether the client's finance team expects last-click, first-click, or multi-touch attribution. If the dashboard uses a different model, flag the discrepancy before the report goes out.

4. 04

   Check data freshness for every source in the dashboard

   Ensure each widget shows data from the expected time window, not a stale cache. A report with yesterday's numbers when the client expects real-time can damage credibility.

5. 05

   Reconcile totals across connected tools to catch double-counting

   For metrics like sessions or conversions that appear in multiple sources, confirm the dashboard deduplicates correctly. Overlapping tracking can inflate numbers and trigger client questions.

6. 06

   Review narrative notes and annotations for accuracy before publishing

   Check that any commentary or AI-generated insights match the underlying data. A wrong explanation of a dip or spike is worse than no explanation at all.

7. 07

   Run a white-label branding check on the final deliverable

   Confirm the client's logo, colors, and domain appear correctly, and that no vendor branding or internal notes leak through. This is the last line of defense before the report reaches the client.