Name every dependency
List the content, access, decisions, and approvals the client must provide, with an owner and due date.
Connect each dependency to the work it unlocks so the effect of a delay is easy to understand.
Use a clear pause rule
State when work pauses and how a new slot is assigned. Reserved capacity cannot always remain open indefinitely.
Send a written status note as soon as a dependency becomes late, including the affected milestone.
Restart with a revised schedule
Confirm what has arrived, what remains missing, and the next available dates. A restart fee may be appropriate when a long pause creates remobilization work.
Document the new schedule rather than relying on an old date everyone knows is no longer realistic.