The Financial Reason You Need a Written Contract for Every Trade

There is a particular kind of helplessness that comes from watching a problem unfold that you already identified, already raised, and already offered a solution for, and being told, politely or otherwise, that your input was noted and the answer was no. Some of the most expensive lessons in construction finance get learned that way. Not because nobody saw the problem coming. Because the person who saw it did not have the authority to fix it, and the person who did have the authority did not feel the urgency until the damage was already done.

The specific scenario that comes to mind is not hypothetical. Subcontractors get angry. Sometimes the anger is legitimate and sometimes it is not, but either way, a sub who decides they are done with a job can do a remarkable amount of financial damage on the way out. Equipment left mid-scope. Partially completed work that the next trade cannot build on until it is either finished or torn out. Material that walks off the site. A month that was supposed to close within budget suddenly hemorrhaging money to cover work that should have already been paid for and completed by someone else.

What makes that scenario not just painful but genuinely expensive is the absence of a contract that defines what happens when it does.

Without a Written Contract, the Financial Exposure Has No Boundary

A handshake agreement between a GC and a subcontractor is not nothing. Courts recognize oral contracts in construction, and a pattern of invoicing, partial payment, and documented work can establish the terms of an agreement even without a signed document. But what an oral agreement almost never contains is the language that protects a GC when the relationship breaks down badly. The termination provisions, the damage remedies, the notice requirements before a sub can legally walk, and the provisions that allow the GC to backcharge the cost of correcting incomplete or defective work against whatever balance remains on the subcontract.

Without those provisions in writing, a sub who leaves a job in bad shape has more leverage than they deserve. The GC is left holding costs they cannot recover cleanly, and the legal path to doing so is more expensive and less certain than it would have been if the contract had been written correctly at the outset. Arizona's construction statutes, for example, spell out the conditions under which a subcontractor can legally suspend or terminate performance, including specific notice periods and the circumstances that justify them. A GC whose subcontract is silent on those same conditions is operating without the contractual counterbalance those statutes assume will exist on the other side of the relationship.

The Cost of a Sub Walking Is Never Just the Work They Left Behind

When a subcontractor abandons a scope mid-project, the direct cost of the unfinished work is the most visible number, but it is rarely the largest one. There is the cost of mobilizing a replacement trade, which typically comes at a premium because the new sub is being brought in under time pressure rather than competitively bid. There is the cost of any work that has to be corrected, redone, or demolished before the replacement can begin. There is the schedule impact, which ripples into every other trade sequenced behind the one that walked, and in commercial construction that schedule impact can carry liquidated damages or owner penalties that fall on the GC regardless of which subcontractor caused them.

Then there is the question of materials. A sub who leaves angry does not always leave cleanly. Equipment that was on-site may disappear. Materials that were already purchased and charged to the job may not be where they were supposed to be when the next crew arrives. A GC without a written contract that includes clear provisions around materials ownership, site security obligations, and the sub's liability for damage or loss has very limited recourse for any of it. The money spent on those materials is gone, and recovering it through litigation against a sub with limited assets is an exercise that costs more in legal fees than it returns.

What a Well-Written Subcontract Actually Protects Against

A subcontract that does its job contains provisions that most GCs either negotiate away in the interest of keeping a relationship comfortable or never include in the first place because the informal agreement was working fine up to the point where it stopped.

Termination for cause provisions define exactly what constitutes a breach by the subcontractor, what notice the GC must provide before terminating, and what the GC's remedies are once termination occurs, including the right to complete the work using other means and charge the cost of doing so back to the terminated sub. Backcharge provisions establish the GC's right to deduct the cost of correcting defective work, cleaning up after an abandonment, or covering costs the sub was contractually obligated to bear from any remaining balance owed under the subcontract.

Damage and property provisions address who owns materials once they are delivered to the site, what the sub's liability is for damage they cause to other trades' work or to the project generally, and what security obligations exist around the sub's scope while the job is active. These are not exotic protections. They are standard elements of any subcontract written by someone who has seen what happens without them, and they are the specific provisions that become relevant the moment a sub decides they are finished before the work is.

Worker Classification Lives in the Contract, Too

A written subcontract also serves a function that has nothing to do with the relationship going wrong. The IRS applies a specific set of criteria to determine whether a worker is a genuine independent contractor or an employee being misclassified for tax purposes, looking at behavioral control, financial control, and the nature of the working relationship. A written subcontract that correctly defines the relationship, confirming the sub's independence, their responsibility for their own tools and equipment, their right to work for other clients, and the scope-based rather than time-based nature of the engagement, is one of the meaningful pieces of documentation that supports the independent contractor classification if that classification is ever questioned.

Misclassifying an employee as an independent contractor carries back taxes, penalties, and interest that can accumulate over several years before the IRS surfaces the issue. A subcontract that is written thoughtfully is not a guarantee against misclassification findings, but it is substantially better than no documentation at all, which leaves the entire determination to be made from behavioral evidence alone.

The Budget Impact Lands Whether or Not Anyone Is at Fault

Here is what gets lost in conversations about contracts and legal protection. The financial damage from a sub walking off a job, damaging work, or leaving a scope half-finished does not wait for a legal determination about fault before hitting the monthly numbers. The replacement costs, the rework costs, the schedule impact costs, all of it shows up in the job cost report immediately and stays there. A GC whose budget for the month absorbs that impact without any contractual mechanism for recovery is simply paying for someone else's failure out of their own margin, and that loss does not get reversed when the dispute eventually resolves, if it resolves at all.

The subcontract is the financial protection that converts an unrecoverable loss into a recoverable one. It does not prevent a sub from walking. It does not prevent a bad situation from becoming a difficult month. What it does is create the legal foundation for recovering costs that would otherwise just be absorbed, and it shifts the consequences of a subcontractor's failure toward the party that caused them rather than the party that was left standing on the job site when they left.

The Conversation That Never Gets Had

The reluctance to require written subcontracts on every trade comes from a few places. Long-term relationships where the informal arrangement has always worked fine. A sense that requiring a formal contract signals distrust of a sub the GC has worked with for years. The practical friction of getting every sub to sign something before mobilization when the schedule is already tight and the relationship feels solid.

All of that is understandable, and none of it changes what happens when a sub who has been working informally for three years decides this is the job where they are not going to finish. The history of the relationship does not create the contractual remedies that were never written down. The mutual trust that made the formal agreement feel unnecessary does not cover the cost of the rework. The schedule pressure that made it feel like there was no time for paperwork does not pause when the budget blows.

The contractors who eventually require written subcontracts on every job, without exception, almost universally got there the same way. They paid for the lesson once and decided they were not willing to pay for it again.

The Bottom Line

A subcontract is not a statement of distrust. It is the document that makes the relationship between a GC and a trade contractor work correctly when something goes wrong, and something eventually always does. The financial exposure of running a construction business on informal agreements is not theoretical and it is not small. It is the specific dollar amount that lands in the job cost report the month a sub walks off and the GC has no contractual basis for recovering what the situation cost them. Writing that protection into every subcontract before work begins is one of the few things in construction finance that costs almost nothing to do correctly and can cost an enormous amount to have skipped.