A roofing change order often starts with a crew uncovering something nobody could see from the ground. The decking is soft. There are two layers of shingles instead of one. The flashing is damaged behind the siding. Work needs to change, but the customer needs to understand what changed, what it will cost, and what happens if they say no.

The manual process is usually a string of interruptions. A crew lead calls the office. Someone tries to reach the owner. The owner checks a photo between other calls, works out a price, and asks the office to send a text. The customer may not respond. The crew waits, moves to another task, or carries on without a clear record of authorization.

You can automate much of that handoff without taking the decision away from your team. The goal is a consistent process that turns a field update into a clear change order, gets approval by text or email, and keeps proof of authorization with the job before extra work begins.

Why change order approvals slip

Roofing work brings plenty of conditions that are hard to confirm before tear-off. A signed estimate may cover a straightforward replacement, but it can’t reliably account for every hidden repair. When the crew discovers a problem, the office needs enough detail to make a decision and explain it in plain language.

The process gets messy when that information arrives across channels:

A crew lead calls while the owner is handling dispatch.
Photos sit in a text thread that isn’t attached to the job.
The office prices the work from memory or an old estimate.
A customer gets a vague message such as “we found more damage.”
The crew starts extra work before anyone can find written approval.
The final invoice includes work the customer doesn’t remember authorizing.

That last point can turn an ordinary repair into a dispute. Even when everyone acted in good faith, an unclear description or missing timestamp makes it harder to settle the question.

Change order automation addresses the handoff, not the underlying judgment. Your crew still identifies the condition. Your pricing rules and people still determine what should be offered. The workflow makes it easier to get the right information, explain the options, and record the customer’s decision.

A roofing change order workflow, step by step

A useful workflow starts with a structured field update. It shouldn’t ask a roofer to fill out a long form while standing on a roof. Make it quick enough to complete on a phone, with a few required details and a way to add photos or a short voice note.

1. Capture the condition at the job

The crew lead opens the job and submits a change order request. The form or agent asks for:

The job identifier and address
The affected area, such as a roof plane, valley, eave, or penetration
What the original scope covered
What the crew found
The proposed additional work
Photos, and optionally a short video
Whether the condition is stopping work or creating an immediate safety concern

For example, “soft decking” is a start, but it isn’t enough to price or explain the change. A stronger update might say that the crew found deteriorated sheathing around a chimney, include two photos, and identify the approximate area that needs replacement.

The workflow should flag missing details before the request reaches the office. That can be as simple as prompting the crew lead to add a photo or clarify the affected area. The point is to avoid a second round of calls to collect basic information.

2. Turn the update into a clear scope

The workflow organizes the field details into a draft the office can review. It separates the observed condition from the proposed work, so the customer can see why the contract scope needs to change.

A customer-facing description might read:

During tear-off, the crew found deteriorated roof sheathing around the chimney. The existing proposal does not include sheathing replacement. We recommend removing and replacing the affected section before installing the new roofing materials.

That explanation gives the customer context without burying them in trade shorthand. It also avoids claiming more than the crew has confirmed. If the affected area is an estimate, say so and explain how the final quantity will be recorded.

3. Apply approved pricing rules

Next, the workflow builds a draft price from your rate card, job rules, or other approved pricing source. For example, it may apply a per-sheet price for sheathing, a set charge for a specific flashing repair, or an approved labor and material rate.

The workflow shouldn’t invent prices or make up a scope. It should use your current rules and send exceptions to a manager. You might require review when:

The repair isn’t covered by a rate card.
The quantity exceeds a set threshold.
The price would take the job below its minimum margin.
The customer’s contract has special approval requirements.
The work affects schedule, warranty, or other scope in a material way.

The draft should show the added work, price, any schedule impact, and what the customer is being asked to approve. If you want to offer options, show them separately. For example, distinguish a necessary repair from an optional upgrade rather than bundling both into one amount.

For more on the business case and common process gaps, see how roofing teams can stop losing money on change orders.

4. Send the approval request by text or email

Once an authorized person approves the draft, send the customer a message through the channel they already use. A text can carry the short explanation and a secure link to the full change order. An email can provide the same information with a more detailed document attached or linked.

The approval page should make the decision straightforward. It should show:

The original condition or reason for the change
The work being added or changed
The additional price and applicable tax
Any schedule effect
A clear approve or decline option
A way to ask a question

Avoid treating a read receipt, a vague “OK,” or a crew member’s recollection as a reliable substitute for explicit authorization. Set up an affirmative approval action that captures who approved, what version they approved, and when.

