Operations
Part of Running social listening operations with access, rights and recovery kept apart
From bounded request to approved deletion, the social listening operating workflow
Build a social listening operating workflow in England with authorised sources, versioned queries, reviewed labels, rights routes and firm stop rules.
From a bounded request through access checks, query lock, triage, rights routing, approved deletion and traceable reporting, this operating workflow takes an England-based social listening team to a closed record with recovery evidence.
What to take away
- Build the route from request to deletion before opening any live social listening feeds.
- A bounded request names the decision, England rule, period, sources, exclusions, recipients and deadline.
- Blocked sources stay blocked; never swap an authorised feed for an improvised collection method.
- Approved deletion must propagate to every saved search, alert, export, presentation, integration and backup.
- Stop the run when a control fails.
1. Accept a bounded request
The requester supplies the decision, England rule, period, permitted sources, key concepts, exclusions, intended recipients and deadline. The operations owner returns requests that ask for "everything people say" or contain no decision use. Geography inferred from a profile is recorded as inference, not residence.
For example, a request might ask: did sentiment toward Brandwatch or Talkwalker change between 1 January and 31 March 2025 across X, Reddit and open review sites, to decide whether to renew a listening licence?
Bounded request intake fields
- Decision and England rule
- Period and permitted sources
- Key concepts and exclusions
- Intended recipients and deadline
- Job record with identifier
- Control owners and query version
- Privacy decision and IP conditions
Open a job record with an identifier and control owners. Link the current source entry, privacy decision, IP conditions and query version. Never copy a previous project's approval without checking whether purpose, people or destinations have changed.
2. Confirm access before collection
The source custodian checks the contracted route, approved use, fields, display restrictions, retention, removal handling and terms date. Platform policies can change, and a global policy record does not prove that an intermediary has granted the buyer the same rights, so read the commercial contracts as well.
Source access check
Is contracted access and approved use confirmed?
collect with terms date recorded
set source state to blocked
If entitlement is unclear, set the source state to blocked. Do not replace an authorised feed with an improvised collection method. Record the last valid timestamp so later reports can disclose the gap.
3. Lock the question and query
Store syntax, language, author, date, intended meaning, exclusions and known ambiguities. Test it against controlled examples, including homonyms, quoted material, spam and negation. An analyst approves the version used for the run.
The government functional standard GovS 010 on analysis describes verification as assuring that analysis was conducted properly and validation as assuring that the right type of analysis was used. Applied here, verification checks that the saved query ran as specified; validation asks whether its returns can answer this job's question.
4. Triage returns without hiding exceptions
Keep automated labels as machine output. Analysts review a documented sample and any item that could trigger crisis monitoring, publication or action about a person. Preserve the original label, human decision, reason and query version. Unknown language or context remains unknown.
Route security alerts, unexpected sensitive material, threats and suspected false identity into their own queues. Do not let a topic dashboard become an incident register or a personnel file.
5. Route rights decisions
Under UK GDPR, a privacy lead receives objections, erasure requests and source-removal signals. The ICO right to erasure guidance states that the right is not absolute and applies only in certain circumstances, and that the guidance is under review after the Data (Use and Access) Act.
A qualified reviewer decides each case; operators carry out only the recorded outcome. Keep the decision with the job record, and use the data protection review to decide what the log may hold about the requester.
6. Propagate an approved deletion
Use the service map to reach saved searches, alerts, exports, presentations, integrations and backup treatment. Log each destination's result. A missing item in the main workspace does not establish that every copy has gone. Failed propagation blocks reuse while the privacy lead reviews the exception.
7. Release a traceable report
The report owner checks source coverage, period, query version, sample method, label limitations, corrections, quotations and audience. Every conclusion points back to evidence. If a required feed failed, say which period is incomplete rather than treating silence as zero.
Before distribution, confirm that copied material has an approved use. A named UK intellectual property reviewer should check the actual extract, because a general rule cannot settle whether a particular quotation or screenshot may be reused.
8. Close with recovery information
Record delivery, recipients, open cases, retained data, deletion date and next permission check. Stop the run after unexplained access, failed propagation, a material classification defect or an unapproved supplier change.
Recovery needs evidence against the failed control and approval of the resulting version. A working login alone is not a release decision. Pair every stop rule with service standards that name a threshold and an owner.
Before you act
- Name the decision, rule, period, sources, exclusions, recipients and deadline.
- Confirm contracted access and terms date before collecting anything.
- Lock and test the query version against controlled examples.
- Route rights decisions to a qualified reviewer, not operators.
- Log deletion results for every destination on the service map.
- Stop the run after unexplained access or failed propagation.
Common questions
What must a requester supply before work starts?
The requester supplies the decision, England rule, period, permitted sources, key concepts, exclusions, intended recipients and deadline. Requests asking for everything people say, or with no decision use, are returned. Geography inferred from a profile is recorded as inference, not residence.
What happens when source entitlement is unclear?
The source state is set to blocked. An authorised feed must not be replaced with an improvised collection method. The last valid timestamp is recorded so later reports can disclose the gap in coverage.
How does an approved deletion get carried out?
The service map reaches every saved search, alert, export, presentation, integration and backup. Each destination's result is logged, and any failed propagation blocks reuse of the material while the privacy lead reviews the exception.
