Common Electrical Bid Exclusions GCs Should Review
An authoritative checklist of electrical exclusions that most often leave the GC holding cost after buyout, with primary sources and what to verify before you award.
Author
Ido Gedanken, CEOPublished

- Type
- Guide
- Read
- 8 min
- Published
On this page
- Why electrical exclusions bite harder than other trades
- The review list GCs should run on every electrical proposal
- Temporary power: assign it or you own it
- Div 26 / 27 / 28 boundaries: fire alarm, low voltage, and controls
- OFCI, mechanical interfaces, and site work
- Testing, commissioning, and closeout
- How to run the electrical exclusion pass
- Lock findings into the subcontract scope letter
- Where Piper fits
- Sources
Electrical proposals bury risk in exclusions and qualifications more reliably than almost any other trade package. The cover price can look competitive while temporary power, fire-alarm programming, OFCI connections, testing, and low-voltage pathways sit outside the number. For GC estimators and precon managers leveling Division 26 packages on commercial, institutional, and industrial work, the job is not to collect a longer exclusion list. It is to match each carve-out back to the drawings, the specs, and a funded owner before the carry locks.
This guide sits inside bid leveling and pairs with the general method in how to review subcontractor exclusions and qualifications. Use it as the electrical-specific pass once proposals are in and addenda acknowledgments are confirmed.
Why electrical exclusions bite harder than other trades
Three structural facts make electrical different from a clean single-trade package.
The CSI map splits what estimators still call "electrical." CSI MasterFormat puts facility power and lighting in Division 26, communications in Division 27, and electronic safety and security (including fire detection and alarm) in Division 28, with integrated automation interfaces often living in Division 25. Older project manuals still echo the pre-2004 Division 16 habit of treating anything with conductors as one electrical sub's problem. When the package language is vague, three specialty scopes and one power contractor all invent different boundaries.
Division 01 temporary work collides with permanent Division 26. Temporary power and lighting are general requirements work until someone assigns them. Electrical subs routinely price permanent installation only, then treat construction power as GC-furnished unless the invitation states service size, panel locations, duration, and protection requirements.
Interface items live between mechanical, controls, civil, and owner procurement. Motor starters, VFDs, disconnects, BAS handoffs, trench and ductbank, and owner-furnished switchgear connections are classic double-exclusions: both trades assume the other has it.
Exclusions vs qualifications. An exclusion omits work from the price. A qualification keeps the work in, but only if an assumption holds (lead times, OFCI delivery, design maturity, labor limits). Both belong as separate rows on the leveling sheet. See tabulation vs leveling vs evaluation.
The review list GCs should run on every electrical proposal
Use this as a forced checklist against the proposal, the Division 26 / 27 / 28 sections, and the drawings. Silence on a line is not agreement. Silence is an open assignment.
| Exclusion or gap | Why it shows up | What to verify before you award |
|---|---|---|
| Temporary power and temporary lighting | Permanent install priced; construction power treated as GC general conditions | Service size, panel locations, circuit distribution by floor or zone, duration, who owns relocation moves |
| Ground-fault protection on temporary receptacles | OSHA requires protection; contract often fails to name who provides it | GFCI or assured equipment grounding conductor program per OSHA 1926.404(b)(1), and who maintains it for other trades |
| OFCI equipment connections | Owner buys switchgear, generators, kitchen or medical equipment; sub prices cable only or nothing | Receiving, setting, terminations, grounding, testing, and who owns mismatches to the drawings |
| Fire alarm and life-safety boundary | Div 28 specialty vs Div 26 rough-in; head-end programming often carved out | Conduit and boxes vs devices vs programming vs commissioning per NFPA 72 and the project sections |
| Low-voltage pathways and devices | Data, AV, security, and nurse call priced by others or excluded entirely | Rough-in only, cable plant, devices, or complete system; Div 27 vs Div 26 ownership |
| Lighting controls and BAS interface | Fixtures in electrical; programming and network handoff in controls | Who furnishes controllers, who programs scenes, who integrates to Division 25 / BAS |
| Motor starters, disconnects, and VFDs | Mechanical and electrical both exclude field-installed gear | Factory vs field, who furnishes, who wires power and control, termination point at the unit |
| Emergency power and transfer | Generator, ATS, fuel, and field conditioning split across packages | Connections, ATS ownership, fuel system, startup support, and who owns paralleling or load bank testing |
| Underground and site electrical | Site lighting and ductbank sit on civil sheets; building electrician excludes outside the footprint | Trench, bedding, backfill, pull boxes, parking-lot lighting, utility coordination |
| Third-party testing and studies | Megger, ground-fault testing, thermography, arc-flash study, and labeling called in Div 01 and Div 26 | Which tests are in the electrical price, which are by engineer or CxA, who pays for retests |
| Commissioning support vs equipment startup | Startup of own gear is not formal Cx participation | Hours for energizing, breaker resets, witnessing, and CxA meetings on healthcare, lab, and mission-critical work |
| Penetrations, sleeves, and firestopping | Everyone cores; nobody patches or firestops unless the package says so | Who cuts, who sleeves, who firestops, who patches finishes at electrical penetrations |
| BIM / coordination drawings | Clash detection treated as "by others" | Required LOD, who owns conduit coordination, and whether electrical BIM is a deliverable or an option |
| As-builts, O&Ms, and closeout | Submittals priced; record documents and warranty packages not | As-built markups, O&M manuals, training, spare parts, and permit closeout ownership |
Temporary power: assign it or you own it
Temporary construction power is one of the most common electrical carve-outs because it is easy to leave unnamed. If the solicitation does not state temporary service size, panel locations, distribution by floor or zone, duration, and relocation responsibility, many electrical proposals will price only the permanent system.
Ground-fault protection is not optional coloring on that package. Under OSHA 1926.404(b)(1), employers on construction sites must provide ground-fault protection for temporary receptacles, either with GFCIs or an assured equipment grounding conductor program. OSHA interpretations make clear that the duty is not limited to a single voltage class, and that each employer remains responsible for protecting its own people even when another contractor installs the temporary service. In leveling language: name who installs temporary power, who maintains GFCI or the assured grounding program, and how other trades are notified when protection is or is not present.
On hard-bid commercial work, temporary power often lives in GC general conditions until buyout, then migrates into the electrical subcontract without a matching price. On CMAR and design-build, the same gap appears when early packages are awarded before temporary requirements are quantified. Either way, an unassigned temporary system becomes GC cost.
Div 26 / 27 / 28 boundaries: fire alarm, low voltage, and controls
CSI's split is the authority here, not field habit.
- Division 26 covers electrical power systems: distribution, lighting, grounding and bonding, generators, and related power work results.
- Division 27 covers communications.
- Division 28 covers electronic safety and security, including fire detection and alarm.
- Division 25 covers integrated automation interfaces that lighting and equipment often touch.
Industry writing on the MasterFormat expansion has documented the practical effect for decades: fire alarm and related electronic systems can stand as independent scopes rather than riding inside the electrical contractor by default. That is good for owners who want specialty vendors. It is dangerous for GCs who still solicit "electrical complete" and then discover that devices, programming, and commissioning were never in the Division 26 number.
On every electrical proposal, force written answers to:
- Does this bid include Division 28 fire alarm devices, head-end, programming, and testing, or only Div 26 rough-in?
- Are Division 27 pathways, cable, and devices included, excluded, or limited to empty conduit and boxes?
- Who owns lighting-control programming and the BAS / Division 25 handoff?
If two specialty bids and one power bid all exclude the same interface, you have a scope gap, not three aligned proposals.
OFCI, mechanical interfaces, and site work
Owner-furnished, contractor-installed equipment is a classic electrical qualification trap. The proposal includes terminations "if equipment is delivered to the electrical room on schedule and matches the approved shop drawings," then excludes receiving, setting, grounding electrode connections, or corrective work when the delivered gear differs from the drawings. List each OFCI item and the connection scope before award. On institutional and industrial projects, switchgear, generators, and process equipment are where this bites hardest.
Mechanical interfaces need the same written boundary. Motor starters, disconnects, and VFDs may be factory-mounted on the mechanical unit, field-furnished by mechanical, or field-furnished by electrical. Control wiring may sit with the controls contractor. If both mechanical and electrical proposals exclude field disconnects, the gap is already funded by nobody.
Site and underground electrical often appear only on civil sheets. Building electricians exclude work outside the building footprint; site contractors exclude electrical. Confirm trench, ductbank, pull boxes, parking-lot and site lighting, and utility coordination against the actual drawing set, not against the Division 26 table of contents alone.
Testing, commissioning, and closeout
Division 01 and Division 26 both reference testing. That overlap is exactly why third-party testing drops out of lump-sum electrical bids. Megger tests, ground-fault testing, thermographic scanning, coordination studies, arc-flash analysis, and labeling are frequently treated as engineer or CxA scope unless the electrical package names them. Do not assume they are buried in the permanent install price.
Separate equipment startup from commissioning support. Startup means the electrical contractor functionally checks its own gear. Commissioning support means technicians available to energize panels, verify connections, reset breakers, and witness owner or CxA procedures. On healthcare, laboratory, and mission-critical work, that delta is real schedule and real cost. Price it or assign it.
Closeout follows the same pattern. Product submittals can be in while as-builts, O&M manuals, training, and warranty packages are not. AIA and ConsensusDocs subcontract forms are built to flow prime-contract obligations down to the subcontractor. If the owner contract requires record documents and your electrical scope letter is silent, the GC still holds the obligation.
How to run the electrical exclusion pass
- Freeze the document basis. Drawing dates, specification sections for Divisions 01, 25, 26, 27, and 28, and addenda numbers. Confirm which addenda each electrical bidder acknowledged.
- Read the full proposal, not the summary page. Exclusions hide in appendices, assumptions, and "clarifications" that are really carve-outs.
- Run the comparison table above as a matrix row set. One row per exclusion family. Columns for each bidder plus a "funded by" column (electrical, specialty, mechanical, GC carry, owner).
- Classify impact. High-impact items change award rank, schedule, or six-figure exposure. Medium items move the comparison. Low items are boilerplate already covered by Division 01 or the prime contract. Spend bid-day hours on high and medium.
- Normalize before you trust the low number. Add-backs, plugs, and clarifications belong in evaluated cost, not as mental notes. Use carry number methodology so submitted bid, evaluated cost, and carry stay distinct.
- Decide clarify, plug, or accept-and-carry. Silence is not a decision. Write the decision while leverage still exists.
| Decision | When it fits | What you must record |
|---|---|---|
| Clarify / add price | Bidder can still revise before award | Question sent, answer received, revised number |
| Plug into GC or another trade | Work is real and market will not reprice in time | Basis, quantity source, confidence, owner of the plug |
| Accept exclusion and carry | Risk stays with GC by design | Why, dollar treatment, buyout watch item |
| Reject / rebid package | Boundary is too broken to level | What the new invitation must name |
Lock findings into the subcontract scope letter
Leveling that dies in a spreadsheet does not protect the job. Migrate inclusions, exclusions, and resolved qualifications into the subcontract scope exhibit before award. AIA A401 and ConsensusDocs 750 both use flow-down structures so prime obligations bind the subcontractor through the subcontract. Industry practice is blunt on this point: lead-letter exclusions that never migrate into the scope sheet are weak protection when the argument starts.
Also know your conflict rules. AIA A201 treats the contract documents as complementary ("what is required by one shall be as binding as if required by all") and does not ship a built-in order-of-precedence ladder among drawings and specifications. ConsensusDocs forms typically do include precedence language. When electrical drawings, Division 26 specs, and a specialty Division 28 package disagree, the GC needs a documented interpretation path, not an assumption that "the electrical sub will figure it out."
Where Piper fits
Electrical exclusion review fails when the reading never finishes. The judgment is knowing which carve-out changes the carry. The failure mode is running out of hours before every proposal is matched to Divisions 26, 27, 28, and the temporary-power notes in Division 01.
Piper is the AI operating system for preconstruction. It builds an evolving understanding of the project from the drawings, specifications, addenda, and your company's scope standards, then uses that same understanding across scope, leveling, and review. On an electrical package, that means exclusions, silent items, and trade-boundary gaps can surface with the clause or drawing behind them, so the estimator spends bid-day hours deciding clarify vs plug vs carry instead of rediscovering the same Div 28 boundary on every pursuit. The estimator keeps control of status, adjustments, and the commitment.
For the surrounding workflow, start with how to review exclusions, bid leveling, and final bid review.
Sources
- Construction Specifications Institute (CSI), MasterFormat divisions for 01 General Requirements, 25 Integrated Automation, 26 Electrical, 27 Communications, and 28 Electronic Safety and Security. Orientation summaries: Division 26, Division 28.
- Security Info Watch, The Future of Bidding and Quoting Fire Alarm Systems (historical Div 16 to Div 26 / Div 28 split and independent fire-alarm bidding).
- Occupational Safety and Health Administration, 29 CFR 1926.404 and interpretations on ground-fault protection for construction (15 May 2002, 7 Feb 2005).
- National Fire Protection Association, NFPA 70 (National Electrical Code) for grounding and bonding practice (commonly Article 250) and NFPA 72 for fire alarm system requirements, as adopted by the project and AHJ.
- American Institute of Architects, AIA A201 General Conditions §1.2.1 (complementary contract documents) and AIA A503 Guide for Supplementary Conditions (model precedence language when an owner insists on a hierarchy).
- American Institute of Architects, AIA A401 (contractor-subcontractor agreement) and ConsensusDocs 750 (constructor-subcontractor agreement) on subcontract flow-down of prime obligations.
- CSI Resources, Kevin O'Beirne, Interpretations and Clarifications Part 3 – Order of Precedence Clauses (AIA / EJCDC complementary-documents approach vs forms that include precedence).
FAQ
Is temporary power always the electrical sub's scope?
No. It is often GC general conditions unless the invitation assigns service size, distribution, duration, and protection. If nobody owns it in writing, the GC owns the cost later.
Does Division 26 automatically include fire alarm?
Not under current MasterFormat practice. Fire detection and alarm live in Division 28. Confirm rough-in vs devices vs programming vs commissioning in writing for every package.
What is the difference between an exclusion and a qualification on an electrical bid?
An exclusion removes work from the price. A qualification keeps work in under conditions (OFCI delivery, design freeze, labor limits). Both need a row on the leveling sheet and a decision before award.
When should we rebid the electrical package instead of plugging gaps?
Rebid when the Div 26 / 27 / 28 boundary or temporary-power assignment is too broken to level fairly, or when add-backs would rewrite the low number past your confidence in the market response.
Where do these findings belong after leveling?
In the subcontract scope letter (or equivalent exhibit), not only in the leveling workbook. Flow-down forms only help if the resolved scope is actually attached to the subcontract.
Related reading
How to review subcontractor exclusions and qualifications
Subcontractor bids bury risk in exclusions and qualifications. Identify them, classify impact, normalize the comparison, and lock decisions into the subcontract scope letter before award.

Construction bid leveling: a practical guide for GCs
How to level subcontractor bids across design-bid-build, CM-at-risk, design-build, and progressive design-build, and why the same spreadsheet does not work for all of them.

How to spot scope gaps before you carry the number
A practical review sequence for finding missing scope, duplicated cost, and unresolved trade boundaries while there is still time to price them properly.

How to set a carry number you can defend
The method for getting from a submitted subcontractor bid to the number that actually goes in the estimate, including evaluated cost, expected-value risk pricing, and the duplicate-contingency trap.

Construction scope generation: a practical guide for GCs
How general contractors turn drawings, specifications, addenda, and company standards into trade scopes a subcontractor can price, an estimator can trace, and a senior reviewer can challenge.

Final bid review: a QA/QC playbook for general contractors
The pre-submission gate between a working estimate and a price you are prepared to submit, explain, contract around, and build. Workflow, checklists, review lanes, delivery-method playbooks, and the KPIs worth tracking.

Piper removes manual review from the critical path and brings project data, company knowledge, and expert checks into every preconstruction decision and workflow
See Piper on your project
Bring a current or completed project and see how Piper saves review time, surfaces scope gaps, and applies your company's knowledge.