The four clauses that decide whether an electrical subcontract makes money

Every construction contract moves risk downhill. The owner pushes it onto the GC, and the GC passes what it can to its subs, usually through a standard form written for the GC's protection, not yours. None of that is unusual or improper. But it means the subcontract is less a description of your work than a decision about who pays when the work doesn't go to plan.

On most commercial jobs, the electrical subcontractor sits where those decisions meet. Electrical work starts underground and ends at energization and commissioning. It touches nearly every other trade, depends on long-lead equipment and the local utility, and is often specified by performance rather than fully designed. So when scope is vague, payment slows, someone gets hurt or the schedule slips, the electrical sub is rarely a bystander.

Four groups of clauses decide most of that exposure: scope, payment, indemnity and insurance, and schedule. This guide looks at how each one works on the page, how courts have treated it, and what an experienced sub does about it. Not every risk can be negotiated away. The goal is to know which ones you're carrying, and to make sure you're paid for them.

1. Scope: the risk you accept before you price it

Most scope disputes aren't about what the drawings show. They're about what the subcontract says you agreed to do around them.

How scope gets written against you

A few phrases do most of the work:

• "Per plans and specifications." Scope defined by reference to the full set of documents, rather than your proposal, picks up every note, detail and spec section that mentions electrical work, including ones you didn't price.
• "Complete and operational" or "fully functional." These turn a symbol on a drawing into an obligation to deliver a working system, including whatever design and components it takes. We've written about this one separately.
• "Including but not limited to" and "all work customarily performed by the electrical trade." Open-ended lists invite arguments about trade custom, which usually means arguments about who blinks first.
• "Coordinate with all trades." Reasonable as a duty to cooperate. Expensive if it's read as an obligation to absorb other trades' changes.

Where electrical scope gaps usually sit

The items below fall between trades or between documents on job after job. Each one should be settled in writing before you sign, either in your scope exhibit or in an exclusions list.

Design that moved onto you

Under the Spearin doctrine, which traces to a 1918 Supreme Court decision, an owner that provides detailed plans and specifications impliedly warrants that they're adequate. A contractor that builds what it was told to build isn't responsible for the design defects in it. Subcontracts often work around this with "review and verify" clauses, performance specifications and delegated design, and states don't apply the doctrine the same way. Texas, which long rejected it, codified similar protection for contracts signed from September 2021, but requires contractors to disclose defects they knew of or should have found with ordinary diligence. Washington allocates responsibility proportionally when bad design and bad workmanship combine.

The practical point: if the subcontract makes you responsible for design, it should say exactly which systems, provide a design fee or allowance, and address professional liability, which general liability policies usually exclude or cover only narrowly.

The change process is your real scope control

Even a well-written scope exhibit won't anticipate everything. What protects you is the change process, and how your field team actually uses it.

• Separate directives from change orders. If the GC can direct changed work before price is agreed, the subcontract should say that you'll be paid for it and how the price will be set.
• Treat RFI answers as potential changes. When an answer to a request for information adds work, price it immediately and in writing.
• Get time-and-material tickets signed daily, by someone the subcontract says can sign them.

Some courts have found that a GC waived a written-change-order requirement by ordering extra work and accepting it. Those are fact-heavy fights that are expensive to win. The cheaper strategy is a paper trail that makes the argument unnecessary. Extra work, no change order covers the field side.

2. Payment: who finances the job

Subcontractors finance construction more than most owners realize. You pay labor weekly and suppliers monthly, and you carry retainage for months. The payment clause decides how long you finance the project, and in the worst case, whether you're financing the owner's failure to pay at all.

Timing or condition?

The difference between the two common clauses is the difference between waiting and not being paid.

• Pay-when-paid sets the timing of payment. The GC pays you after it's paid by the owner. In Thos. J. Dyer Co. v. Bishop International Engineering Co. (6th Cir. 1962), the owner went insolvent and the GC argued it never had to pay. The court disagreed: reading the clause to require the sub to wait for a payment that might never come would be unreasonable. Courts that follow Dyer read pay-when-paid as giving the GC a reasonable time to collect, not a release from paying.
• Pay-if-paid makes the owner's payment a condition precedent to yours. If the owner never pays, the GC may never owe you, which shifts the owner's credit risk onto the sub.

