Standards.
Defining what good project-controls capability looks like.
At a glance
What standards cover
- The competence the credential represents
- The knowledge areas and their weighting
- Ethical and AI-responsible practice
- How capability is assessed
Developed with rigour
This develops as the institute matures, and PCI makes no claims beyond what is true today.
How the standard is built
At the centre of the standard is the twelve-competency model — the view that project controls is one integrated discipline rather than a loose set of techniques. It spans project management, planning and scheduling, cost estimating and control, forecasting, earned value, risk, commercial management, project finance, financial awareness, reporting and analytics, and AI governance.
Treating these as a connected whole is deliberate. On a real project, a schedule decision is a cost decision and a risk decision at once; the standard reflects that reality, and it makes AI governance a competency in its own right because AI now touches every part of the work.
How the standard is applied and maintained
The standard is not an abstract document — it is what the PCI credentials certify, what the examination assesses, and what the body of knowledge explains. That alignment is what lets the credential mean the same thing for everyone who holds it.
It is also maintained rather than fixed. As practice evolves and AI reshapes how controls work is done, the standard is intended to keep pace, so that what the credential certifies stays meaningful over time.
Common questions
Are PCI’s standards accredited?
Developed with reference to ISO/IEC 17024.
Who do the standards serve?
Professionals seeking to demonstrate capability and employers evaluating it.
Are they fixed?
They are reviewed as practice and AI evolve.
Why this matters
This matters because a credential earns its value from substance, not marketing — clear standards, fair process, transparent governance and honesty about status. Everything here is written to that test: useful to professionals and employers, and never claiming more than is true today.
PCI builds in the open. That means being candid about what is in place and what is still developing, designing around the ISO/IEC 17024 personnel-certification principles, and never implying recognition it does not yet hold. That honesty is part of how trust is earned.
- Substance over marketing
- Fair, transparent process
- Honesty about our status
- Responsible, governed use of AI
How a PCI standard is made
A standard is only as good as the process behind it. PCI's standards work follows a deliberate sequence: practitioners draft against real project experience; drafts are exposed to consultation so the community can challenge scope and wording; the standards committee reviews and resolves the feedback; and the adopted text is then reviewed periodically so it tracks practice rather than fossilising. Throughout, the framework is developed with reference to ISO/IEC 17024 personnel-certification principles — meaning the separation of duties, impartiality and review disciplines those principles describe are designed in from the start. How the committee itself is constituted and governed is set out in its terms of reference.
What the standards define
The standards describe competence — what a capable professional can actually do — across the integrated discipline:
Planning & scheduling
Building schedules with sound logic and a defensible basis, and maintaining them as a decision tool.
Cost engineering
Estimating, budgeting and cost control through the project lifecycle, with change managed against baseline.
Earned value & forecasting
Measuring performance honestly and forecasting outcomes by methods that can be explained and defended.
Risk
Identifying, quantifying and managing uncertainty so contingency reflects analysis rather than habit.
Project finance
Understanding how projects are funded and how controls information serves investment decisions.
Governed AI
Using AI within stated rules — human accountability for outputs, verification before reliance, transparency about use.
How the standards are used
For candidates, the standards resolve into the body of knowledge — the published statement of what each PCI examination assesses, and therefore what to study. For the institute, they anchor the certification scheme: eligibility, examination and recertification all trace back to the same competence definitions, which is what keeps the credential coherent. For employers, they offer a shared vocabulary — role descriptions, development plans and interviews can reference the same definitions of capability that the credential assesses, so competent means the same thing on both sides of the hiring table.
The standards are also living documents. As governed AI practice matures and reporting conventions evolve, scheduled reviews keep the competence definitions aligned with what good practice actually looks like on projects — so the credential examines the discipline as it is, not as it was.