Enterprise DNA
Guide Intermediate Omni Ops

How to Manage Change Orders on Roofing Jobs

Use a clear roofing change-order workflow to document scope changes, get customer approval, update job records, and keep crews from proceeding too soon.

Sam McKay |
How to Manage Change Orders on Roofing Jobs

Why roofing change orders get messy

A roofing job rarely stays exactly as quoted. Once the crew removes shingles, they may find rotten decking, damaged flashing, a failed underlayment, or a condition around a chimney that wasn’t visible during the inspection. The work may be necessary, but the original estimate doesn’t automatically cover it.

The problem is often not deciding what needs to be done. It’s making sure the change is described, priced, approved, and recorded before the crew moves ahead.

When that process lives in a foreman’s text messages, a photo on someone’s phone, and a verbal conversation with the customer, details get lost. The crew may install extra materials before the office has approval. The customer may remember a different price. An invoice may reach them weeks later with work they don’t recognize.

For a roofing business, these are not harmless admin gaps. Across trades businesses, leakage can add up. Change orders are only one source of that leakage, but they’re a clear place to tighten the process because the work, approval, and price should all be traceable.

The fix is a simple operating rule: document the condition, send the change for approval, and update the job record before the crew proceeds.

Build a change-order workflow crews will follow

A process only helps if a foreman can use it from the job site without making five calls or writing a long report. Start with a small number of required steps and make the same sequence work for every change.

1. Pause the affected work

When the crew finds an issue outside the approved scope, the foreman should pause that portion of the work. They don’t necessarily need to stop the entire job. They do need to avoid completing the extra work before the customer has approved it.

For example, the crew may be able to keep working on the main roof while waiting for approval on a section of damaged decking. The job record should show what’s on hold and what can continue.

This distinction matters. A vague note like “found damage, call office” doesn’t tell dispatch, the project manager, or the customer what is happening. A useful note names the affected area and the next action.

2. Capture the condition at the roof

Ask the foreman to record a few specific details while the condition is visible:

  • The address and job number
  • The roof area or component affected
  • What the original scope included
  • What the crew found
  • Photos or short video showing the condition
  • The recommended repair and any reasonable alternative
  • Whether this affects the crew’s schedule or other work

Keep the description factual. “Decking is soft and deteriorated near the north eave” is more useful than “bad wood.” If the crew can estimate the affected area, record that too. If they can’t, mark the amount as an estimate that needs confirmation.

Photos should include enough context to show where the issue is, not just a close-up of a damaged board. A wide shot and a closer image often make the change easier for the customer and office to assess.

3. Convert the field note into a priced change

The office or project manager turns the field evidence into a clear change order. That document should state:

  • The work being added, removed, or changed
  • The reason for the change
  • The price, including any relevant quantity or unit basis
  • Any schedule impact
  • Whether the change affects warranty or other terms
  • The customer’s approval method and timestamp

Avoid sending a bare dollar amount with a photo. The customer needs to understand what the crew found and what the proposed work will do. If the exact quantity is uncertain, say how it will be measured and priced rather than presenting an estimate as a final amount.

For a closer look at the approval process, see how to manage change-order approvals. The details vary by job, but the core is the same: show the reason, price the change, and get a record of approval.

4. Get approval from the right person

Send the change order to the customer or authorized decision-maker listed on the job. Don’t assume that whoever is home, the tenant, or a site contact can approve a price change.

Use a method that leaves a durable record. A signed digital change order is useful, but a clear approval through the customer’s existing messaging channel may also work if it is captured in the job record and accepted under your company’s process. Your company should set its own rules for what counts as authorization.

The approval request should make the decision easy to understand. It should say what changed, why it changed, how much it costs, and whether waiting will affect the schedule. If the customer declines, record that decision and confirm how the crew will leave the affected area.

5. Update the job record before work resumes

Approval in a text thread is not enough if the office can’t see it. Before the crew starts the added work, update the job record with the approved scope, price, customer response, photos, and any schedule or material changes.

Then notify the foreman that the approval is recorded and the work can proceed. The message should identify the approved change, not just say “you’re good to go.” That keeps the field instruction tied to a specific scope.

This order prevents a common dispute: the crew remembers getting a verbal go-ahead, while the customer remembers only discussing a possible repair. A complete record connects the condition, proposal, approval, and work performed.

6. Close the loop at invoice time

At completion, compare the approved change order with the work performed and the invoice. If the actual scope or quantity changed again, document that difference and obtain any required additional approval.

Make sure the customer can see the change-order line item and connect it to the reason for the work. Don’t bury the added charge in a single total that looks different from the approved price.

For more on reducing missed revenue from unrecorded work, see how trades businesses can stop losing money on change orders. The habit that protects margin is not simply “charge for extras.” It’s keeping the estimate, approval, job record, and final invoice aligned.

What the workflow looks like on a real job

