Skip to content
Documentation

FloatGuard, in order.

Watch the schedule for the delay that is already happening.

FloatGuard

Watch the schedule for the delay that is already happening. Included from Pro upwards.

1. Import the schedule

The programme as it stands, with its logic and its float.

2. Watch what is eating float

Which paths are tightening, which activities have lost their slack, and what that costs in days.

3. Record the event

A delay recorded when it happens, with its evidence, is an extension-of-time submission later. One reconstructed afterwards is an argument.

What it will not do

  • It reads the schedule, not the site. An activity marked complete is treated as complete.
  • A time impact analysis here is a working document, not a claim.

On a paid plan every program opens a sample set, so none of this has to be read before trying it. A free trial starts blank, on your own drawings. See the sample project.