Use cases
By organization
Featured stories
Latest from the blog
AI with full project context: Connect Nodes & Links with AconexNovember 5, 2026All blog posts →Featured guide
GuideThe Executive Guide to AI for Project DeliveryTest date confidence, understand project risk and focus interventions, with auditable evidence.Read the guide →All guides →Watch, read and learn
WebinarsLive sessions and on-demand replays.WhitepapersLong reads on where project delivery is going.ResearchThe peer-reviewed work behind the models.Platform coursesShort videos on getting more from the platform.The Physics of Project AccelerationOur book on pulling project dates forward.All resources →Use cases / Delay recovery
Find the root cause, rank your options and see days gained against cost.
Same ground truth models underneath. Flip between the answer and the Delay Navigator view behind it.
Handover is 385 days late. Two added activities, the entrance structure and client review F003, drive almost half of it.
Click any bar to inspect it.
Click any bar to inspect it.
Click any bar to inspect it.
The added activity of C.B.1034 caused 100 days of delay to H.B.1002, which is 27% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2470 caused 74 days of delay to H.B.1002, which is 20% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3520 caused 48 days of delay to H.B.1002, which is 13% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2390 caused 44 days of delay to H.B.1002, which is 12% of the total delay.
Click any bar to inspect it.
The start slip of C.B.1002 caused 26 days of delay to H.B.1002, which is 7% of the total delay.
Click any bar to inspect it.
The start slip of P.B.1012 caused 22 days of delay to H.B.1002, which is 6% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3020 caused 15 days of delay to H.B.1002, which is 4% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3470 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The relationship changes of C.B.1000 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The duration increase of C.B.1001 caused 7 days of delay to H.B.1002, which is 2% of the total delay.
Click any bar to inspect it.
The relationship changes of E.G.1670 caused 4 days of delay to H.B.1002, which is 1% of the total delay.
Click any bar to inspect it.
Click any bar to inspect it.
Click any bar to inspect it.
The added activity of C.B.1034 caused 100 days of delay to H.B.1002, which is 27% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2470 caused 74 days of delay to H.B.1002, which is 20% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3520 caused 48 days of delay to H.B.1002, which is 13% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2390 caused 44 days of delay to H.B.1002, which is 12% of the total delay.
Click any bar to inspect it.
The start slip of C.B.1002 caused 26 days of delay to H.B.1002, which is 7% of the total delay.
Click any bar to inspect it.
The start slip of P.B.1012 caused 22 days of delay to H.B.1002, which is 6% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3020 caused 15 days of delay to H.B.1002, which is 4% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3470 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The relationship changes of C.B.1000 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The duration increase of C.B.1001 caused 7 days of delay to H.B.1002, which is 2% of the total delay.
Click any bar to inspect it.
The relationship changes of E.G.1670 caused 4 days of delay to H.B.1002, which is 1% of the total delay.
Same ground truth models underneath. Flip between the answer and the Delay Navigator view behind it.
Handover is 385 days late. Two added activities, the entrance structure and client review F003, drive almost half of it.
Click any bar to inspect it.
Click any bar to inspect it.
Click any bar to inspect it.
The added activity of C.B.1034 caused 100 days of delay to H.B.1002, which is 27% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2470 caused 74 days of delay to H.B.1002, which is 20% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3520 caused 48 days of delay to H.B.1002, which is 13% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2390 caused 44 days of delay to H.B.1002, which is 12% of the total delay.
Click any bar to inspect it.
The start slip of C.B.1002 caused 26 days of delay to H.B.1002, which is 7% of the total delay.
Click any bar to inspect it.
The start slip of P.B.1012 caused 22 days of delay to H.B.1002, which is 6% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3020 caused 15 days of delay to H.B.1002, which is 4% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3470 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The relationship changes of C.B.1000 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The duration increase of C.B.1001 caused 7 days of delay to H.B.1002, which is 2% of the total delay.
Click any bar to inspect it.
The relationship changes of E.G.1670 caused 4 days of delay to H.B.1002, which is 1% of the total delay.
Click any bar to inspect it.
Click any bar to inspect it.
Click any bar to inspect it.
The added activity of C.B.1034 caused 100 days of delay to H.B.1002, which is 27% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2470 caused 74 days of delay to H.B.1002, which is 20% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3520 caused 48 days of delay to H.B.1002, which is 13% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2390 caused 44 days of delay to H.B.1002, which is 12% of the total delay.
Click any bar to inspect it.
The start slip of C.B.1002 caused 26 days of delay to H.B.1002, which is 7% of the total delay.
Click any bar to inspect it.
The start slip of P.B.1012 caused 22 days of delay to H.B.1002, which is 6% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3020 caused 15 days of delay to H.B.1002, which is 4% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3470 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The relationship changes of C.B.1000 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The duration increase of C.B.1001 caused 7 days of delay to H.B.1002, which is 2% of the total delay.
Click any bar to inspect it.
The relationship changes of E.G.1670 caused 4 days of delay to H.B.1002, which is 1% of the total delay.
Same ground truth models underneath. Flip between the answer and the Delay Navigator view behind it.
Handover is 385 days late. Two added activities, the entrance structure and client review F003, drive almost half of it.
Click any bar to inspect it.
Click any bar to inspect it.
Click any bar to inspect it.
The added activity of C.B.1034 caused 100 days of delay to H.B.1002, which is 27% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2470 caused 74 days of delay to H.B.1002, which is 20% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3520 caused 48 days of delay to H.B.1002, which is 13% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2390 caused 44 days of delay to H.B.1002, which is 12% of the total delay.
Click any bar to inspect it.
The start slip of C.B.1002 caused 26 days of delay to H.B.1002, which is 7% of the total delay.
Click any bar to inspect it.
The start slip of P.B.1012 caused 22 days of delay to H.B.1002, which is 6% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3020 caused 15 days of delay to H.B.1002, which is 4% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3470 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The relationship changes of C.B.1000 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The duration increase of C.B.1001 caused 7 days of delay to H.B.1002, which is 2% of the total delay.
Click any bar to inspect it.
The relationship changes of E.G.1670 caused 4 days of delay to H.B.1002, which is 1% of the total delay.
Click any bar to inspect it.
Click any bar to inspect it.
Click any bar to inspect it.
The added activity of C.B.1034 caused 100 days of delay to H.B.1002, which is 27% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2470 caused 74 days of delay to H.B.1002, which is 20% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3520 caused 48 days of delay to H.B.1002, which is 13% of the total delay.
Click any bar to inspect it.
The added activity of E.G.2390 caused 44 days of delay to H.B.1002, which is 12% of the total delay.
Click any bar to inspect it.
The start slip of C.B.1002 caused 26 days of delay to H.B.1002, which is 7% of the total delay.
Click any bar to inspect it.
The start slip of P.B.1012 caused 22 days of delay to H.B.1002, which is 6% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3020 caused 15 days of delay to H.B.1002, which is 4% of the total delay.
Click any bar to inspect it.
The added activity of E.G.3470 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The relationship changes of C.B.1000 caused 11 days of delay to H.B.1002, which is 3% of the total delay.
Click any bar to inspect it.
The duration increase of C.B.1001 caused 7 days of delay to H.B.1002, which is 2% of the total delay.
Click any bar to inspect it.
The relationship changes of E.G.1670 caused 4 days of delay to H.B.1002, which is 1% of the total delay.
Asked in AI Mode
When a delay hits, know your options fast. AI Mode tests recovery scenarios against your live schedule and tells you how many days each one wins back.
Real customer projects, anonymized
“If steel erection slips 2 months, how do we still finish on time? A 6-day week is an option for some trades.”
CCompressing downstream work recovers up to 28 days. Adding a 6-day week on steel trades recovers 15 to 17 more, closing almost all of the 51-day gap.
Why it mattered. The team knew it needed both levers, and to start the completion date conversation early rather than wait.
“If steel erection slips 2 months, how do we still finish on time? A 6-day week is an option for some trades.”
CCompressing downstream work recovers up to 28 days. Adding a 6-day week on steel trades recovers 15 to 17 more, closing almost all of the 51-day gap.
Why it mattered. The team knew it needed both levers, and to start the completion date conversation early rather than wait.
“What slipped since the last update, and what does it do to the end date?”
O50 activities had slipped by exactly 7 days each, all traced to one upstream drainage work package. Winning back 7 days there restores the previous end date.
Why it mattered. Recovery could focus on one work package instead of chasing 50 activities.
“Piping slipped due to manufacturing issues. Find every chance to recover before the final walkdown.”
P21 to 56 days of recovery were available, from running test prep alongside piping to double shifts on two critical installs.
Why it mattered. A three-step plan: start with 21 low-risk days, step up to 35, and hold the full 56 in reserve.
Open any answer in Platform Mode and check the math yourself. How it works
“Our plan is to mandate the use of Nodes & Links on ALL projects in the near future.”
Delay Navigator walks back from the late activity, re-running the schedule with baseline logic to isolate what each change caused.
Yes. Every contribution is tagged by reason: start slip, duration increase, relationship changes or added activity.
Yes. AI Mode tests recovery scenarios against your live schedule and tells you how many days each one wins back.
No. Your original schedule is never modified. Optimized schedules come back as a new XER file.