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.Case studiesHow teams use Nodes & Links on live projects.The Physics of Project AccelerationOur book on pulling project dates forward.All resources →Customer stories / Data center
A 47-day slip to explain, across 4,857 changed tasks.
The team used Change Control and Delay Navigator to get to the answer, with every result traceable to the schedule.
Change Control compared every changed task in minutes, not days.
What changed since the last submission
What drove the delay, by reason
The slip explained, and 87 days of recovery found off the critical path.
The same change management analysis, available to every team. Shown here as examples, not part of this story’s results.
Which projects had the biggest critical path changes in their latest submission?
The team used Change Control and Delay Navigator to get to the answer, with every result traceable to the schedule.
Change Control compared every changed task in minutes, not days.
What changed since the last submission
What drove the delay, by reason
The slip explained, and 87 days of recovery found off the critical path.
The same change management analysis, available to every team. Shown here as examples, not part of this story’s results.
Which projects had the biggest critical path changes in their latest submission?
The team used Change Control and Delay Navigator to get to the answer, with every result traceable to the schedule.
Change Control compared every changed task in minutes, not days.
What changed since the last submission
What drove the delay, by reason
The slip explained, and 87 days of recovery found off the critical path.
The same change management analysis, available to every team. Shown here as examples, not part of this story’s results.
Which projects had the biggest critical path changes in their latest submission?
An answer is only useful if it holds up. Nodes & Links records the reasoning and model outputs behind every answer, so the team can see each step, check the math and share a recommendation that’s traceable.
What explains the slip, and where is the time hiding?
Yes. Every story comes from a real customer project. Some are anonymized to protect sensitive programs.
They’re listed under “Under the hood” on this page, with a link to the full use case.
Every project is different, but the same models and AI Mode are available to every customer. Book a demo to see them on projects like yours.
On the Customers page, where you can filter every story by use case.