WEBVTT

00:00:00.900 --> 00:00:05.377
Two schedule terms help you focus attention: critical path and float.

00:00:05.638 --> 00:00:09.740
We'll start with a simple example, then read a real comparison screen.

00:00:10.013 --> 00:00:13.765
The goal is to ask better questions about the work driving completion.

00:00:14.988 --> 00:00:20.402
In this simple schedule, foundation takes five working days, structure takes three, and

00:00:20.402 --> 00:00:21.752
inspection takes two.

00:00:22.012 --> 00:00:24.252
Each waits for the previous activity.

00:00:24.525 --> 00:00:28.602
That connected sequence takes ten working days and drives the finish.

00:00:28.875 --> 00:00:31.215
It is the critical path in this example.

00:00:32.428 --> 00:00:36.868
Total float describes how far an activity can move before it affects the relevant

00:00:36.868 --> 00:00:40.530
scheduled finish, under the schedule's logic and constraints.

00:00:40.790 --> 00:00:44.968
Imagine landscaping finishes two working days before it must be ready.

00:00:45.228 --> 00:00:49.005
In this simple example, that leaves two working days of float.

00:00:50.228 --> 00:00:52.405
Real schedules are more complex.

00:00:52.678 --> 00:00:57.505
Calendars, date constraints, and critical activity settings affect the results.

00:00:57.778 --> 00:01:01.355
Ask the scheduler to confirm the sequence driving completion.

00:01:01.628 --> 00:01:05.205
A critical flag by itself is not a complete explanation.

00:01:06.452 --> 00:01:11.592
Here, marine foundation works is now marked critical, and its float delta is minus

00:01:11.592 --> 00:01:12.418
four days.

00:01:12.690 --> 00:01:14.155
Delta means difference.

00:01:14.415 --> 00:01:16.505
Its float decreased by four days.

00:01:16.765 --> 00:01:20.755
That value alone does not tell you its current total float or the cause

00:01:20.755 --> 00:01:21.542
of the change.

00:01:22.760 --> 00:01:27.725
When an activity becomes critical, ask what changed in its dates, duration, or

00:01:27.725 --> 00:01:28.550
connections.

00:01:28.822 --> 00:01:31.700
Then confirm how it affects the finish milestone.

00:01:31.960 --> 00:01:35.612
You now have the language to make that conversation more precise.