Schedule leads can damage schedule quality because they allow a successor to start before its predecessor reaches the event defined by the relationship. That overlap may look efficient. However, it often hides the actual handoff, assumes knowledge of future progress, and weakens critical path and float analysis.
A lead is also called a negative lag or negative offset. For example, a finish-to-start relationship with a five-day lead may appear as FS-5d. The successor starts five working days before the predecessor finishes. Although scheduling software can calculate the relationship, the resulting plan may not represent how the work can actually be executed.
The better approach is usually to identify the partial completion, information release, or physical handoff that permits the successor to begin. The scheduler can then model that event with a discrete activity or milestone.
What Schedule Leads Actually Represent
Microsoft describes a lead as an offset that permits a successor to start before its predecessor completes. That definition explains the calculation, but it does not establish whether the relationship reflects valid execution logic. See Microsoft’s description of task dependencies, leads, and lags.
Consider this simple relationship:
- Activity A: Complete subsystem test, 20 days
- Activity B: Analyze test results, 10 days
- Relationship: A FS-5d to B
The lead directs the analysis to start five days before testing finishes. Yet the relationship does not explain what test data will be available, who releases it, or whether the available results support meaningful analysis. The schedule contains an overlap, but it lacks the event that makes the overlap possible.
This is the central weakness of schedule leads: they express a date calculation instead of a verifiable dependency.
Why Schedule Leads Weaken Critical Path Analysis
They require an assumption about future progress
A lead effectively assumes that a predecessor will reach a usable condition a fixed number of days before its forecast finish. However, duration remaining does not always indicate technical maturity. A 20-day activity with five days remaining may be 75 percent through its duration without having produced the item needed by the successor.
The GAO Schedule Assessment Guide explains that leads imply unusual foresight about future events. GAO recommends making every effort to replace them with shorter activities and clearer relationships. This approach exposes the actual dependency instead of relying on a predetermined overlap.
They can obscure the driving predecessor
A sound network shows which predecessor event controls an activity’s start or finish. A negative offset changes that date without identifying a separate, measurable event. As a result, managers may see the calculated driver without understanding the technical condition behind it.
This issue becomes more significant at convergence points. A successor may have several predecessors, while one relationship contains a large lead. The calculated driver can shift during updates even though the underlying handoff has not changed. For more on interpreting these relationships, see what a driving predecessor means.
They can distort float and path rankings
Total float depends on durations, calendars, constraints, relationship types, and relationship offsets. Therefore, adding a lead can change early and late dates across the network. It may compress a path, alter the apparent critical path, or create misleading float values.
The Department of Energy’s EVMS and Project Analysis Standard Operating Procedure states that leads can adversely affect critical path analysis, distort total float, and create resource conflicts. This concern matters when the team uses float to set management priorities or evaluate milestone achievability.
Float is not simply spare time assigned to an individual activity. It is a calculated property of the network. See how total float works in project scheduling before interpreting a path that contains leads.
A long lead can produce a logic failure
GAO identifies a particularly serious condition when a finish-to-start lead exceeds the successor’s duration. In that situation, the successor can finish before the predecessor finishes, even though the stated relationship says the predecessor’s finish controls the successor’s start.
For example, assume a three-day successor has an FS-5d predecessor relationship. The successor may both start and finish before the predecessor reaches completion. The network calculation is possible, but the relationship no longer communicates a rational finish-to-start dependency.
Leads Hide Scope That the Team Should Manage
Many leads are substitutes for missing scope. The hidden scope may include a preliminary release, partial installation, draft review, first-article completion, data package transfer, or completion of work in one physical area.
Unlike an activity, a lead has no responsible organization, duration basis, resource assignment, or objective completion status. The team cannot report it as started, delayed, or finished. It also cannot carry a clear activity description or acceptance criterion.
This loss of visibility affects more than schedule mechanics. In an Integrated Master Schedule (IMS), the network should connect technical work, program events, and organizational handoffs. Replacing a real handoff with a negative offset removes information that control account managers (CAMs) and program managers need for execution.
A Fictional Program Example
Assume the Falcon Ridge radar program plans environmental qualification and data analysis as follows:
- Conduct environmental qualification testing: 20 days
- Analyze qualification results: 10 days
- Relationship: Testing FS-5d to Analysis
The planner added the five-day lead because engineering expects to analyze early test data while the chamber completes its final sequences. However, the schedule does not distinguish early data from final qualification results.
During execution, the first test sequences finish as planned. The final thermal cycle then identifies an intermittent failure. Engineers must repeat part of the test and revise earlier conclusions. Although the scheduling tool allowed analysis to start, the original logic never showed the technical dependency between final test evidence and the completed analysis.
A more executable model
The planner could replace the lead with these activities:
- Conduct initial qualification test sequences.
- Release preliminary test data.
- Perform preliminary data analysis.
- Conduct final qualification sequences.
- Release approved qualification data set.
- Complete qualification analysis and report.
The revised model still permits legitimate concurrent work. However, it identifies what information becomes available and when. It also allows the team to status each handoff and evaluate the effect of a failed test sequence.
If detailed decomposition would create unnecessary administrative burden, the scheduler could consider start-to-start and finish-to-finish relationships. Those relationships must still reflect real execution logic. For example, analysis may start after testing starts, but analysis cannot finish until the approved test data set is complete.
Schedule Leads Complicate Statusing and Forecasting
A lead may appear reasonable in the baseline and then become unstable during updates. Suppose the predecessor starts late, progresses unevenly, or receives a longer remaining duration. The scheduling engine recalculates the successor from the predecessor’s forecast finish and the fixed negative offset.
However, the recalculated date may not match the actual availability of partial output. The successor might appear ready to start even though the necessary drawing, test result, component, or approval does not exist. Conversely, the successor may have started based on a valid partial handoff that the schedule never captured.
These conditions often lead to out-of-sequence progress, manual date adjustments, or added constraints. Each workaround can further weaken the network. Constraints should not be used to repair unclear logic; see the distinction between hard and soft schedule constraints.
Effects on EVMS and Schedule Risk Analysis
In an Earned Value Management System (EVMS), schedule activities often support the time-phasing and objective measurement of budgeted work. A lead does not automatically create an EVMS compliance issue. However, an unexplained lead may indicate that the schedule and the planned accomplishment criteria do not describe the work consistently.
For example, a work package may plan budget for successor work before the predecessor produces its required output. If the team cannot define the partial handoff, the Performance Measurement Baseline may rest on an optimistic assumption rather than an executable sequence.
Leads also reduce transparency in schedule risk analysis (SRA). A negative offset has no independent duration or status. Therefore, analysts cannot model it like a normal activity with its own uncertainty, risk exposure, or mitigation action. NASA’s Schedule Management Handbook identifies improper use of leads and lags as a schedule health concern and recommends replacing hidden waiting periods with activities.
Are Schedule Leads Prohibited?
Do not treat every schedule-quality metric as a universal contractual requirement. Whether a program must prohibit, limit, document, or report leads depends on its contract, contract data requirements, agency direction, approved scheduling procedures, and program tailoring.
Several government guides set a strong quality expectation. The DoD Risk, Issue, and Opportunity Management Guide presents zero leads as the goal in its summary of the Defense Contract Management Agency 14-point schedule metrics. In addition, the Department of Energy’s Planning and Scheduling guide directs covered DOE capital asset projects not to use leads.
GAO uses more qualified language. It recommends avoiding leads where possible and using them only judiciously with compelling justification. Therefore, a scheduler should verify the applicable contractual and agency criteria rather than present one organization’s assessment threshold as a regulation for every program.
When Overlapping Work Is Legitimate
Concurrent work is common and often necessary. The problem is not overlap itself. The problem is using a lead when the schedule could show the overlap more clearly.
Legitimate overlap may occur when:
- A design team releases drawings by zone or subsystem.
- A test organization provides data in approved increments.
- Production moves units through a repeatable workflow.
- A proposal team reviews completed sections while authors draft others.
- Software teams deliver builds through defined integration events.
In each case, identify the event that permits downstream work. Use discrete activities, release milestones, or justified start-to-start and finish-to-finish logic. Also confirm that the successor cannot finish before receiving all required predecessor output.
How to Review Leads in an IMS
A scheduler should filter all incomplete relationships for negative lag during development, monthly status, baseline reviews, and customer delivery preparation. Do not rely only on a percentage metric. One lead on a critical or near-critical path may present more risk than dozens of harmless relationships elsewhere.
For each lead, ask:
- What physical item, information, approval, or condition permits the successor to begin?
- Can the schedule represent that condition with an activity or milestone?
- Can the team objectively status the handoff?
- Does the lead assume uniform progress through the predecessor?
- Could the successor finish before the predecessor provides its final required output?
- Is the lead longer than the successor’s duration?
- Does the overlap create an unrealistic resource demand?
- How does removing the lead affect the critical and near-critical paths?
- Is the reason documented in the schedule basis or activity notes?
After correcting the relationships, recalculate the schedule and trace the longest path to the relevant completion milestone. Then evaluate total float, negative float, and path continuity. The process in critical path analysis for an IMS provides a broader framework for that review.
Practical Rule for Schedulers
Do not use a lead merely because two activities will overlap. First, identify why the successor can start before the predecessor finishes. If a measurable handoff exists, show it in the network.
If the program retains a lead, document the technical basis and test the relationship during every update. Also verify that the overlap remains achievable, does not conceal missing scope, and does not produce an illogical completion sequence.
A schedule should explain how the program will execute the work. Schedule leads often replace that explanation with arithmetic. Clear activities and relationships produce a more credible critical path, a more useful forecast, and a schedule that managers can act on.
Frequently Asked Questions
Is a lead the same as a negative lag?
Yes. Scheduling tools commonly represent a lead as a negative relationship offset. For example, FS-5d allows the successor to start five days before the predecessor’s forecast finish.
Do all leads automatically make a schedule invalid?
No. A lead does not automatically invalidate an entire schedule. However, each lead warrants review because it may hide a handoff, distort float, or create a sequence that cannot be executed. Applicable contracts or agency procedures may impose stricter criteria.
Should a scheduler replace a lead with start-to-start logic?
Not automatically. A start-to-start relationship is appropriate only when the predecessor’s start genuinely enables the successor. Often, the better solution is to divide the predecessor into smaller activities and link the true partial completion to the successor.
Why do schedule health checks target zero leads?
Zero is a useful quality goal because leads frequently hide logic and make the schedule harder to status and analyze. However, a metric is a screening tool. The scheduler must still examine the technical meaning and contractual context of each relationship.