Roofing Change Order Communication: A Field-to-Customer Workflow That Protects the Scope

A roofing crew opens an area and finds deteriorated decking, an unexpected flashing condition, or a detail that does not match the visible pre-job assessment. The field team needs an answer quickly, but moving fast should not turn a spoken observation into unapproved work. A change-order communication workflow gives the crew a safe pause point and gives the customer a clear explanation of what changed before the scope moves.

The workflow is not about making every field discovery a sales event. It is about separating evidence, technical recommendation, customer choice, and release to proceed. The exact contract language, pricing rules, code requirements, manufacturer instructions, insurance requirements, and safety decisions belong to the contractor and qualified professionals. The job record should make each of those decisions easier to trace.

Set the trigger before production day. Define which conditions require a pause and owner review: concealed damage beyond the approved allowance, a material substitution, changed access, a code or safety issue, a customer-requested addition, or a condition that makes the signed scope unworkable. Give crews a simple instruction: capture the condition, protect the area as appropriate, and contact the designated owner before doing extra billable work. The trigger should be clear enough to follow under a busy roof day.

Collect focused field evidence. Take overview photos that establish the roof area and closer photos that show the changed condition. Add a short factual note describing location, condition, and any immediate protection or work already performed. Avoid writing a conclusion that goes beyond the evidence. For example, note visible deteriorated decking at the rear valley rather than asserting a cause that has not been verified.

Give one person authority to coordinate. The production lead, project manager, or another named owner should gather the evidence, check the signed scope, and decide who needs to be consulted. Crews need a reliable contact, not a group thread where several people may offer conflicting answers. Identify a backup owner for absences and state which decisions require customer approval before a revised instruction can be issued.

Explain the change in customer language. Tell the customer what the team found, where it is, why it affects the agreed work, what option or recommendation is being proposed, and what will happen if the decision is delayed. Use the photos to support the explanation, not as a replacement for it. Avoid vague phrases such as we have to do more. A customer should be able to understand the boundary between the accepted scope and the new requested authorization.

Keep proposed work distinct from approval. A crew can identify an option and a price can be prepared, but neither is permission to begin. Use your normal estimate or change-order process to record the revised scope, price, timing effect, and the authorized decision maker. If the customer declines or cannot be reached, document the operational decision: make safe, defer, resequence, or stop according to company policy and applicable requirements. Do not let a text message with an unclear response silently change the job.

Issue a revised field instruction. Once the required approval is complete, give the crew a concise release that identifies the approved addition, exact location, materials or labor change, and any schedule impact. If the decision is not approved, give an equally clear instruction about what is excluded and the next step. A crew should not have to infer the final decision from an old photo thread or an estimate draft.

Update downstream promises. A changed scope may affect delivery, labor, inspection, payment timing, or a homeowner's expectations. The owner should determine which appointments, documents, and customer updates need revision. Do not promise a specific completion date solely because an additional scope was accepted; production capacity, weather, permits, and supplier availability may still require human scheduling decisions.

How Joby supports the workflow. Joby's job records, photos and documents, estimates, tasks, scheduling, field-worker assignments, and communication history can keep the evidence, customer decision, and field handoff connected. Joby does not automatically approve changes, determine code compliance, validate insurance coverage, or choose how a crew proceeds; the contractor remains responsible for those decisions.

Review the change log after the job. Look for recurring triggers such as missing pre-job photos, unclear allowances, material assumptions, or delayed customer contact. Improve the estimate language, readiness review, or field checklist that would make the next job clearer. The best outcome is not zero change orders; it is a documented change handled before it becomes an avoidable surprise for the crew or customer.