AI is now part of the discipline. We certify it.
The PCL-AI assesses the applied, governed use of AI across forecasting, risk and reporting — not generic literacy.
"AI proposes. The professional disposes."
Artificial intelligence can draft a forecast, flag an anomaly or write a variance narrative. It cannot be accountable for the result. The certified professional can.
That is the line the PCI certifications are built around: every output a credential-holder relies on must be explainable, validated, and owned by a competent human who can defend it to an auditor.
- Applying ML forecasting and predictive analytics to real project data
- Detecting anomalies and assuring data integrity at scale
- Using generative AI for reporting — with human-in-the-loop validation
- Governing models for bias, drift, privacy and explainability
- Knowing the limits of AI, and when to override it
Six modules of applied, governed AI.
Beyond the dedicated AI knowledge area in every section, the AI & Data Science core takes learners from foundations to assurance.
ML foundations for projects
What AI/ML can and cannot do, framed entirely in project use cases.
Predictive analytics in practice
Framing a controls problem as a model, and reading its output critically.
Anomaly detection & data integrity
Detecting bad data, progress anomalies and potential fraud — responsibly.
NLP & document intelligence
Extracting risks, commitments and changes from contracts and minutes.
AI governance, ethics & assurance
Validation, bias, drift, explainability and human accountability.
Practical AI tooling
Using analytics and AI tools responsibly in day-to-day controls.
Certify the way you actually work.
AI is already in your toolkit. The PCL-AI proves you can use it responsibly — and own the result.
How the standard works in practice
The standard is not anti-AI — it is about governing it. In day-to-day controls work that means a simple sequence, repeated for every AI-assisted output.
AI proposes
An AI tool produces a forecast, schedule or analysis.
The professional validates
Judges whether the output can be trusted, and where it might be wrong.
…and explains
Can account for how the result was produced and why it holds.
…and owns it
Takes personal responsibility for the decision that follows.
Common questions
What does the AI standard require?
That professionals govern AI rather than defer to it — AI proposes, the professional disposes. In practice: validating AI-generated outputs, being able to explain how they were produced, and taking personal responsibility for the decisions that follow.
Is AI governance really part of the credential?
Yes — it is assessed as a competency in its own right within the PCI certifications, not bolted on. The examination tests whether you can judge, explain and own AI-assisted work in realistic project situations.
Does this mean PCI is anti-AI?
Not at all. Used well, AI is genuinely powerful in controls work. The standard is about using it responsibly — capturing the benefit while keeping judgement and accountability with a competent human.
Will the standard change as AI changes?
Yes. AI is evolving quickly, so the standard is maintained rather than fixed, and is intended to keep pace so that what the credential certifies stays meaningful.
Why this matters
This matters because AI is already changing how project controls is done, and the risk is not that professionals use it — it is that they use it without judgement. The whole point of the standard is to make the responsible use of AI explicit: AI proposes, the professional disposes, and a competent human validates, explains and owns every AI-assisted output.
PCI is deliberately careful here. It does not overclaim what AI can do, nor what its own credential guarantees. It sets a clear, honest expectation for governing AI in controls work and certifies professionals against it — keeping accountability where it belongs.
- Substance over marketing
- Fair, transparent process
- Honesty about our status
- Responsible, governed use of AI
Five questions before you rely on an AI output
The standard becomes practical the moment an AI tool hands you something — a forecast, a schedule health check, a drafted variance narrative. Before that output reaches a report or a decision, a governed practitioner runs the same short interrogation every time.
What data sits behind this?
If you cannot describe the data the output rests on — its source, currency and known gaps — you cannot vouch for the output itself.
Does it survive an independent check?
Test the AI's answer against a conventional method: an earned-value trend, a benchmark, a bottom-up estimate. Convergence builds confidence; divergence demands investigation, never averaging.
Can I explain the driver?
You should be able to say in plain language why the result moved — which inputs pushed the forecast — not merely that the model said so.
What is the cost of being wrong?
A drafting suggestion carries little risk; a completion forecast feeding a funding decision demands far heavier scrutiny. Match the depth of validation to the consequence of error.
Is the use disclosed?
The people relying on your work should know where AI assisted and what human validation followed, consistent with PCI's responsible-AI framework.
The record that makes AI-assisted work defensible
Owning an AI-assisted output means being able to show, months later, how it was produced and checked. A short, disciplined record — kept in the normal project controls file, not a separate system — is what separates governed use from quiet reliance.
A defensible record usually captures five things:
- the tool used and the task it was given;
- the inputs supplied, including any data that was cleaned, corrected or excluded;
- the validation performed — the independent cross-check, who reviewed it, and what it found;
- what was changed before the output was used, and why;
- the named professional who accepted the result and stands behind it.
None of this needs to be heavy. A few lines against each significant output is enough to answer an auditor, a client or a review board. The habit also sharpens judgement: writing down the check you performed exposes the occasions when you performed none. This is human oversight made routine — and it is the working behaviour the PCI examinations are designed to test. For the underlying method, see the knowledge hub's treatment of AI governance in project controls.