Start with the specific disagreement
A milestone-payment dispute should begin with the definition of the milestone, not simply the percentage of the project completed. Identify the output, approval or event that was meant to trigger payment. Then compare the actual record with that trigger. A task can be substantially complete while its acceptance process remains unclear, and a client’s new request may not be part of the same milestone.
Work through the facts, one step at a time
Identify the payment trigger
Read the milestone description and any acceptance conditions. Check whether payment follows delivery, approval, a date or another event. Note who can approve the work and whether required client inputs were provided.
Separate incomplete work from new scope
List the agreed items still missing and any later additions. Use specific delivery evidence. If the client rejects the milestone, ask which criterion is not met rather than treating all negative feedback as the same objection.
Discuss status and next actions
Propose completion of named items, a review date or a defined payment discussion. If part of the milestone is accepted, describe that clearly. Any revised sequence should explain what happens to later milestones as well.
What this can look like
A software milestone is tied to an agreed import workflow. The workflow is delivered, but the client adds a request for a new report before approving payment. Comparing both requests with the milestone definition keeps the original acceptance issue distinct from the proposed addition.
This is an invented scenario to explain the approach, not a customer result or a prediction of your outcome.
Records worth gathering
- Milestone definition
- Acceptance criteria
- Delivery and approval records
- New change requests
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 infer a legal right to payment or withholding from a completion percentage alone. Contract wording and applicable rules may determine the effect of acceptance or rejection.
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.
What if the client never approves?
Ask for a specific criterion-based response and review the agreed approval process. Do not assume silence is acceptance; seek appropriate advice if a formal payment or dispute step becomes necessary.
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.