Deposit vs Milestone Payments: Which Fits the Job

Fifty per cent up front, fifty on delivery. On a three-week job worth $6,000 those two numbers are fine: the most you can lose is $3,000 and about eleven working days of your life. Deposits, milestones and holdbacks are three answers to that arithmetic, and a job that short only needs the first. Put the identical split on a five-month rebrand worth $18,000, though, and you have agreed to finance $9,000 of somebody else's project through to October, with exactly one chance to discover whether they pay.

The search that lands people here is usually about the percentage. The percentage is the second question. The first is which of the three shapes the job has, because each structure protects against a different failure and each costs you something different to run. Get the shape wrong and no percentage rescues it.

Nothing on this page is legal advice; I do not practise law. Every statute quoted below carries its section number and the date the text was read, and where that text came from somewhere other than the body that issued it, the sentence says so.

Short, fixed, and finished before anyone changes their mind

Three weeks. Scope written down. One deliverable, maybe two. Here the structure is a deposit and a balance, and the reason is not cash flow — it is that the job is too short for anything else to be worth administering.

What the deposit protects against is the client who disappears. Not the one who disputes an invoice; the one who stops replying in week two with your work sitting on their server. A deposit converts that from a total loss into a partial one, and it does a second job most freelancers never claim: it sets the floor under a cancellation. Clause 11.3 of the AIGA Standard Form of Agreement for Design Services (2022 update, read 22 August 2026) provides that on termination the designer is compensated the greater of any advance payment, a prorated portion of the fees, or hourly fees for work performed — plus, where the client terminates for convenience, an early termination fee of 25 per cent of the total project fee. Read the first limb again. The advance payment is not merely credited against what you are owed; it is one of the three candidates for what you are owed, and the largest one wins. A deposit you never earned out is a kill fee you already collected.

What it costs you is a conversation and, at larger clients, a real procedural problem: systems that pay only against a receipted invoice referencing a purchase order have nothing to receipt on day one. That is solvable. The two ways round it are in the questions at the end.

One drafting choice inside the deposit is worth making on purpose. AIGA's introduction sets out the options plainly: some designers apply the deposit to the first progress billing, which makes it a pre-payment for phase one; others hold it to the end and apply it to the final invoice, in which case, the guidance notes, you should point out that no interest accrues while you hold it, and that on cancellation the deposit is refunded less amounts due. The second version is not really a deposit. It is a holdback pointed the other way, and it behaves like one.

Four months, four phases, one invoice per phase

Now the job has a middle. Discovery, concept, production, delivery — or research, draft, revision, final. Milestones exist for exactly this shape, and what they buy you is a ceiling: your maximum unpaid exposure stops being the contract value and becomes the value of one phase.

The second thing they buy is harder to see. Every milestone is a checkpoint at which the client has to look at the work and pay for it, so a client heading for a dispute reveals it in month two rather than in month five. That is worth more than the cash flow.

The cost is administration and one specific brittleness. Federal acquisition drafting names it: performance events can be severable, where completion is independent of everything else, or cumulative, where an event depends on a previous one being finished first (FAR 32.1004(a)(2)). Subparagraph (a)(2)(i) draws the consequence out: the contract "shall not permit payment for a cumulative event or criterion until the dependent event or criterion has been successfully completed." Read on 22 August 2026 from the eCFR text of title 48, which that day gave 7 August 2026 as its latest issue date and 20 August 2026 as the date it was up to date to.

The schedule that quietly fails is the one where every milestone turned out to be cumulative and nobody noticed while drafting it. Phase two sign-off sits with a marketing director who is on leave, and because phases three and four were written to depend on it, three invoices freeze behind one absent signature — none of them late, none of them collectable, and none of it anybody's fault in a way you could put in a letter. Mark each event severable or cumulative deliberately, and keep the early ones severable so a stall in one lane does not stop the money in another.

The job whose end keeps moving

The third shape is the one nobody structures, because it does not look like a project. Ongoing content. A monthly retainer that grows. A production whose delivery depends on the client's client. An engagement where "done" is defined by a launch that has already moved twice.

Milestones are the wrong tool here, because a milestone needs an end to be measured against. What fits is time-boxed billing: a defined period, invoiced on a fixed calendar date whether or not the phase concluded, with a stated capacity and a stated way for either side to stop. Your maximum exposure becomes one billing period plus your payment terms, and it stays there for as long as the job runs.

You give up the large payment at the end, which for some people is the whole psychological point of the structure. You also hand the client a clean exit at every period boundary. In exchange you stop carrying a receding deadline on your own balance sheet. AIGA's clause 4.5 addresses the adjacent problem — a suspension fee equal to hourly fees for idle time caused by client delay, unless the designer secures other work for that time at the same or greater compensation — which is the same instinct applied to a gap rather than an end.

