Social listening for UK public sector: a practical guide

What to take away

UK public sector listening answers to FOI and data protection law, as well as applicable GCS propriety and election-period guidance.
Treat every note, screenshot and query log as a record that may be disclosable, and write it for a stranger to read.
Fix and record the lawful basis before collection, and assess whether a DPIA is needed.
Pause scoring of named candidates or parties during the relevant pre-election period.
Set a retention period and follow the organisation's records-management schedule.

What makes public sector listening different

Council, NHS trust and central government teams monitor mentions for service reasons. The question is rarely how the organisation looks. It is what residents are telling us, and what we owe them in reply.

Council reputation monitoring often starts after a complaint spike or a contested decision. The brief should say what would count as a resolved issue.

A commercial team can quietly drop an awkward dataset. A public body generally cannot, because a requester may ask what it holds and how the data was used. That single difference drives most of the rules that follow.

Central government teams also work under Government Communication Service propriety rules, which keep government communication separate from party communication.

FOI turns a dashboard into a disclosable record

The Freedom of Information Act 2000 gives anyone the right to ask a public authority what information it holds. Social listening outputs, vendor reports and internal notes fall inside that scope unless a specific exemption applies.

For Scottish public authorities, check the Freedom of Information (Scotland) Act 2002 (FOISA) and guidance from the Scottish Information Commissioner. The Freedom of Information Act 2000 applies to public authorities elsewhere in the UK, including Wales and Northern Ireland.

Is it disclosable under FOI?

Does the public authority hold it?

Yes

falls inside FOI scope

outside FOI scope

Ask whether you could hand the material to a colleague and defend it. If a spreadsheet describes a named resident in loose terms, without context, that wording travels into the disclosure.

Writing a social listening disclosure policy is a practical defence. It names what you collect, what you will not collect and how corrections work. Set retention periods in the organisation's records-retention schedule and apply UK GDPR Article 5(1)(e), the storage-limitation principle. The ICO's Guide to the UK GDPR, under “Storage limitation”, explains the principle; there is no single retention period for all listening data.

Lawful basis, rights and the limits of consent

Where monitoring is necessary for a public task, the usual lawful basis is UK GDPR Article 6(1)(e), not consent. The task must have a basis in law and the processing must be necessary for it. The ICO's Guide to the UK GDPR, section “Lawful basis for processing”, explains the test; the ICO's legal-framework guidance is also relevant.

Lawful basis and Article 9 conditions

Public task basis

Typical use: Most public sector listening
Extra requirement: None beyond public task
Examples: Service monitoring
Before collection: Record public task basis

Special category data

Typical use: Health or political opinions
Extra requirement: Documented Article 9 condition
Examples: Public health, election monitoring
Before collection: Record Article 9 condition

Special category data needs a further condition. Health information and political opinions both sit in that category. Public health monitoring and election monitoring each need a documented Article 9 condition before collection begins.

Individuals still hold rights over their data. An access or erasure request can arrive through a complaints route or a press enquiry. The ICO's Guide to the UK GDPR, section “Individual rights”, explains the rights and the steps and timescales for responding.

The pre-election period changes what you publish

During the pre-election period, often called purdah locally, public bodies must avoid activity that could be seen to favour a candidate or party. Routine service monitoring can continue, but teams should pause public-facing commentary where it risks breaching applicable guidance. There is no single UK-wide statutory purdah period: check the poll's official timetable and the guidance that applies to your organisation, including the GCS Propriety Guidance or, for local authorities in England, the Code of Recommended Practice on Local Authority Publicity.

Scoring sentiment on named candidates is where teams get into trouble. A tool that clusters posts by party is producing political opinion data by another name, whatever label the dashboard uses.

Public health campaigns need a narrower brief

Flu, vaccination and screening campaigns attract a predictable mix of genuine questions, misinformation and organised opposition. Monitoring that separates the three is more useful than a single sentiment score.

Tag questions that need an operational answer, such as a booking problem, and route them to the service team. Leave the rest for trend reporting at the end of the campaign.

Where sentiment analysis runs at all, sentiment analysis under UK GDPR rules mean aggregated scores and a written purpose, not named individuals.

Examples of platforms with social listening capabilities include Brandwatch, Meltwater, Talkwalker and Sprout Social. These are examples to assess, not endorsements: check the specific product's coverage, data handling, accessibility, security and procurement requirements before choosing a tool.

A four-step approval sequence

Write down the decision the monitoring supports and the date it will be taken.
Record the UK GDPR Article 6 lawful basis and, if special category data is involved, the specific Article 9 condition. Screen for a Data Protection Impact Assessment (DPIA); complete one before processing if it is likely to result in a high risk to individuals. Update the Article 30 record of processing activities where required.
Check the tool or vendor on data location, retention, sub-processors and exit terms before collection starts, and record the decision and retention schedule.
Set review dates before the campaign, at the start of the pre-election period and 30 days after it ends, each with a named owner.

Common questions

Can a council monitor social media without consent?

Yes, where the processing is necessary for a public task and proportionate. The usual basis is UK GDPR Article 6(1)(e), but a public post does not remove data protection obligations. If the monitoring involves special category data, identify an Article 9 condition too. Record the assessment, screen for a DPIA and complete one if the processing is likely to result in high risk.

Is social listening data covered by the Freedom of Information Act?

Often yes, when a public authority holds it. Vendor reports, query logs and internal notes sit in scope, subject to any exemption that applies. Plan on a request arriving.

What changes during a local election pre-election period?

Routine service monitoring may continue, but public-facing commentary that could favour a candidate or party, and scoring of named candidates, should pause where required by applicable guidance. There is no single UK-wide statutory purdah period. Check the official timetable for the poll and your organisation's applicable guidance; for local authorities in England, this includes the Code of Recommended Practice on Local Authority Publicity.