Say a crew removes shingles and finds a damaged section of roof decking near a valley. The original estimate covers the agreed roofing work but not replacing that decking.

The foreman pauses work on the affected area, takes a wide photo and a close-up, and enters a field note against the job. The note says where the damage is, what was uncovered, and how much decking appears affected. The crew can continue in other areas that don’t depend on this repair.

The office reviews the photos and prepares a change order. It describes the decking replacement, states the price and any schedule effect, and sends it to the authorized customer. The customer approves through the company’s chosen method. The approval and timestamp are attached to the job record.

The foreman receives a message naming the approved work and can proceed. After the repair, the crew records the completed quantity and adds a completion photo. The office checks that against the approved change before preparing the invoice.

No one has to reconstruct the decision from memory. The record shows what the crew found, what the customer accepted, and what was ultimately billed.

If you’re reviewing the software side of this process, roofing change-order automation covers ways to reduce manual handoffs. But software won’t fix a workflow that lets crews proceed before approval. Set the rule first, then make the system support it.

Where an AI agent can help

An AI agent shouldn’t decide whether a roof needs repair or approve a price on behalf of a customer. Those decisions belong with your people and your customer. The agent can take care of the repeatable handoffs around the decision.

A change-order process could work like this:

  1. The foreman submits a field note, photos, and the job number through the tool your team already uses.
  2. An agent checks that the required details are present. If the location, evidence, or proposed work is missing, it asks for that information before sending the request to the office.
  3. The office reviews the evidence and confirms the scope and price.
  4. The agent prepares the customer-facing request using the approved details, then sends it through the channel your company has chosen.
  5. The agent records the customer’s response and updates the job status. If there’s no response, it reminds the right person to follow up.
  6. After approval, it updates the job record and notifies the foreman that the change is cleared to proceed.
  7. When the work is marked complete, it prompts the team to add final notes and checks that the approved change is reflected in the invoice workflow.

The important control is that the agent does not invent a price, treat an unanswered message as approval, or mark work ready before the required approval is recorded. Your team defines those rules, and the agent follows them.

This process also touches the rest of the operation. A dispatch agent can support call handling and dispatch handoffs, depending on how your team configures it. An agent can support estimate follow-up according to your process. That’s useful when a separate repair or upgrade estimate comes out of a roofing visit and would otherwise sit without a next step.

If your process includes buying materials between jobs, automating parts ordering between jobs can help address another handoff that competes for the same office time.

What to measure before changing the process

Start with a short review of recent jobs, not a large software project. Look at a sample of completed roofing jobs and ask:

  • How many had work added after the original estimate?
  • How often was the approval recorded before the added work began?
  • How often did the final invoice match the approved change?
  • How much time passed between the crew reporting the issue and the customer receiving a request?
  • How many jobs needed an office call or text to clarify what the crew found?
  • How often did the customer question an added charge?

The answers show where the process is breaking. If approvals are usually timely but invoice details are missing, improve job closeout. If foremen report issues by phone and the office has to chase photos, improve field capture. If customers don’t respond, define who follows up and when.

Keep the review practical. You don’t need to track every possible metric to find the first fix. A consistent record of scope, approval, and completed work is a good starting point.

Put a dollar value on the gaps

The cost of a missed change order is not always the full price of the work. Some changes may not be approved, and some work may be included in a revised agreement. But when extra work gets done without a clear approval trail, the business can lose revenue, spend time resolving disputes, or delay payment.

Consider how many change orders your team handles in a month, what the typical added amount is, and how often the record is incomplete. Use your own job data rather than a generic industry number. Compare what was proposed, approved, completed, and invoiced.

That calculation sits alongside other operational leakage. Missed calls can cost a business potential work, depending on the circumstances. Owners and admins can also spend significant time routing crews and chasing details. Those are different problems, but they often share the same cause: important work depends on someone being available to catch and pass along information.

A process that captures changes at the roof and makes approval visible can protect margin without asking the owner to be the human switchboard for every job.

Start with an Omni Audit

An audit can be a working session to review how work moves through your business and identify handoffs to improve.

For roofing change orders, we’d look at how foremen report field conditions, who prices and sends a change, where customer approval is stored, how crews are notified, and how the final invoice is checked. We’d also look at nearby workflows, such as missed calls and estimate follow-up, to see where the same information gets lost.

Book a 60-min Omni Audit to map the process with your team. You can also see Omni for trades businesses and review how the audit applies to roofing and other field-service operations.

For a practical worksheet focused on calls that come in after hours, use the After-Hours Call Recovery Plan for Trades. It gives your team a way to review who answers, how urgent work is routed, and what happens when a caller doesn’t leave a message. You can also open the downloadable plan directly.

The worksheet is useful on its own, but the change-order process still needs a clear owner and a firm rule on approval before work proceeds. If you want to review both the field and office handoffs, book your 60-min Omni Audit. We’ll map the current process and identify the next operational change worth making. You can also return to the AI audit for trades businesses for more detail.