For Employers.
A consistent project-controls capability standard for your organisation.
Overview
Employers need teams that produce reliable schedules, credible forecasts, clear cost reports and timely risk insight — and, increasingly, people who can apply AI to that work without losing accountability. The PCL-AI gives organisations a single, dependable signal that a professional can do all of this as one connected discipline.
Used well, the credential becomes a practical tool across the employee lifecycle: a clear bar when hiring, a defined target for development, and added assurance that the AI-assisted outputs your teams rely on are validated, explainable and owned by a competent human who can defend them to a client or auditor.
PCI makes no claims beyond what is true today: it is, building toward reference to ISO/IEC 17024 principles. Credential verification is available now — free and instant on the verification page.
Explore more
Why employers choose PCI
Why employers should take note.
For organisations
How PCI works with employers and partners.
Corporate programmes
Developing whole teams to one standard.
Workforce development
Building controls capability at scale.
Employer recognition
Recognise it.
Credential verification
How credential verification works.
What the credential gives an employer
When you hire or develop someone with a PCI credential, you are relying on an independent judgement of their competence — not a self-description. It is built to give employers a clear, verifiable signal across the whole controls discipline, including the governed use of AI that now runs through planning, cost and risk work.
Verifiable competence
An impartial, third-party assessment of integrated controls ability — something you can check rather than take on trust.
A common benchmark
One standard to develop your controls team against, instead of a patchwork of courses and job titles.
AI assurance
Evidence that a professional can govern AI outputs — validate, explain and own them — rather than defer to a tool.
Less re-testing
A recognised credential reduces how much you re-assess capability at every hire or bid.
Targeted development
The competency model shows exactly where to invest in upskilling existing staff.
A clearer hiring signal
A shared reference point that helps you compare candidates fairly and consistently.
Common questions
How does the credential help employers?
A common capability language, stronger forecasting and reporting discipline, and responsible AI governance.
Can we verify a candidate’s credential?
Yes — free and instant, on the credential verification page. Honorary awards are clearly labelled as honorary recognitions.
Does PCI claim employer recognition?
No — beyond what is true today.
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 to use the credential in hiring — honestly
The simplest way to start is in the job description. List a PCI credential as desirable rather than mandatory while the programme is in its founding cohort phase — that keeps your candidate pool open and reflects the credential's actual maturity. As the registry comes online, verification can move from a courtesy check to a standard step in your screening process.
The credential is most useful when it shapes the interview, not just the shortlist. The Body of Knowledge gives you a ready-made structure for competency questions: ask a candidate to walk through a forecast they personally defended, explain how they set contingency on a real project, or describe a time they overruled an AI-assisted output and why. A certified candidate should handle those questions fluently; a strong uncertified candidate may too — which is exactly the comparison you want to be able to make on equal terms.
Building one standard across an existing team
Certifying a team works best as a staged programme rather than a blanket mandate. A pattern that works in practice:
1. Baseline
Map current roles against the Body of Knowledge domains. Most teams find pockets of depth — strong planners, strong cost engineers — with gaps where the domains meet, such as forecasting and finance.
2. Prioritise
Put forward first the people whose roles span domains: PMO leads, controls managers, senior planners moving into reporting. They gain most from an integrated standard.
3. Protect study time
Preparation competes with delivery. Teams that ring-fence regular study time see candidates through; teams that leave it to evenings see attrition.
4. Cohort, don't scatter
Enrol people in small groups so they prepare together and share worked examples from your own projects. Corporate programmes support this directly.
5. Maintain
Certification is a start line. Use the CPD framework to keep capability current, and fold recertification into annual development planning.