Continuous Improvement.
PCI treats certification as a system that should get better as evidence accumulates.
Overview
A certification body earns trust over time by learning. PCI gathers feedback, audit findings, performance data and outcomes, and uses them to improve its standard, examinations and service in a continual loop.
At a glance
What drives improvement
- Candidate and stakeholder feedback
- Internal audit findings
- Complaints and appeals outcomes
- Examination performance and item statistics
- Changes in project-controls practice and AI
How changes are made
PCI applies this consistently and records what it does, so the process can be checked and improved. The detail is governed by the related policies linked below and is published as the institute matures.
Common questions
How does PCI decide what to improve?
Inputs are reviewed and prioritised, then changed through corrective action or policy revision and monitored.
Are changes communicated?
Yes — material changes are published before they take effect.
Who oversees improvement?
PCI management review, supported by internal audit and the quality policy.
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
Founding-stage document · Version 1.0 — effective date to be confirmed · Reviewed under PCI governance. PCI makes no claims of accreditation or recognition beyond what is true today.
Plan–Do–Check–Act, applied to certification
Plan
Decide what to change and why, based on evidence — a cluster of complaints, an audit finding, item statistics drifting, or a gap the team has named itself.
Do
Make the change deliberately and under control: documents are versioned, affected people are told, and the old way is retired rather than left running alongside the new.
Check
Watch whether the change did what was intended. A fix that merely moves a problem somewhere less visible is not an improvement.
Act
Standardise what worked, unwind what did not, and record both — so the same lesson is never paid for twice.
The loop runs at every scale. A single examination item can move through it in one review cycle; a change to the standard itself moves through the same four steps over a much longer period, with more people involved. The discipline is identical — only the stakes and the timescale change.
How candidates and members feed the loop
Improvement inputs are not abstract; most begin with a person telling us something. The formal channels all feed the same system:
- A complaint signals a service or process failure worth examining beyond the individual case that raised it.
- An appeal, whatever its outcome, tests whether a decision process is working as designed — patterns in appeals are studied as carefully as the appeals themselves.
- Examination data — item performance, timing patterns, pass-point behaviour — is reviewed routinely, not only when something visibly breaks.
- Plain feedback, sent through any channel, is logged even where no immediate action follows, because weak signals accumulate into strong ones.
Improvement without disruption
A certification body carries a particular duty when it changes things: candidates plan months around a syllabus, an examination format, a policy. So every change is weighed for candidate impact before it is made, introduced with notice rather than by surprise, and kept away from mid-cycle candidates wherever possible. Where a change corrects an identified fault rather than refining something sound, the corrective action procedure governs how the root cause is closed out. Improvement and correction are related, but they are not the same discipline — one makes a working system better, the other stops a failure recurring — and PCI runs both deliberately.
Keep going
How improvement actually enters the system
Improvement inputs are specific: candidate and employer feedback, appeal and complaint outcomes, examination statistics (item performance, pass-rate drift), audit findings and incident reports. Each is reviewed on a cycle; accepted changes go through controlled revision — the standard and its documents are versioned, and material changes are announced before they bite.
What this means for you: if a question was unfair, a process was slow, or a policy is unclear, telling us is not shouting into a void — it enters a documented loop with an owner and an outcome.