Commercial Electrical / Change Management
Find the extra work hiding in your project records.
ScopeGuards compares your electrical subcontract scope against RFIs, drawing revisions, field directives, meeting minutes, and daily reports—then assembles the evidence for potential change-order opportunities.
Built for commercial electrical contractors. Now selecting founding design partners.
Built for commercial electrical subcontractors
Reads the project record against contracted scope
Project manager makes the final decision
Four ordinary records. One potential change.
Illustrative example
- 01
Subcontract — Exhibit C
Executed 03/04
2" EMT feeder conduit
- 02
RFI-117
Response 07/02
Pathway requirement revised
- 03
Drawing E4.01
Rev 3 — 07/09
4" RMC shown at AHU-4 riser
- 04
Daily report
Field record 07/17
4" RMC pulled at AHU-4 riser
Read separately, every one of these looks routine. Read against the contracted baseline, they describe work your crews installed that nobody priced.
A change rarely announces itself.
There is no single document that says the scope grew. The evidence arrives across separate records, issued by different parties, on different days — a revision here, an RFI response there, a field note weeks later. Each one looks routine on its own.
Illustrative example — not a customer result.
- 1
Contracted work is established
Drawing E4.01 Rev 0 · Subcontract Exhibit C
The bid set and subcontract Exhibit C carry 2" EMT for the AHU-4 feeder pathway. This is the baseline your crews priced.
- 2
The requirement moves
RFI-117 response · Bulletin 04
An RFI response and an accompanying bulletin change the pathway requirement. Drawing E4.01 is reissued at Rev 3 showing 4" RMC.
- 3
The field confirms the work
Daily report, 07/17
Three weeks later the installed condition is recorded in a daily report. Nobody compares that entry back to the contracted baseline.
- 4
The records are connected
ScopeGuards analysis
ScopeGuards ties the baseline requirement, the revision that changed it, and the field record that confirms it into a single potential change with its sources attached.
- 5
The project team reviews commercial impact
Project manager review
Your project manager weighs the contract language, the notice window, and the commercial relationship, then decides whether to pursue it.
One potential change. Every supporting record.
A finding is only useful if a project manager can check it. Each one states the contracted requirement, what changed it, where the field record agrees, and which document every claim came from.
Illustrative example — not a customer result.
Potential change
AHU-4 feeder conduit increase
Original requirement
2" EMT
Exhibit C / E4.01 Rev 0
Revised requirement
4" RMC
RFI-117 / E4.01 Rev 3
Sources
- Subcontract — Exhibit CExecuted 03/04Baseline scope: 2" EMT feeder
- Drawing E4.01Rev 0 — 02/18Bid-set pathway shown
- RFI-117Response 07/02Pathway requirement revised
- Drawing E4.01Rev 3 — 07/094" RMC shown at AHU-4 riser
- Daily report07/17Installed condition recorded
Why it may be out of scope
The executed subcontract scope references the Rev 0 pathway. A later RFI response and Rev 3 issue show a different conduit type and size, and a field record indicates the revised condition was installed. Whether this constitutes compensable extra work depends on the contract documents and is for your team to determine.
Important date
Field record 07/17 → estimated notice window closes 07/23
Recommended action
PM review — confirm contract notice terms before acting.
Evidence package preview
- Baseline citation
- Exhibit C §2.4 / E4.01 Rev 0
- Change citation
- RFI-117 response / E4.01 Rev 3
- Field confirmation
- Daily Report 07/17
- Record span
- 02/18 – 07/17
- Sources attached
- 5 documents
The records your team already manages.
Nothing new to produce. ScopeGuards reads the same record types your project engineers file every week, and reads them against the contracted baseline instead of in isolation.
Illustrative example
- Exhibit C §2.4
Subcontracts & exhibits
Establishes the contracted electrical scope and notice terms.
- Div 26 05 33
Specifications
Material and installation requirements referenced by the contract.
- E4.01 Rev 3
Drawing revisions & bulletins
Reissued sheets where the requirement quietly moves.
- RFI-117
RFIs
Clarifications that frequently carry a scope consequence.
- FD-08
Field directives
Direction to proceed issued ahead of pricing.
- OAC #14, item 6
Meeting minutes
Verbal direction and agreements captured in writing.
- DR 07/17, crew 3
Daily reports
Field confirmation of what was actually installed.
- RE: AHU-4 pathway
Email & correspondence
Direction and acknowledgements outside formal channels.
The system flags. Your project team decides.
ScopeGuards identifies and documents potential changes. Your project team makes the final contractual and commercial decision.
Flagged
ScopeGuardsPotential change identified against the contracted baseline, with every source record cited.
Evidence reviewed
Project engineerThe baseline, the revision, and the field record are checked against the documents themselves.
PM decision
Project managerYour team decides whether to pursue, hold, or dismiss it — and owns that decision.
Start with a completed project.
A finished job is the fastest honest test: the outcome is already known, so you can judge whether what we surface would have mattered. We are working with a small number of contractors at this stage.
- Who this suits
- Commercial electrical subcontractors, complex negotiated work
- What you provide
- One completed project record set + workflow feedback
- What you receive
- Written findings, early access, direct influence on the product
- Commercial terms
- Agreed individually — no public pricing at this stage
- 1
Scoping call
We confirm the project type, the record set that exists, and whether a review is likely to be useful. Roughly 30 minutes.
- 2
Handling terms in writing
Before anything is transferred we agree which documents are in scope, how they move, who can access them, and how long they are retained.
- 3
Completed-project analysis
We run the contracted baseline against the project record and assemble the potential changes we can support with citations.
- 4
Findings review with your team
We walk through each finding with your project manager and executive. You keep the written findings regardless of whether you continue.
Project records deserve a clear handling process.
Subcontracts and field records are among the most sensitive documents on a job. We would rather understate this than overstate it, so below is what is in place today and what is not.
In place today
Encrypted in transit
Everything submitted on this site, including your project analysis request, is sent over HTTPS.
Requests are not publicly readable
Request records are stored with row-level security that denies public read, update, and delete access. They cannot be queried from the browser — only trusted server-side ScopeGuards code can read them.
No project files on the public form
The public form asks only for business contact and qualification details. Drawings, subcontracts, and job records are never requested or uploaded here.
Handling terms agreed first
If an analysis goes ahead, we agree in writing which documents are in scope, how they are transferred, who can access them, and how long they are retained — before anything is shared.
Planned — not yet available
- Role-based permissions
- Access and activity audit logs
- Single sign-on (SSO)
- Advanced administration controls
- Third-party security certifications and audits
- Direct integrations with project management systems
ScopeGuards holds no third-party security certifications and claims none. We are happy to walk through current practices in detail before any documents are discussed.
Built for the trade, not for a demo.
ScopeGuards is an early-stage company focused on one problem: extra work that is visible in the project record but never converted into a change order. It is being built specifically for commercial electrical subcontractors, and we are actively seeking contractor input to shape it.
We have no customer results, endorsements, or certifications to show yet, and we will not imply otherwise. What we can show is how the analysis works on a real completed project.
Precision over volume
A short list a project manager trusts beats a long list nobody opens. We would rather surface three defensible findings than thirty guesses.
Every claim cites a document
A finding without its sources attached is an opinion. Each one points back to the subcontract, the revision, the RFI, or the field record it came from.
The decision stays with your team
Contract interpretation, notice strategy, and client relationships are your call. We do not make entitlement determinations.
Fit the existing record process
Your team already files these documents. The work is reading them against the contracted baseline, not adding another system of record.
Questions from project teams.
Have a completed project worth reviewing?
Send us one finished electrical project. We agree handling terms in writing, run the contracted baseline against the record, and walk your team through what we find.