WEBVTT 00:00:00.900 --> 00:00:06.540 Schedule reports become easier to read when three terms are clear: baseline, forecast, 00:00:06.650 --> 00:00:07.440 and data date. 00:00:07.700 --> 00:00:12.303 They describe the agreed plan, the current expectation, and the point through which 00:00:12.303 --> 00:00:13.965 progress has been recorded. 00:00:15.188 --> 00:00:19.452 A baseline is a saved reference schedule used to measure performance. 00:00:19.750 --> 00:00:24.502 For reporting against the agreed plan, confirm which baseline your project has approved. 00:00:24.737 --> 00:00:28.490 A new monthly update does not automatically replace that reference. 00:00:29.720 --> 00:00:34.585 The forecast is the current expected finish, informed by progress and the remaining 00:00:34.585 --> 00:00:34.973 work. 00:00:35.232 --> 00:00:40.398 In this teaching example, an agreed November twentieth finish is now forecast for 00:00:40.398 --> 00:00:41.560 November twenty seventh. 00:00:41.832 --> 00:00:43.672 That is seven calendar days later. 00:00:44.880 --> 00:00:48.958 The data date marks the progress cutoff used to schedule the remaining work. 00:00:49.218 --> 00:00:52.532 August thirty first tells you the update's status point. 00:00:52.793 --> 00:00:57.070 It is separate from the day someone uploaded the file or reviewed the report. 00:00:58.280 --> 00:01:03.732 Back in Kairos, the selectors show July and August updates with their data dates. 00:01:03.992 --> 00:01:06.982 This comparison measures change between updates. 00:01:07.230 --> 00:01:12.145 To discuss baseline variance, first confirm that the reference version is the approved 00:01:12.145 --> 00:01:12.745 baseline. 00:01:13.948 --> 00:01:17.000 Try explaining your next report in three sentences. 00:01:17.272 --> 00:01:18.600 This is the reference plan. 00:01:18.872 --> 00:01:20.962 This is the current expected finish. 00:01:21.222 --> 00:01:22.762 This is the progress cutoff. 00:01:23.022 --> 00:01:25.850 Clear dates make a clearer management conversation.