Describe the material rather than the logo
A source name is not a complete collection requirement. Public posts, comments, video captions, selected profiles and historical versions may use different collection routes and have different availability. Put each necessary content type into the brief.
When evaluating a top narrative intelligence platform, begin with the subjects and questions you need to observe. Create a roster that names the platform, content type, language, time window and expected record fields. Separate mandatory sources from useful background material.
Keep a field for access limitations. A source can be available for some queries or periods and still leave an important gap in your task. Record the boundary in terms another reviewer can understand.
Use a source coverage worksheet
| Field | Example requirement | What to demonstrate |
|---|---|---|
| Content | Public posts and relevant replies | Representative records, query and collection route |
| History | Agreed lookback period | Available dates and known discontinuities |
| Timing | Review within the operating window | Publication, collection and alert timestamps |
| Evidence | Source-linked export | Usable record, retained material and access limits |
Use real requirements in the worksheet. A hypothetical example helps explain the fields but cannot establish that a particular vendor has access. Ask the provider to fill the same sheet and attach evidence for mandatory rows.
Distinguish missing collection from a query problem
For a known record that does not appear, check the time window, query, language treatment, duplicate rules and source route. A result may have been collected but excluded by the query, or may have been grouped into another item. Those explanations require different fixes.
Use a small reference set with exact names, paraphrases, common abbreviations and ambiguous matches. Record each test condition. Re-running a query after a configuration change should produce a new result note rather than overwrite the original observation.
Ask how sampling, processing delays and unavailable material are represented. The team receiving the briefing needs to know whether a quiet chart reflects low observed activity or an interrupted collection.
Test profile changes as a separate requirement
A stream of mentions does not establish a complete history of a chosen profile. If a bio, username, external link or other public field matters, specify the field and ask to see the retained versions, timestamps and collection cadence.
Define what should happen when a page is unavailable or content is removed. Ask what the product can retain, what must remain a link and how that affects later review. Scope permitted access and retention with the provider under your organization’s policies.
Can a second reviewer reconstruct what was visible when the finding was made, and can they see the collection limits?
Carry coverage limits into every report
A coverage audit is useful only if its limits travel with the analysis. Keep the source roster, changes in collection and unresolved gaps beside the reporting template. Date the worksheet and assign an owner to update it when access or scope changes.
During procurement, include required sources, export conditions and the process for notifying your team about a material change. Recheck the roster when the monitoring question expands to a new market, language or kind of public record.
Questions for the brief
Does a very large source count mean the platform covers our requirements?
A large total does not answer a specific source-level question. Test the content types, dates, languages and collection routes you require, and ask how the provider documents known gaps.
How can we compare a live feed with a historical archive?
Treat them as separate requirements. Confirm when live collection begins, which earlier records are available and whether the archive has different source or search limits. Label the periods in your analysis.
We need a record of a public profile before and after a change. What should the demo show?
Ask for the exact field, both retained versions, collection times and the interval between checks. Document whether intermediate changes could be missed and how unavailable content is represented.