The Short Version
I've watched builders tolerate a sub who was clearly costing them money — missed starts, warranty callbacks, client friction, schedule delays — for six months to two years past the point where the relationship should have ended. The delay is almost never about the money or the relationship. It's about the transition cost: finding a new sub, managing the handoff, getting the client comfortable with the change. The math almost always says fire sooner. A sub who costs you one schedule delay per project is costing you $3,000-$8,000 in delayed overhead absorption, rushed rework, and client management. Finding a new sub typically costs two weeks of coordination and one partially-completed phase. The delay always costs more than the transition. Here's how to make the decision and how to handle the transition professionally.
Sound Familiar?
If any of these patterns describe a relationship with one of your subs, the math says fire them:
- You've had a conversation about the same quality or reliability problem three or more times with no improvement
- A sub has missed their scheduled start date on one of your projects in the last six months
- You've done rework on work a sub delivered because it wasn't done to the quality standard your project required
- A client has mentioned being frustrated with a specific sub's communication or work quality
- You're keeping a sub because they're available, not because they're reliable
- You've said to your PM or foreman 'just make sure [sub name] doesn't do that again' — and it has happened again
- You have a backup sub for this trade that you're not using because you feel obligated to the current sub
What We Found
The Seven Warning Signs That Say: Fire This Sub
Not every warning sign is a termination trigger. Some require a direct conversation before you pull the trigger. Others are pattern problems that don't get fixed with a conversation. Here's how to tell the difference.
Terminate immediately — no conversation needed:
- Safety violations. A sub who cuts corners on site safety creates liability you carry. This is non-negotiable. If you see it, address it directly and immediately. If it happens again, terminate and document.
- Fraud or misrepresentation. A sub who submits invoices for work not performed, bills using another company's license, or misrepresents their capacity or experience. These are disqualifying events. Terminate, document, do not re-hire under any circumstances.
- Substance use on site. If you have direct evidence that a sub or their crew is impaired on your job site, terminate immediately. The liability exposure is catastrophic and the risk to your crew and project is unacceptable.
Direct conversation first — then terminate if no improvement:
- Missed scheduled start. One missed start might be a crisis. Two missed starts is a pattern. If you've had one conversation about reliability and it happens again, move to termination.
- Quality issues that require rework. One quality issue is fixable. A pattern of quality issues — especially after you've documented the standard — is a capacity or care problem that conversations don't solve.
- Communication breakdown. A sub who doesn't respond to schedule confirmations, ignores RFIs, or goes silent on open issues isn't reliable enough to manage in a production environment.
- Price increases mid-project. A sub who presents a price increase after starting work — outside of a documented scope change — is testing whether you'll pay it. If you pay it once, you'll pay it again. Terminate and find a sub who honors their agreement.
The rule: a conversation is required before termination for most reliability and quality issues. But if you've had that conversation and nothing changed, the second instance is grounds for termination — not a third conversation.
The Firing Conversation: How to Do It Directly Without Destroying the Relationship
The firing conversation is not complicated. The difficulty is that most builders avoid it until they're angry, which makes the conversation harder than it needs to be. Here's the script structure that works:
The frame: Start by acknowledging the relationship and what it's been. "I want to be direct with you. We've worked together for [X] months/years, and I respect what you've done on [specific project]. That's not the conversation we're having today."
The decision: State clearly what's happening. "I've made the decision to end our working relationship. Your last day on my projects is [specific date]." Don't hedge, don't make it conditional. The sub needs a clear ending to process and move on.
The reason: Give the specific reason. Not a general "it's not working out" — that leaves the sub wondering what they did wrong and guessing at the real reason. "The specific reason is that you've missed [X] scheduled starts in the last six months, and that creates schedule risk I can't carry on my projects." Be factual and brief. Don't make it personal.
What you're not doing: Don't threaten termination and then not terminate. Don't use the conversation to attack the sub's character. Don't blame them for everything that went wrong. Don't promise future work if you don't mean it. Don't leave them not knowing what happened.
The sub's reaction is not your problem. They may be angry, defensive, or confused. Listen to what they say, confirm their perspective if it's valid, hold the decision. You do not need to justify yourself beyond the factual reason. The conversation should take 5-10 minutes maximum.
Professional close-out: Confirm the close-out terms: final invoice date, what's owed and when it will be paid, lien release requirements, and any remaining work. Handle final payment promptly — the goal is for the sub to walk away with money in their account, not a grievance.
The Transition: Managing the Work, Your Team, and the Client Without Disasters
The worst transitions happen when the builder fires the sub and then realizes they don't have a replacement ready, the client doesn't know what's happening, and the work stoppage is going to cost more than the firing was supposed to save. The transition plan starts before the firing conversation.
Before you fire: identify the replacement
Never fire a sub without knowing who comes next. Have a backup sub identified, vetted, and ready to mobilize before you end the current relationship. The backup sub should be on your approved sub list with current insurance on file and a clear schedule slot. If you don't have a backup, find one before you fire — even if it means tolerating the current sub for another 2-3 weeks while you secure the replacement.
Tell your team first
Your PM and foreman need to know before the sub knows. Not because they'll tell them — because they need to manage the work while you handle the transition. Brief them: who you're replacing, who the replacement is, when the switch happens, and what they should say to the client if asked. Don't disparage the departing sub to your team — it creates a bad culture signal and it's unprofessional.
Tell the client simply and professionally
"I want to let you know that we're making a change to the [trade] scope of your project. [New sub name] will be on site starting [date]. [Old sub name] did good work on [specific reference], and this change is about ensuring we maintain the schedule and quality standards your project requires." You don't need to explain the details of why. Own the decision, don't blame the sub, and focus the client on what's coming next.
Build in transition time
Most gravity trades need 2-4 weeks from decision to mobilization of a new sub. During that window, the work may be at a standstill or on partial hold. Budget for that delay. It's cheaper than firing a sub and then having nothing happen for three weeks while you scramble.
The Documentation That Protects You Post-Termination
After firing a sub: document the termination in writing (email is fine), maintain all correspondence about the reason for termination, confirm final payment terms in writing, obtain lien releases for all completed work, and note the termination in your sub scorecard so you never re-hire this sub by accident. If the sub files a payment claim or dispute, your documentation is your defense.
For more on building a sub network that doesn't leave you exposed when one relationship fails, see the network-building post — it covers the approved sub list structure that gives you reliable alternatives before you need them.
Diagnose your sub management gaps in 5 minutes
The GO First diagnostic evaluates your current sub network structure, relationship accountability system, and the gaps between where you are and where you need to be for consistent project delivery.
Book Your Free Diagnostic CallFrequently Asked Questions
The test: take the cost of the transition — finding a replacement, managing the handoff, any schedule delay — and compare it to the cost of continuing. If you've done rework on a sub's work, you've had schedule delays from missed starts, or you've had client complaints because of this sub — and those costs over the last six months exceed the transition cost, you're waiting too long. Most builders who ask this question have already been tolerating problems for too long. The math usually says fire now.
Direct conversation first for most quality and reliability issues. If you've had one specific conversation about a problem and it hasn't changed, the second occurrence is grounds for termination. For safety violations, fraud, or substance use — go straight to termination, no conversation required. For communication and responsiveness problems, sometimes a direct 'this is what I need to see from you by [date]' works. If it doesn't, you know they can't deliver and you terminate.
Decide immediately: does this sub finish their current phase or stop now? If they're mid-phase and stopping creates a worse gap than finishing, give them 1-2 weeks to close out what they started — and pay them on time for it. If they've already demonstrated they can't manage the work reliably, stop immediately and bring in the backup. Communicate the timeline to your client and PM, manage the gap explicitly, and don't let the uncertainty extend the disruption.
This risk is real and it's why most builders wait too long. Mitigation: before you fire, vet the replacement properly using your standard pre-qualification process — don't lower your standards just because you need someone fast. If the replacement underperforms in the first 30 days, you've confirmed you need a better sub list and you make another change. Two transitions in one year is painful. Staying with a bad sub for three years is worse.
Only if you have evidence the underlying problem has been fixed — not just an apology. A sub who missed starts because they were overbooked needs to show you their current workload before you take them back. A sub with quality problems needs to demonstrate improvement on a trial basis before you restore them to your primary list. Forgiveness without evidence of change is just resetting yourself for the same failure. The sub scorecard tracks this: restore to probationary status, not to approved status.
The same problems recurring with different subs is a process problem, not a people problem. If you've fired three electricians in two years for the same issues, your issue isn't finding better electricians — it's that your scope, inspection, or payment structure is creating the conditions for failure. Review what happened: unclear scope? Unenforced quality standards? Payment terms that create friction? Fix the system, then hire the next sub into a system that works.
