Study guide

Verify Data Quality for the Data Preparation Go/No-Go

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

Verify Data Quality for the Data Preparation Go/No-Go

Key Takeaways Explain This Topic AI

Domain III Task 8 asks whether you have the right raw data; this Domain IV gate asks whether preparation produced a training-ready dataset that is correct, representative, and free of leakage — a project can pass the first and fail the second.

Split integrity is checked at key level: the same customer or claim appearing in both training and test, or a test period overlapping training, inflates every result and the inflation only surfaces in production.

Preparation itself can create bias, so when the rows dropped for incompleteness concentrate in a protected or business-critical segment, that is a bias finding requiring remediation, not routine cleaning.

This gate can land on go, conditional go on a documented subset, iteration back to Phase 3 or Phase 2, or stop — returning for better data is a designed CPMAI outcome, not a failure.

The gate's deliverable is a data readiness memo naming the dataset version, checks run, imputation and exclusion rules, known limitations, and open remediation items, so the modeling team inherits limitations instead of discovering them.

Last updated: August 2026

Two Data Gates, Two Different Questions

CPMAI puts a decision point at the end of each phase, and Domain IV, Task 5 is easy to confuse with the one before it. Keep them apart.

Domain III, Task 8 closes Phase 2, Data Understanding . It asks: do we have the right raw data? Enough volume, enough history, the right granularity, legally usable, actually obtainable.

Domain IV, Task 5 closes Phase 3, Data Preparation . It asks: did preparation produce a training-ready dataset that is correct, representative, and free of leakage?

A project can pass the first and fail the second. The raw claims history can be complete and lawful, and the prepared table can still be ruined by a join that multiplied rows, an imputation default nobody sanctioned, or a split that lets the model see the future. This gate exists because the cheapest place to catch that is before a single model is trained.

The Final Quality Assessment Runs on the Prepared Dataset

Re-run quality checks against the table that will actually be fed to the algorithm, not the raw extract you assessed in Phase 2:

Row and column counts against what the preparation specification predicted.

The record funnel — how many rows survived each pipeline stage. A pipeline that silently discards 40 percent of the input is a finding, not a footnote.

Null rate per feature after imputation , against the threshold agreed for each field. A feature that is 60 percent imputed is a feature carrying almost no information.

Value ranges and referential integrity after joins, plus duplicate key detection.

Label distribution against the event rate the business believes is real.

Validating That the Transformations Did What Was Intended

Three checks earn their keep here.

Trace records back to source. Pull 20 to 30 prepared rows and walk each field back to the originating system with the data SME present. This unglamorous exercise catches the errors automated checks miss: currency in dollars where the pipeline assumed cents, timestamps in local time where downstream logic assumed UTC, and joins that quietly duplicated rows so one claim now appears four times.

Compare distributions before and after. Imputing a median into 30 percent of a field collapses its variance and can make a genuinely predictive feature look inert. A simple before-and-after comparison per feature exposes it.

Verify the splits. Confirm proportions match the plan, then check overlap at key level — the same customer, claim, or device appearing in both training and test inflates every number you are about to report. Near-duplicates count. For any time-dependent problem, confirm the test period sits strictly after the training period, and that no feature is computed using information dated after the prediction point. Temporal leakage produces a model that looks outstanding at the gate and collapses in production, which is precisely why the check belongs here rather than at model evaluation.

Representativeness and Bias, Re-Checked on the Prepared Data

Bias assessment in Phase 2 tested the raw population. This gate tests the population that survived preparation, because preparation itself can introduce bias the raw data never had .

Dropping incomplete records is the usual mechanism. Incompleteness is not random: it concentrates in whoever the organization captures least well — newer customers, a channel with a weaker feed, a rural branch, a partner-sourced segment, applicants outside the standard employment model. Drop them all and you have built a dataset for a population that is not the population you will serve.

So profile the exclusions. Compare the segment composition of dropped rows against retained rows, and compare the prepared dataset against the real deployment population. When dropped rows correlate with a protected or business-critical segment, that is a bias finding requiring remediation, not routine cleaning. Remediation options, in rough order of preference: recover the missing data at source, impute with an explicit "unknown" indicator rather than dropping, re-weight the sample, or narrow the deployment scope and document the exclusion openly.

The Readiness Decision

You run the gate. The data science lead, the data SME, and the data owner or steward sign; privacy or compliance signs whenever personal data is involved; the sponsor is informed of the outcome and of anything that changes scope. The gate then lands somewhere, and only one of the landing places is a plain go to Phase 4, Model Development.

It can land on a conditional go , which releases a defined subset or a narrowed scope with the limitation written down and a named remediation owner and date against it. It can send the work back to iterate — to Phase 3 to redo transformations, or further back to Phase 2 to acquire more or better data. And it can stop , when preparation has demonstrated that the data cannot support the solution at all.

Returning to an earlier phase is a designed CPMAI outcome, not a project failure. It costs a fraction of what the same discovery costs after the build.

Verification check Method Failure signal Decision impact

Completeness after preparation Null rate per feature before and after imputation; row funnel per pipeline stage A feature past its agreed null threshold, or an unexplained drop in surviving rows Iterate on Phase 3; do not train on a field that is mostly imputed

Transformation correctness Trace 20 to 30 prepared records field by field back to source with the SME Mismatched units, currency, or time zone; joins that multiplied rows Stop and fix the pipeline — every downstream metric is invalid

Distribution sanity Compare each feature's distribution before and after cleaning and scaling Variance collapse after imputation; impossible values surviving Revisit the imputation strategy and flag affected features to modeling

Split integrity Key-level overlap and near-duplicate detection across train, validation, and test The same customer or claim appears in more than one partition Rebuild the splits; results are otherwise inflated and undeployable

Temporal leakage Confirm the test period follows the training period; check each feature's as-of date against the prediction point A feature that could only be known after the outcome Remove the feature or redefine the split before any training

Label quality Sample re-labeling and SME adjudication against the written label definition Reviewer disagreement above the agreed level; ambiguous definitions Settle the label definition first — label quality is the ceiling on model quality

Representativeness Compare prepared-data segment mix against the live deployment population A segment materially under-weighted relative to real volume Conditional go with narrowed scope, or return to Phase 2 for more data

Preparation-induced bias Profile dropped and excluded rows against retained rows by segment Exclusions concentrate in a protected or business-critical group Bias finding requiring remediation — not acceptable as routine cleaning

Privacy and permitted use Confirm the prepared dataset stays inside consent and lawful basis after joins A join re-identifies de-identified data or merges incompatible consents No-go until privacy or legal clears it

Documenting Findings so the Modeling Team Inherits Them

The deliverable is a data readiness memo (or data quality report) that travels with the dataset into Phase 4. It names the dataset version identifier, the checks run and their results, the imputation and exclusion rules applied, the split definition and why it was chosen, the segments known to be under-represented, every open remediation item with an owner and date, and the decision itself with signatures.

Its purpose is transfer. The modeling team should inherit known limitations, not rediscover them at model evaluation after weeks of tuning, and the operations team should not learn about an excluded segment from a customer complaint. A gate that produces a decision but no memo has done half the job.