If periodic billing is refused, the fallback is a longstop: a calendar date on which the balance falls due whether or not the launch happened. That date has to go in at signature. It is unnegotiable six weeks after the launch slipped.

A milestone has to be verifiable by a stranger

Here is the mechanic that decides whether any of the above works. A milestone is a trigger, and a trigger tied to a feeling is not a trigger.

The clearest published statement of the test comes from federal contract financing. FAR 32.1004(a)(1) requires each event or performance criterion to be an integral and necessary part of contract performance, identified in the contract "along with a description of what constitutes successful performance of the event or attainment of the performance criterion." It then rules out the events people reach for when they cannot think of a deliverable: the signing of contracts or modifications, the exercise of options, the passage of time "or other such occurrences do not represent meaningful efforts or actions and shall not be identified as events or criteria for performance-based payments." The sentence that matters most to a freelance schedule is the one closing that paragraph — an event need not be a critical event to trigger a payment, "but the Government must be able to readily verify successful performance of each such event or performance criterion." That is government financing policy and it governs nobody's design retainer. The drafting test survives the translation intact. Could a stranger holding only your contract and your delivery email tell whether the event happened?

Apply it to what people actually write. Milestone 2: client approves concept direction. A stranger cannot verify that, and neither can you, because approval is a state of mind until somebody writes it down. Milestone 2: delivery of three concept routes as PDF to the addresses in Schedule B, and expiry of the review period in clause 4.4. Same event, now with an edge on it.

The second half is what turns acceptance from a hope into a date. The AIGA form gives the client five business days from receipt of each deliverable to notify the designer in writing of any failure to comply with the specifications, or of any objections, and then closes the loop: "In the absence of such notice from Client, the Deliverable shall be deemed accepted." Silence completes the trigger instead of suspending it. Acceptance criteria themselves belong upstream — a scope of work that survives the client is where deliverable formats and review windows get defined, and the payment schedule should quote its clause numbers rather than paraphrase them. The clause-by-clause version of the same fight is in the nine clauses that decide whether you get paid.

Holdbacks, and the release condition nobody writes

A holdback keeps a percentage of every payment back until some later event. In construction it is called retainage, and it is old, standardised, and increasingly capped by statute.

The federal construction clause shows the shape at its most explicit. Under FAR 52.232-5(e), retainage is not automatic: where satisfactory progress was achieved the progress payment is authorised in full, and only where progress has not been satisfactory may the contracting officer retain a maximum of 10 per cent, until satisfactory progress is achieved. When the work is substantially complete the officer releases the withheld funds apart from an amount considered adequate for protection (read 22 August 2026). Two features, both missing from most freelance paper: withholding has a stated cause, and release has a stated event.

California now legislates the ceiling for private jobs. Civil Code section 8811, added by SB 61 (Stats. 2025, Ch. 49) and applicable to contracts relating to a private work of improvement entered into on or after 1 January 2026, provides that a retention payment withheld by an owner from a direct contractor — and by each contractor from those below — shall not exceed 5 per cent of the payment, and that total retention proceeds shall not exceed 5 per cent of the contract price. The cap carries its own carve-outs — for a subcontractor who fails to furnish a performance and payment bond after being told one would be required, and for residential projects that are not mixed-use and run to four storeys or fewer. Section 8812 makes the owner pay the retention within 45 days after completion of the work of improvement, and where there is a good faith dispute allows withholding of no more than 150 per cent of the disputed amount (both read 22 August 2026). These are works-of-improvement rules. They do not reach a design retainer or a video edit, and quoting them at a marketing client would be a mistake. What they show is that where legislators have looked hard at holdbacks they have written three things every time: a percentage cap, a deadline for release, and a limit on how much a dispute lets you freeze.

Your contract will have none of the three unless you put them there. The clause that costs freelancers real money reads like this: 10% of the total fee shall be released upon final client approval and launch. Two undefined events, both controlled by people outside the contract, neither carrying a date. Launch moves, and the holdback moves with it. Ten per cent of an $18,000 job is $1,800 that never becomes collectable, because nothing has technically gone wrong.

If a client insists on a holdback, insist back on three things in the same sentence: a percentage, an event you can verify, and a longstop date on which the balance falls due regardless. Federal financing policy caps performance-based payments at 90 per cent of the contract price (FAR 32.1004(b)(2)(ii)), which tells you where the floor sits even in the most generous public regime. Something is held to the end. The argument worth having is about what releases it.

Where the date you wrote is also a statutory deadline

There is a reason to write dates that has nothing to do with negotiation.

New York General Business Law section 1411 — part of the Article 44-A that took effect on 28 August 2024 (NYS Department of Labor) — requires contracted compensation to be paid on or before the date it is due under the terms of the contract, or, where the contract specifies neither a date nor the mechanism by which that date will be determined, no later than thirty days after completion of the freelance worker's services.

