Quick answer

Plan about 40–55 hours over 6–8 weeks for the CIPM. Work through the six BoK v4.2.0 domains in order, from framework and governance through the operational life cycle (assess, protect, sustain, respond). Start case-study practice by week 2, aim for about 300 practice questions including one full 90-question timed mock, and think like a programme manager rather than a lawyer.

The CIPM is IAPP's privacy programme management credential. It's less about memorising rules and more about knowing how to build, run and improve a privacy programme in a real organisation. This plan is built around that.

Week-by-week CIPM plan

Week 1 – Domain I: Developing a privacy programme framework

  • Programme vision, mission, scope and charter; aligning with business strategy.
  • Identifying applicable laws, regulations, standards and contractual duties across jurisdictions.
  • Choosing a framework (for example the NIST Privacy Framework, ISO/IEC 27701 or fair information practices) and developing policies.
  • Practice: 30 questions plus one case study.

Week 2 – Domain II: Establishing programme governance

  • Governance models (centralised, local, hybrid) and their trade-offs.
  • Roles: privacy leader or DPO, privacy team, privacy champions, steering committees.
  • Stakeholder engagement across legal, security, HR, IT, marketing and product.
  • Training and awareness programmes.
  • Practice: 30 questions plus two case studies.

Week 3 – Domain III: Assessing data

  • Data inventories and data mapping, which are the foundation for everything else.
  • Privacy impact assessments and DPIAs: when, who and how.
  • Vendor and third-party assessments; contracts.
  • Privacy in mergers, acquisitions and divestitures.
  • Practice: 40 questions plus two case studies.

Week 4 – Domains IV and V: Protecting data and sustaining performance

  • Privacy by design and its seven principles (highlighted in v4.2.0).
  • Information security controls, data minimisation, retention and deletion.
  • Metrics: what to measure, for which audience; maturity models.
  • Monitoring, audits and continuous improvement.
  • Practice: 40 questions plus two case studies.

Week 5 – Domain VI: Responding to requests and incidents

  • Data subject request processes: intake, verification, fulfilment, recording.
  • Complaints handling.
  • Incident response: preparation, detection, containment, assessment, notification, remediation and lessons learned.
  • Practice: 40 questions, then mixed sets.

Week 6 – Full mock

90 questions in 2.5 hours with the break, reviewed by domain.

Week 7 – Targeted revision and cram

Focus on your two weakest domains, then work through the CIPM cram guide.

The content that matters most, domain by domain

The weekly plan tells you when to study. This section tells you what each domain actually tests and the concepts candidates most often get wrong.

Domain I: Developing a privacy programme framework

This domain is about getting a programme started. Expect questions on:

  • Vision and mission: why a programme needs a statement of purpose that links privacy to business goals.
  • Scope: which entities, jurisdictions, data types and processing activities the programme covers.
  • Frameworks: using established frameworks (fair information practices, the OECD Guidelines, the NIST Privacy Framework, ISO/IEC 27701) to structure controls rather than inventing your own.
  • Policy hierarchy: a privacy policy at the top, supported by standards, procedures and guidelines. Know the difference: policies set direction, standards set mandatory requirements, procedures describe steps, guidelines advise.
  • Legal and regulatory awareness: identifying applicable laws first, before writing controls.

Domain II: Establishing programme governance

Governance modelHow it worksFits when
CentralisedOne privacy office makes decisions for the whole organisationSingle country, consistent operations
Local (decentralised)Business units or countries run their own privacyHighly autonomous units, very different local rules
HybridCentral office sets policy; local teams implementMost multinationals

Also know: the DPO's position and independence under GDPR Articles 37–39 (reporting to the highest management level, no instructions on how to perform tasks, no dismissal for performing them, no conflict of interest), privacy committees and champions networks, and training and awareness. A recurring exam theme is that training must be role-based: HR, marketing, engineering and customer service need different content.

Domain III: Assessing data

  • Data inventories and mapping: what data you have, where it lives, who uses it, where it flows, how long you keep it.
  • PIAs and DPIAs: when they're needed, who is involved, and when to start (early in design, not before launch).
  • Vendor assessments across the lifecycle: due diligence before contracting, contract terms, ongoing monitoring, offboarding and data return or deletion.
  • Mergers, acquisitions and divestitures: privacy due diligence before the deal, then integrating or separating programmes, notices and data after it.

Domain IV: Protecting personal data

Privacy by design and its seven foundational principles, information security controls from a privacy point of view (access control, encryption, logging), data minimisation, retention schedules and secure deletion. Know that retention is a privacy issue: keeping data "just in case" increases breach impact and conflicts with storage limitation.

Domain V: Sustaining programme performance

Metrics and audits. Know the difference between activity metrics (training completed) and outcome metrics (incidents reduced), how to tailor metrics to each audience (board, executives, operational teams), the types of audit (first-party internal, second-party supplier audits, third-party independent audits), and how maturity models show progress over time.

Domain VI: Responding to requests and incidents

