Operations
Part of Running social listening operations with access, rights and recovery kept apart
Checks to run before a social listening release leaves the team
Check an England social listening release for source permission, query fitness, human review, rights propagation, secure delivery and recorded limitations.
Use this social listening quality checklist immediately before an England-focused report is released. Each answer needs a named owner, dated evidence and a decision. A tick without an artefact is not a pass, and the completed checklist cannot guarantee accuracy, lawful processing or complete source coverage.
What to take away
- A tick without a named owner, dated evidence and a decision is not a pass.
- The checklist cannot guarantee accuracy, lawful processing or complete source coverage.
- A query can execute correctly and still be unsuitable for the intended decision.
- Keep the report on hold after unexplained access, missing logs or broken deletion.
- Record the defect, affected output, containment owner and evidence for a new review.
Purpose and population
- Does the job record identify the decision, England inclusion rule, time window and recipient?
- Are UK-wide, England-specific and global inputs labelled separately?
- Does the report avoid treating public conversation as a representative sample of residents or customers?
- Are assumptions, unknown locations and excluded languages visible beside the finding they affect?
Fail if the team cannot describe what a result is meant to support. A broad dashboard theme is not a research question.
Purpose and population checks
- Identify decision, England rule, window, recipient
- Label UK-wide, England-specific and global inputs
- Avoid treating public conversation as representative sample
- Show assumptions, unknown locations, excluded languages
Source and permission
- Is every source tied to a current contract, platform record or other authorised route?
- Does the register state permitted purpose, fields, display, retention, removal and downstream use?
- Were outages and start or end dates preserved?
- Has a named custodian checked changes since the previous run?
Reddit's global Data API Terms say the APIs may change or cease and restrict retention beyond an approved use. The exact buyer arrangement may differ. Treat this record as a prompt to verify current entitlement, not permission for a listening project.
Query and classifier
- Is the deployed syntax identical to the approved version?
- Are homonyms, spam, quotation, negation and ambiguous names represented in tests?
- Does the codebook define each human and automated label?
- Were consequential items and a documented sample reviewed by people?
- Are disagreements, overrides and limitations retained rather than overwritten?
The AQuA Book applies to government analysis, yet its distinction between verification and fitness-for-purpose validation is useful. A query can execute correctly and still be unsuitable for the intended decision.
Privacy decision
- Is purpose, role allocation, lawful-basis analysis and transparency evidence present?
- Are fields, recipients, access and retention limited to that approved purpose?
Rights and deletion execution
- Can the team recognise an objection or erasure request arriving outside a dedicated inbox?
- Does the system map include alerts, exports, reports, integrations and backups?
- Has each applicable correction, restriction or deletion action produced a destination-level result?
ICO guidance calls the right to object conditional in several non-marketing contexts. It is also marked under review after the DUAA. The qualified decision and its propagation record are separate evidence. Fail the release if either is missing.
IP and publication
- Is every quotation, screenshot, image and substantial extract listed with its planned audience?
- Is permission, licence or a reviewed exception recorded?
- Are paraphrases clearly separated from source words?
- Can an upstream removal reach scheduled and already-produced reports?
The UK copyright overview gives general boundaries, not a case-specific answer. Route uncertainty to a named IP reviewer.
Security and delivery
- Do users have only the access needed for their task?
- Are administrator changes, exports and integrations logged where the service supports it?
- Is the incident lead able to suspend a source and preserve evidence?
- Has recovery been tested with controlled material?
- Do headings, tables, reading order, alternatives and colour use survive the final export?
Do not pass an inaccessible PDF because the dashboard itself is usable. Keep the report on hold after unexplained access, missing logs, uncontained disclosure, broken deletion, failed source permission or a material label error. Record the defect, affected output, containment owner and evidence required for a new review.
Before you act
- Name an owner, date the evidence and record a decision.
- Label UK-wide, England-specific and global inputs separately.
- Verify every source against a current contract or authorised route.
- Check the deployed query syntax matches the approved version.
- Confirm deletion actions produced a destination-level result.
- Hold the release after a material label error.
Common questions
What makes a checklist answer count as a pass?
Each answer needs a named owner, dated evidence and a decision. A tick without an artefact is not a pass. The completed checklist also cannot guarantee accuracy, lawful processing or complete source coverage.
Why can a working query still be unfit for release?
The AQuA Book distinction between verification and fitness-for-purpose validation applies. A query can execute correctly and still be unsuitable for the intended decision, so the team must describe what a result is meant to support.
When should the report be kept on hold?
Keep it on hold after unexplained access, missing logs, uncontained disclosure, broken deletion, failed source permission or a material label error. Then record the defect, affected output, containment owner and evidence required for a new review.
