PPI Home / Our Approach / Schedule Readiness Review

Our Approach · Scheduling and Readiness

Is this schedule ready to execute?

The Schedule Readiness Review checks your turnaround schedule against PPI turnaround doctrine at each development cycle, so the schedule your team baselines is one the field can execute and leadership can trust.

Request a pilot review Take the free 24-question self-assessment

Not sure this is the right starting point? See all three free assessments.

Schedule problems are created before execution, and found during it

Execution rarely rescues a weak schedule. It exposes it. Broken logic, hard dates fighting the network, long activities nobody can measure, and project settings that quietly change every float value all sit in the schedule for months before the event starts. They surface on day three of execution, when the cost of fixing them is highest.

Schedule quality is bounded by the quality of what goes into it: Gold In → Gold Out. The Schedule Readiness Review is the checkpoint at the scheduling stage, before the schedule becomes the baseline every contractor, supervisor and executive works against.

Turnaround Excellence Framework lifecycle with the Schedule Readiness Review at the Scheduling and Readiness phases StrategyPremiseScopePlanning ExecutionCloseout &learning SchedulingReadiness Schedule Readiness Review one review per development cycle baseline candidate in-event control (Critical Mass Control)
The review runs through the Scheduling and Readiness phases of the Turnaround Excellence Framework (TEF), one pass per schedule development cycle, until the schedule is a baseline candidate.

What we review

Each cycle, a PPI scheduler runs your Primavera P6 export through PPI's Schedule Review Engine and works the findings with your team. The engine screens; the scheduler judges.

Structural health

A turnaround screen informed by DCMA 14, with thresholds tightened or replaced where the generic defaults do not fit a short, intense event.

Plan health and standards

Activity durations against shift length and progress method, constraints, calendars, levelling settings and project options, checked against PPI's schedule development standards.

Forecast readiness

Whether the schedule carries what in-event forecasting will need: a defined execution window, an event finish milestone and a bulk-scope target.

Review engine summary for an anonymized 2024 refinery turnaround: 6,995 activities, 13,067 relationships, and three screens showing pass, review and fail counts
One review cycle on an anonymized 2024 refinery turnaround: 6,995 activities and 13,067 relationships, screened in one pass.
Why a generic check is not enough. On the same schedule, the published DCMA 14 default for missing logic (5% or less of incomplete activities) would score it a Pass: 17 of 6,790, or 0.25%. The turnaround standard allows no unexplained open ends, so the review flags 15 activities for the scheduler to fix or justify. In a 35-day event, each one is a place where the schedule can stop telling the truth.
Structural-health screen row showing 15 unexplained open ends: a Fail against the PPI threshold, a Pass against the DCMA default
Each finding shows the result, the PPI threshold, what the generic DCMA default would have said, and a drill-down to the activities involved.

How a review cycle runs

The review fits the rhythm your schedulers already work in. P6 on one screen, the review on the other.

  1. ExportYour scheduler exports the working schedule from P6.
  2. ScreenThe engine screens it; we read the failures first.
  3. DecideEach finding is fixed in P6 or accepted with a written rationale.
  4. RecordOwners, due dates and accepted deviations go in one report.
  5. RepeatSame thresholds every cycle, until the schedule is a baseline candidate.

The baseline decision stays with your lead scheduler and turnaround manager. A clean screen is a prompt for judgment, not an acceptance certificate.

What you get

Findings reportEvery finding with its rationale, owner, due date and status, plus the deviations your team accepted and why.
Baseline candidate decisionA clear view of what stands between the current schedule and a baseline your team can defend at the readiness gate.
Capability in your teamYour schedulers work the findings alongside a PPI scheduler and learn the reasoning behind each threshold. The aim is that the next event needs less of us.
Your data stays with youThe schedule file is read in the browser during the review session. It is not uploaded to or stored on a PPI server.

Start with a schedule you already know

Send us the P6 schedule from a past turnaround. We will run a review cycle and walk your team through what it finds, then compare it with what actually happened in the field. That comparison is the fastest way to judge whether this approach is worth applying to your next event.

Request a pilot review