Direct answer
Tell the client early, with the record open: what is done, exactly which step is missing, and the new date you will hit.
A subcontractor has let you down, the work your client is waiting for has a hole in it, and two clocks are now running. One is the recovery clock: the missing piece still has to be produced, by you, by a replacement, or by re-sequencing the job around it. The other is the trust clock: every hour the client spends imagining the worst costs more than the delay itself, because a client who learns about a problem late, or vaguely, assumes the whole job is in trouble. Most people work the recovery clock first and the trust clock last, which is backwards. The working order is facts first, client early, recovery in the open. Get the staged record in front of you so you can name exactly which step is missing and which steps are done and checked, tell the client in one message that carries the done list, the missing step, your recovery move, and a new date, then execute the recovery where the client can see it land. This page gives you the first hour, the recovery order, the exact wording for the client and for the subcontractor, and the setup that stops a repeat.
Updated November 19, 2026. First published November 19, 2026. The records quoted below are real and public, read back from the live service on November 19, 2026.
Step 1. Spend the first hour on facts: what was promised, what arrived, what is missing
Before anyone is told anything, establish the three facts the whole response stands on. What exactly was the subcontractor contracted to deliver, by when, in what form: the brief, the date, and the acceptance shape you agreed, in writing if you have it. What actually arrived: a partial delivery, a delivery that fails its purpose, or nothing at all, and which of those three it is changes everything downstream. What is missing, stated as a step, not a feeling: not the project is behind, but step three of five, the drafted section, has not arrived, while steps one and two are complete. Resist the two first hour temptations: chasing the subcontractor in escalating messages before you know your own position, and reassuring the client before you know the facts. One hour spent pinning the done list and the missing step is what makes the client message in step 3 short, calm, and believable, because every sentence in it can be pointed at.
Step 2. Choose the recovery move before you message the client: cover, replace, or re-sequence
The client message must carry a plan, so the plan is chosen first, and there are only three moves. Cover it yourself: right when the missing step is small, or inside your own skill, or the deadline is close enough that briefing a replacement costs more time than doing it. The cost is your hours, and it is usually the fastest route back to the promised date. Replace the subcontractor: right when the step is large or specialist, with the brief, the materials, and the done steps handed over as a package so the replacement starts from the record and not from your retelling. Re-sequence the job: right when later steps do not depend on the missing one, deliver and get acceptance on everything that is ready, and let the missing step land as a named second delivery on a stated date. Most real recoveries combine the second and third: re-sequence today so the client receives real work on the original date, and a replacement or your own cover closes the missing step on the new one. Decide who bears the extra cost now, too: between you and the subcontractor it follows your agreement with them; between you and the client, the delay is yours to own, because the client contracted with you.
Step 3. Show the client the staged record, so the gap is one named step and not the whole job
The conversation goes well or badly on one thing: whether the client can see the shape of the job. A staged record shows steps, states, and decisions, so the missing piece appears as exactly what it is, one step not yet delivered inside a job whose other steps are done and checked, instead of a fog in which everything might be missing. 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 states a staged job moves 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 them the way your client will. The accepted record is a job that closed cleanly: 4 steps, all checked, decided by the client on a stated date, release state ok_to_release. The pending record is a job mid flight: 5 steps checked and a hold state, visibly waiting on its next decision rather than lost. Your job, shown this way, lets the client count with you: these steps are done, this one step is the gap, this is the move that closes it, and this is its date. That counting is what turns a confession into a status report, and it is why the record is opened before the message is written, not attached later as an apology exhibit.
Step 4. Send the client message in this shape: done, missing, move, date
The message, word for word in shape: A quick status on the job, because one part of it needs a change of plan. Steps one and two are complete and ready for you at the link below. Step three, the section I had placed with a specialist, has not arrived to the standard the job needs, so I am [covering it myself / bringing in a replacement / delivering it as a second drop], and it will be with you on [date]. Everything else on the job is unchanged, and the final date moves to [date] / holds. I will confirm again on [day] either way. Notice the jobs each line does: the done steps come first because they are the truth that frames the gap; the subcontractor is named as a role, never blamed as a drama, and never used as the reason the client should accept less; the move and the date are commitments, not hopes; and the next confirmation is promised before the client has to ask. Send it as soon as the facts and the plan exist, the same day you know, because the identical message sent three days later reads as concealment even when it was only delay.
Step 5. Handle the subcontractor separately, in writing, and close the loop on cost
The subcontractor conversation is a different conversation, kept off the client's thread entirely. It is short and written: the brief and date you agreed, what arrived or failed to arrive, the consequence you have had to act on, and the money consequence that follows your agreement, part payment for the usable part, nothing for the missing step, or the recovery cost where your terms provide for it. Give a genuine emergency its human hearing, once, and let it change the tone without changing the record: sympathy and a settled account can coexist. What you do not do is leave the account vague out of awkwardness, because a vague close is how the same arrangement gets proposed again on the next job. Record the outcome where you keep supplier notes, in one factual line, so the next hiring decision starts from a fact and not from a forgiving memory.
Honest limits
This page is general information about handling a failed subcontract, not legal advice: your liability to the client, and the subcontractor liability to you, are set by the agreements you each signed and by local rules, and a large or regulated engagement deserves advice for your situation. Owning the delay to the client is a working rule, not a legal admission drafted for you. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove a step is good, and it does not produce the missing work, which is why the recovery move and its date, not the record alone, are what the client is actually being given.
Step 6. Rebuild the setup so one letdown cannot reach the client again
Four changes, made once, cover nearly every repeat. Stage the subcontract: the subcontractor delivers in two or three checked stages with dates, so a failure surfaces at the first missed stage while recovery is still cheap, instead of at the final deadline. Hold a buffer: the subcontractor date sits days ahead of the client date, always, and the gap is never spent in planning. Keep a named second option for every specialist step you regularly buy, even a loose one, because a replacement found in calm is a different hire from one found in panic. And run the whole job on the staged record from the start, your steps and theirs in one place, so the state of the job is a page you open rather than a set of inboxes you search. A subcontractor letting you down will happen again across a long career. With this setup it becomes a step you reassign on a Tuesday, not a deadline you explain on a Friday.
Frequently asked questions
A subcontractor I hired let me down and my client is waiting for the work. What do I do?
Work three moves in order, the same day. First, facts: what the subcontractor was contracted to deliver and by when, what actually arrived, and the missing piece stated as one named step inside the job. Second, choose the recovery before you message anyone: cover the step yourself, bring in a replacement briefed from the job record, or re-sequence so everything ready is delivered on the original date and the missing step lands as a named second delivery. Third, tell the client early in one message shaped done, missing, move, date: the completed steps first, the one missing step named plainly, the recovery you have already started, and the new date with a promised next confirmation. Handle the subcontractor separately, in writing, and never on the client's thread.
Should I tell the client the problem was a subcontractor?
Tell them the fact without making it the excuse. The client contracted with you, so the delay is yours to own and yours to fix, and a message that leads with blame reads as an attempt to hand the problem across. The working shape names the role once, factually, a specialist step I placed has not arrived to the standard the job needs, and then spends the rest of the message on what is done, what you are doing, and the date. Clients are consistently more forgiving of a subcontractor failure handled this way than of a smaller problem handled late or vaguely, because what they are judging is not whether your supply chain is perfect. It is whether you noticed early, told them straight, and had a move ready.
Who pays for the replacement or the extra work?
Between you and the client, you do: the price and the date they agreed were with you, and a subcontractor failure does not reopen either. Between you and the subcontractor, your agreement with them decides: part payment for the part that arrived usable, nothing for the step that never arrived, and recovery costs only where your terms provide for them, which is a reason to put one line about late or failed delivery into every subcontract before work starts. Settle the subcontractor account in writing, separately from the client, and record the outcome in one factual line where you keep supplier notes. Absorbing the cost once, cleanly, is cheaper than the reputation shape of a client who watched you pass your problem down the chain.
How quickly should I tell the client?
The same day you know the step has failed, once you have the facts and a recovery move, which should take hours, not days. Early is the whole value of the message: told on the day, a missing step is a status report with a plan, and clients routinely accept a moved date given that way. Told after the deadline, or after the client asks, the identical facts read as concealment, and the conversation stops being about the step and becomes about whether they can trust the next date you give them. If the facts are still forming, send the holding version the same day: one step is in difficulty, here is what is done, I will confirm the recovery and the date by a stated hour tomorrow, and then hit that hour exactly.
How does a job record help when a subcontractor lets me down?
It turns the client conversation from a claim into a count. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own staged record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so you open one page with the client and show steps done and checked, the one step that is missing, and the acceptance state of everything delivered so far, instead of asking them to trust a summary written under pressure. 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 your next subcontracted job on one staged record, so a letdown is one named step with a date, never a fog over the whole job: 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
- How do I prove I delivered the work to a client?
- My client keeps asking for a progress update every day. How do I handle it?
- My client cancelled the project and wants all the half-finished work handed over. What do I send?
- My client will only pay me after their own client pays them. Should I agree?
- Can I show a client's logo and name in my portfolio if they never gave permission?
- Start with your problem: every problem in this directory, routed to its page