How to Manage Electrical Change Orders

A change order is not paperwork for its own sake. It is the mechanism that converts the inevitable gap between "what we agreed to build" and "what the job actually required" into revenue instead of loss. Contractors without a change order system still do the changed work — they just discover at job close that the margin is gone and the customer thinks the extras were included.

This guide covers the full process: what qualifies as a change order, where changes come from, how to measure their labor, material and schedule impact, how to price them at your required margin, the documentation and authorization discipline that makes them collectible, and the KPIs and weekly review that keep the system honest. One boundary up front: this is a business-process guide. It is not contract-law advice, and it does not address jurisdiction-specific contract requirements — for those, work with a qualified attorney in your state.

What Qualifies as a Change Order

The definition is shorter than most contractors expect: any work outside the written scope the price was built on. Not "anything the customer complains about" and not "anything over some dollar threshold" — anything outside the scope. The fixture count changed. The panel location moved. The wall that was supposed to be open is finished. The spec called for one thing and the building contains another.

The test your field team needs is one sentence: is this in the scope? If the answer is no, the work is a change, and changes follow the process — documented, priced, authorized — regardless of size. This only works if the original scope is written clearly enough to test against, which is why change order discipline begins at the estimate, not in the field.

Scope Creep: The Silent Margin Leak

Most contractors do not lose money on big, obvious changes — those get noticed. They lose it on scope creep: the accumulation of small extras, each individually too minor to stop the job over. "While you're here, can you add a receptacle?" "Can we move that to the other wall?" "Just swap these fixtures for the ones we bought." Each takes twenty minutes. Twenty of them take a full day of loaded labor that was never priced.

The countermeasure is cultural as much as procedural: technicians who recognize extras and flag them, a standing rule that even small changes get written down, and a company posture that treating changes professionally is good service, not nickel-and-diming. Customers respect clear scope far more than contractors fear. The sales process guide covers the scope conversation at estimate time — that is where creep is prevented, long before it has to be managed.

Where Change Orders Come From

Changes arrive through four doors, and each has its own handling:

• Customer-requested changes — additions, upgrades, relocations, revisions. The cleanest kind: the customer wants more, you price more, they approve more. Handle promptly and professionally; a well-managed requested change often improves both margin and the relationship.
• Field-discovered conditions — the opened wall reveals knob-and-tube, the conduit path is blocked, the existing panel cannot support the addition. These are nobody's fault and everybody's problem. Document the condition with photos before touching it, price the resolution, and get authorization.
• Design changes — revised drawings, spec updates, owner-directed design revisions mid-project. Compare the revision against the documents you priced, quantify the delta, and submit the change against the revision itself.
• Scope gaps and clarifications — the gray zone where your scope said one thing and the customer understood another. These are the hardest to collect and the cheapest to prevent: plain-language scope and stated exclusions at the estimate stage.

Labor, Material, Schedule and Equipment Impact

Every change touches more than the obvious line item. A disciplined impact review walks the full list before pricing:

• Labor — hours to perform the changed work at your loaded labor cost, including remobilization, working around finished areas, and the inefficiency of out-of-sequence work. Changed work almost never runs at the productivity of planned work; price it honestly.
• Material — the added material, plus waste, delivery, and the restock or return cost of anything the change makes obsolete. The material management guide covers purchasing and returns discipline.
• Schedule — the duration impact, stated in the change document. Schedule is part of the change, not a side effect; a price without a time impact is an invitation to argue about both later.
• Subcontractors and equipment — any sub or equipment impact, quoted from the sub in writing and carried through with your markup, exactly as in the base estimate.

On larger projects, also consider the cumulative effect: a dozen small changes can disrupt sequencing and productivity far beyond their individual hours. When that is real, say so in the documentation.

The Change Order Pricing Formula

Changed work gets priced with the same discipline as original work — which means it recovers its full cost, its share of overhead, and your required profit:

Added cost is labor at your loaded rate plus materials, equipment and sub impact. Overhead recovery and profit apply at the same rates your estimating system uses — if your base estimate divides cost by (1 − target margin), your change orders do too. The markup vs. margin guide covers why the divisor matters, and the Markup vs Margin Calculator runs the conversion.

Written Documentation and Authorization

The change order document itself is simple. It states what the change is, what it costs, what it does to the schedule, and it carries a signature or equivalent written authorization. That is the whole artifact. Everything else in this guide exists to make that one page accurate and collectible.

The rule that makes the system work is four words: authorization before work. Verbal approval, a nod on site, "the GC said go ahead" — none of these survive the invoice. Work performed without written authorization becomes, at billing time, a negotiation you have already weakened by completing the work. Stop-work on an unauthorized change feels confrontational the first time and routine the fifth; customers and GCs learn the process quickly when it is applied consistently.

Make authorization easy to give: a standard form the tech can send from the field, clear pricing, and a same-day turnaround. The companies that collect their changes are rarely the ones with the most aggressive paperwork — they are the ones whose paperwork arrives while the customer still remembers asking for the work.

Emergency Exceptions

One legitimate exception exists: conditions that threaten safety or property, where waiting for paperwork is not reasonable. The exception has its own discipline — document the condition with photos first, stabilize only what the emergency requires, notify the customer or GC immediately, and put the authorization in writing as fast as possible afterward.

The exception is narrow on purpose. "It was faster to just do it" is not an emergency; it is a habit that quietly converts your change order system back into free work.

Photos and Supporting Records

