Freeze a dashboard snapshot with its refresh time and filter state, then compare each export against that snapshot and an independent source control. A live dashboard and an older PDF can both be accurate for different cutoffs. Confirm comparability before treating the difference as an error.
Map the same number through every output
Synthetic example RP-OUT-01. A frozen source contains $1,000 spend. The refreshed dashboard and spreadsheet agree; an older PDF and a slide copied from it contain $950.
| Output | Spend USD | Cutoff | Decision |
|---|---|---|---|
| Source export | 1,000 | 10:00Z | Independent control |
| Live dashboard snapshot | 1,000 | 10:05Z | Matches source at agreed cutoff |
| 950 | 09:00Z | Stale; refresh and export again | |
| Slide | 950 | Copied from 09:00Z PDF | Replace after PDF check |
| Spreadsheet | 1,000 | 10:05Z | Matches control; inspect formula range too |
The PDF differs by −$50 (−5% relative to the source). In this fixture its stored refresh record establishes staleness. In a real workflow, a timestamp alone is not enough: confirm the refreshed data and the filters used.
Export inspection sequence
- Refresh and freeze. Record source cutoff, dashboard refresh, and export time separately. Wait for required charts and sources to finish.
- Capture controls. Save date range, channel, account, currency, comparison period, and page-level filters. Record which state applies to each output.
- Inspect completeness. Count expected pages, charts, rows, and sections. Look for errors, empty charts, clipped tables, or missing pages.
- Recompute and round once. Compare full-precision totals before presentation rounding. A displayed sum may differ from the sum of rounded displayed rows.
- Review the recipient’s artifact. Open the final PDF, slide file, and spreadsheet after export. Check links, labels, units, formulas, and narrative.
Google’s PDF guidance says to apply controls before downloading and notes that exports can be incomplete. Export settings can include only selected pages. Verify the downloaded artifact rather than assuming a successful click guarantees a complete report.
Passing this check
The acceptance record should identify the exact output versions, source control, filters, exceptions, and reviewer. Agreement establishes consistency for that frozen slice. It does not prove all source tracking, attribution, or future refreshes are correct.
Sources and reproducibility
Technical references checked October 27, 2026. Worked examples are synthetic ReportPatch fixtures, checked by automated calculations.