Study guide
Monitor Regulatory and Policy Compliance
PMI Certified Professional in Managing AI PMI-CPMAI
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: PMI-CPMAI Exam Foundations & the CPMAI Methodology
The PMI-CPMAI Exam: Format, Eligibility, Fees & Scoring The CPMAI Methodology: Six Phases and Data-Centric Iteration CPMAI vs Waterfall, Agile, and CRISP-DM
2 Chapter 2: AI and Machine Learning Fundamentals for CPMAI
The Seven Patterns of AI Supervised, Unsupervised & Reinforcement Learning Why AI Projects Fail: Value, Data Readiness & Right-Sizing
3 Chapter 3: Domain I — Support Responsible and Trustworthy AI Efforts (15%)
Oversee the Privacy and Security Plan Manage AI/ML Transparency in Data and Algorithm Selection Conduct Bias Checks on Model, Data, and Algorithm Monitor Regulatory and Policy Compliance Manage Accountability Documentation and the Audit Trail
4 Chapter 4: Domain II — Identify Business Needs and Solutions, Part 1 (26%)
Identify the Problem to Be Solved Evaluate Initial AI Feasibility Conduct Security, Safety, and Ethics Risk Assessments Develop the AI Project Scope Statement Determine Return on Investment
5 Chapter 5: Domain II — Identify Business Needs and Solutions, Part 2
Manage Adoption and Integration Risks Draft the AI Solution Define Success Criteria and KPIs Support Business Case Creation Identify Project Resources: People, Hardware, and Contractors
6 Chapter 6: Domain III — Identify Data Needs, Part 1 (26%)
Define the Required Data Identify Data Subject-Matter Experts Identify Data Sources and Locations Coordinate the AI Workspace and Infrastructure Gather the Required Data
7 Chapter 7: Domain III — Identify Data Needs, Part 2
Check Data Privacy, Compliance, and Access Oversee Data Evaluation Determine If the Data Meets Solution Needs: The Phase 2 Go/No-Go Convey Data Understanding to Leadership
8 Chapter 8: Domain IV — Manage AI Model Development and Evaluation (16%)
Oversee AI/ML Model Technique and Algorithm Selection Oversee Model QA/QC and Configuration Management Manage AI/ML Model Training Manage Data Transformation and Data Preparation Verify Data Quality for the Data Preparation Go/No-Go Verify the Model Is Ready for Operationalization
9 Chapter 9: Domain V — Operationalize AI Solution, Part 1 (17%)
Manage Creation of the AI Solution Deployment Plan Manage the AI Solution Deployment Oversee Model Governance in Production Oversee AI Solution Metrics and Performance Monitoring
10 Chapter 10: Domain V — Operationalize AI Solution, Part 2
Prepare the Final Report and Lessons Learned Manage the AI Solution Transition Plan Oversee the AI Solution Contingency Plan
Monitor Regulatory and Policy Compliance
Key Takeaways Explain This Topic AI
Domain I, Task 4 is worded 'monitor regulatory and policy compliance' — it demands a standing watch with a named owner and a fixed review cadence, not a one-time sign-off.
The ECO grounds regulation in GDPR, CCPA, and 'evolving AI regulations and industry standards'; sector overlays in healthcare, financial services, employment, insurance, and the public sector decide the real obligations on the same model.
A regulatory change that never becomes a backlog item with an owner and a date has not been managed — every watch item ends in 'applies', 'monitor', or 'not applicable', in writing.
When a new regulation lands mid-project, the first move is a documented impact assessment with legal and compliance — never a unilateral redesign and never deferral to post-launch.
Compliance checks belong on the CPMAI phase gates and inside the build pipeline, where a violation costs an afternoon instead of a remediation program.
Last updated: August 2026
Compliance Is a Standing Duty, Not a Checkbox
Domain I, Task 4 uses the verb monitor — not confirm , not obtain . A project that was fully compliant at the Business Understanding gate can be out of compliance by Model Operationalization without a line of code changing: the law moved, the data source changed its terms, or the model was pointed at a population it was never approved for. Your job is not to collect one clearance; it is to run a process that keeps noticing.
Stand Up a Regulatory Watch
Tracking evolving AI regulations and industry standards only happens if someone is accountable by name.
Owner. A named person — usually in legal or compliance — with you as the project-side counterpart. A department is not an owner.
Cadence. A monthly scan, a standing agenda item at the quarterly steering review, plus an event-driven trigger whenever a regulator, enterprise customer, or vendor sends notice.
Sources. Regulator bulletins and registers for your sector, your industry association, the standards bodies your contracts cite, and change notices in your data and platform agreements.
Intake path. This is the part projects skip. Every watch item must reach a written decision — applies , monitor , or not applicable . "Applies" becomes a backlog item with an owner and a date. "Not applicable" is recorded with a reason. A regulatory change that never becomes a backlog item has not been managed.
Track two horizons. Enacted law creates requirements you must meet. Proposed rules and voluntary industry standards create design options worth preserving — a human-review hook costs little now and a great deal to retrofit. Risk-tiering regimes and voluntary AI risk-management frameworks belong on the watch as inputs your customers and auditors will ask about, not as the structure of your project.
Sector Overlays: One Model, Different Obligations
GDPR (General Data Protection Regulation) and the CCPA (California Consumer Privacy Act) apply horizontally — lawful basis, purpose limitation, data minimization, and individual rights of access, deletion, and opt-out. Treat them as the floor, not the ceiling. What surprises AI projects is sector-specific: the same churn model is ordinary marketing analytics in retail, a fair-lending artifact in a bank, and a protected-health-information system in a hospital.
Sector Typical AI obligation Who signs off Evidence the PM keeps
Healthcare Protected health information under a data use or business associate agreement; de-identification before model use; clinical decision support may fall under medical-device rules Privacy officer plus clinical governance lead or medical director Data use agreement, de-identification memo, clinical review minutes
Financial services Independent model validation, fair-lending testing, and a specific explainable reason when a decision is adverse Model risk management plus compliance Validation report, adverse-action reason mapping, model documentation
Employment / HR Bias auditing and candidate notice for automated employment decision tools in a growing number of jurisdictions Employment counsel plus HR leadership Bias-audit report, candidate notice text, accommodation and appeal path
Insurance No unfair discrimination in rating or claims handling; regulator expectations on AI use programs; filings where a model affects rates Chief actuary or product compliance plus the state filing team Filing package, rating-factor justification, claims-review sampling
Public sector Procurement and public-records rules, algorithmic impact assessment or transparency disclosure, accessibility Agency counsel plus the contracting officer Impact assessment, published disclosure, records retention schedule
Jurisdiction follows the people and the use, not your office. If the model scores residents of a jurisdiction, or its output is acted on there, its rules are in scope even if your team never leaves headquarters.
Coordinate With Legal and Compliance — and Escalate on Triggers
Bring counsel in at Business Understanding , not at deployment. The cheapest compliance change is the one made before data is collected. Give them what they actually need to answer: the purpose, the population, the decision the model influences, the data elements, the retention period, who sees the output, and whether the decision can be adverse to an individual.
Escalate immediately when any of these appear:
New personal or special-category data enters scope.
The output starts driving a decision about an individual — credit, hiring, care, claims, benefits.
Data crosses a border, or a vendor sub-processes it or trains on it.
The model is repurposed to a population or a use it was not built for.
A regulator, auditor, or enterprise customer asks a question you cannot answer from the file.
Put counsel's answer in the decision log in writing. An oral clearance is not evidence.
Build the Checks Into Gates and the Pipeline
Attach each compliance question to the gate that can still act on the answer: permitted purpose at the Business Understanding gate; lawful basis, consent scope, license terms, and retention at the Data Understanding and Data Preparation gates; bias results and required notices at the Model Evaluation gate; logging, the human-review path, and AI disclosure at the Model Operationalization gate.
Then automate what can be automated inside the build pipeline. Fail the build when a restricted field appears in a feature set, when a dataset carries no license tag, when a model artifact has no named owner, or when a mandatory documentation field is empty. The value is timing, not elegance: a violation caught in continuous integration costs an afternoon, while the identical violation surfaced in an audit costs a remediation program. Close the loop with reporting — a standing compliance line in your status report covering open items, watch changes, and gates cleared, plus a periodic control report to whoever owns enterprise risk.
Keep the File Audit-Ready Continuously
Nobody has ever successfully reconstructed an evidence file after the audit letter arrives. Assemble it as you go, in one indexed and versioned location: the data inventory with source and license basis, privacy and impact assessments, consent and contract terms, bias-check results with the groups tested, model documentation, signed gate approvals, the regulatory-watch log, and monitoring reports. Retain it on your records policy's schedule, not the project's — the project ends and the obligation does not.
How the Exam Tests a Mid-Project Regulatory Change
A new regulation lands mid-project. Your first move is a documented impact assessment with legal and compliance : does it apply, to which components, by when, and at what cost. Only then do you decide. Redesigning unilaterally is wrong because you do not yet know what applies, and an unassessed redesign is an undocumented scope change. Logging it for the retrospective, deferring it to post-launch, or escalating to the sponsor before you know the impact all fail for the same reason — the assessment is the first deliverable.