Staged payments turn one large risk into several small ones

The exposure that builds quietly

On a long project paid at the end, your exposure grows every day. Week one, almost nothing is at stake. By the final week, months of work sit unpaid and everything depends on a single event: the client settling in full.

That’s a large amount of risk concentrated in one moment, and it is entirely avoidable. Staged payments cap the maximum that can ever be outstanding, which converts a single potentially fatal outcome into a series of survivable ones.

Tie stages to events, not to dates

Stages linked to the calendar create an argument whenever the schedule slips, and schedules slip for reasons that are frequently the client’s own — material not supplied, decisions not taken, feedback not given. Invoicing on a date when the work has been held up by the payer is an awkward position to defend.

Stages linked to completed pieces of work avoid that entirely. A payment falls due when something identifiable has been delivered, which is a fact rather than an interpretation. It also gives the client something visible in return for each payment, which makes the arrangement easier to accept in the first place.

The stages should be things a non-specialist can recognise. A milestone the client cannot see the completion of is a milestone that will be queried, and the whole purpose is to remove queries from the payment process.

The shape that tends to work

A common pattern is something before starting, one or more payments as defined pieces are delivered, and a final amount on completion. The exact split varies by trade and by project length, and there is nothing sacred about any particular arrangement.

Two principles are worth holding to. The first payment should cover your early costs, so that you aren’t funding the client’s materials as well as your own time. And the final payment should be small enough that losing it would be annoying rather than serious, because the final payment is the one most likely to be delayed, disputed or forgotten.

That last point deserves emphasis. Once the work is delivered, the client has what they wanted, and their motivation to settle promptly is at its lowest point of the whole engagement. Structuring around that reality is not cynicism, it is design.

It gives both sides a place to stop

A staged arrangement means an unhappy client can end the engagement having paid for what they received, and you can stop work having been paid for what you did. Neither party is trapped in a project that is not working by the sheer size of what is outstanding.

That’s a genuine benefit to the client and it is worth saying so when proposing it. A great many buyers are more nervous about committing to a large project than suppliers assume, and an arrangement that limits their exposure as well as yours frequently makes the sale easier rather than harder.

What to do when a stage is not paid

The point of stages is that they give you information early, and information is only useful if it is acted on. A stage that has not been paid is a signal, and continuing to work through it wastes the protection you built.

Pausing is easier to do gracefully if the possibility was stated at the outset — that work continues once each stage is settled. Framed as a term agreed in advance, stopping is administrative. Introduced for the first time in the middle of a dispute, it reads as a threat.

A pause is also usually enough. Most non-payment at this stage is a process failure inside the client organisation rather than an inability to pay, and a polite note saying work will resume on receipt tends to locate the invoice quite quickly.

Where staging does not apply

Short jobs do not need it, and imposing three payments on a two-day piece of work adds administration for both sides in exchange for very little.

Some clients also have payment processes that make multiple invoices genuinely painful, and in those cases a deposit plus a final payment may be the practical compromise. As with most of this, the aim is not to apply a rule uniformly. It’s to make sure the amount of unpaid work you are carrying at any moment is an amount you chose to carry.

There is a version of staging that does not involve money at all and is worth mentioning, because it solves a related problem. Breaking a large piece of work into visible deliverables, whatever the payment arrangement, gives both sides checkpoints at which the direction can be corrected cheaply. Projects that go badly wrong rarely do so suddenly; they drift, and a checkpoint every few weeks is how the drift gets caught while it is still small.