Data governance and GDPR for Perth organisations: controls that produce evidence

Nobody in Perth has ever called us because they wanted governance. They call because an auditor, a regulator or a customer asked a question they could not answer.

This page covers data governance and compliance for analytics estates in Perth: what the Information Commissioner's Office (ICO) expects under UK GDPR and the Data Protection Act 2018, which sector rules bite hardest given the local economy of energy generation and supply, insurance and reinsurance, and agriculture and agribusiness, and how to implement controls in Microsoft Purview and Power BI that produce evidence rather than paperwork.

What the Information Commissioner's Office (ICO) expects of an analytics estate

Under UK GDPR and the Data Protection Act 2018, the duties that bite hardest in analytics are minimisation, retention limits, access control, and being able to respond when someone asks what you hold or asks you to delete it. Analytics estates fail these quietly: a warehouse accumulates every column from every source because it was easier than deciding, retention defaults to forever, and permissions are granted to individuals who then change role.

• UK GDPR data-minimisation and storage-limitation duties apply directly to analytics copies of personal data, which is where most estates quietly fail.
• Consumer Duty outcome monitoring has made customer-level analytics a supervisory expectation for regulated firms, not an optional capability.
• SECR energy and carbon reporting requires auditable activity data, which usually means the same lineage discipline as financial reporting.
• The Procurement Act 2023 regime governs public-sector buying routes, including analytics work bought through frameworks.

None of this requires a governance department. Four things, none of which needs a department: a catalogue that gets used, a classification scheme that actually drives retention and labelling, access through groups rather than individuals, and evidence anyone can generate on request.

Sector rules that bite in Perth

Perth's economy means the governance conversation here is not generic. With energy utility corporate functions and insurance and financial operations shaping the local client base, these are the obligations that come up in practice.

Insurance and reinsurance

Claims data frequently includes health and criminal-conviction information, which attracts the stricter GDPR special-category conditions. Policy, premium and claims data where the same risk is represented differently in underwriting, finance and claims systems, and where development over time is the whole point.

The practical consequence for an analytics estate is that access design cannot be retrofitted. Row-level and object-level security have to reflect how authority is actually delegated in the organisation, and the design needs testing from a non-privileged account rather than assumed from documentation.

Tourism, hospitality and events

Guest data is personal data with cross-border transfer implications when group systems sit outside the region. Typical systems in scope: property management system, booking channels and OTAs, revenue management system, EPOS and CRM.

Agriculture and agribusiness

Subsidy claims and traceability records are audited, so calculation methods and supporting evidence must be reproducible.

Who can see what, and how you prove it

This is the question that exposes an estate, and the fix is unglamorous. Years of individual grants cannot be summarised without someone going and looking. The same estate, with access delegated through directory groups that match how authority is actually delegated, answers the question from a report.

The sequence is always the same: extract the permissions that actually exist, design groups around how the organisation really delegates authority, migrate and remove the individual grants, then make the evidence self-service so your second line runs the report instead of raising a request. For a business in insurance and reinsurance, the groups normally need granularity by function and by entity or site.

Classification, labels and the export problem

The leak is usually an export, not an attack. Someone needed the figures in a spreadsheet to do their job, and the spreadsheet then went somewhere nobody tracked. Sensitivity labels applied in Power BI travel with the exported file, so encryption and access restrictions persist outside the platform, and export can be blocked entirely for specific labels or audiences.

The classification scheme has to align to the information security policy you already have rather than introduce a competing taxonomy, and retention has to be enforced against your actual obligation under UK GDPR and the Data Protection Act 2018 instead of kept forever by default. Every control is then verified from a non-privileged account, because the most common finding in a governance review is a restriction that was configured correctly and never actually tried.

Working with British organisations: the practical constraints

• Most UK engagements run remote-first with on-site workshops for definition sessions and go-live.
• IR35 and off-payroll rules make a fixed-scope statement of work cleaner than a day-rate contractor arrangement for many clients.
• Public-sector buyers typically route analytics work through established frameworks rather than open tenders.

UK GDPR diverges from the EU regime in places, so an organisation operating on both sides needs a position on each rather than one pack covering both. Where you process EU personal data as well, both regimes apply and the documentation has to reflect that.

A 90-day plan that produces evidence

1. Days 1 to 15: assessAccess extract versus policy, data map, classification gaps, retention reality. Output is a risk-ranked remediation plan, ordered by exposure rather than by ease.
2. Days 15 to 35: defineAn operating model that names who owns what, a classification scheme, retention rules tied to the actual obligation, and access standards. Agreed with legal and with the business, because a scheme they did not approve will not survive contact with them.
3. Days 35 to 70: implementPurview scanning and catalogue populated, labels published and applied, access rebuilt onto groups, lineage switched on, suppression implemented in measures.
4. Days 70 to 90: evidenceAccess evidence reporting, audit pack generation, steward training, and the first governance review run with your team rather than for them.

That sequence works because each stage produces something usable on its own. If the programme stops after the assessment, you still hold a risk-ranked plan an auditor would accept. Book a technical review if you want that assessment for a Perth organisation.

We work across United Kingdom and deliver into neighbouring markets regularly. Nearby pages worth reading if your group has sites elsewhere: Exeter, Stirling, Norwich, Peterborough, York and Ipswich.

Frequently asked questions