WEBVTT

00:00:00.800 --> 00:00:04.162
October, and Harbor Renewal shows no new warning.

00:00:04.162 --> 00:00:05.213
Good news?

00:00:05.213 --> 00:00:07.463
Only if the information is current.

00:00:07.463 --> 00:00:11.387
The ninth update has not arrived, and a dashboard cannot flag what it

00:00:11.387 --> 00:00:12.925
has not been told.

00:00:13.950 --> 00:00:16.938
The last data date is the thirty first of August.

00:00:16.938 --> 00:00:21.325
Everything since then is unknown, however calm the summary looks.

00:00:21.325 --> 00:00:23.675
The empty period is still empty.

00:00:24.735 --> 00:00:26.922
Kairos makes the gap visible.

00:00:26.922 --> 00:00:31.698
The worklist lists Harbor Renewal's update number nine as not submitted, its

00:00:31.698 --> 00:00:36.235
planned submission date, and the reason recorded against it: awaiting site

00:00:36.235 --> 00:00:37.710
progress records.

00:00:38.710 --> 00:00:43.110
On the executive one pager the same gap appears in the count: twenty

00:00:43.110 --> 00:00:47.635
one of twenty four monthly updates received, so the board sees the uncertainty

00:00:47.635 --> 00:00:49.360
instead of a clean page.

00:00:50.415 --> 00:00:52.490
A reason is worth recording.

00:00:52.490 --> 00:00:55.890
It is not a replacement for the update, and the gap stays open

00:00:55.890 --> 00:00:57.640
until the file arrives.

00:00:58.695 --> 00:01:03.120
The useful question for every summary is simple: current as of when?

00:01:03.120 --> 00:01:06.695
Put that date on the slide, and the quiet becomes honest.

00:01:07.760 --> 00:01:11.435
Missing information, named and dated, is a risk you can manage.

00:01:11.435 --> 00:01:12.347
Know sooner.

00:01:12.347 --> 00:01:13.660
Act faster.
