What a client delay clause should answer
- Which client inputs, approvals, files or access are required?
- How quickly must the client respond?
- Does the project pause when a dependency is missing?
- Does the delivery date move automatically or get recalculated?
- Does a long pause move the project to the next available production slot?
- Can priority or restart work involve additional fees, if legally and commercially appropriate?
Project dates depend on the Client providing the materials, feedback, approvals and access identified in the project schedule by the agreed dates. If a required client dependency is late, affected work may pause. Any impacted delivery date will be recalculated against the Contractor’s next available production capacity and existing commitments. A client delay therefore may move the delivery date by more than the number of elapsed delay days.
Why “equivalent delay” language can be too simple operationally
A clause that says every client delay moves the project by exactly the same number of days is easy to understand, but it may not match the way a busy freelance calendar works. If the original slot has passed and the next week is already booked, the next available capacity can be farther away.
Whatever wording you use, it should match the scheduling practice you can actually follow consistently.
Use the policy and the calculator together
The agreement sets the expectation. The calculator handles the real event when it happens: when was the input due, when did it arrive, what work remains and where does that work now fit?
A client delay has already happened?
Use SlotReset to calculate the operational impact before you discuss the revised date.
Calculate the new delivery date