STO·SPR · Schedule Performance Review
Your baseline made a promise. The as-built, the gate log, the change orders, and the daily reports recorded what happened. STO·SPR joins them all, measures the event against the commitment, and tests every explanation for why against your own records, so your closeout is evidence, not memory, and your next turnaround starts ahead.
The post-mortem, computed, not recalled.
The problem
Most closeouts are a room full of memory and a binder that gets filed. Yet the reason the date moved is already written down, scattered across records nobody joins up: the schedule, the gate log, the change-order log, the daily reports. Until the explanations are tested against those records, the closeout is a story, and the same misses return.
What people remember and what the schedule records are rarely the same thing.
Without a measured cause, the fix is a slogan, and the slip comes back.
Leadership asks what happened, and the answer is a story, not a number.
What it measures
STO·SPR task-matches the frozen baseline to the completed schedule, then measures the event at every level. Every figure is computed by the engine; the written account is validated against it, never the other way around.
Where the days were won and lost, from the whole event down to the single unit and the clearing, maintenance, and startup windows.
What actually governed execution, how much of the planned path survived, and what entered and left it.
The completed schedule’s earned hours against the gate-log actuals, by craft, so productivity is measured, not guessed.
Where the days went
Productivity by craft
Earned hours over gate-log actuals, execution window. Reported only where the gate log covers enough of the hours to be meaningful.
Why it slipped
The engine raises thirteen candidate explanations deterministically from the measurements themselves, scope growth, late adds, productivity, undermanning, a critical-path shift, discovered work, external events among them. Each hypothesis is then tested against the change-order log and the daily reports, and returns a verdict, supported, partially supported, unsupported, or insufficient evidence, with a stated confidence. What could not be established is said plainly, so you know exactly which answers deserve action.
The records we pull in
| Baseline + as-built | Task-matched, so variance and the critical path are read against the frozen promise. |
| Gate log | Labor actuals in whatever format the site keeps, normalized to craft for earned-over-actual productivity. |
| Change-order log | Parsed to structured rows: dates, reasons, magnitudes. Corroborates where the added hours came from. |
| Daily reports | Indexed and searchable, so every hypothesis is tested against the field record. |
| Cost report | Client-supplied, read as indicative context, never treated as ground truth. |
The verdicts that come back
Did the plan predict reality
We score the baseline’s own quality against the outcome it produced. Each risk the plan carried is paired with what actually happened, and classified, so the readiness review that came before is held to account and the next one gets sharper.
Critical path · plan vs as-built
Flagged, then what happened
| Flagged in the baseline | What actually happened |
|---|---|
| Readiness: Conditional | Missed the committed date by 20 days Materialized |
| C2 unexplained float (Severe) | 53% of matched activities finished late Materialized |
| C3 path reach (Material) | 0% of the planned critical path survived Materialized |
| Materials on-site risk | Mitigated, delivered to need date Held |
| Not flagged | PSSR drove 25% of the startup slip Emerged unflagged |
What you get
The report ranks the credible causes by confidence and states what could not be established. The deliverable is a register of specific, owned actions in two tiers, next-event and systemic, each tied to a tested cause. It closes the assurance loop into the next event’s premise, and the coded outcomes build your benchmark over time.
Every number is computed by the engine behind a hard wall: the model weighs the evidence and writes the account, is validated against the figures, and never invents one. Any cost you supply is reported as indicative, never treated as ground truth.
STO·SPR runs as a standalone review, or as the performance engine inside a STOAR4 closeout, where it opens the lessons workshop on measured facts.
What changes
Send us the baseline, the as-built, and the records you already keep. We will show you where the time went, why it went there, and how much confidence each answer deserves.