Resources · 40
Triage social listening signals before acting
Separate volume, origins, reposts and verified facts to route useful cases.
· 6 min
What this guide helps achieve
- Describe collection
- Deduplicate
- Verify facts
- Route and close
Quick check
- Which sources and languages are missing?
- Are mentions independent or reposts?
- What do we know beyond the post?
- What real-world effect warrants escalation?
- Has resolution been confirmed?
Step-by-step method
- 01
Define the question
Specify decision, themes, platforms, languages, period and collection limits. Do not treat online participants as a representative population.
Deliverable: protocol and declared coverage.
- 02
Keep provenance
Record link, date, visible context and discovery method for each signal. Retain only personal data needed for handling.
Deliverable: dated signal record.
- 03
Deduplicate repeats
Group quotes, copies, screenshots and follow-up posts about the same event. Separate distribution volume from independent cases.
Deliverable: timeline and origin clusters.
- 04
Check claims
Seek primary sources, context and contrary evidence. Mark what is confirmed, plausible or unknown without inferring intent from one post.
Deliverable: fact status and confidence.
- 05
Route by effect
Apply severity criteria and assign complaints, security risk or rumors to the right team. Draft responses that distinguish facts from ongoing inquiry.
Deliverable: owner, timing and decision.
- 06
Close and learn
Confirm the outcome, correct public statements where needed and refine search terms and triage rules. Compare resolved cases, not only mentions.
Deliverable: closure and method review.
Management indicators
| Indicator | What it measures | First action |
|---|---|---|
| Coverage | Sources and languages actually observed | Flag blind spots |
| Deduplication | Distinct cases per repost cluster | Avoid double count |
| Qualification | Cases with facts and confidence | Extend verification |
| Resolution | Escalated cases actually closed | Review ownership and timing |
Common pitfalls
- Treating mentions as representative opinion
- Counting each copy as a new incident
- Publishing conclusions before checking
- Retaining unnecessary personal data
Frequently asked questions
Does a mention spike prove a crisis?
No. It may come from a campaign, changed collection or repeats of one message.
Must every signal get a response?
That depends on impact, verification, channel and amplification risk.
How should uncertainty be shown?
Separate observed facts, hypotheses and information still being sought.
Citation chains and social monitoring
Useful social listening explains what circulates, which records support a claim and which decision needs preparation. Ten reposts of one document do not become ten confirmations. This dossier adds a way to read documentary dependencies and a briefing structure for OSINT monitoring, reputation and crisis communication.
Official reference: RESIST 3, published 29 October 2025. CIE applications, cases and workshop rules are educational material, not an official RESIST tool or a disinformation diagnosis.
Government Communications · RESIST 3 · RESIST 3 · 2025 · consulted 2026-10-23
Six stages from a signal to a reviewed decision
| RESIST 3 stage | Short reference | Original practical application |
|---|---|---|
| 1. Recognise Recognise | Separate checkable information, opinion and missing context. | CIE application: retain the exact question to be checked before classifying content. Strong criticism does not establish manipulation. |
| 2. Early warning Early warning | Organise monitoring around defined risks. | CIE application: record time window, channels, languages, queries and exclusions. Compare like-for-like periods and document collection outages. |
| 3. Situational insight Situational insight | Turn observations into decision-relevant information. | CIE application: separate message counts, cited documents and observed effects. Identify the question that remains unanswered. |
| 4. Impact analysis Impact analysis | Prioritise consequences and uncertainties. | CIE application: name the exposed service, owner and next review. A rise in reposts alone cannot quantify harm. |
| 5. Strategic communications Strategic communications | Choose a proportionate response or monitor without responding. | CIE application: specify the audience to help, useful fact and suitable channel. Consider whether a public response would increase the content’s visibility. |
| 6. Tracking effectiveness Tracking effectiveness | Evaluate communication and the response process. | CIE application: define an observable outcome before action, then record what actually changes and what remains unknown. Clicks and resolution are different measures. |
ABCDE: prepare a briefing without filling unknowns
| Field | Question to document | Pitfall to avoid |
|---|---|---|
| Actor | Which accounts or organisations are actually identified? | Inferring nationality, intent or coordination from tone. |
| Behaviour | Which actions were observed, and when? | Turning timing similarity into proof of coordination. |
| Content | Which exact claim and document version? | Treating a headline, cropped image and full text as equivalent records. |
| Degree | What spread was measured, within which scope? | Presenting mentions as unique people or representative opinion. |
| Effect | What effect was observed, and on whom? | Conflating possible effect, observed harm and established causation. |
Government Communications · RESIST 3 quick reference · RESIST 3 · 2025 · consulted 2026-10-23
Workshop: trace references
Choose a small fictional network. An arrow “A → B” means only that A cites B. The workshop follows references reachable from the selected record and shows declared source documents, relays, missing references and cycles. Changing the starting record shows why reading scope matters.
Local calculation on eight closed datasets: no social media collection, transmission, storage or download. “Source” means a declared leaf in the exercise, without external verification. Two distinct identifiers establish neither independence, corroboration nor truth. The result measures neither real audience, a campaign nor an actor’s intent. Displayed loops are those encountered during traversal, not an exhaustive inventory of every possible cycle.
Traversal result
Eight documented readings, available without JavaScript
S01 · Three relays, one document
Starting record : D
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Declared source | — |
| B | Relay | A |
| C | Relay | A |
| D | Relay | B, C |
D reaches three relays and one leaf A. B and C are not two additional confirmations.
S02 · Two declared documents
Starting record : C
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Declared source | — |
| B | Declared source | — |
| C | Relay | A, B |
Two leaves are declared. Their independence and agreement on a particular claim would still require examination of the actual documents.
S03 · Shared origin behind two intermediaries
Starting record : D
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Declared source | — |
| B | Relay | A |
| C | Relay | A |
| D | Relay | B, C, A |
Three paths reach A. The workshop deduplicates the identifier rather than counting each path as a new source.
S04 · A missing reference
Starting record : B
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Declared source | — |
| B | Relay | A, X |
A is present, X is absent from the dataset. This does not establish that X is false or nonexistent; it records a reading limitation.
S05 · Two relays cite each other
Starting record : A
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Relay | B |
| B | Relay | A |
The A → B → A cycle provides no declared leaf. Circular repetition does not resolve origin.
S06 · One leaf and a cycle
Starting record : B
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Declared source | — |
| B | Relay | A, C |
| C | Relay | B |
One leaf A is reachable alongside the B ↔ C cycle. A’s presence does not remove the circular dependency.
S07 · An undocumented origin
Starting record : B
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Unknown origin | — |
| B | Relay | A |
A is not declared a source: its origin is unknown. A record without citations must not automatically be promoted to an originating source.
S08 · The starting record changes scope
Starting record : B
| Fictional record | Declared type | Cites records |
|---|---|---|
| A | Declared source | — |
| B | Relay | A, A |
| C | Relay | Z |
| D | Unknown origin | — |
From B, only B and A are reachable despite the repeated A reference. C and D stay outside the traversal. Selecting C reveals missing reference Z.
Checks before circulating a monitoring brief
| Check | Expected record |
|---|---|
| Scope | Period, time zone, channels, languages and coverage limits. |
| Counting unit | Distinguish messages, observed accounts, documents, interactions and people. |
| Dependency | Trace citations and keep unknown origins unknown. |
| Version | Compare publication time, collection time and the version actually read. |
| Alternative hypothesis | Check editorial reuse, mistakes or a different context before attribution. |
| Decision | Name the action, owner, deadline and new evidence that would change the brief. |
For an actionable brief, keep three statements separate: what was observed, what was inferred and what is missing. Link each inference to its records and limitation. Monitoring without a public response can be an explicit decision; give it an owner and a review deadline.
Sources, editions and credits
Original CIE summaries informed by Government Communications, RESIST 3 (2025) and its quick reference. English headings help locate official sections. No institutional logo, diagram or photograph is reproduced. Graph examples are fictional and describe no real person or operation.
Government Communications · RESIST 3 · RESIST 3 · 2025 · consulted 2026-10-23
SHA-256 : 014c25d96b2538b056541179fee24adb086770c8bdf9e382eff055279f01756b
Government Communications · RESIST 3 quick reference · RESIST 3 · 2025 · consulted 2026-10-23
SHA-256 : a27c918181a50443826fb5eb9c140741a0c53fcc4291cc45f4f3d975d82133b1
Official references
References consulted: . The method and worksheet propose checks to adapt to your context; they do not constitute certification.
Continue exploring
Related analysis
