Roofing Change Order Follow-Up SOP: Stop Extra Work From Delaying Jobs and Payment

Roofing change orders stall jobs when scope, price, approval, and scheduling live in separate places. Use this SOP to keep extra work documented and moving.

A roofing crew removes the old material and finds damaged decking around a valley. The original scope does not cover the added labor and materials. The field lead sends photos to the office, but the customer approval, schedule change, and billing task end up in different places.

Now the crew is waiting, the homeowner is confused, and nobody can say whether the extra work is approved.

A roofing change order follow-up SOP gives US roofing contractors one process for documenting the condition, preparing the change, securing the required approval, updating the job, and carrying the added amount through billing.

Why roofing change orders get stuck

Extra work creates a fast chain of handoffs. The crew finds the issue. A qualified team member confirms the scope. The office prepares the price and terms. The customer reviews the change. Purchasing may need more material. Dispatch may need to adjust the schedule. Billing needs the approved amount.

When those steps live in texts, job-site photos, inboxes, and memory, the roofing change order process breaks. The field team may move ahead without the required documentation, or stop work while the office tries to rebuild what happened.

The roofing change order follow-up SOP

Keep the admin process simple enough for a trained VA or office coordinator to manage. A qualified roofing professional should confirm the field condition and technical scope. The company should also follow its contract, approval requirements, and applicable local rules.

Step 1: Capture the field condition before it disappears

As soon as unexpected work is found, add it to the existing job record.

Record the job address, original scope reference, date discovered, person reporting it, written description, labeled photos or video, affected roof area, immediate safety or weather concern, and requested decision time.

Use a standard field note instead of a message such as “more decking needed.” The office needs enough detail to prepare the change without chasing the crew for basic facts.

Step 2: Define the added scope and price

Assign a qualified estimator, production manager, or owner to confirm what is outside the original scope.

The change order should identify the added or removed work, labor, materials, price adjustment, payment terms, schedule effect, exclusions, and the approval method required by the agreement.

Step 3: Use CRM stages that show the real status

A note that says “change order sent” is not enough.

Useful roofing change order stages include field issue reported, scope review needed, pricing in progress, change order ready, sent for approval, customer question pending, revision needed, approved, declined, materials needed, schedule update needed, work completed, added amount ready to invoice, and paid.

Step 4: Send a clear customer update

When the issue is found:

“Hi [Name], our roofing team found [condition] in the [roof area] after the existing material was removed. This work is outside the current scope. We are documenting it now and will send the proposed change, price, and schedule effect for your review by [time or date].”

When the change order is ready:

“We sent the roofing change order for [brief scope]. It shows the added work, price adjustment, and expected schedule effect. Please review it through the approval method in your agreement. We will not mark the change approved until the required confirmation is received.”

If there is no response:

“Following up on the roofing change order sent on [date]. The job is currently waiting on the required decision for [scope]. Please reply with any questions, or complete the approval step so we can confirm materials and scheduling.”

Step 5: Carry approval into production and billing

After the required confirmation is received, attach it to the job record. Update the approved amount, materials, crew notes, production schedule, customer communication, and billing task.

Step 6: Review the exception queue every business day

The VA or office coordinator should review all open roofing change orders daily.

Flag field reports with missing photos, changes waiting on scope review, pricing with no owner, approvals past due, customer questions with no response, approved work with no schedule update, completed extra work with no billing task, and invoiced changes with no payment status.

What this looks like in real life

Imagine a roofing company has five active jobs with extra-work questions.

In a messy process, one decking issue is in a crew text, two customers are waiting for prices, an approved ventilation change never reached purchasing, and a completed change has not reached billing. The owner spends the afternoon calling the production manager and searching for photos.

In a clean process, all five changes sit in BoostOps CRM with the field evidence, stage, owner, and next date. The VA checks for missing details and sends approved updates. The production manager confirms scope. The estimator prepares the price. Dispatch updates approved work. Billing receives a task when the added work is complete.

The owner sees only the exceptions that need authority or judgment.

Put roofing change order admin with the right person

A trained VA plus BoostOps CRM gives a roofing company a practical job approval tracking system. The VA keeps records complete, follows up on required approvals, updates stages, and connects production to billing. Roofing professionals control technical scope. Managers control pricing and exceptions.

BoostOps CRM is $199/month. If you need the person and the system, BoostOps also places a full-time Filipino VA with a fully set up CRM for $11.86/hour, billed monthly for a full-time VA.

Start simple

Start with this roofing change order checklist:

  1. Add every potential change to the existing job record.
  2. Attach a clear description, labeled photos, and the original scope reference.
  3. Assign a qualified person to confirm the added work and price.
  4. Set the CRM stage, owner, and next-action date.
  5. Send the customer the change, schedule effect, and required approval step.
  6. Attach the approval or decision to the record.
  7. Update materials, production, dispatch, and crew notes.
  8. Create the billing task when approved work is complete.
  9. Review the open change order exception queue every business day.

Connect this process to the roofing material order follow-up SOP so approved materials do not stall. Use the roofing permit follow-up SOP when added work affects permit steps. For insurance-related additions, use the roofing insurance supplement follow-up SOP. The home service dispatch cleanup SOP can catch approved changes that never reached the schedule.

The rule is simple: no roofing change order should sit without evidence, a status, an owner, and a next date.

FAQ

What is a roofing change order follow-up SOP?

A roofing change order follow-up SOP is a repeatable process for documenting extra work, preparing the scope and price, securing the required customer approval, updating production, and moving the approved amount into billing.

What should a roofing contractor include in a change order record?

A roofing contractor should include the original scope reference, field condition, photos, added or removed work, price adjustment, schedule effect, customer communication, approval evidence, owner, status, and next-action date.

Can a virtual assistant manage roofing change order follow-up?

Yes. A trained VA can check records for missing details, send approved customer updates, track approval status, update CRM stages, assign tasks, and connect production with billing. Qualified roofing staff should control technical scope and pricing.

When should a roofing change order move to billing?

A roofing change order should move to billing according to the company’s agreement and process after the required approval is documented and the invoice milestone is reached. The CRM should show the approved amount, completed work status, and billing owner.

Stop extra work from becoming unpaid work

Extra roofing work should not depend on scattered photos, verbal approvals, or owner memory.

BoostOps can help build the CRM stages, change order checklist, approved messages, and VA-owned follow-up process that keeps added work visible from the field report through billing.

Book a BoostOps discovery call and we will map where roofing change orders are delaying jobs or payment.