Study guide
Manage Accountability Documentation and the Audit Trail
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
Manage Accountability Documentation and the Audit Trail
Key Takeaways Explain This Topic AI
A decision record answers four questions — what was decided, by whom, on what evidence, and what alternative was rejected and why; the fourth is the one teams skip and auditors ask for.
Every accountability record must point at the specific artifacts behind a result — the dataset snapshot, the training run, the model version — by identifier rather than describe them in prose; the technical pinning discipline itself belongs to Domain IV model QA/QC.
Every CPMAI phase ends in a go/no-go, and each needs a signed record naming the approver and their authority, the evidence reviewed, and every condition attached with an owner and due date.
Chain of custody for training and test data covers origin, every hand that touched it, and the license or consent that permits model training specifically — permission to analyze is not permission to train.
The reproducibility test: could an independent auditor rebuild this model result 18 months from now from your records alone, with no access to the project team?
Last updated: August 2026
Documentation Is the Deliverable That Proves Everything Else Happened
The other Domain I tasks produce claims : we protected the data, we made the model explainable, we tested for bias. Task 5 produces the evidence . Treat the decision log as a first-class deliverable with an owner, a template, and a slot in the schedule — not something written up at the end. (Keep it distinct from Domain V, Task 3 model governance, which supervises the model after go-live — drift, retraining, decommissioning — while accountability documentation records how it was built and who approved it.)
What a Decision Record Actually Contains
Four fields, every time:
What was decided — stated as a decision, not a status.
By whom — a named person with the role and the authority to make it.
On what evidence — the analysis, SME opinion, or test result relied on, with a pointer to it.
What was rejected and why — the alternative considered and the reason it lost.
The fourth is the one teams skip and auditors ask for. "We trained on 18 months of history" is a status. "We trained on 18 months because the 2023 pricing change made earlier data non-comparable; the 36-month option was rejected for that reason, confirmed by the pricing SME on 4 March" is a record.
Decisions worth logging: the problem framing, the target label definition, the inclusion or exclusion of a data source, the fairness metric and groups tested, the decision threshold, the accept/reject on a candidate modeling technique, and every scope change.
Point the Record at the Artifacts, Not at a Description
The enabler behind this task calls for version control over models, data, and training processes . The technical discipline that delivers it — pinning the dataset snapshot, the code commit, the configuration, the seed, and the environment — is covered under Domain IV model QA/QC, so learn the pinning rules there. What Domain I asks of you sits one step away from the tooling and is the part teams miss: every accountability record must point at those artifacts by identifier rather than describe them in prose.
In practice that means a decision record cites the run it relied on, a gate approval cites the evaluation report and the exact candidate it cleared, and a deployment record cites the model version together with the dataset snapshot behind it. "Trained on the customer table" is a description; a snapshot identifier with an as-of timestamp is a reference someone else can follow two years later. Your own test is a walk: take the model that is live today and see whether the file lets you step from the deployed version to the run that produced it, from the run to the data it consumed, and from that data to the permission that allowed its use. You do not operate the tools that store those identifiers, but you require them in the plan, budget the effort, and spot-check that the fields you will one day be asked for are actually populated. A spreadsheet is acceptable at small scale only if each row still resolves to a specific run.
Signed Approvals at the Go/No-Go Gates
CPMAI is phased, and each phase ends in a go/no-go decision. A signed approval must exist for each. Record the gate, date, decision, the named approver and their authority, the evidence reviewed, every condition with an owner and due date, and any dissent. The classic failure is the conditional go whose conditions are never written down: six months later the record reads as unconditional approval. "The steering committee approved it", with no name, date, or artifact list, is not an approval record.
Chain of Custody for Training and Test Data
Three questions, answered in writing for every dataset:
Where did it come from? Source system, data owner, extraction date, extraction method.
Who touched it? Every transfer, transformation, and access grant between the source and the training run.
What permits its use? The contract clause, consent text, or terms of service — including purpose limits, expiry, and specifically whether model training is permitted, which is not the same as permission to analyze or report.
Test and holdout data need their own custody trail: the entire value of a holdout is that the model never saw it, provable only from records. The recurring trap is a purchased or scraped dataset whose license covers "internal analysis" being quietly read as covering model training.
The Accountability Artifact Set
Artifact What it records Who owns it When it is produced
Decision log What was decided, by whom, on what evidence, what was rejected and why Project manager Continuously, every phase
Data inventory and source register Each source, its owner, extraction date, and the license or consent that permits use Project manager with the data SME Data Understanding
Chain-of-custody record Every transfer, transformation, and access grant for training and test data Data engineering lead; PM verifies completeness Data Understanding into Data Preparation
Experiment tracking run record Parameters, dataset version, code commit, metrics, and artifacts for each run Data science lead Model Development and Model Evaluation
Model registry entry Which run became a candidate, which was approved, current stage, what it supersedes Model owner with MLOps Model Evaluation into Model Operationalization
Model documentation (model card) Purpose, training data, performance including by group, known limits, prohibited uses Model owner; PM reviews Before the operationalization gate
Signed go/no-go memo Gate, decision, named approver and authority, evidence reviewed, conditions, dissent Project manager; signed by the gate authority End of each CPMAI phase
Accountability report Readable synthesis for executives and regulators, with pointers into the evidence Project manager At operationalization and on a set review cycle
The Reproducibility Test
Apply one question to the whole file: could an independent auditor, 18 months from now, with no access to anyone who worked on the project, rebuild this result from your records alone? Walk the chain — the deployed model version, the run that produced it, the exact data snapshot, the transformations, the configuration, the evaluation results, and the approval with its conditions. Any break is an audit finding waiting to happen. Run the test yourself at the operationalization gate, while the people who know the answers are still around.
Preparing the Accountability Report
Executives and regulators do not read the decision log; they read a synthesis that points into it. Write for a reader with no project context, covering: what the system does and which decision it influences; what data it was built on and under what authority; how it performed, including by group; known limitations and where it must not be used; who approved it and when; what monitoring and human-review path exists; and where the evidence is stored. If the report cannot be read on its own, it is a log extract, not an accountability report.