What a social listening report should include

A social listening report should be more than a screenshot of a dashboard. If you are writing a brief, reviewing a vendor’s delivery, or deciding whether a zip of files is enough, you need a way to tell a thorough reading from a slide deck of charts.

This is a checklist you can hold a delivery against, and then one public example of how dumub packages that work. It is not a claim that dumub’s format is the only possible one, and it is not a ranked list of tools. For how a report is bought versus a dashboard subscription, see Why not a dashboard?. For how pay-per-report work is priced in general, see Social listening without a subscription.

Start with the brief

Before anyone starts, the brief should say what “done” looks like.

Write down the question you need answered — a launch, a campaign, a reputation issue, a category debate. Name the markets, the sources you care about, and the dates. Say whether the output is a decision, a campaign readout, or a board pack, and who has to open the file. If you cannot state that, you will get volume without a finding.

A dashboard can keep watching a query after the work is filed. A report cannot. If what you need is alerts next month, say so now, and buy a desk. If what you need is a reading of this conversation, say what would change your mind when you see the evidence.

The contents of a complete report

Any serious report, from any vendor, should include at least the following.

The question and the scope. What was asked, which markets and dates, and what was left out.

How the material was found. Which platforms were searched or which links were pasted, and how the sources in the report were chosen. A headline comment count without this is hard to trust.

Volume in context, not only a headline count. How many sources, how many comments, and what share of the conversation the main themes represent — enough to see whether a finding is a thread or a handful of posts.

Grouped themes, with the smaller points inside them. The report should tell you what people said and why, not only how many mentions matched a keyword.

Comments you can actually read. A sample of quotes in the original language, with a translation beside them, and a link back to the platform. If you cannot open the original, you have a summary, not a report.

How tone or sentiment was judged, and on how many comments. A single score is not enough. The method should be visible, including whether tone was scored on every comment or on a sample.

The limits of the work. What was not covered: platforms left out, languages not claimed, forums or messaging apps that were never in scope. A complete report is honest about the edge of the brief. If HardwareZone, LINE, or a print clipping desk was never in the work, it should say so, rather than leave you to infer coverage from a logo list.

A slide pack or a one-pager is useful for a meeting. It is not a substitute for the evidence file. If you are sharing the work with a client or a board, they should be able to open the comments, not only the slides, without buying a seat.

A worked example: dumub’s public samples

dumub publishes two public walkthroughs of real reports, as they were delivered: the F1 Singapore Grand Prix sample (14 October 2026, 40 public posts, 11,448 comments) and the Singapore Airlines new-cabins sample (12 November 2026, 39 public posts and articles, 6,621 comments). They are sample reports, not client testimonials, and they are both Singapore-set. Use them to see the format, not as wins.

On the homepage, the zip is listed as report.html, slides.html, a deep-dives/ folder, comments.xlsx, a data/ folder, and START-HERE.html. You own the files: no seats, no login to open them, and no expiry. The written report opens with the finding, then the numbers, the themes with comments behind them, and the same report as a three-slide deck. Each source also gets a deep dive.

The demo walkthrough describes how tone is worked out: read the post first, judge the comment in its own language — including sarcasm and in-jokes — then match that judgment to a fixed scale. Tone is scored on a sample from every group, and the report says how many comments were scored. Every quote has an English line beside the original, and a permalink.

On the homepage, finding and pricing the conversations takes about 12 minutes for one market, and a typical report after you approve takes about 30 minutes. Searching a brand, the estimate, and the sample report are free. dumub is in closed beta: running a report needs an invite. To try one, claim US$300 of free credit with a work email; they say they set it up within one working day, as places open. The rate card is on the pricing page.

How to check the evidence

Open the comments file. Pick a theme that would change a decision. Follow a permalink, read the original and the English line, and see whether the theme still holds. If the quote does not support the heading, the report is not finished.

Do the same for tone. The demo method asks you to read the comment in context before any score appears. If you cannot reconstruct that step — or you cannot see how many comments were scored — you are looking at a chart, not a reading.

If you cannot do this at all, because the delivery is a dashboard login or a slide deck with no comments file, you have a summary. Ask for the evidence.

When you still need a dashboard

A report will not notify you when volume or tone shifts next week, and it will not watch the category after you close the file. Always-on monitoring and alerts are where subscriptions win. Dashboards of that kind typically find the mentions a Boolean query tells them to find, and they report volume. A report finds the conversations and tells you what people said and why. If you need both, buy both — but do not expect one to do the other’s job. The longer comparison is Why not a dashboard?.

FAQ

What should a social listening report include?

The question and scope, how the material was found, the main themes, a sample of comments you can read and click through, a clear note on how tone was judged and on how many comments, and the limits of the work. A slide deck alone is usually not enough.

How is a report different from a dashboard?

A dashboard is for ongoing monitoring, seats, and alerts. It typically finds the mentions a query tells it to find, and reports volume. A report is a finished reading of a question — what people said and why — with files you can keep. For the buying decision, see Why not a dashboard?.

Can I see a sample social listening report?

Yes. dumub publishes walkthroughs at dumub.com/demo and dumub.com/demo/sia. They are sample reports, not client work.

What files does dumub deliver?

A zip: report.html, slides.html, a deep-dives/ folder, comments.xlsx, a data/ folder, and START-HERE.html, as listed on the homepage on 16 November 2026. There is no login and the files do not expire. Re-check the live product copy for the exact file names before publishing.

How long does a dumub report take?

On the homepage, finding and pricing the conversations takes about 12 minutes for one market, and a typical report after you approve takes about 30 minutes. That is the live site’s wording as of 16 November 2026.

Does a report replace a listening subscription?

Not if you need always-on coverage or alerts. It can replace a subscription for a one-off or occasional question. See the category guide and Why not a dashboard?.

To see a delivery, open a public sample. The rate card is on pricing. Searching a brand is free. To run a report, claim US$300 of free credit with a work email.

Country and language questions are covered separately: Singapore, Malaysia, Indonesia, and social listening in Southeast Asian languages.

This page is published by dumub.

Claim $300 of free credit

What a Social Listening Report Should Include (With a Public Example)