On this page
A lag adds waiting time to a relationship. A lead is negative lag: it permits the successor’s relevant event to occur earlier than the predecessor’s driving event would otherwise allow. Neither tells the reviewer why the time is there.
That missing explanation matters. A five-day curing requirement, a five-day approval wait and five days inserted to make bars line up can look similar in a relationship column while representing very different project conditions.
- 01Inspect the fileDates, logic, calendars
- 02Read the contractEdition, clause, exceptions
- 03Check the fieldSequence, access, resources
- 04Record the decisionOwner, evidence, next action
Read the complete relationship
Record the predecessor, successor, relationship type, sign, magnitude, unit and governing calendar. Finish-to-start and start-to-start links do not measure from the same event. A lag stated in working time is not automatically the same elapsed period as a calendar-day wait.
P6 offers different calendar choices for scheduling relationship lag; Oracle describes them in the schedule settings reference. Preserve that choice when comparing two runs.
A fictional waiting-period example
An inspection finishes Friday at the end of the workday. The next task has a sixteen-working-hour lag, with eight-hour days and no holidays. On a Monday–Friday lag calendar the waiting period occupies Monday and Tuesday. On an every-day calendar it occupies Saturday and Sunday. The successor’s own calendar then determines its available start.
The label “two days” hides both choices. A useful narrative states the waiting requirement in its actual units and identifies the calendars used to model it.
Decide whether the wait deserves an activity
| Situation | Useful modeling question |
|---|---|
| A wait needs status reporting | Would a named activity expose its start, finish and remaining duration? |
| A party must respond | Can the response be assigned to an owner and linked to a record? |
| A physical waiting period is fixed | Does the selected calendar represent the actual elapsed requirement? |
| Trades overlap | Can the handoff be modeled with a defined work area or quantity? |
A named activity can make an important wait easier to manage, but changing a model must preserve its intended logic. Review the contract’s requirements before replacing relationships or adding activities.
Review leads with the field team
A negative lag may model overlap, but it can also make a successor depend on a forecast finish rather than on a measurable handoff. Ask what physical condition allows the next trade to begin. “Area A released” is easier to verify than “start three days before the other activity finishes.”
To see how an SS or FF lag, or a lead, moves early and late dates, try it in the critical path calculator and open “Show the math”.
Keep a relationship-change log between updates. If a lead or lag disappears, identify whether the team changed its construction method, corrected an error or merely changed the model. That distinction helps explain finish movement later.
Continue with calendar review and monthly schedule narratives, or start a full review from the Schedule Forensics hub.
Share this article