Start with the specific disagreement
If client feedback or materials are delaying a project, make the dependency visible. Name the missing decision and explain which work it prevents. Avoid blaming the client for every delay when some tasks can still progress independently. A useful proposal separates what you can complete now from what needs their input and shows the effect on delivery dates or milestones.
Work through the facts, one step at a time
List the inputs still needed
Identify the exact copy, access, approval or decision and the person responsible. Refer to earlier requests by date. “Waiting on the client” is less useful than “homepage copy approval is needed before layout can be finalized.”
Explain the practical effect
Show which tasks depend on the input and which do not. If a reserved production slot will be lost, explain that clearly. Distinguish a delivery consequence from any proposed extra charge or change to the agreement.
Agree a revised sequence
Ask for a decision date and discuss the work that follows. Where payment depends on a milestone, clarify whether the milestone is complete or blocked. Do not silently treat lack of feedback as acceptance unless properly established terms support that conclusion.
What this can look like
A developer can finish responsive styling but cannot connect a booking service without access credentials. A task list shows these separately. The client can prioritize access while the developer continues work that does not depend on it.
This is an invented scenario to explain the approach, not a customer result or a prediction of your outcome.
Records worth gathering
- Requests for client inputs
- Task dependencies
- Agreed milestone definitions
- Earlier schedule changes
Keep originals and prepare copies of the relevant parts. Redact unrelated personal details before sharing. Explain any gaps in the record rather than filling them with assumptions.
Open a clearer conversation
Edits stay on this page and are lost when you leave. Nothing is sent automatically. This is a discussion starter, not a legal notice or settlement agreement.
Before you agree to the next step
Do not share passwords in a public dispute record. Use secure access arrangements and describe the missing permission without exposing credentials.
Put any proposed outcome into specific terms: who will act, what they will do, the amount if money is involved, and the date. Identify what remains unresolved. An invitation, a discussion and a signed agreement are different stages.
Does no feedback mean approval?
Do not assume so. Check the actual agreement and circumstances. A clearer approach is to request an explicit decision and discuss what should happen if the client cannot respond by the proposed date.
A private place to prepare your side
SettleBetween provides private AI guidance for each person and a shared space to discuss approved information. You choose what to share and whether to agree. Availability depends on both parties’ locations and the dispute type.
Free to start. The case starter pays $79 only after both parties sign. The invited party never pays the agreement fee. See included access and pricing.
Prepare your side freeAI can make mistakes. This guide is practical preparation, not legal advice. Use appropriate official schemes or independent advice when needed. A discussion here does not pause external deadlines or guarantee payment.