Readiness checklist
ISO 27701 checklist for small and medium businesses
This checklist follows clauses 4 to 10 of ISO 27701 and names the evidence you should be able to show for each point. Work through it before you answer a supplier questionnaire or start the self-assessment. Every gap you find is a task with an owner and a date.
01: Overview
What an ISO 27701 readiness checklist should cover
ISO/IEC 27701 describes a privacy information management system (PIMS). The 2025 edition stands on its own and can be certified without ISO 27001. The 2019 edition extends an existing ISO 27001 ISMS and requires one. Check which edition your customer or tender refers to before you start.
The list below follows the high level structure of the standard, clauses 4 to 10. Each point names the evidence companies usually hold. If you can hand that document to a purchasing department or a customer audit today, tick the point. If you cannot, it goes on your work list.
02: Clauses 4 to 6
Context, leadership and planning: six points to check
These clauses decide what the system covers and who answers for it. Most gaps here are missing decisions, not missing tools.
Role as controller or processor
Record for each service whether you act as controller or processor. Evidence: a role table per processing activity and the data processing agreements you signed with customers.
Scope of the PIMS
State which services, locations and data flows the system covers. Evidence: a scope statement and a list of the services in scope.
Legal and contractual requirements
List what applies to you: the revFADP, the GDPR, sector rules and customer clauses. Evidence: a requirements register with a named owner and a review date.
Privacy policy and responsibility
Management approves a privacy policy and names the person responsible. Evidence: the signed policy and the appointment of the privacy lead or data protection advisor.
Privacy risk assessment
Assess the risks to the data subjects, then those to your company, and decide on treatment. Evidence: a risk register with likelihood, impact and treatment decision per risk.
Privacy objectives
Set objectives you can measure, such as the time taken to answer access requests. Evidence: an objectives list with owner, target and date.
03: Clauses 7 and 8
Support and operation: where most of the evidence sits
Clause 8 is the longest part of the checklist, because it covers the daily handling of personal data. Auditors and customers look here first.
Competence and awareness
Everyone who handles personal data knows the rules. Evidence: training attendance lists, an onboarding checklist and signed confidentiality undertakings.
Controlled documents
Policies and procedures have an owner, a version and an approval. Evidence: a document register.
Record of processing activities
Purposes, data categories, recipients, retention periods and transfers abroad are written down. Evidence: the record itself, updated within the last year.
Data subject rights
Requests for access, correction and deletion are answered within the legal deadline. Evidence: a request log with dates received and answered, plus reply templates.
Privacy by design and by default
New features and projects get a privacy review before release, and the default settings collect the minimum. Evidence: a design review checklist and impact assessments for higher-risk projects.
Processors and international transfers
You know every processor and subprocessor and have contracts with each. Evidence: signed processing agreements, a subprocessor list and the transfer mechanism for data leaving Switzerland or the EU.
Breach detection and notification
Staff know whom to tell, and someone decides whether to notify the authority and the data subjects. Evidence: an incident procedure, a breach register and a documented test run.
Retention and deletion
Data is deleted when the retention period ends. Evidence: a retention schedule and deletion logs or ticket records.
04: Clauses 9 and 10
Evaluation and improvement: proving the system keeps running
A system that was set up once and never looked at again does not meet these clauses. They ask for dated records of review and correction.
Monitoring and measurement
Track a few figures: response times for data subject requests, number of incidents, open risks. Evidence: a simple monitoring sheet filled in on a fixed rhythm.
Internal review
Someone who did not write the procedures checks them against the standard. Evidence: a dated review report with findings.
Management review
Management looks at results, incidents and objectives and decides on actions. Evidence: minutes of the meeting.
Corrective action
Every finding and every breach leads to an action with a cause, an owner and a closing date. Evidence: an action list showing closed items.
05: Evidence
Which documents to have ready for each clause
Small companies often hold several of these in one file. A single privacy manual with a scope statement, role table and policy is enough if it is current and approved. What matters is that each document exists, has an owner and carries a date.
| Clause | Evidence to have ready | Usually held by |
|---|---|---|
| 4 Context | Scope statement, role table, requirements register | Management, legal |
| 5 Leadership | Signed privacy policy, appointment of the privacy lead | Managing director |
| 6 Planning | Risk register, privacy objectives | Privacy lead |
| 7 Support | Training records, document register | HR, quality management |
| 8 Operation | Record of processing, request log, breach register, processor contracts | Privacy lead, IT |
| 9 Performance evaluation | Internal review report, management review minutes | Privacy lead, management |
| 10 Improvement | Corrective action list | Process owners |
06: With Zertify
From checklist to ISO 27701:2025 certificate
Once the checklist is worked through, the Zertify self-assessment is a short step. It has 42 yes/no questions on ISO 27701:2025. 15 of them are mandatory requirements of the standard and must all be answered yes. Among the other 27 you need at least 18 yes answers to pass.
After you pass and pay, the certificate arrives within 4 hours. It is issued by Zertify under licence from SICE, and SICE reviews every assessment before issue. There is no on-site audit. Each certificate can be verified publicly by number and QR code, which is what a customer or tender office will open.
The price is CHF 799 (€799) in the first year, then CHF 529 (€529) per year including the yearly online re-audit. The certificate is valid for 3 years.
07: FAQ
Questions about the ISO 27701 checklist
08: Guide
Related pages
Test your readiness against the real questions
Answer the 42 questions for ISO 27701:2025 and see at once whether you pass.
Free and without registration.