You delivered the milestone, the client says "we'll review it later," and the payment is left hanging. I see this often in my practice with agencies, freelancers, and remote teams.
Almost never is the client the problem: the problem is how the milestone-based payment is written.
→ Undefined milestone: what is delivered and when it is considered complete.
→ Acceptance with no deadline: if the client doesn't respond, is it approved or left open forever?
→ Payment tied to a subjective "approval" rather than verifiable criteria.
→ Scope changes with no process: the milestone moves and the price doesn't.
→ Currency, exchange rate, and fees left undefined in international payments.
→ What happens to ownership of the work if the milestone isn't paid.
If you charge or pay by milestones with parties in other countries and want to review your contract, message me on WhatsApp or through the website for an initial consultation.
Which of these points has caused you the most problems?
Informational content. Validity depends on the jurisdiction of the parties.
Top comments (4)
"Acceptance with no deadline" is the one that hurts freelancers most. A clause we've seen work: if the client doesn't raise specific issues within X working days of delivery, the milestone counts as accepted. Do you find clients push back on deemed acceptance, or is it usually accepted once it's explained?
Thanks, that’s exactly the mechanism I’d recommend. In my experience, the resistance is rarely to the principle, but to its terms. A review window that’s too short, or acceptance that kicks in silently, is what makes clients balk. Three things make it easier to agree on: a realistic window (5–10 working days depending on the deliverable), a requirement that objections be specific and in writing, and a notice at delivery that starts the clock, ideally with a reminder before it expires. Framed that way, it protects both sides: the client gets a clear review period, and the freelancer isn’t left waiting indefinitely.
Where I still see friction is with clients who need internal approvals: a fixed window can clash with their own review chain. What we usually propose is that the client names a single point of contact with authority to approve, and allows one extension (say, 5 extra working days) if they notify in writing that an internal review is still pending. That way silence still counts as acceptance, but a client who is actively engaged doesn’t get caught out by the clock. How do you handle that on your side?
"Acceptance with no deadline" is already getting the attention it deserves. The quieter trap is payment tied to a vague "approval." The fix that holds up: a short acceptance list in the milestone, covering what is in scope and what "works" means on the staging URL, with the invoice pointing to that list. And keep ownership, including repos and credentials, until it's paid.
Agreed, and that's the part that connects acceptance to IP. An acceptance list tells you when the work is done; the contract also needs to say when the rights transfer. I'd make the assignment of IP expressly conditional on full payment, with a limited license in the meantime so the client can test and use the staging environment, but not exploit the work commercially. That way "keeping ownership until it's paid" isn't just a practical leverage point (repos, credentials), it's a clear contractual position. One caveat: the clause should also say what happens to the client's own materials and to third-party or open-source components, which usually don't transfer at all. Do you usually split the assignment by milestone, or only on final payment?