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

Platform Ground truth models Change Control

Schedule change analysis

See every change between schedule updates, and what it did to your critical path.

Change Control compares any two schedule versions activity by activity, shows which changes moved the critical path and flags the edits that shouldn’t have happened.

Book a demo
See the technical detail
DC Echo Change Control
v6 vs. v5
All 1,327
Added 66
Removed 71
Dates 1,190
Duration 360
Relationships 435
Constraints 11
Corruption 39
NAME
SCOPE
STATUS CHANGE
C.U.2006
Install switchgear, week 05 shutdown
Added
Not started
C.U.3278
Pull HV cables, south feed
Changed
Not started
C.U.3298
Pull HV cables, north feed
Changed
Not started
→
In progress
C.U.1044
Penetrations to ceiling, switch room
Changed
Not started
→
Done
C.G.1042
Temporary propping, entrance roof
Removed
Not started

Why teams choose it

Three reasons it earns its place.

01

Every change, sorted for you.

Added and removed activities, dates, durations, relationships, calendars and constraints, each in its own filter with a live count.

Eight change types
02

Know what moved the finish.

Scope the comparison to the critical path or a targeted path, and see before and after side by side on the Gantt.

Critical and targeted paths
03

Red flags, caught on submission.

The corruption filter surfaces changed actual dates, progress going backwards and work marked done in the future.

Corruption filter

Technical specification

Built for schedule reviewers and claims teams.

Compare
Any version with an earlier data date, typically the baseline or the previous update
Scope
Full schedule, critical path, or a targeted path to any activity with an optional pass-through
Change types
Added, removed, dates, duration, relationships, calendars, constraints and corruption
Overview
Completion date shift, progress, performance index, critical path activity count and float
Grouping and filters
Group by WBS, or filter to one contractor’s activity code
History
Change volume by type and project slip across every version, with a total delta per activity
Drill-down
Field-by-field before and after for any activity, with a link into Delay Navigator
Export
PNG, PDF and CSV, plus Change History to Excel

Overview

The headline before the detail.

Open Change Control and the net change in completion date, progress, critical path size and float is right at the top, against whichever version you compare.

  • Completion date shift
  • Critical path float
  • Progress
Completion date
+2m 25d
vs. comparison schedule
Progress
53% vs 70%
vs. comparison schedule
Critical path activities
+61
vs. comparison schedule
Critical path float
−85
vs. comparison schedule

History

See whether a schedule is being managed or manipulated.

Change History stacks every change type across every submission, with the project slip line on top, so you can see exactly when the logic started to drift.

  • Every version
  • By change type
  • Project slip trend
6,0004,0002,0000+150d+100d+50d0DC Echo v2vs v1DC Echo v3vs v2DC Echo v4vs v3DC Echo v5vs v4DC Echo v6vs v5+106d slip

Data integrity

Catch the edits that shouldn’t happen.

Three kinds of suspicious change are flagged automatically, and each opens a side-by-side view of the before and after values.

  • Modified actuals
  • Regressing progress
  • Future actuals
Modified actual dates
An activity’s recorded actual dates changed in a later submission.
Progress going backwards
Percent complete dropped, for example from 80% to 30%.
Future actuals
Work marked complete on a date that hasn’t happened yet.

Put it to work

Change management use case
Disputes and claims use case
Data center submission story

FAQ

Questions, answered.

Technical questions about Change Control.

Talk to our team

Any version whose data date comes before the schedule you’re viewing, typically the baseline or the previous update.

Added and removed activities, dates, durations, relationships, calendars and constraints, plus a corruption filter for suspicious edits.

Modified actual dates, percent complete going backwards and activities marked complete on dates that haven’t happened yet.

Yes. Scope the comparison to the critical path, or to a targeted path into any milestone, with an optional pass-through activity.