WEBVTT

00:00:00.775 --> 00:00:04.575
A week slipped on Harbor Renewal, and the first argument is not about

00:00:04.575 --> 00:00:05.450
the week.

00:00:05.450 --> 00:00:09.500
It is about what moved: the forecast, or the agreement itself?

00:00:09.500 --> 00:00:13.075
They are different things, and mixing them up is how disputes start.

00:00:14.135 --> 00:00:17.085
The baseline is the reference the owner accepted.

00:00:17.085 --> 00:00:19.873
The forecast is what the team now expects.

00:00:19.873 --> 00:00:24.110
Keep both in view, and every variance has a meaning: seven days later

00:00:24.110 --> 00:00:25.260
than agreed.

00:00:26.295 --> 00:00:27.970
Then look behind the date.

00:00:27.970 --> 00:00:31.595
The marine foundation works grew by a week and the chain behind them

00:00:31.595 --> 00:00:32.595
followed.

00:00:32.595 --> 00:00:35.883
A later finish is the start of a question, not the answer to

00:00:35.883 --> 00:00:36.570
it.

00:00:37.615 --> 00:00:40.552
Kairos tracks the baseline as its own record.

00:00:40.552 --> 00:00:45.490
Harbor Renewal's latest baseline revision, revision two, is at revise and

00:00:45.490 --> 00:00:48.990
resubmit, last submitted on the fourth of September.

00:00:48.990 --> 00:00:53.440
Until it is accepted, the reference everyone compares against stays the version

00:00:53.440 --> 00:00:56.715
the owner accepted: the twentieth of November.

00:00:57.775 --> 00:01:01.163
Sometimes the team does propose a new reference plan.

00:01:01.163 --> 00:01:05.425
That is a decision to record: the proposal, the version, the date it

00:01:05.425 --> 00:01:09.600
takes effect and who approved it, through the project's own process.

00:01:10.655 --> 00:01:14.892
Bring both dates to the next review, explain what moved, and check whether

00:01:14.892 --> 00:01:18.155
anyone actually authorized a change to the reference.

00:01:18.155 --> 00:01:19.117
Know sooner.

00:01:19.117 --> 00:01:20.430
Act faster.