Features · Time & resources
Time and resource control
Connecting events to the baseline schedule and critical path
Delay becomes dangerous when it isn't seen, or gets lost among events with no real impact. Kolang links the documented event to the project schedule so its effect on the critical path and resources is clear.
The goal isn't to manufacture a number; Kolang separates defensible delay from idle downtime so the construction manager and owner can decide based on evidence.
Live scheduling
Verified events are seen against the baseline schedule and aren't limited to a monthly report.
Separating meaningful delay
Idle downtime is separated from delay that actually shifts the critical path.
Recovering the timeline
Every claim is traceable back to the first message and photo; the case record forms from the moment the event happens.
Linking to financial impact
Once each event's timing and source are clear, its contractual and financial impact is estimated based on jobsite reality.
From event to project impact
-
01
Documented event
A record with time, location, and the responsible party that doesn't rely on anyone's memory weeks later.
-
02
Mapped to the baseline schedule
The event is linked to its related activity or work package in the project schedule.
-
03
Critical-path assessment
It becomes clear whether the delay shifted the critical path or was just noise.
-
04
Output for action
The construction manager and owner see the bottleneck, risk, and basis for contractual action in one summary.