When to use it
A team is preparing a growth report and needs concrete checks for chart purpose, axis integrity, color emphasis, dashboard density, caveats, ownership, and approval state before the report is used as decision evidence.
Checklist
Check whether charts, dashboards, and reporting notes are clear enough to support a growth recommendation without hiding caveats, owners, or approval state.

Decision frame
Decide whether a chart, table, dashboard, or memo is ready for review before it becomes the basis for a growth action.
A team is preparing a growth report and needs concrete checks for chart purpose, axis integrity, color emphasis, dashboard density, caveats, ownership, and approval state before the report is used as decision evidence.
OpenAnalyst should review Reporting Visualization Readiness Checklist, compare the decision evidence with the caveats, and keep the next recommendation approval-gated until the reviewer accepts it.
Reporting visuals help teams turn analytics into action. Charts, dashboards, and visual summaries should remain clear, accurate, and easy to trust before influencing SEO or business decisions.
This checklist helps teams validate whether reporting visualizations are ready for review, sharing, and decision-making.
Reporting visualizations should be accurate, easy to understand, and decision-ready before teams rely on them. Clear reporting improves trust and helps teams move faster with confidence.
It is ready when the chart type matches the reader task and the comparison job can be stated without a verbal correction. The metric definition, date range, segment, and reviewer question should be visible enough that another reviewer would understand whether the chart is showing ranking, movement, relationship, density, or exception inspection.
Hold the report when baseline, interval, sorting, unit choice, or axis range could change what the reviewer believes the movement means. The team can fix the chart or name the scale caveat, but it should not ask for approval while the visual magnitude is still ambiguous.
It prevents the team from treating decoration as evidence. Color should point to the decision signal, status, exception, or caveat. If color implies a false grouping or makes every category compete for attention, the reviewer can mistake visual weight for analytical confidence.
The reporting owner should remove monitoring-only context, move it behind the decision note, or create a separate memo when the dashboard is too dense for approval. The reviewer owns acceptance of the caveat and approval state; those responsibilities should not be merged into an informal "looks good."
Approve only the next evidence-backed reporting recommendation. If the recommendation affects a campaign, page, dashboard, or reporting cadence, keep that action held until the reviewer accepts the caveat and the operating owner explicitly approves the change.