A recovery plan needs a reason to work

See the review behind the recommendation.

Follow an update from the reported movement to the review finding and next action.

30 minutes · Demonstration data · No project upload required

Build your internal business case

0:00 / A week earlier. What changes on site?

The contractor proposes to recover the week: back from the twenty seventh of November to the twentieth. Good news, if it is real. The useful question is what will change on site to make that date possible.

0:13 / Follow the work that drives the finish.

Start on the critical path. Finishing the temporary access works early does nothing for the reopening. Recovering a week means recovering it on the marine foundation works or the pier structure, where the finish is actually decided.

0:28 / Make the change concrete.

Make the change concrete. A second crew on the piles? A different sequence for the deck segments? Each option carries assumptions about access, calendars and dependencies that the team must be able to explain and test.

0:43 / Review the proposal like any other submission.

In Kairos a recovery schedule is reviewed like any other submission: imported, compared with the current plan, tested for quality, and recorded in OnPoint. The record here is the monthly review, with the same fields: which meetings were held, the recommendation, the letter issued.

1:01 / The next update is the test.

A credible plan names who will do what by when, and says what the next update should show. If the thirtieth of September update does not show the piles ahead of plan, the recovery is a hope.

1:14 / An earlier date is the goal. The work makes it credible.

An earlier date is the goal. The work, recorded and tested update by update, is what makes it credible. Know sooner. Act faster.