ProcessKey steps to know in order
Data subject requestsReceive and log; verify identity; locate data; review exemptions and third-party data; respond within the legal deadline; record the outcome
Incident responseDetect and report; contain; assess risk to individuals; notify authorities and individuals where required; remediate; review lessons learned

Exam questions often test the order of steps, for example containing a breach before notifying, or verifying identity before releasing data.

How CIPM questions differ from CIPP/E questions

The CIPP/E asks what the law says. The CIPM asks what a privacy manager should do. That means:

  • The best answer is usually the one that is sustainable and fits the organisation's maturity, not the most aggressive one.
  • Answers that skip steps (buying a tool before understanding the data, writing policies before knowing the laws) are usually wrong.
  • Legal detail matters less, but you still need to know common requirements such as breach notification timing and DPIA triggers.

Compare the two exams in CIPM vs CIPP/E: which is harder?

Hours by domain

DomainScored Qs (approx.)Suggested hours (of 50)
I. Developing a framework14–1810
II. Programme governance12–169
III. Assessing data12–169
IV. Protecting personal data9–137
V. Sustaining performance7–95
VI. Requests and incidents10–147
Mock and review–3
Think like the privacy manager in the scenario. For every question, ask: what's the programme-level action? Who needs to be involved? What comes first? Answers that go straight to a technical fix, or to legal interpretation, without the governance step are often distractors.

Key concepts checklist

  • Governance model selection and the reasons behind it
  • The privacy team structure and the DPO's independence
  • Policy hierarchy: policies, standards, procedures, guidelines
  • Data inventory as the foundation for PIAs, DSARs and incident response
  • When to perform a PIA or DPIA, and how to act on the findings
  • Vendor lifecycle: due diligence, contract, monitoring, offboarding
  • Metrics for different audiences (board, executives, operations)
  • Privacy maturity levels
  • The incident response plan and team; breach notification decision-making

See CIPM operational workflows for the processes in detail.

Three sample CIPM questions (original Archuz items)

Q1Framework

A company is building its first privacy programme. Which step comes first?

  • ASelect privacy management software to run the programme
  • BPublish an updated privacy policy on the website
  • CRun company-wide privacy awareness training
  • DDefine the programme's scope and identify applicable laws and stakeholder expectations
Show answer

Correct: D — Define the programme's scope and identify applicable laws and stakeholder expectations

Framing comes first: scope, applicable laws and what stakeholders expect (D). Software (A), a policy (B) and training (C) are all things you design once you know what the programme must cover.

Q2Governance

Which role helps embed privacy in business units without making them full-time privacy staff?

  • AAn external auditor
  • BThe data protection officer
  • CInformation security analysts
  • DPrivacy champions
Show answer

Correct: D — Privacy champions

Privacy champions are business-unit staff who promote privacy practices alongside their main jobs (D). Auditors (A) provide independent assurance rather than embedding practice, the DPO (B) is a dedicated privacy role, and security analysts (C) work in a specialist function rather than in the business units.

Q3Sustaining performance

Which is the best indicator of programme maturity?

  • ADocumented processes that are followed, measured and improved
  • BA comprehensive library of approved privacy policies
  • CA privacy team sized to the company's headcount
  • DAnnual training delivered to every employee
Show answer

Correct: A — Documented processes that are followed, measured and improved

Maturity models look for processes that are defined, consistently applied, measured and improved (A). Policies (B), team size (C) and training delivery (D) are inputs; they don't show whether the programme works.

Common CIPM study mistakes

  • Over-studying law, which the CIPM treats as context
  • Skipping case-study practice until the final week
  • Memorising definitions without learning workflows and sequences
  • Choosing activity metrics over outcome metrics

Everything this plan needs

The CIPM Complete Pack includes a Cram Guide, 300 BoK v4.2.0 questions (18 case studies in three 100-question sets) and an After You Pass guide.

Get the Complete Pack

Frequently asked questions

How long does it take to study for the CIPM?

Most candidates need 40–55 hours over 6–8 weeks. IAPP recommends at least 30 hours.

What is the hardest part of the CIPM?

Many candidates find framework and governance scenarios (Domains I–II) and multi-question case studies the hardest.

Do I need privacy work experience for the CIPM?

No, but it helps. Without it, spend more time on scenarios to build practical judgment.

What are the three CIPM governance models?

Centralised (one privacy office decides for the organisation), local or decentralised (units manage privacy themselves) and hybrid (a central office sets policy, local teams implement). Hybrid is the most common in multinationals.

Is the CIPM only about the GDPR?

No. The CIPM is jurisdiction-neutral. It tests how to run a privacy programme, using examples from several laws. You need general awareness of common legal requirements, not deep knowledge of any one law.

Sources

  1. IAPP Store: CIPM Exam
  2. Privacy Bootcamp: CIPM BoK 2025–2026
  3. OpenExamPrep: CIPM BoK overview
  4. NIST Privacy Framework

Last reviewed: October 2026.