Lag is a waiting time added to a dependency: the successor waits that many days after the link would otherwise allow it to start or finish. It models time that passes without work, such as concrete curing or a supplier's lead time.

Lag is written after the link type with a plus sign: 2FS+3 means start three days after task 2 finishes. It can be added to any of the four types.

Lag is not a task, so it uses no resources and has no owner. When the wait is real work someone has to do, model it as a task instead, so it can be tracked.

Worked example

TaskDurationDepends onScheduledTotal float
1. Pour concrete2 daysNoneDays 1 to 20 days
2. Strip formwork1 day1FS+3Day 60 days

Pour concrete finishes on day 2. With 3 days of curing lag, Strip formwork starts on day 6, not day 3.

Open this example in the free delay simulator to change the durations, the links or the delay and watch the schedule move.

Learn more

Related terms

Lead

Lead is negative lag: it lets the successor start before the dependency would otherwise allow, so the two tasks overlap.

Finish-to-start (FS)

A finish-to-start (FS) dependency means the successor cannot start until its predecessor has finished.

Start-to-start (SS)

A start-to-start (SS) dependency means the successor cannot start until its predecessor has started.

See it on your own plan

Depentra calculates every date, link and float in your plan and shows what moves when something slips.