Payment "On Approval": The Freelance Clause That Holds Your Invoice Hostage

The clause to find

Open the contract and search for words like "approval," "acceptance," "satisfaction," and "sign-off." You are looking for any sentence that ties payment to the client’s judgment rather than to an objective trigger like delivery or a number of days. Common phrasings include "payment is due upon final approval of the work," "the contractor will be paid when the deliverables are accepted to the client’s satisfaction," and "the client may withhold payment until accepted." If the trigger is the client’s opinion rather than a fact, you have found the clause.

The problem is not that the client wants to be happy with the work — that is reasonable. The problem is that subjective approval has no deadline and no standard. Without language constraining it, "approval" is a door the client controls, and your invoice sits on the wrong side.

How the trap actually plays out

Picture the standard scenario. You finish a project, deliver everything specified in the brief, and send the invoice. The client responds a week later with vague comments and asks for changes. You revise, resubmit, and wait. They come back with more vague comments. Weeks pass. Each round of feedback feels slightly different, and you cannot tell whether they are unhappy, distracted, stalling, or simply unable to make a decision. Meanwhile, your invoice has not been paid, because "approval" has not happened.

Without a clause that says what approval means and when it must occur, you have no way to force the issue. You can keep revising forever, or you can stop and demand payment — but the contract gives the client the position that they have not approved, so they do not owe you. Many freelancers in this situation eventually accept a partial payment or walk away unpaid simply to end it. The clause did the damage; the client may not even have intended it.

Why clients use the language (sometimes innocently)

It is worth knowing that not every client who uses "approval" language is trying to scam you. Many client contracts are copied from templates without much thought. Some clients sincerely want a quality check before they release payment, which is fair on its face. The clause is dangerous regardless of intent, because once it is in writing it gives the client unilateral control whether they wanted that or not. So pushing back on the language is not an accusation — it is making sure a reasonable instinct does not turn into an unreasonable outcome by accident.

The fix: objective triggers and a clock

The clean replacement for subjective approval is an objective trigger plus a deadline. Two structures work well, alone or together. First, tie payment to delivery: payment is due a defined number of days (often 14 to 30) after you deliver the work, regardless of approval. Second, use a deemed-acceptance clause: the client has a fixed window (say 7 to 10 business days) to review and provide written, specific objections; if they do not respond within that window, the work is deemed accepted and payment is due. Either structure puts the clock back in your court and forces feedback to be timely and specific.

You can keep an approval concept and still be safe. A reasonable middle ground is: the client may review and request revisions within a defined window; any revisions are limited to objective failures to meet the agreed specification; and once revisions are complete (or the window closes), the work is accepted and payment is due. That preserves the client’s genuine quality check without leaving you in indefinite limbo.

Define what "the work" actually is

Approval traps thrive on vague deliverables. If the contract says you will provide "a website" or "marketing materials" without specifying the scope, the client has wide latitude to declare it incomplete or unsatisfactory. The defense is a clear scope of work, attached to or referenced in the contract, listing exactly what is being delivered: which pages, how many designs, what file formats, which platforms, what is in and what is out. Specific deliverables make approval a check against an agreed list rather than an opinion.

A clear scope also lets you handle scope creep without a fight. New requests beyond the listed deliverables go through a written change order with their own price and timeline; they cannot be used to hold up payment on the original work. The combination of a specific scope and an objective payment trigger is what makes the project actually finishable.

Cap the revisions

Even with a clear scope, an unlimited-revisions clause can simulate the approval trap. If the client can demand changes "until satisfied," they can extend the project indefinitely and delay payment indirectly. Pair your objective payment trigger with a revision cap: a defined number of revision rounds (often two or three) within the scope, with any additional rounds billed at your rate. That converts indecision into a cost the client bears, not a delay you bear.

Milestones for longer projects

For projects longer than a few weeks, do not put all of your payment risk at the end. Break the work into milestones — discovery, draft, revision, delivery — each with its own payment due on completion. Now an approval trap can only delay one milestone at a time, and you can see trouble coming. If the client refuses to release a milestone payment, you have an early warning to address the issue before you have invested ten more weeks. Milestones also align both sides: the client sees progress in stages, you get paid as the value is delivered.

Suspension and late-payment remedies

Add teeth so the deadlines mean something. A clause letting you suspend or stop work if an invoice goes more than a set number of days unpaid (often 10 or 15) puts pressure back on the client. Interest or a late fee on overdue invoices, commonly 1 to 1.5 percent per month, makes delay expensive rather than free. These additions are entirely standard in fair freelance contracts and are usually accepted without much pushback when you ask for them. Without them, a slow-paying client faces no consequence for stalling.

Sample language to ask for

You do not need to draft like a lawyer. Plain, clear sentences do the job, and most clients accept them once they see the alternative is open-ended:

• Payment is due within 14 days of delivery of each milestone, regardless of approval status.
• The client has 10 business days after delivery to provide written, specific revision requests; absent such requests, the work is deemed accepted.
• Revisions are limited to two rounds within the original scope of work; additional revisions are billed at the hourly rate set out below.
• The contractor may suspend work if any invoice remains unpaid more than 10 days past its due date.
• Overdue invoices accrue interest at 1.5 percent per month from the due date.

What to do if you already signed one

If you are already in a contract with an approval trap and the project is stalling, do a few things before things deteriorate further. Put everything in writing: send a written summary of where the project stands, what was delivered against the brief, and what specifically the client says is missing or unsatisfactory. That forces vague dissatisfaction to become a concrete list, which you can then address or rebut. If the client refuses to specify, that itself becomes evidence that they are not actually rejecting the work — they are stalling.

Many disputes resolve once a freelancer politely asks for the specific objections in writing, because the client either makes the list (and you finish it) or cannot (and you have a stronger position to demand payment). If it ultimately becomes a real fight, the strongest documentation is what wins: emails, briefs, deliverables, and any evidence the work meets the agreed specification. Small-claims court is a viable option for amounts within its limits in your state, and it is designed to be used without a lawyer.

The bottom line

A clause that ties your payment to the client’s subjective approval — without a deadline, an objective standard, and a deemed-acceptance fallback — is the single most common way freelancers end up working for free. Find the approval language, replace it with a delivery-plus-window trigger, cap revisions, break long projects into milestones, and add suspension and late-payment remedies. If you want help spotting these terms in a client’s contract, ClauseAudit reviews the agreement in about a minute, flags subjective payment triggers and unlimited revisions, and gives you the exact language to ask for. The clause is solvable; the trick is fixing it before you sign, not after the invoice goes unpaid.