Decision Latency From Explicit Dates Tool

Description

Return elapsed and elapsed minus pauses as activeLatency.

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.

Return elapsed and elapsed minus pauses as activeLatency.

When to use this tool

Use Decision Latency From Explicit Dates when you need one explicit scheduling or delay-budget component.

How to use the tool and how it works

Enter requestTime, decisionTime, pausedDuration. Use the units and conventions below.
Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
Read elapsed, activeLatency. Use the output convention below.

Require decisionTime ≥ requestTime and pausedDuration within elapsed time. Return elapsed and elapsed minus pauses as activeLatency.^[1]

Input field	Meaning and units	Accepted input
requestTime	Request Time	Required. Finite number.
decisionTime	Decision Time	Required. Finite number.
pausedDuration	Paused Duration	Required. Finite number; minimum 0.

Output field	Interpretation	Returned shape
elapsed	Elapsed	Required. Finite number.
activeLatency	Active Latency	Required. Finite number.

json

{
  "input": {
    "requestTime": 10,
    "decisionTime": 40,
    "pausedDuration": 5
  },
  "output": {
    "elapsed": 30,
    "activeLatency": 25
  }
}

Limitations and assumptions

Use compatible time units; pause intervals, business calendars, and causes of delay are not inferred.
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

Calculation and input contract: management/decision-latency-from-explicit-dates — tool.io

Similar or alternative tools

Task Blocked Time Share
Sum all observed time and blocked time, then divide blocked time separately by positive observedTime and plannedDuration.
Lead Stage Dwell Duration
Subtract excludedTime from leftAt - enteredAt for dwell.