Client Delay Impact
Quantify schedule and cost impact from a client-caused delay.
Description
Client-delay planning estimates unrecovered days and resulting team cost under supplied assumptions.
Client-delay planning estimates unrecovered days and resulting team cost under supplied assumptions.1
Quantify schedule and cost impact from a client-caused delay.
When to use Client Delay Impact
Use this tool to quantify schedule and cost impact from a client-caused delay.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Client Delay Impact and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter plannedCompletionDays, clientDelayDays, recoverableDays, dailyTeamCost using the field table and calculation rules, then run the tool.
- Read netDelayDays, revisedCompletionDays, incrementalCost. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| plannedCompletionDays | Planned completion duration (days) | number; minimum: 0 | Required |
| clientDelayDays | Client-caused delay (days) | number; minimum: 0 | Required |
| recoverableDays | Delay days recoverable through resourcing (days) | number; minimum: 0 | Required |
| dailyTeamCost | Daily team cost | number; minimum: 0 | Required |
Enter nonnegative days/cost and return net delay/revised days/incremental cost.
net=max(0,delay−recoverable); revised=planned+net; cost=net×dailyCost Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| netDelayDays | Net schedule delay (days) | number; minimum: 0 |
| revisedCompletionDays | Revised completion duration (days) | number; minimum: 0 |
| incrementalCost | Incremental delay cost | number; minimum: 0 |
{
"input": {
"plannedCompletionDays": 30,
"clientDelayDays": 10,
"recoverableDays": 4,
"dailyTeamCost": 1000
},
"output": {
"netDelayDays": 6,
"revisedCompletionDays": 36,
"incrementalCost": 6000
}
}Limitations and assumptions
No schedule dependencies, actual recovery or contractual reimbursement is established.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Rescope Change Log: Quantify audit rescoping changes and change-log completeness. For a complementary task, use Workpaper Assembly Deadline: Check workpaper assembly completion against a supplied deadline window.
References
-
Client Delay Impact — tool.io
Similar or alternative tools
- Rescope Change Log
Quantify audit rescoping changes and change-log completeness.
- Workpaper Assembly Deadline
Check workpaper assembly completion against a supplied deadline window.