Resources & Knowledge.
Guides, research and learning across project controls in the AI era.
Overview
PCI’s resources help professionals and employers understand modern project controls — from the fundamentals through to project finance and the responsible use of AI. They are openly available and exist to build understanding, not to sell exam preparation, which is provided separately by Certuvo.
The resource library is being built as a practical companion to the credential and the standard — the place a project-controls professional comes for material they can actually use, not marketing. Its organising principle is the twelve-competency model: resources are mapped to the competencies that make up the discipline, from planning and cost control through to the governed use of AI, so you can find help for the part of the work you are facing.
Over time it will bring together several kinds of material: explanatory guides to the discipline and the standard; practical aids such as checklists and worked examples; guidance on applying and governing AI in controls work; and career and certification resources that help you plan your path. Everything is intended to be vendor-neutral and grounded in how the work is genuinely done, rather than tied to a particular tool.
the library is growing rather than complete, and we would rather publish a smaller set of genuinely useful material than pad it out. As the institute and its community grow, so will the depth here — with members and certified professionals helping shape what gets prioritised.
The library is being built out across several formats: plain-language explainer guides, an overview of the body of knowledge, research and industry reports, webinars and recorded sessions, and an insights blog covering the standard, the discipline and AI in controls. Everything maps back to the PCL-AI body of knowledge, so what you read connects directly to what the credential certifies.
Common questions
Are the resources free?
Yes — PCI’s knowledge resources are openly available.
Do they prepare me for the exam?
They build understanding; structured preparation is offered separately by Certuvo.
How do they relate to the credential?
They map to the PCI bodies of knowledge.
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 in the institute's resources is written to that test: genuinely 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, refusing to publish invented data or figures it cannot stand behind, and letting the community shape what gets prioritised. Trust, earned this way, is harder to lose.
- Substance over marketing
- Fair, transparent process
- Honesty about our status
- Responsible, governed use of AI
Where to start, by situation
The library serves three quite different readers, and the right entry point depends on which one you are today.
New to the discipline
Begin with the plain-English explainers — starting with what project controls actually is and how it differs from project management — before moving into the Knowledge Centre for method-level depth.
Preparing to certify
Work through the body of knowledge domain by domain, using Knowledge Centre articles to shore up the areas you use least at work, and sample questions to understand how the exam asks things. Structured preparation sits separately, with the training arm.
Leading a team or function
Head for the governance material — particularly the guidance on governing AI in controls work — which is written to help you set a defensible position for your own team, not just pass an exam.
Turning reading into recorded development
Passive reading fades within weeks. A few deliberate habits make it stick — and make it usable as evidence of development under the CPD framework.
- Read against a live problem. Choose material because of something your project faces this month — a forecast that will not converge, a baseline under change pressure — and apply one idea from it within the week.
- Keep a two-line note per piece: what question it answered and what you will do differently. That note is exactly the kind of record a CPD audit expects to see.
- Discuss it. Walking a colleague through an article's argument tests whether you actually understood it, and the mentoring conversation is development for both of you.
And if you look for something that is not here yet, say so via the contact page. The library grows against real demand, and a specific request — a worked example of schedule risk analysis on a small project, say — is far more useful to us than general encouragement.