Logic, lags and leads: the practice

Links are easy to draw, and easy to draw wrong. Four habits from the best-practice article, each shown on a schedule with a fault.

First habit: no open ends. Backfill has no successor, so its thirteen days of float are never tested. Link it to Handover, and the same thirteen days become a real limit: Handover now waits for it.

Second habit: finish-to-start is the default, nine links in ten as a target. The others need a reason. By location, wall two waits for wall one's pour, and the formwork crew idles. Handover: 21 December.

Linking by crew: Wall 2 formwork waits for Wall 1 formwork, not for the pour. By crew, formwork moves wall to wall and rebar follows. Same link type, true sequence: Handover, 8 December.

Third habit: a lag that is really work is an activity. Curing is three days of something happening. Add it with Edit, Add many: one line, Cure 3d. It lands after the selected row.

Make it an activity: Cure, finish-to-start, lag zero. Now it can be seen, updated and reported. Fourth habit: no leads. Mobilise starts five days before procurement ends, with no float: a hidden risk.

Procurement slips two days, to seventeen, and Handover follows: 10 December. A lead promised time nobody had. Split it: order, then deliver; mobilise after the order. Ten days of float, and an honest 11 December.

The longest path runs Order, Deliver, then the formwork, wall to wall. Mobilise has room to spare.

That was the logic audit. Last in the Guide: the whole Scheduler in five minutes.

Taken from the video’s English captions.