Direct answer
Fairly means the sub hears it from you today, in writing, with an outer date, and the next job is sequenced so this cannot repeat.
Your subcontractor did the work, you accepted it, and the money to pay them is sitting in your client's accounts department. You are the middle of a chain, and the chain has stalled above you. The unfair version of this moment is the one most subs know well: silence, vague promises, and a payment that arrives whenever it arrives, while the sub carries your client's delay as if it were their own risk. It was never their risk. The sub contracted with you, delivered to you, and is owed by you, and your client's lateness is a problem you own, not one you pass downhill by saying nothing. Fair handling has a precise shape: the sub hears the true position from you today, before they have to chase it; they get whatever part payment genuinely exists now; the balance carries a named outer-limit date that you will meet even if the client has still not paid; and both jobs sit on records, so the sub can see the client-side state that affects them without seeing a single client confidence. This page gives you that shape step by step, the exact message to send today, and the changes to make in both agreements so the next job funds itself in the right order.
Updated November 22, 2026. First published November 22, 2026. The records quoted below are real and public, read back from the live service on November 22, 2026.
Step 1. Name the real shape: the client's delay is your problem, not the sub's debt
Start by getting the obligations straight, because every fair move follows from them. The sub's claim is on you. They did agreed work, you accepted it, and the amount and the date it fell due come from your agreement with them, which says nothing about your client unless you wrote it to. Your client's late payment is real, and it may be genuinely outside your control, but it sits between you and your client. Passing it downhill silently does not share the problem, it transfers it, to the party with the least information and usually the least cushion. Subs judge this moment more than any other in the relationship: not by whether a delay ever happens, because every experienced sub knows chains stall, but by whether they heard it early, in plain terms, with a date attached, or discovered it by chasing an overdue invoice into a voicemail. The first version keeps a good sub for the next job. The second version is how firms quietly lose every good sub they had and end up staffing rush work with whoever is left. Everything below is machinery for being the first version, even when the cash position is genuinely tight.
Step 2. Tell the sub today, in writing, with three facts and an outer-limit date
Do not wait for the sub to ask, and do not have this conversation only by phone. Send it in writing today, while the payment is late or plainly about to be, and include three facts. Fact one: what is owed, the exact amount, for what work, and that the work is accepted, so the sub never has to wonder whether the delay is a disguised dispute about quality. Fact two: the true state above you, at the level you can honestly share: the client stage that funds this payment is delivered and accepted, the invoice is in, and payment is outstanding, with whatever date the client has given you, named as the client's date and not your promise. Fact three, the one that makes the message fair: an outer-limit date, a calendar date by which you will pay in full even if the client has still not paid you. Choose that date from your real position, reserves, other income, a credit line you actually hold, never from optimism about the client, because the whole value of the date is that the sub can plan on it and you can meet it. A short wait with a real outer date is a business arrangement. An open ended wait tied only to someone else's payment is the sub financing your client for free, indefinitely, and no wording makes that fair.
Step 3. Pay what you can now, and tie the balance to dates, not just to the client
If any money genuinely exists, a part payment today is worth more than its amount: it proves the debt is live in your accounts, it shrinks the sum the sub is carrying, and it costs you the one thing silence never costs, a visible commitment. State it plainly in the same message: this amount today against the balance, the remainder by the outer date, and sooner the moment the client's payment lands, within a stated number of days of it arriving. Where the client pays in stages, mirror the stages honestly: as each client stage payment arrives, the matching sub stage follows within days, and the sub can see which stage is which, so progress above them is visible as progress for them rather than as rumour. Keep the arithmetic in the open: total owed, paid today, balance, outer date. A sub holding those four numbers can run their own cash planning like a business. A sub holding a promise to be paid when you are paid holds nothing they can plan with, and will price that uncertainty into every future quote they give you, if they quote at all.
Step 4. Put both jobs on records, so the sub can see the state without seeing confidences
The sub does not need, and should never get, your client's emails, pricing, or internal delays in detail. What the sub legitimately needs is the state of the chain that their payment hangs on: the stage was delivered, the stage was accepted, the invoice stage is outstanding, and their own work is accepted with the amount recorded. Two job records give them exactly that and nothing more. The client-side record shows stages and decisions. The sub-side record shows their work, its acceptance, and what is owed against it. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the decision states those records move through:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the accepted record as the state your sub wants to see on the client side: status accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release state ok_to_release, 4 steps checked. The decision that releases the money is recorded, with a decider and a date, not rumoured on a call. The pending record shows the honest other state: 5 steps checked, release state hold, work complete and visibly waiting on its decision, which is precisely the picture a sub can plan around when you share it early. Run both jobs this way and the hard conversation in step 2 becomes a link and three facts, because the states are already sitting where both sides can open them.
Step 5. Send the message in this shape: amount, state, part payment, outer date
The message, word for word in shape: I am writing before you have to chase this, because you should hear it from me. Your work on [the stage] is accepted and I owe you [amount]. The client stage that funds it is delivered and accepted, the invoice is in, and their payment is outstanding; they have given [date], which is their date, not one I can promise on. Here is what I can promise. I am paying [part amount] today against the balance. The remainder will be with you within [number] days of the client's payment landing, and in any case by [outer-limit date], even if they have still not paid me. The records for both jobs are at [links], so you can see the stage states yourself. Notice what the shape never does: it never asks the sub to share a risk they never agreed to, never blames the client in terms that invite the sub to doubt you will ever be paid, and never uses the word soon. Every commitment in it is a number or a date, and the outer date is yours alone to keep.
Honest limits
This page is general information about handling a payment chain fairly, not legal advice: clauses that tie a subcontractor's payment to the client paying first are treated very differently in different places and sectors, timing wording and condition wording can have different effects, and some construction payment regimes restrict them outright, so a material sum or a disputed clause deserves advice for your situation. An outer-limit date only helps if you can truly meet it; naming a date you cannot fund replaces one broken promise with a dated one. A job record shows stages, acceptance, and amounts as saved; it cannot create cash, and a verifiable receipt proves the saved result was not changed since it was saved, not that any party in the chain is solvent or will pay.
Step 6. Fix both agreements before the next job: sequence the money in writing
The permanent fix is sequencing, written into both agreements before work starts. On the client side: a deposit before stage one, staged payments tied to acceptance of each stage, and stage dates set so client money for a stage lands ahead of the date you must pay the sub for that stage, with a short acceptance window so stages cannot sit undecided while sub invoices age. On the sub side: payment terms that state the honest sequence, you pay within a stated number of days of the matching client stage payment, and in any case by a stated outer number of days from acceptance of the sub's work, so the sub prices and plans with the whole picture in front of them and never discovers the chain mid-job. Never promise pay-when-paid silently, and never let the sub's terms say one thing while your cash plan assumes another. Add one buffer habit: hold a small reserve from each completed job against exactly this gap, because chains stall even with perfect paperwork. With the sequence written and a reserve behind it, the next stall becomes a short, dated, already-explained wait, and your subs learn the thing that keeps them loyal: working for you, they hear bad news first, in writing, with a date they can bank on.
Frequently asked questions
I cannot pay my subcontractor until my client pays me. How do I handle it fairly?
Tell the sub today, in writing, before they have to chase you. State the exact amount owed and that their work is accepted, so the delay never reads as a disguised quality dispute. State the true position above you: the client stage is delivered and accepted, the invoice is in, payment is outstanding. Pay whatever part payment genuinely exists now, and give the balance two dates: within a stated number of days of the client's payment landing, and in any case by a named outer-limit date you will meet from your own resources even if the client has still not paid. Keep both jobs on records the sub can open, so they see the stage states themselves. Fair is not instant payment you do not have; fair is early truth, real numbers, and a date that is yours to keep.
Can I make my subcontractor wait until the client pays me?
What you agreed controls first: read what your agreement with the sub actually says about timing, because many agreements simply set a number of days from invoice or acceptance, with no link to your client at all. Where wording does tie sub payment to client payment, its effect varies a great deal by place and by sector, and timing wording is often read differently from wording that makes client payment a strict condition, with some construction payment regimes restricting such clauses outright. That is a question for advice on your documents and your sums. Whatever the paper says, the fairness practices on this page still apply: early notice, the true state, a part payment if one exists, and an outer date, because a clause may set your legal position without making silence a decent way to treat the people who did the work.
What should I say to my subcontractor when the money has not arrived?
Four things, in writing, in one message: the amount owed and that the work is accepted; the state of the client payment, delivered, accepted, invoiced, outstanding, with any date the client gave named as theirs; the part payment you are making today, if any; and the outer-limit date by which the balance will be paid even if the client has not paid you. Then point to the two job records so the sub can watch the states change. Avoid the two phrases that destroy trust in this conversation: soon, which is not a date, and any version of blaming the client so hard that the sub starts doubting the money exists at all. Calm, numbered, dated, and early is the whole technique.
How do I stop this happening on the next job?
Sequence the money in both agreements before work starts. Client side: a deposit before stage one, staged payments on acceptance of each stage, a short acceptance window, and stage dates set so the client's stage money lands ahead of your payment date for the sub's matching stage. Sub side: terms that state the sequence honestly, payment within a stated number of days of the matching client stage, and in any case by a stated outer number of days from acceptance of the sub's work, so the arrangement is priced and planned in the open rather than discovered mid-job. Hold a small reserve from each finished job against the gap, because even well sequenced chains stall, and the reserve is what turns your outer-limit date from a hope into a commitment.
How do job records help when I am stuck in the middle of a payment chain?
They let the sub see the state their payment hangs on, delivered, accepted, invoiced, waiting, without seeing your client's confidences, and they let you prove your own stage was accepted rather than asking the sub to take your word for the delay. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so the client-side acceptance and the sub-side amount owed sit on pages both sides can open. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run both jobs on records, so the next time the chain stalls the sub sees the state and your outer date instead of chasing silence: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.
Related
- The agency that hired me says their client has not paid them yet. How do I get paid?
- How do I ask a client for a deposit before starting work?
- How do I split a big project into milestone payments so I do not get burned?
- My client tried to hire my subcontractor directly behind my back. What do I do?
- My client keeps cancelling our meetings at the last minute and the project is drifting. How do I handle it?
- Start with your problem: every problem in this directory, routed to its page