Terminating a subcontractor feels like the end of a problem. Done without the right paperwork behind it, it's often the start of a bigger one — against the GC, not the sub.
Key takeaways
Courts generally look for a serious, material breach before accepting that a termination for cause was justified: abandonment of the site, persistent failure to correct defective work, insolvency, or a pattern of non-performance that goes to the heart of the contract. A single missed deadline, an isolated quality complaint, or a personality conflict on site is not, on its own, the kind of material breach this standard describes — the bar is a pattern or a fundamental failure, not an irritation.
This matters because the label a GC puts on a termination doesn't control the outcome. Calling it “for cause” in a letter doesn't make it so if the underlying facts don't clear that bar when tested later.
Insolvency is worth separating out from the others, because it can move faster than the ordinary notice-and-cure process allows for. A subcontractor that stops paying its own suppliers or workers creates lien exposure that runs against the project regardless of how quickly the GC acts, which is part of why insolvency is treated as its own category of cause rather than folded into ordinary non-performance.
Many contracts require written notice of the default and a specific period to fix it before termination is permitted. Skipping straight to termination without giving that notice and that window is a common and costly mistake — not just a technicality, because skipping a required cure period can itself constitute a breach on the terminating party's part, which flips the legal exposure onto the GC even where the sub's underlying performance really was deficient.
The notice and cure step also has a practical benefit beyond legal protection: it creates the first entry in the documentation trail that will matter if the termination is ever challenged, and it gives a sub a genuine, recorded opportunity to fix the problem before the relationship ends — which strengthens the GC's position either way, whether the sub cures the default or fails to.
The essential records are photos and dates of incomplete or defective work, communications showing missed deadlines, prior written warnings, and payment records. Terminating on a hunch, without documentation, is the pattern that leaves a GC exposed if the subcontractor challenges the termination afterward — and if the stated cause doesn't hold up, the GC may end up being treated as having breached the subcontract instead of the other way around.
None of this documentation is useful if it's assembled retroactively, after the decision to terminate has already been made. The file needs to exist in real time, as the pattern of non-performance develops, so that the notice-and-cure letter and any eventual termination letter are supported by a contemporaneous record rather than a reconstruction written after the fact.
CCDC 2's own description of its scope references dispute resolution procedures and the prerequisites for Ready-for-Takeover as subjects the general conditions address, which signals that termination and default sit inside a defined process on a CCDC 2 project rather than being left entirely to the parties' discretion. The specific clause numbers and exact termination wording sit behind CCDC's paid document text, so a GC operating under CCDC 2 (or a CCDC-based subcontract) should confirm the actual termination clause in that specific contract rather than assuming a generic version of it — the general shape described here is the mechanism, not a substitute for the contract's own wording. Where a project's supplementary conditions modify the default rights around notice or termination, those modifications control over the general conditions' version.
Where the terminated subcontractor's obligations are backed by a bond, termination has consequences beyond the two parties to the subcontract. A CCDC 221 Performance Bond exists specifically to guarantee performance of the contract by the contractor, and a CCDC 222 Labour and Material Payment Bond guarantees that labour and material payment obligations incurred in performing the contract will be satisfied. A surety standing behind either bond generally needs to be notified early — often before a final termination decision, not after — because the bond's own terms typically require that notice as a condition of the surety's obligations continuing to apply, which is one more reason the bonding relationship itself has to be actively maintained, not treated as paperwork filed once at award and forgotten.
A worked example
A framing subcontractor misses three consecutive scheduled start dates over five weeks, with crew no-shows documented by site sign-in logs and photos of an empty site on each missed date. The GC sends written notice citing the pattern of non-performance and gives seven calendar days to cure, referencing the specific subcontract clause requiring notice before termination.
The sub does not return to site within the cure period. The GC terminates, citing the documented pattern of missed dates, the notice already given, and the expired cure period — each element supported by a dated record created as the events happened, not reconstructed afterward. When the sub later disputes the termination, the GC's file (sign-in logs, photos, the notice letter, and proof of the cure period's expiry) is what turns “the GC says we were terminated for cause” into a termination that actually holds up.
Only if the contract doesn't require one, which is unusual, or in the narrow circumstances a specific contract carves out for immediate termination (such as insolvency). Where a cure period is required and skipped, that omission can itself be treated as a breach by the party terminating.
No. A subcontractor's statutory lien rights arise from having supplied labour or materials to the improvement and exist independently of why or how the subcontract ended — termination for cause doesn't extinguish a lien right that has already accrued for work actually performed.
The surety typically needs to be notified, often before the termination is finalized, because the bond exists to guarantee the contractor's performance and most bond forms condition the surety's continuing obligations on being given that notice. Terminating first and notifying the surety later can jeopardize the bond coverage.
No. Termination for cause requires a material breach and, typically, notice and an expired cure period, as described above. Termination for convenience is a separate contractual right some agreements grant to end the relationship without alleging fault, usually with its own compensation mechanics for the terminated party — the two are governed by different clauses with different consequences.
A 30-minute call is enough to tell you whether AI pays for itself here.
