How to calculate a revised delivery date
Start with the moment the blocked work can genuinely resume. Then allocate the remaining production hours across your normal working days, removing protected bookings and dates where no capacity is available. The first date on which the remaining workload reaches zero is the realistic revised delivery date.
The inputs that matter
- Resume date: the earliest date the project can actually continue.
- Remaining hours: the work still required from that point onward.
- Normal daily capacity: realistic production time, not total hours in the day.
- Working days: the days you normally schedule delivery work.
- Protected commitments: hours already promised elsewhere.
- Days off: dates with no usable capacity.
Do not promise the first date that looks possible
The purpose of revising a delivery date is to replace uncertainty with a date you can reasonably hold. Compressing the schedule immediately after a delay can create a second missed deadline, which is harder to explain than the first reset.
A better process is to calculate the normal-capacity date first, then separately test whether extra hours can rescue some or all of the delay.
What to send to the client
Keep the explanation factual. State what input was due, when it became available, the original delivery date and the recalculated date. You do not need to argue about blame. The schedule change is the operational consequence of the changed dependency.
Get the revised date
Use SlotReset to allocate the remaining work across the calendar you actually have now.
Calculate a revised delivery date