Courts generally treat a clause as pay-if-paid only when the intent is clear and unambiguous, and the words "condition precedent" often decide the question. Ambiguity tends to be read against the party that drafted the clause.

The law depends on where the job is

Some states refuse to enforce pay-if-paid at all. California's Supreme Court held in Wm. R. Clarke Corp. v. Safeco Insurance Co. (1997) that a pay-if-paid clause is in substance a waiver of mechanics lien rights and unenforceable. New York's highest court reached a similar result in West-Fair Electric Contractors v. Aetna Casualty & Surety Co. (1995). Other states enforce these clauses when they're clearly written. On federal projects, courts have held that a payment bond surety can't use a pay-if-paid or pay-when-paid clause to defeat or delay a sub's Miller Act bond claim, unless the sub validly waived its bond rights.

Two further points apply almost everywhere. A GC generally can't rely on the clause when its own breach caused the owner to withhold payment. And many states have prompt payment statutes that set deadlines for paying subs once the GC has been paid, sometimes with interest or penalties. California's rules are here.

The clauses that compound the payment risk

The payment clause rarely works alone. Read it together with:

• Retainage, especially release tied to completion of the whole project rather than your scope.
• Pay application requirements, such as forms, deadlines and backup that can be used to reject an otherwise valid invoice.
• Set-off and backcharge rights, particularly clauses that let the GC withhold money on this job for disputes on another one.
• Lien waiver requirements, which should be conditional on payment actually received.
• Suspension rights, or the lack of them, when payment stops.

What to ask for

• A fixed payment deadline, such as 30 days after your invoice, regardless of upstream payment.
• If the GC insists on pay-when-paid, an outside date after which payment is due anyway.
• No language making owner payment a "condition precedent."
• A right to suspend work on written notice if payment is overdue, with time and cost for remobilizing.
• Information about the owner's financing. The AIA's standard general conditions give the GC a right to request reasonable evidence of the owner's financial arrangements. Ask for that evidence, or for the same right in your subcontract.
• No advance waiver of lien or bond rights, anywhere in the document.

If you can't change it, price it. A sub carrying pay-if-paid risk on a thinly capitalized owner's project is extending credit, and should be paid like a lender.

3. Indemnity and insurance: who pays when something goes wrong

The indemnity clause decides who bears the cost of an injury or property damage claim. The insurance exhibit decides whether that cost lands on an insurer or on your balance sheet. They have to be read together, because the most expensive gaps sit between them.

Three forms of indemnity

Most states have anti-indemnity statutes for construction contracts, but they differ widely. Some void only broad-form indemnity. Others go further. Texas, for example, has since 2012 voided most clauses that require a sub to indemnify the GC or owner for their own negligence, with an exception for injuries to the sub's own employees, and it voids additional-insured requirements to the same extent. Subcontract forms are often written to reach as far as each state allows, and multi-state forms sometimes reach further than the state where your job is.

The duty to defend can cost more than the claim

Indemnity usually comes with a duty to defend, and the two work differently. The duty to indemnify pays covered losses once liability is established. The duty to defend pays for lawyers from the moment a claim is made, based on what the claim alleges.

In Crawford v. Weather Shield Manufacturing (2008), the California Supreme Court held that a subcontractor had to pay a developer's defense costs under its subcontract even though a jury found the subcontractor wasn't negligent. California has since changed the rules for most commercial subcontracts signed from 2013 on (Civil Code section 2782.05). But the lesson travels: a defense obligation can be triggered by allegations alone, and in construction defect litigation defense costs can exceed the damages.

Where insurance and indemnity stop matching

The insurance exhibit typically requires additional insured status for the GC, owner and others, for ongoing and completed operations, on a primary and non-contributory basis, with a waiver of subrogation and often a per-project aggregate. Each requirement has a cost, and some can't be met by every policy.

Then there's the coverage for the indemnity itself. A standard commercial general liability policy excludes liability you take on by contract, but gives it back for an "insured contract," which includes taking on another party's tort liability. Two common endorsements change that:

• CG 24 26 limits that coverage to injury or damage caused in whole or in part by you.
• CG 21 39 removes it almost entirely.