You can see Omni for trades businesses to understand how an audit can map this workflow to your current tools and approval rules.

5. Record the decision before extra work begins

When the customer approves, the workflow updates the job record with the change order and the approval details. The record should include the approved scope and price, customer identity, date and time, delivery channel, and any related photos or messages.

If the customer declines, the system should record that too and notify the right person. The job record can then show the next action, such as calling the customer to discuss an alternative or continuing only with the original scope.

A useful operating rule is simple: no extra work begins until the required approval is recorded. Your process should define who can authorize exceptions, particularly when there’s a safety issue or a need to protect the property from further damage. Don’t leave that decision to an improvised text exchange.

What the agent does, and what your team decides

A change order agent can collect the crew’s update, check whether required details are missing, prepare a customer-ready draft, route unusual pricing for review, send the approved request, and store the customer’s decision. It can also remind the office when an approval is still outstanding.

Your team remains responsible for the parts that need trade and business judgment:

Confirming that the proposed repair is appropriate
Deciding which pricing rules apply when the case is unusual
Reviewing high-value or high-risk changes
Handling customer questions and exceptions
Deciding whether work can proceed in a genuine emergency

That distinction matters. Automation should shorten the path between “we found a problem” and “the customer has made an informed decision.” It shouldn’t quietly commit your business to work or pricing nobody approved.

The same principle applies to adjacent admin work. An Estimate Follow-Up Agent can help keep sent estimates from disappearing without a next step. A 24/7 Dispatch Voice Agent can answer calls, qualify urgent jobs, book a slot in the dispatch tool, and text a confirmation. Those are separate workflows, but they can reduce the interruptions that slow down change order approvals.

Connect the workflow to your job records

Before you automate, decide where the official change order lives. If a draft is created in one system, approved by text, and stored only in someone’s inbox, you still have a fragmented process.

Map each step to the systems your office already uses:

Job management: Match the request to the correct customer and project.
Photos and field notes: Store evidence with the job rather than in a personal message thread.
Pricing: Pull only from approved rates and clearly defined rules.
Customer communication: Send the request through a channel your business can track.
Approval record: Save the signed or explicitly approved version to the job.
Billing: Pass the approved change to the invoice or accounting process.

Start with one common change type, such as sheathing replacement, and test the workflow on real jobs with a manager reviewing every draft. Track how often requests arrive complete, how long approvals take, and whether the approved amount makes it into the final invoice. Then adjust the form, rules, and customer message based on what your crew and office actually encounter.

If the workflow also depends on getting parts to the right crew, automating parts ordering between jobs can address that handoff. For a separate look at field-to-office approvals, timesheet approval automation for trades businesses shows how to structure a similar review process.

The dollars behind a cleaner approval process

Process gaps can create financial leakage for trades businesses. That’s a broad range, not a promise that every roofing company loses that amount from change orders alone. Small process gaps can accumulate across a trades operation.

You can estimate your own exposure with a simple calculation:

Unapproved or underbilled changes per month × average missed gross profit per change × 12

For example, if a company misses two billable changes a month and each would have produced $400 in gross profit, that’s $9,600 in annual gross profit left uncollected. Those are example inputs, not an industry benchmark. Use your own job records to see whether the result is meaningful.

The cost isn’t limited to the missing charge. Your office may spend time finding the right photos, calling the crew, explaining the invoice, or resolving a customer complaint. A structured approval record can reduce that rework while giving the customer a clearer view of what they’re authorizing.

If you’re also trying to recover missed calls after hours, download the After-Hours Call Recovery Plan for Trades. It’s a practical worksheet for mapping who answers, what gets captured, and how the next step reaches your dispatch process. You can also download the plan directly.

Map your approval workflow in an Omni Audit

In an Omni Audit, we’ll map how a field change currently moves from the crew to the customer and back into the job record. We’ll work through:

A workflow map showing the current handoffs and where requests stall.
An automation plan identifying what an agent can handle, what needs human review, and what should remain a manual decision.
A priority list with the systems, approval rules, and first change type to test.

The session is about your process, your software, and where an improvement would make a difference. If your team is already juggling missed calls, dispatch, and customer follow-up, we can include those connected workflows without losing focus on change orders.

Book a 60-min Omni Audit and we’ll work through the approval path with you. You can also review the AI audit for trades businesses before you book.

A good first test is narrow: pick one frequent change, define the information the crew must submit, set the approval rule, and make sure the final authorization reaches the job record. Once that works, expand to the next type of change. To plan that first pass with us, book your Omni Audit.

Automate Roofing Change Order Approvals