Description
Add lag to predecessorFinish for dependencyStart, then take the later of that value and successorEarliest for scheduledStart.
Schedule differences use a common time coordinate and may preserve negative slack or lead times. A scalar lag or float term does not recalculate a full dependency network.
Add lag to predecessorFinish for dependencyStart, then take the later of that value and successorEarliest for scheduledStart.
When to use this tool
Use Task Dependency Finish Start Lag when you need one explicit scheduling or delay-budget component.
How to use the tool and how it works
- Enter predecessorFinish, lag, successorEarliest. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read dependencyStart, scheduledStart. Use the output convention below.
Add lag to predecessorFinish for dependencyStart, then take the later of that value and successorEarliest for scheduledStart.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| predecessorFinish | Predecessor Finish | Required. Finite number. |
| lag | Lag | Required. Finite number. |
| successorEarliest | Successor Earliest | Required. Finite number. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| dependencyStart | Dependency Start | Required. Finite number. |
| scheduledStart | Scheduled Start | Required. Finite number. |
{
"input": {
"predecessorFinish": 10,
"lag": 2,
"successorEarliest": 11
},
"output": {
"dependencyStart": 12,
"scheduledStart": 12
}
}Limitations and assumptions
- Negative lag is allowed; all coordinates must share a unit and calendar, and other dependencies are not considered.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Use a complete dependency plan and working calendar to assess critical paths, resource constraints, and completion forecasts.
References
Similar or alternative tools
- Work Item Slack To Promised Date
Subtract forecastFinish from promisedAt for signed slack.
- Handover Overlap Coverage Gap
Subtract incomingStart from outgoingEnd for signed overlap and subtract nonnegative requiredOverlap for margin.