How to turn social video data into an executive summary leadership will actually read

Most listening output lands as a dashboard or a chat thread. Leadership does not have time to interpret either. The finding sits three clicks deep, the numbers mix plays with reach, and nobody can say which video started it.

A one-page summary is what gets read. Below is the template, filled in with an illustrative example, with a method note that holds up when a senior reader asks "is this real or AI?"

What belongs in a one-page executive summary

Five blocks, in this order. Each with a short prompt your team can paste into the report.

• What happened. One sentence with the headline finding.
• What it means. The business consequence in plain language.‍
• What we recommend. Two or three actions, each with an owner and a date.‍
• Evidence. Three to five source posts you can open, labelled with platform, date and what was said. Plus a link to the underlying result set or export that the aggregate numbers came from.‍
• Method note. Window, sources, dedup rule, exclusions.

Put the bottom line first. The pattern public plain-language guidance recommends: state your purpose and the bottom line, and put the most important information at the beginning. Executives read in that order; the summary matches it.

For teams running a recurring version, our monthly insights series is the template as a cadence.

The template filled in: a worked example

Illustrative only, not a dig benchmark.

Fernlight Coffee (fictional) monitors October. The summary reads:

• ‍What happened. A complaint about leaking travel-cup lids spread in video in the last two weeks of October: 1,420 posts with a transcript in the window, 880 of them in the final week. A further 115 posts had no transcript (image carousels, short visual-only clips) and are counted separately.‍
• What it means. The issue is product, not service, and most of the discussion is spoken on camera rather than written in the post description.‍
• What we recommend.- Packaging confirms the lid batch by 7 November (Packaging, Dana Levin).- Social replies with the fix on the three highest-play videos by 4 November (Social, Jo Park).- Comms holds a statement ready by 5 November for publication on request (Comms, Priya Shah).‍
• Evidence.- Earliest post, 10 October, 180K plays, speech-only (link).- Highest-play post, 24 October, 2.4M plays, caption and speech (link).- Representative post, 28 October, 320K plays, speech-only (link).- Full result set: Monthly brand monitor export, October (link).‍
• Method note. Window 1-31 October 2026, 00:00 UTC. Sources TikTok, Instagram, YouTube. Dedup by platform post ID. 1,420 posts had a transcript and are the denominator for the speech-only split. 115 further posts had no transcript (image carousels, short visual-only clips) and are counted separately as a known gap, not folded into either side of the split. Counts are dig's collected corpus, not the whole internet.

The three source videos show that the complaint is real. The 1,420 figure comes from the export linked under evidence; the videos illustrate it, they do not prove it on their own.

What that split actually says about caption search

Of the 1,420 posts with a transcript, 920 mention the lid only in speech. A search restricted to post descriptions would miss those 920. It would surface the other 500 only when the description itself contained the brand or product term; the number that would actually surface depends on the exact query used.

What the transcript-only split does not show

The exclusion is also a story. 115 posts had no transcript. Many of those are image carousels or very short visual-only clips, which can show the leaking lid without anyone speaking about it. A readout that stops at "spoken on camera" counts those as background, when they may be the clearest demonstration. Pair the speech split with a hand review of the no-transcript cohort before concluding.

Writing each section

"What happened" as a finding, not a metric

A metric is "plays were up." A finding is "a complaint spread." Finding first; metric in the method note.

Recommendations with an owner and a date

"We should respond" is not a recommendation. "Packaging confirms the lid batch by 7 November" is. Every bullet carries a name and a date.

Plays, reach and engagement on separate lines

Example: "Plays: 18.6M. Engagement rate: 3.9%." Never a blended "impact score." Different metrics measure different things, and a blended number hides the mix.

Evidence that supports interpretation vs. recommendation

A factual claim needs supporting evidence: a link to the export, a hand-reviewed sample, a cited source. An interpretation ("the issue is product, not service") and a recommendation ("hold a statement") are judgment calls built on that evidence. Label them that way so the reader knows what they are reading.

The method note

Three to five lines at the foot of the page.

• Window: dates and time zone.
• Sources and networks covered.
• How duplicates and reposts were handled.
• Exclusions, with the count (minimum view count, comment cap, no-transcript posts).
• A line saying the counts come from the tool's collected corpus, not the whole internet.

Platforms define views differently. On Meta, for example, reel plays are now called "Views". Name the metric each platform reports; otherwise a comparison across networks silently misrepresents one of them.

Making the summary repeatable

Fix the template, the window and the metric definitions, then change only the content.

The Dashboard Builder app in the dig app store keeps the same views month to month, so the evidence block refreshes rather than rebuilds. The summary itself stays a written page the team owns.

Pro tip

Every factual claim needs supporting evidence. Label interpretations and recommendations clearly.

Key takeaways

• Leadership reads conclusions plus evidence, not dashboards.
• Use five blocks: what happened, what it means, what we recommend, evidence, method note.
• Keep plays, reach and engagement on separate lines.
• Link factual claims to the export or sample behind them; label interpretations and recommendations as such.
• State window, sources, dedup and exclusions in a method note, including the count of excluded no-transcript posts.
• Fix the template and definitions so each month is a refresh, not a rebuild.

Frequently asked questions

What should a social listening executive summary include?

A headline finding, its business meaning, two or three recommendations with owners and dates, links to the source posts and the underlying export, and a method note covering window, sources, dedup and exclusions. Keep it to one page.

How long should an executive summary of social media insights be?

One page. If it needs more, the extra material is appendix evidence, not summary. Leadership should get the finding and the recommendation in the first two lines.

Should I put engagement and reach in the same number?

No. Plays, reach and engagement measure different things and platforms define them differently. Report each on its own line and name the platform definition in the method note.