How it works
ChangeSpan is built around closed-loop project controls. The schedule is not a picture—it’s a model that drives results, forecast, impacts, and explainability.
Closed-loop model
1) Schedule logic
Activities, ties, constraints
→
2) Results
Dates, float, critical path
→
3) Controls + forecast
Work packages + curves
4) Impacts + scenarios
Compare changes safely
→
5) Explainability
“Why did it change?” tied to events, assumptions, and logic.
Explainability is a feature, not a promise
When dates or costs move, ChangeSpan is designed to show the chain of reasoning: what changed, where it propagated, and what assumptions were used.
Visual placeholder: “Why did it change?” panel
Scenario compare keeps baselines safe
Run alternatives without corrupting the baseline. Compare outcomes side-by-side and keep review workflows clean.
Visual placeholder: Baseline vs Scenario compare