That wording needs a note about where it came from. On the re-check of 22 August 2026 it was read from a commercial code library, because the legislature's own page answered with a bot-challenge screen both times it was requested that day. It matches the Article 44-A text read first-hand three days earlier for New York's Freelance Isn't Free Act, and the state labour department's own model contract, below, prints the same two branches on its face. Enforcement of the statewide article runs through the Attorney General rather than the labour department — which matters when you file rather than when you draft, and is worked through on that page.

California Business and Professions Code section 18102, added by SB 988 (Stats. 2024, Ch. 870) and effective 1 January 2025, sets out the same two branches in the same order, with one gap worth knowing about: its fallback opens only "if the contract does not specify when the hiring party shall pay", and there is no equivalent of New York's reference to a mechanism for determining the date. Read from the state's own code display on 22 August 2026.

These two are an illustration, not a survey. Other states, and a number of cities, run freelance payment rules of their own with different money thresholds, different deadlines and different agencies to complain to; this site maps those separately rather than flattening them into one sentence here. Both sections above are rechecked every 90 days whether or not anything has moved, which puts the next pass on this page due by 20 November 2026.

Follow that through into your schedule. Every milestone date you write becomes a date on which compensation is due under the terms of the contract, and that is the date the statute attaches to. A milestone with no date and no mechanism does not give you thirty days from the milestone. It gives you thirty days from completion of the whole engagement, which on a five-month job is a different quarter. This is also where net terms stop being decoration and start counting from something specific, worked through in what the invoice clock counts from.

The New York Department of Labor's own model Freelance Worker Agreement (read 22 August 2026) makes the preference visible. Its compensation section offers cash, money order, cheque, or Installments — three lines, each with a blank for an amount and a blank for a date due. Not three lines for events. Its term section then makes the drafter tick one of exactly three boxes: payment on or before a named date, no later than 30 calendar days after completion, or the instalments above. So if you bill on acceptance rather than on the calendar, the contract needs the mechanism sentence as well, so that an acceptance-triggered milestone still resolves to a determinable date.

Both statutes carry the same prohibition, aimed straight at end-of-job leverage: once you have started work, the client may not require you to accept less than the contracted amount as a condition of being paid on time. California's version adds a second limb: nor may the client require you to hand over more goods, more services or more intellectual property rights than the contract already gave them. The call that opens with "we can release the final 20 per cent this week if you can do something on the number" is, in both of those states, the thing the legislature wrote that sentence about.

Blanks to fill in before the first invoice goes out

Notice first where the industry paper leaves all of this. AIGA's clause 3.1 says only that fees are payable in the amounts and according to the payment schedule set out in the Proposal — the standard terms never see the schedule at all. Everything below therefore lives in a document you write yourself, which is an argument for writing it before the client asks. Adapt it to the defined terms in your own agreement, and have someone admitted in the governing-law state read it before you rely on it.

Start with the table, because it is the part a stranger can check.

Every cell gets filled. A trigger with no date, or a date with no trigger, is where the money stops. Three sentences elsewhere in the agreement decide whether the cells hold their shape once the job is under way, and each one props up a different column.

Amount column: say what the deposit turns into

Client shall pay an advance of $[___] on execution, which shall be applied to [the first progress billing / the final invoice]. On termination for any reason the advance is [non-refundable / refundable less all amounts due to Contractor for Services performed through the termination date].

Choose one option in each bracket and delete the other. A deposit whose treatment on cancellation is left unstated is the first thing argued about when a job dies, and it is the row of the table people most often fill in with a number and nothing else.

Trigger column: keep achievement out of other people's hands

A Milestone is achieved on the later of (a) Contractor's delivery of the items listed for that Milestone in Schedule [], in the formats specified there, and (b) expiry of the review period in clause []. Client's internal approvals, approval by any third party, and any launch, publication or go-live date are not conditions of achievement.

The second sentence is the one that gets struck. Watch for it coming back in the redline, because striking it hands the trigger to a marketing calendar and a client's client.

Date due column: a holdback needs a date of its own

Client may withhold []% of each payment, to a maximum of []% of the total fee. The withheld amount is due on the earlier of (a) [__] days after final delivery and (b) [date]. Where Client disputes a specific deliverable in writing, Client may withhold no more than 150% of the disputed amount and shall release the remainder on the schedule above.

That last sentence borrows the shape of California's construction rule rather than its authority, which is exactly why it has to be written into your contract to do anything at all.

None of these percentages is a standard, and anyone who quotes you one without asking how long the job runs is describing their own habits rather than a rule. The number is the part you negotiate. The shape is the part you decide before the conversation starts.