Blog.
Articles and analysis from the Institute.
Overview
The PCI blog shares practical guides and analysis on project controls, cost, forecasting, careers and AI — written to be useful to practitioners and employers, and grounded in the discipline PCI certifies.
The blog is the institute's more regular, conversational channel — shorter pieces on the discipline, the credential, and the practical realities of project controls in an AI-enabled world. Where the standard is formal, the blog is where ideas are explored in plain terms.
Topics will range across the things practitioners actually talk about: making schedules and forecasts more credible, using AI tools without losing accountability, preparing for certification, and the day-to-day judgement calls that define good controls work. The intent is usefulness over volume.
we would rather publish something worth your time occasionally than fill a feed. Membership and the wider community will increasingly shape what gets written about here.
Explore more
Common questions
Who writes the blog?
PCI, drawing on project-controls expertise.
Is it free?
Yes.
How does it relate to the credential?
It informs and reflects the body of knowledge that the PCL-AI credential certifies. The standard, the resources and the assessment are kept aligned deliberately, so that what you engage with here connects directly to what the credential recognises — the integrated controls discipline, with AI governance as a first-class part of it.
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
How to turn an article into practice
An article only earns its keep when it changes how you work. The pieces here are written to be applied, and the quickest way to apply one is to test it against a project you already know — while the data, the politics and the pressures are still fresh in your mind.
Test it on live data
Reading about a method is not the same as running it. Take one control account or work package you own and work the article's approach through it end to end. The gaps you hit are where the real learning sits.
Argue with it
Every method rests on assumptions. List the ones that do not hold on your project and work out what breaks when they fail. Challenging the basis before trusting the number is the core habit of the discipline.
Record the judgement calls
Where a piece flags a judgement call, note how you would make it and why. Those notes double as preparation for scenario-style assessment and for the project reviews where you defend a forecast for real.
Using and sharing the blog
Can I suggest a topic or contribute an article?
There is no formal guest-author programme at this stage. Ideas and questions are welcome through the contact page — the questions practitioners actually ask are the strongest signal of what we should write next.
Can I share or cite articles?
Yes. Links can be shared freely, and short quotations with attribution are welcome. For reuse of substantial extracts, the copyright policy sets out what is permitted and how to ask.
Does reading the blog count towards CPD?
Passive reading on its own is a weak development record. Structured reflection on an article — what you tested, what changed in your practice as a result — is far stronger evidence. The CPD framework describes the kinds of activity PCI recognises and how to record them.
Keep going
How we write, and where to start
Editorial rules here are the Institute’s rules: no invented statistics, no vendor puffery, positions argued from practice and first principles. Where a topic is contested we say so; where our view serves our interest, we declare it.
New to the discipline? Read in this order: what project controls is (and is not), the planning-engineer craft piece, then the AI adoption essay — together they map the terrain the PCL-AI credential assesses.