Electrical Variation Orders: How to Document and Claim

What Is an Electrical Variation Order?

An electrical variation order (EVO), also called a change order or variation claim, is a formal document that records a change to the agreed scope, specification, or programme of a contract — and the associated adjustment to the contract price. For panelboard and switchgear manufacturers supplying to electrical contractors or head contractors, variations are common and can have a significant impact on project profitability.

Variations arise for many reasons: design development that wasn't complete at tender, client-directed scope changes, specification revisions, or discovery of site conditions that change the product requirements. Not all variations increase the contract price — some reduce scope and may result in a price reduction (an omission). The key principle is that any change from the agreed contract scope should be formally documented and agreed, in either direction.

When to Raise a Variation

The rule is simple: raise a variation whenever something falls outside what was agreed at contract award. In practice, the triggers for panelboard and switchgear manufacturers include:

• A revised SLD or specification issued after award — even minor changes can affect circuit counts, device ratings, or busbar sizing
• Additional boards or circuits added to scope post-award — common when design development continues after contract execution
• A change in specified manufacturer or product type — e.g., switching from a specified brand to a different one at client request
• Additional documentation requirements — test reports, third-party certification, as-built drawings not in original scope
• Accelerated programme requirements — overtime, expedited material orders, or priority manufacturing
• Changes to IP rating, Form separation, or enclosure finish — post-award specification upgrades
• Material price escalation clauses — if the contract includes a price variation clause for material escalation

What should not be claimed as a variation: errors or omissions in your own quote, risks that were known and included in the contract risk allocation, or scope that is reasonably implied by the contract documents even if not explicitly stated.

How to Document a Variation

1. Identify the Change Clearly

Every variation claim must start with a clear, unambiguous description of what changed. This means referencing:

• The original document (e.g., "SLD Rev A dated 15 January 2026")
• The revised document (e.g., "SLD Rev B dated 10 March 2026")
• The specific change (e.g., "MSB-01 incomer rating increased from 800A to 1000A, and two additional 125A outgoing circuits added")

Vague variation descriptions like "design changes to MSB" are harder to approve and easier to dispute. Specificity makes claims faster to process and harder to reject.

2. Quantify the Cost Impact

The cost breakdown of a variation claim should follow the same logic as the original quote — broken into:

• Material delta: the cost difference between original BOM and revised BOM (include supplier quotes for material additions)
• Labour delta: additional assembly, wiring, testing, and documentation hours at the applicable rate
• Subcontract costs: any additional third-party testing, certification, or specialist labour
• Overhead recovery: overhead applied to direct costs at the contract rate
• Margin: applied at the contract margin rate

If the contract specifies a schedule of rates or agreed labour rates for variations, use those. If not, use your standard rates and be prepared to justify them.

3. State the Programme Impact

Variations don't just affect cost — they can affect delivery. If a scope change affects your delivery date (e.g., new materials require 4 weeks additional procurement lead time), state this clearly in the variation claim. Failing to notify the client of programme impact at variation stage can be used against you if deliveries are delayed later.

4. Submit Within the Contract Timeframe

Most contracts specify a notice period for variation claims — typically 5–20 working days from the date the varied instruction is received. Missing this window can make the variation unenforceable, even if the underlying change is legitimate. Track incoming instructions carefully and raise variation notices promptly.

Common Variation Mistakes

Absorbing Changes Without Documentation

The most costly mistake is proceeding with changed work without documentation. In the moment, it often feels easier to just absorb a small change rather than creating paperwork. Over a project lifecycle, multiple absorbed "small changes" can cumulatively represent significant margin erosion. Establish the practice of documenting every change, regardless of perceived size.

Claiming the Wrong Basis

A variation claim that's poorly justified — for example, claiming a variation for something that was reasonably implied by the original scope — creates friction and damages client relationships. Only claim what is genuinely out of scope. A smaller, well-justified claim is more likely to be paid in full than a larger claim that the client perceives as opportunistic.

Not Getting Written Approval

Most contracts require written approval before proceeding with varied work. If you proceed on verbal instruction and the client later disputes the variation, your position is weakened. Where proceeding on verbal instruction is unavoidable (e.g., programme urgency), document it immediately in writing to the client: "Following our phone call with [name] on [date], we will proceed with [change]. We confirm this is a variation to contract scope and will submit a cost claim within [x] days."

Losing Track of Revision History

Panelboard and switchgear projects often involve multiple drawing revisions. Without a clear system for tracking which revision you quoted against and what changed between revisions, it becomes very difficult to accurately price variations — and easy to miss scope additions or double-count them. Maintaining a revision log for each project, recording what changed at each revision, is essential for both variation management and future dispute avoidance.

Structuring Your Variation Register

For any project with likely variation exposure, maintain a variation register — a live log of all potential and submitted variations. At minimum, track:

• Variation number (sequential)
• Date the change was notified or discovered
• Description of the change
• Amount claimed
• Status (draft, submitted, approved, disputed, rejected)
• Approved amount (if different from claimed)

A live variation register gives you a clear picture of the true contract value at any point in the project — which is important for both commercial management and cash flow forecasting.

Conclusion

Variation management is as important to project profitability as the original estimation. Panelboard and switchgear manufacturers who document changes promptly, price them accurately, and claim them assertively recover the true cost of project complexity. Those who absorb changes informally find that their margins tell a very different story to their original win rate. Build the discipline of variation documentation into your project delivery process — it pays for itself many times over.