New: Document Integrations with Aconex and Procore are live. See what your AI can read now

Use cases / Change management

Change management

What changed since the last update, and how did it affect my critical path?

Every change since the last update, and what it did to your critical path.

Book a demo
See the proof
AI ModeDC EchoAuditable
What changed since the last update, and how did it affect my critical path?
Routed throughChange ControlChange HistoryCritical path
  • Activities added, removed and re-sequenced
  • Float consumed off the critical path
  • The new driving path
Changes since the last update traced to the new driving path. Planning lead alerted.

Ask the AI. Or check the math yourself.

Same ground truth models underneath. Flip between the answer and the Change Control view behind it.

DC Echo Latest scheduleAI Mode
What changed since the last update, and how did it affect my critical path?

373 of the 1,327 changes since v5 touch the critical path. Logic changes on switchgear and HV cable pulls are the ones moving it.

  • Changes since v51,327
  • On the critical path373
  • Relationship changes on it165
Change ControlChange HistoryCritical path
Evidence trail attached

Asked in AI Mode

Real questions. Real answers.

See exactly what changed between updates, and why. AI Mode separates new scope from schedule drift, so every change is visible and accounted for.

Real customer projects, anonymized

AI ModeData centerAuditable

“Final commissioning slipped 6 months between submissions. What drove it, and was any of it change?”

What AI Mode found3 of 6 drivers

At least 3 of the 6 drivers came from change, including a structural instruction across 4 data halls and 70 added fire detection units. Commissioning durations barely moved; the work simply could not start.

Why it mattered. The consultant could separate change-driven delay from performance, with the evidence chain to back it up.

From your data to a decision you can defend.

01 · Your data
  • Schedule versions
  • Change orders
  • RFIs
02 · Ground truth models
  • Change Control
  • Change History
  • Critical path
03 · Evidence trail
  • Activities added, removed and re-sequenced
  • Float consumed off the critical path
  • The new driving path

Open any answer in Platform Mode and check the math yourself. How it works

Decisions that paid off.

All customer stories
Turner & Townsend · hyperscale data center
232 hrs
saved every month
Read the story
Data center
87 days
of recovery found off the critical path
Read the story
Data centers · Owner
+114 days
caught before the submission was accepted
Read the story
“Being able to identify these critical changes efficiently would enable planners to have more time to work with the client and the contractor on mitigating these challenges and enhance project outcomes.”
Lindsay MacKay, Associate Director, Turner & Townsend

More decisions it answers

Quality and compliance
Progress verification
Risk and forecasting
Delay recovery
Acceleration
Disputes and claims

FAQ

Questions, answered.

Questions about change management.

Talk to our team

Added and removed activities, plus every change to dates, durations, relationships, calendars and constraints between schedule versions.

Yes. You can see exactly which changes impacted the critical path, and how.

Yes. Follow the full history of changes and trends across every schedule version, from baseline to finish.

Yes. It flags changed actual dates, progress going backwards and work marked done in the future.