If your indemnity is broader than your coverage, you're self-insuring the difference. And if you don't provide the additional insured coverage the subcontract requires, you can end up owing the GC what the insurer would have paid. The insurance page of your subcontract goes through each requirement.

What to ask for

• Indemnity limited to claims "to the extent caused by" your negligence or breach.
• Deletion of language such as "regardless of whether caused in part by a party indemnified."
• A defense obligation that's proportional, or reimbursed once fault is allocated.
• Your broker's written review of the indemnity clause and the insurance exhibit, together, before you bid.
• The cost of required endorsements, extended completed-operations coverage and higher limits priced into your number.

4. Schedule and delay: where weeks become dollars

Electrical work is often on or near the critical path from start to finish: underground and rough-in early, then gear, terminations, utility coordination, energization, testing and commissioning. When a project is late, the question of who caused the delay is often answered in the electrical sub's direction, and the subcontract decides what that answer costs.

Liquidated damages passed down

Owners set liquidated damages to reflect what a late building costs them, and courts generally enforce them when they're a reasonable forecast of harm that would be hard to prove later. GCs pass those rates down. A daily rate set for a hospital, data center or plant can exceed a subcontract's margin within weeks, and without apportionment the sub can be charged the full rate for a delay several trades caused. Why a low LD can be your friend explains the trade-off with consequential damages.

No damages for delay

A no-damages-for-delay clause gives you more time but no money when the owner or GC causes a delay. These clauses are enforced in most states, subject to exceptions. Courts commonly refuse to apply them to delays caused by bad faith or active interference, delays the parties didn't contemplate, delays so long they amount to abandonment, and fundamental breaches. New York's highest court set out an influential version of those exceptions in Corinno Civetta Construction Corp. v. City of New York (1986).

Some states go further by statute. Washington, Ohio and Kentucky restrict these clauses on public and private work, and several others, including Colorado, Louisiana, North Carolina and Virginia, restrict them on public contracts.

Notice is where most delay claims are lost

Subcontracts typically require written notice of a delay, and of a claim for time or money, within a short period, sometimes days, in a set form, to a named person. Many courts enforce those requirements strictly. The delay claims that fail aren't always the weakest ones. They're the ones that were noticed late, or not in writing.

Acceleration: directed or constructive

When a project falls behind, the GC may order you to add crews, work overtime or work out of sequence. A written order to accelerate is the easier case: it's a change, and the fight is about the amount.

The harder case is constructive acceleration. You're entitled to more time, you ask for it, the GC refuses or doesn't answer, and you're told to hold the original date. Boards and courts, particularly on federal work, generally look for an excusable delay, a timely request for more time, a denial or no response within a reasonable time, an order to finish on the original schedule, notice from you that you treat that order as a change, and added cost actually incurred. Skip the request or the notice and the extra effort can be treated as voluntary.

What to ask for

• Liquidated damages only for delay you cause, apportioned among responsible parties, capped as a percentage of your subcontract and stated as the only remedy for delay.
• A mutual waiver of consequential damages at least as broad as the one in the prime contract.
• Time extensions for owner and GC delay, weather, utility delay and documented supplier delay on long-lead equipment. Long-lead gear and escalation covers the supply side.
• Realistic notice periods, counted from when you knew of the delay, with email to the project manager accepted as notice.
• A written directive and cost agreement before you accelerate, and a written request for time, with a reservation of rights, before you accelerate on your own.

Reading the subcontract like a risk manager

Experienced subs don't try to win every clause. They sort each risk into one of four responses: strike it, limit it, price it, or manage it in the field.

Two habits make the difference once the contract is signed. First, turn the subcontract into a one-page summary for the project manager and foreman: notice deadlines, who can authorize changes, payment application dates, insurance requirements and the claim process. Second, revisit the four risks at every job start-up and closeout meeting, while there's still time to act on them.

None of this requires a confrontational negotiation. A short, specific redline on the clauses that matter reads as professional, and GCs generally prefer subs who raise risk early to subs who raise it in a claim. Which redlines to fight for covers how to prioritize.

For general information only, not legal advice. The law on each of these clauses varies by state, and the contract language controls. Get advice on the specific subcontract and project before you sign.