Most PR dashboards fail not because the data is wrong but because they are designed for the comms team rather than the people who approve budgets and make strategic calls. An executive-ready dashboard answers three questions: Are we visible? Is the coverage helping or hurting? What should we do about it?
If your dashboard takes more than 90 seconds to read, it will not get read.
The six metrics that belong on page one
Executives do not want 20 charts. They want a tight signal. After working with UK comms teams across financial services, healthcare, and infrastructure, these six metrics consistently survive the "does leadership actually use this?" test:
| Metric | What it shows | Update cadence | |--------|--------------|----------------| | Share of voice (quality-weighted) | Competitive visibility in Tier 1 and Tier 2 outlets | Monthly | | Coverage volume trend | Total mentions with 13-week rolling average | Weekly/monthly | | Sentiment split | Positive / neutral / negative as percentage, trended | Monthly | | Message pull-through | % of coverage that includes at least one key message | Monthly | | Top outlet and journalist list | Where and who is driving coverage | Monthly | | Issue/risk flag | Any emerging negative theme or regulatory mention | Real-time / weekly |
Keep these on a single page or screen. If you are using Meltwater, Cision, or Signal AI dashboards, build a saved view that shows only these metrics -- do not link to the full platform.
Structure the dashboard for scanning
Executives scan top-left to bottom-right. Structure accordingly:
Top row: The headline number. This quarter's quality-weighted SOV with a directional arrow (up/down/flat) and the percentage-point change vs last quarter. Make the font large. If SOV went from 28% to 32%, the arrow and the "+4pp" should be the first thing anyone sees.
Middle row: Two or three small charts. Coverage volume trend (line chart, 13 weeks), sentiment split (stacked bar, 3 months), and message pull-through (single percentage with trend). Keep axis labels minimal. No gridlines.
Bottom row: The narrative and actions. Two short paragraphs, not a wall of text.
Right sidebar or second page: The issue/risk flag and the top outlets/journalists table.
Tools like Power BI, Looker Studio (free), or Tableau can pull data via API from Meltwater or Cision. If you do not have BI tools, a well-structured Google Slides deck updated monthly works. The format matters less than the discipline of keeping it tight.
Write the narrative that makes the numbers matter
The narrative is the most important part of the dashboard and the part most teams skip. Two paragraphs:
Paragraph 1 -- What changed: "Coverage volume increased 18% month-on-month, driven primarily by the FCA regulatory announcement on 12 January. Sentiment shifted negative (42% negative vs 28% baseline) due to Guardian and FT reporting on compliance costs. Share of voice declined 3pp as competitor X dominated trade coverage with their product launch."
Paragraph 2 -- What we recommend: "We recommend a proactive briefing with FT and Times journalists to reframe the regulatory story around our compliance readiness. The competitor SOV spike is likely temporary and does not warrant a reactive response. We will monitor for a further two weeks before reassessing."
This is the section that turns a dashboard from a scorecard into a decision tool. Without it, executives look at the charts, nod, and move on.
Include a methodology note (but keep it short)
Every executive dashboard should include a one-paragraph methodology note, either as a footnote or an appendix slide. It should state:
- Which monitoring platform provides the data (e.g., Meltwater, Signal AI)
- The source set (e.g., "423 UK outlets including all national dailies, top 30 trade titles, BBC/Sky/ITV/Channel 4 broadcast transcripts")
- How sentiment is scored (automated NLP, human-validated, or hybrid)
- How quality weighting is applied (Tier 1/2/3 multipliers)
- The reporting period and any known data gaps
This prevents the meeting from derailing into "where do these numbers come from?" The first time a CFO or non-executive director questions the methodology, you will be glad the note exists.
Common mistake: the everything dashboard
A FTSE 250 corporate affairs team built a 14-page monthly dashboard in Cision covering every possible metric: coverage by outlet type, journalist sentiment, social echo, message variants, regional breakdown, competitor deep-dives, and historical comparisons going back 18 months. The CEO stopped reading it after month two. The head of corporate affairs found out three months later when the CEO's EA mentioned it went straight to archive.
The team rebuilt the dashboard as a single page with five metrics and a two-paragraph narrative. The CEO now reads it the morning it arrives and references it in board discussions.
The lesson: dashboard scope should match the audience's attention budget. Comms teams can have a detailed operational dashboard with 15+ metrics. The executive version should be a curated summary.
Delivery logistics that affect adoption
- Timing: Send the dashboard at the same time each period. Tuesday morning works well for weekly summaries (Monday data is processed). First week of the month for monthly. Consistency builds the habit.
- Format: PDF attachment or a direct link to a live dashboard. Do not embed charts in the email body -- they break across email clients.
- Length: One page for the monthly executive summary. A second page for the methodology note and detailed tables if wanted.
- Access: If using a live dashboard (Power BI, Looker Studio), make sure every recipient has access before launch. Nothing kills adoption faster than a broken link on first send.
Checklist: before you send
- [ ] Dashboard fits on one page / one screen
- [ ] Directional indicators (arrows, pp change) are visible at a glance
- [ ] Two-paragraph narrative explains what changed and what to do
- [ ] Methodology note is included
- [ ] Competitor set and source list are documented
- [ ] Sent at the same time as last period
- [ ] All recipients confirmed they can access the dashboard
Build for the decision-maker, not for the analyst. The operational detail lives elsewhere. The executive dashboard exists to drive one thing: the next decision.