Planning & Scheduling.
Building and controlling the timeline that everything else depends on.
Overview
Planning and scheduling define when work happens and what depends on what. Strong scheduling reveals the critical path, exposes slippage early, and gives every other control a reliable timeline to work against.
What this area covers
Why it matters
This is a core part of the PCL-AI body of knowledge — assessed as part of the credential and applied on real projects. It connects to the wider discipline and, increasingly, to responsible AI use, so professionals can demonstrate the integrated judgement PCI certifications assess.
Taught, then tested.
Every knowledge area maps to the examination blueprint and is assessed through realistic, scenario-based questions — not rote recall. Explore the full body of knowledge or the certification roadmap.
Common questions
Is this part of the PCI examinations?
Yes — this is one of the knowledge areas assessed in the PCI examinations. The exam is built around the twelve-competency model, so each competency, including the governed use of AI, is tested as part of an integrated whole rather than in isolation. The emphasis is on applying it with judgement in realistic project scenarios, not on reciting definitions.
Do I need prior expertise?
No prior expertise is needed to get involved or to begin preparing. For certification specifically, the entry requirement is around three years of relevant professional experience in any field rather than a particular qualification — the aim is to keep the credential open to capable people from many backgrounds. What matters is your ability to meet the standard the assessment sets, which you can work towards at your own pace.
How does AI fit in?
AI runs through everything PCI certifies, but always under the principle at the heart of the standard: AI proposes, the professional disposes. AI governance is treated as a competency in its own right, and the responsible use of AI is woven through the other competencies too. The point is not to use AI for its own sake, but to use it well — validating, explaining and owning AI-assisted outputs so that accountability stays with a competent human.
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
Building a schedule worth trusting
A schedule is only as good as its network. Dates are outputs; logic, durations and calendars are the inputs that make them mean something. A useful test before anyone reads dates off it: could a colleague reconstruct why each activity starts when it does from the logic alone? What good looks like:
- Closed network. Every activity except the start and finish milestones has at least one predecessor and one successor. Open ends let slippage pass through silently.
- Constraints as exceptions. Date constraints appear only where a genuine external commitment exists, and each one is documented. A constraint that overrides logic quietly severs the critical path.
- Durations with a basis. Each estimate traces to quantities, production rates or comparable history — not to the date somebody wanted.
- Detail proportional to control. Near-term work is planned at working level; later work sits in planning packages refined by rolling wave, so the schedule stays maintainable as well as complete.
- Honest float. Total float is read as a shared early-warning signal, not padding to be hidden in durations or consumed without discussion.
Statusing without self-deception
Updating is where schedules are won or lost. A disciplined cycle looks like this: fix a single data date for the whole programme; record actual start and finish dates as they happened; then reassess remaining duration for in-progress work by asking what is left to do, rather than back-calculating it from a percent complete. Re-run the network, compare against the baseline, and explain the movement — which paths gained or lost float, and why — before publishing dates to anyone.
Three habits corrupt updates faster than anything else: progress-override settings that let completed logic drag incomplete work forward; out-of-sequence progress left unresolved, so the network no longer reflects the real plan; and nudging percent complete to match the plan rather than the work. Each produces a schedule that agrees with expectations and disagrees with reality. The honest update feeds directly into earned value and forecasting — the same data date, the same progress, one version of the truth.