Your customers keep asking how you handle personal data. A big client wants proof beyond a privacy policy and a DPA. You’ve tightened your security for ISO 27001, but GDPR still feels like a moving target. That’s where ISO 27701 earns its keep: it makes privacy governance auditable and practical.
Why consider ISO 27701 — and where it fits
ISO 27701 extends ISO 27001 and 27002 with a Privacy Information Management System (PIMS). Think of it as the bridge between information security and data protection law. It doesn’t replace GDPR or the UK Data Protection Act; it turns their principles into management-system controls you can run, evidence and improve.
For many organisations, the draw is simple: fewer client questionnaires, cleaner processor agreements, and a common language between security, legal and operations. It’s especially useful if you handle personal data at scale, operate as a processor, or sell into regulated sectors.
Define your scope and roles first
Before documents or tools, decide what part of your business the PIMS will cover and whether you act as a controller, processor, or both. That choice drives which controls apply and what evidence we’ll ask for at audit. Be realistic: over-scoping makes audits painful; under-scoping makes the certificate less useful to customers.
Typical scoping examples
- A SaaS provider processing customer end-user data as a processor for EU and UK clients.
- An e-commerce retailer acting as a controller for marketing and order fulfilment data.
- A payroll bureau processing client employee data and its own HR data (processor and controller).
- A healthcare app with a UK-only pilot, scoping to the app platform while excluding internal R&D systems.
Write the scope in plain language and map the supporting locations, systems and suppliers. If your ISO 27001 scope exists, align to it and state any differences.
What auditors expect to see in a working PIMS
You don’t need a wall of policy. You do need a clear thread from risk to control to evidence. In practice, we look for:
- Data inventory and purposes: A current register of processing activities describing PII categories, purposes, lawful basis and recipients.
- Role clarity: Whether you are controller, joint controller or processor for each processing activity.
- Risk assessment: A method that considers privacy harm to individuals, integrated with your ISMS risk process.
- Privacy by design: A simple way product and engineering teams factor privacy into changes and projects.
- DPIAs: Proportionate impact assessments for higher-risk processing, with outcomes tracked.
- Data subject rights: A workable process for access, erasure, rectification and restriction requests, with timeframes and evidence.
- Consent management: Where consent is used, records of capture, withdrawal and refresh.
- Retention and deletion: Rules tied to purpose and law, and logs that show deletion actually happens.
- Third-party management: Due diligence, contracts with appropriate clauses, and monitoring of processors and sub-processors.
- International transfers: Your mechanism (e.g. SCCs), risk assessments, and a way to track changes.
- Incident and breach handling: Criteria for notifiability, rehearsed playbooks and post-incident learning.
- Awareness and training: Role-based training for people who actually handle PII.
- KPIs and monitoring: Measures that drive action, such as rights-request turnaround and deletion success rates.
- Internal audit and management review: Periodic checks and leadership decisions that change resources or priorities.
If you already run ISO 27001, you’ll reuse a lot: risk, supplier management, access control, asset inventories and continual improvement. ISO 27701 adds the privacy-specific layer that clients and regulators expect to see.
A straightforward path to certification
If you want a formal stamp that your PIMS meets the standard, you can pursue ISO 27701 certification. The work is manageable when broken into clear steps and owned by the right people.
- Run a practical gap assessment: Compare what you do today against ISO 27701 controls and GDPR obligations to prioritise work.
- Confirm scope and map data flows: Document systems, locations, suppliers and transfers for each processing activity in scope.
- Assess risks and select controls: Integrate privacy into your ISMS risk method and choose applicable 27701 controls for controllers and processors.
- Document what matters: Keep policies short, push detail into procedures and templates, and link each to risks and controls.
- Operate and gather evidence: Run the processes for a cycle so you have real records, tickets and decisions to show.
- Internal audit and management review: Check effectiveness, raise findings, and have leadership approve actions and resources.
- Plan Stage 1 and Stage 2: Book audits with enough lead time, share core documents early, and make subject-matter owners available.
Small teams often appoint a privacy lead who coordinates legal, security and operations. That reduces duplication and stops policies drifting away from how work actually gets done.
Evidence that lands well at audit
Auditors don’t want glossy decks; we want to see your system working. The following artefacts help:
- A living processing register with versions and owners.
- A couple of recent DPIAs with clear outcomes and mitigations.
- Records of rights requests showing timelines and decisions.
- Deletion job logs from production systems tied to retention rules.
- Supplier risk reviews and signed DPAs with sub-processor lists.
- Examples of privacy-by-design in change tickets or user stories.
- Incident reports showing triage, root cause and lessons learned.
- Training completion rates and content tailored to roles.
- Management review minutes with actions, owners and due dates.
When evidence is thin, we’ll ask to see the process live. Be ready to demonstrate in a sandbox or staging environment if production access is restricted.
Common pitfalls (and how to avoid them)
- Over-scoping: Certifying the entire enterprise on day one overwhelms teams; start with the high-value services and expand.
- Policy bloat: Long policies nobody reads produce nonconformities; keep them lean and follow them.
- Legal-only approach: Great clauses without operational follow-through fail; pair legal with engineering and ops.
- One-off DPIAs: Treating DPIAs as a checkbox misses changes; embed them in your change and project gates.
- Unproven retention: Schedules exist but deletion never runs; automate where possible and sample monthly.
- Processor oversight: Supplier onboarding is strong but monitoring is weak; review high-risk processors annually.
- People risk: Training is generic; tailor for support, engineering, marketing and HR.
Integrating with ISO 27001
If you already hold ISO 27001, build the PIMS into your existing ISMS. Use the same risk register, audit calendar, supplier process and corrective action tracking. Add privacy roles, privacy risk criteria and the 27701 control set, and avoid duplicating governance.
If you don’t have ISO 27001, you can still implement 27701 by adopting the ISMS elements it relies on. You’ll need risk management, document control, internal audit and management review. In practice, many organisations develop both together because the systems overlap heavily.
How long it takes and the effort involved
Once you have your scope, most organisations can get to audit readiness in a few months if they already operate a working ISMS. If you’re starting from scratch, expect longer while you build the management-system basics and generate evidence. The biggest time sinks are usually data mapping, processor contracts and making deletion real rather than aspirational.
Budget time for the teams that carry the load: engineering to wire in deletion and logging, support for rights requests, legal for contracts, and HR or marketing for controller activities. A weekly stand-up with clear owners keeps momentum without turning the project into admin theatre.
Certification isn’t about perfection; it’s about control and improvement. You can carry known gaps into audit with plans, as long as risks are understood and actions are credible.
If you’d like to talk through your scope, approach and timelines, we’re always happy to share what works in practice. Get in touch with UKCTL to discuss how we would plan and deliver an audit that focuses on what matters and respects your team’s time.
