What changes when client feedback arrives late
The obvious change is that work starts later. The less obvious change is that the original production slot may no longer exist. If another project was scheduled to begin after the expected review window, that work is now occupying time the delayed project would need.
This is why “the feedback was two days late, so delivery moves two days” can be wrong even when everybody agrees on the facts.
A practical response to late feedback
- Record the agreed feedback date.Keep the dependency timeline factual.
- Record when usable feedback actually arrived.If feedback is incomplete, the project may still be blocked.
- Recalculate from current capacity.Do not assume the old production slot is still free.
- Communicate the revised date promptly.Put the new date near the top of the message.
- Protect the new schedule.Confirm the next client dependency and its deadline.
Should you charge for the delay?
That depends on your agreement, jurisdiction and commercial relationship. SlotReset does not decide whether a fee is contractually due. Its optional priority amount is a planning tool that can help you understand the value of additional rescue capacity if you choose to offer it.
Prevent the same problem next time
Future statements of work can identify the client inputs that the schedule depends on, the expected turnaround for feedback, what happens when a review window is missed and whether a paused project returns to the next available production slot.
Feedback is already late?
Calculate the new delivery date against your current calendar before sending the client an update.
Reset the timeline