Penguin ePulse · BRAND LISTENING
Social Listening Brief Template: Query, Coverage and Review
Download a social listening brief template for query rules, source coverage, sentiment review, methodological disclosure and an accountable research handoff.
A decision question, query rules, source coverage, reporting period, review method and limitations. This brief helps an analyst explain what the collected conversation can answer before a team turns it into a brand decision.
Download the social listening brief
The CSV contains planning prompts, query-testing checks and a handoff record. Open it in Excel or Google Sheets and add your own source permissions, query syntax and review owners. No account or email is required.
Start with the decision, not the keyword list
“Monitor our brand” is too broad to tell an analyst what to deliver. A more useful brief asks a specific question: which delivery complaints appeared in the public sources we can access during the launch week, and which complaints need a customer-service follow-up? That question gives the work a period, topic and recipient.
Separate research from individual case handling. A research summary can describe observed themes using aggregated evidence. A service case needs a source link, ownership and a private channel for personal details. Avoid spreading names, order numbers or other unnecessary identifying information through a general research worksheet.
Define the unit you will count
A post, a comment, an author and a conversation thread are different units. Select one for each metric. Record whether reposts, quoted posts and multiple messages from the same account count separately. If the team changes that rule halfway through a project, preserve the earlier version and explain the break in comparability.
Test query rules before the full review
List the official brand name, common misspellings, product names and ambiguous terms. Specify exclusions only when you can explain why they remove irrelevant matches. Write query syntax for the actual collection provider; Boolean operators and available filters are not universal across platforms.
| Check | Record in the brief | Reason |
|---|---|---|
| Ambiguous name | Examples of relevant and irrelevant matches. | A generic word can inflate brand volume. |
| Misspellings | Observed variants and the source of each variant. | Do not invent a large list that mostly adds noise. |
| Exclusions | Excluded expression and the rationale. | A broad exclusion can remove real complaints. |
| Coverage | Accessible networks, geography, language and historical window. | Unavailable sources are not evidence of no conversation. |
| Query version | Saved query, timestamp and owner. | A later analyst should be able to reproduce the scope. |
Review a small test set manually before relying on totals. Save a few non-identifying examples of false positives and false negatives. The aim is to make classification rules understandable, not to assert an accuracy score without a defined evaluation set.
Worked example: a fictional product launch
This scenario is illustrative. A fictional outdoor brand, Northstar Packs, wants to review public comments about a new delivery option. The brief covers a seven-day window, two accessible public sources and English-language matches. The analyst counts comments, records duplicate exclusions and reviews the theme “delivery delay” manually.
If the collection contains 120 reviewed comments and 18 discuss delays, the descriptive share is 18 ÷ 120 = 15% of that reviewed comment set. It is not the percentage of all customers affected, a representative estimate of public opinion or a delivery failure rate. A separate operational dataset would be needed to answer those questions.
The handoff records the exact query version, dates, review rules, count of excluded duplicates and unavailable sources. The service owner receives actionable case links separately. The marketing owner receives an aggregated theme summary with the limitations attached.
Make automated sentiment reviewable
Keep “unknown,” “mixed” and “needs review” available rather than forcing every item into positive or negative. Sarcasm, quoted criticism, multilingual text and a favorable product comment paired with a service complaint can all require context. Record whether AI assisted selection or coding and which human review rules were used.
AAPOR's disclosure standards address methodological transparency, including content-analysis units, sources and AI assistance. Use that transparency principle when preparing the brief; the worksheet does not turn a convenience collection into a representative sample.
The ESOMAR guideline on social media research provides professional research guidance. Its scope differs from a platform's access rules. Confirm the provider's permissions and applicable requirements for your own project before collecting or reusing identifiable material.
Finish with a bounded finding
- State the question and the sources actually available.
- Explain the unit, period, exclusions and review method.
- Report counts with their denominators, including unknown classifications.
- Distinguish an observed change from a claim about its cause.
- Name the next decision, owner and review date.
A useful finding might be: “Delivery-delay language appeared in 18 of the 120 comments reviewed in this collection. Service operations will compare these cases with its delivery records.” That statement can guide a follow-up without claiming that listening has measured all customers.
Questions teams ask
Does the template collect data from social networks?
No. It is a planning and review document. The actual data sources, coverage and access permissions depend on your collection provider and connected accounts.
Should I compare sentiment percentages across tools?
Only after checking the collection scope, classifier definitions, languages, unknown-category handling and human review method. Similar-looking percentages can describe different sets of content.
Can I publish excerpts from private messages?
The worksheet does not grant permission to publish private material. Use aggregated, non-identifying findings and obtain the required permissions for any example you plan to share.
Sources and scope
- AAPOR disclosure standards: transparency about methods, units and sources.
- ESOMAR social media research guideline: professional research guidance.
Penguin ePulse created the brief and fictional example. They are not official AAPOR or ESOMAR templates and do not imply endorsement.
Use and attribution
You may use, copy and adapt our original worksheet text and CSV template for internal or client work. Attribution is welcome and optional; a backlink is not required. Third-party sources retain their own terms. This resource does not imply their endorsement.
Read the related field guide · See all free toolkits · Discuss your workflow