Photos are the change order's memory. Field-discovered conditions especially: the opened wall gets closed, the blocked path gets rerouted, and six weeks later the customer is looking at an invoice for work they cannot see. Photograph the condition before work, the work in progress, and the completed result. Attach them to the change record.

Supporting records extend beyond photos: the revised drawing the change responds to, the sub's written quote, the delivery ticket for the added material, the email where the customer asked for the upgrade. None of this is bureaucracy — it is the difference between a dispute about memory and a review of the record, and records win.

Pricing Methods

Conceptually, changed work gets priced three ways, and the right one depends on how well the work can be defined:

• Firm price — the change is well-defined, so you estimate cost, apply overhead and profit, and quote a fixed number. Best for both sides when the scope of the change is clear.
• Unit pricing — repetitive work priced per unit (per device, per foot, per drop) with quantities counted as installed. Useful when quantity is the only unknown.
• Time and material with a not-to-exceed — for conditions that cannot be scoped until opened, priced at stated rates with a ceiling and honest daily records. The ceiling is what makes this acceptable to the customer; the daily records are what make it collectible for you.

Whichever method applies, the formula underneath does not change: full cost, overhead recovery, required profit.

Allowances, Credits and Deducts

Changes run both directions. When the customer removes work, the deduct change order credits the estimated cost of that work — and here the discipline runs in reverse: the credit reflects what the removed work actually carried in cost, not the retail price of the line item. Margin and overhead treatment on deducts is a contract question; the business discipline is that deducts get documented with the same rigor as adds, because an undocumented deduct is just a quieter way to lose track of the job's economics.

Allowances deserve the same treatment: an allowance is a placeholder budget, and the reconciliation between allowance and actual selection is a change — up or down — priced and documented like any other.

Disputed Changes

Most change disputes are won or lost months before the argument, at the moment the documentation either did or did not happen. When a dispute lands anyway, the process is calm and sequential: pull the original scope, the change documentation, the authorization trail and the photos; restate what was agreed and what changed; and respond in writing, promptly, without heat.

Some disputes are genuine misunderstandings — resolve those generously; the relationship is worth more than the line item. Some are negotiations wearing the costume of a misunderstanding — those are what the records are for. Either way, a disputed change is a receivable until resolved, and the accounts receivable guide covers the follow-up cadence that keeps aged disputes from silently becoming write-offs.

Invoice Integration

Changed work must be visible as changed work when you bill it. Whether a change appears as its own line on a progress invoice, its own invoice, or a schedule-of-values amendment depends on the job — but it never disappears silently into the base contract amount. Silent folding is how change revenue vanishes and how customers end up genuinely surprised by a final number.

Invoice approved changes promptly — at the next billing cycle, not saved for the end. Prompt billing keeps cash moving (the cash flow guide covers why invoice speed matters), keeps the customer's memory fresh, and shrinks the end-of-job reconciliation to a review instead of a trial.

Job-Cost Tracking for Changed Work

In your job costing, changed work is its own line — revenue and cost tracked against the change, not absorbed into the base job. The reason is feedback quality: if change revenue and change cost blend into the base numbers, you can no longer tell whether the original estimate was accurate, and the estimate-to-actual loop that improves your bidding breaks. The job costing guide covers the estimated-vs-actual structure, and the Job Cost Calculator runs the comparison.

Tracking changes separately also answers a question most contractors cannot: are change orders actually profitable at your company? Priced correctly they often carry better margin than the base bid — but only the numbers can confirm it.

Change Order KPIs

The change order system reports five numbers, all simple, all per period:

• Change order revenue — total approved change revenue in the period
• Change order cost — the actual cost of performing changed work
• Change order margin — revenue minus cost, divided by revenue; compare it to your target margin
• Unapproved extra work — the value of extras performed without documented authorization. The leak indicator. If this number is more than trivial, your field process is giving away work the company will struggle to collect.

Approval rate tells you whether your pricing and documentation are landing; the other four tell you whether changes are a profit source or a leak. All five belong on the dashboard described in the KPI guide.

The Weekly Change Order Review

Change orders decay with time — memories fade, conditions get covered, customers move on. The weekly review is what keeps the pipeline current. Fifteen minutes, same time each week:

• Every open change: priced, submitted, awaiting authorization — and how long waiting?
• Anything performed in the field this week that was outside scope but not yet documented?
• Approved changes not yet scheduled or not yet billed?
• Any change aging toward a dispute, and what record do we have for it?

The review's real output is speed: changes priced while conditions are fresh, authorized while the customer remembers asking, and billed in the current cycle. This is exactly the kind of recurring management procedure the SOP guide recommends documenting — the change order workflow, from field identification to invoice, written as one standard procedure.

Common Mistakes

• Working first, paperwork later — the single most expensive habit in contracting. Authorization before work, every time, or accept that some of the work is a gift.
• Pricing changes at bare cost — changed work consumes overhead-bearing capacity; pricing without overhead recovery and profit guarantees the change loses money.
• Ignoring schedule impact — a price with no duration statement creates an argument about time the moment the project runs long.
• Treating small extras as free goodwill — scope creep is a margin leak with a friendly face. Document small changes; collect the legitimate ones; give away deliberately, never accidentally.
• Folding changes into the base contract — invisible on the invoice, invisible in job costing, and a broken estimate-feedback loop.
• No photos of discovered conditions — the wall closes, the evidence disappears, and the invoice becomes a memory contest.
• Letting submitted changes age — an unauthorized change three weeks old is a dispute in training. The weekly review exists to keep the pipeline moving.

Frequently Asked Questions