WEBVTT 00:00:00.775 --> 00:00:05.612 Harbor Renewal's August update has every date filled in: thirty six activities, 00:00:05.612 --> 00:00:07.650 neat rows, nothing blank. 00:00:07.650 --> 00:00:09.475 It still may not connect. 00:00:10.535 --> 00:00:14.810 Take the inspection: it can only happen after the marine works are built. 00:00:14.810 --> 00:00:18.373 If that link is missing, the dates look fine and the plan is 00:00:18.373 --> 00:00:19.248 wrong. 00:00:19.248 --> 00:00:21.985 A missing link does not look like anything. 00:00:21.985 --> 00:00:26.510 Nothing forces inspection to wait for construction, so the plan cannot warn you 00:00:26.510 --> 00:00:28.260 when the foundations slip. 00:00:29.270 --> 00:00:34.070 A quality check looks for conditions like that: open ends with no predecessor 00:00:34.070 --> 00:00:38.895 or successor, durations too long to control, constraints that pin a date 00:00:38.895 --> 00:00:40.445 regardless of the work. 00:00:41.495 --> 00:00:43.758 Kairos tests every update. 00:00:43.758 --> 00:00:49.045 August scores ninety one point seven: eleven of twelve checks pass, and logic 00:00:49.045 --> 00:00:53.495 fails, with eight percent of incomplete activities missing a link against a target 00:00:53.495 --> 00:00:54.670 of five. 00:00:54.670 --> 00:00:59.070 Two of twenty five incomplete activities, counted beside the target. 00:01:00.160 --> 00:01:04.060 Read each finding beside its target and ask the scheduler about the work 00:01:04.060 --> 00:01:05.172 behind it. 00:01:05.172 --> 00:01:07.835 A good score does not certify a plan. 00:01:07.835 --> 00:01:11.998 The answer either fixes the plan or explains it, and both belong in 00:01:11.998 --> 00:01:13.360 the review record. 00:01:14.390 --> 00:01:17.890 A quality check tells you where to look first, and Kairos tests each 00:01:17.890 --> 00:01:22.190 update as it arrives, so the list is there before the review starts. 00:01:22.190 --> 00:01:23.153 Know sooner. 00:01:23.153 --> 00:01:24.465 Act faster.