Home/Resources/Infographic
Infographic2 min

Anatomy of an 11-day slip.

One late approval is rarely just one late approval. Here's how a single 9-day design-review delay cascades into an 11-day miss on the finish date — and the moment AI catches it.

Owner-caused Knock-on Critical path Result
0
Day
Owner-caused · EC1030

Design review & approval starts.

A routine approval enters the workflow. On the baseline it takes 5 days. Nothing looks wrong yet.

+9
Days
+9dOwner-caused · EC1030

Approval slips by nine days.

Comments cycle twice. The activity finishes 9 days late — captured and timestamped the day it happens.

Cascade
blockedKnock-on · EC1160

Heat-pump procurement can't start.

Procurement is logically tied to the approval. It can't begin until the design is signed off, so the 9-day slip flows straight downstream.

0
Float
0 floatCritical path

Total float erodes to zero.

The procurement chain was near-critical. With its buffer gone, it becomes the longest path — now every day of slip moves the finish 1:1.

Result
Forecast finish
+11 days
A 9-day approval slip became an 11-day finish-date miss once float ran out.
0.94SPI
82.7Health
OwnerAttribution
Where OPTEAM catches it

The slip is flagged at +9 days — not at the result. OPTEAM recomputes the critical path on the update, attributes the delay to the owner, and drafts the notice-of-delay before the cascade reaches the finish date.

Catch the slip at day nine, not day ninety.

Connect your P6 file and let OPTEAM flag drift the moment it happens.

Keep reading

Related reads