Trade scope is the total body of work assigned to a specific trade discipline on a project, which an electrical subcontractor is responsible for, distinct from scope of work, which specifically refers to the written contractual description of that responsibility. Trade scope is the substance; scope of work is the document that defines it.
Understanding a trade’s full scope requires pulling together information scattered across the entire drawing and spec set, not just reading a single dedicated section. Here’s how the electrical trade scope does and doesn’t apply to various sections and divisions. Most of the time, it’s in division 26 and electrical drawings, but fire alarm work could be in division 28. Low-voltage systems would be in their own division, and there can be coordination notes in the architectural or mechanical drawings that also reference electrical work.
This scattered nature is exactly why extracting and organising scope notes by trade, rather than relying on someone remembering every relevant reference across a large document set, adds real value during estimating and buyout. A complete trade scope picture assembled deliberately from every relevant source tends to be far more reliable than one built from memory or a quick read-through of the sheets someone assumes are relevant.
Trade scope boundaries between adjacent disciplines are where the most consequential ambiguity tends to concentrate, since a note that could reasonably belong to either of two trades needs a clear, deliberate assignment rather than being left for both trades to interpret independently, each potentially reaching a different, self-serving conclusion about whether it’s actually theirs.
A useful cross-check worth running during estimating: after assembling a trade’s full scope from every scattered source across the document set, compare that assembled picture against the trade’s own standard scope checklist to confirm that nothing standard for that trade was somehow missed. This comparison, done in both directions, tends to catch both project-specific additions that the checklist wouldn’t anticipate and routine items that were simply overlooked during the document review.
Trade scope definitions can shift between projects even for the same subcontractor, depending on how a given GC has chosen to package work for that specific job a sub who typically includes certain items on most projects might find that same item excluded from their scope on a project where the GC packaged it differently, which is exactly why relying on assumed standard scope rather than confirming this project’s actual scope of work is a persistent source of buyout friction.
