When a Roof Supplement Is a Revision vs. a New Scope Problem

A lot of supplement friction comes from mixing two different jobs together: tightening a packet that already fits the submitted roof scope, and introducing genuinely new scope after the fact.

Those are not the same thing, and the packet should not treat them as if they were.

A revision usually stays inside the original file set

• The carrier pushed back on an item already supported by the submitted scope
• The original measurement, estimate, and photos already contained the relevant issue
• The clarification needed is about packaging, quantity support, or explanation rather than a newly discovered condition

A new scope problem usually changes the factual boundary

• The condition was discovered only after submission or tear-off
• A different structure, elevation, or accessory condition now needs to be documented
• The new request depends on evidence that was not part of the original packet

Why the distinction matters

When a contractor blends both categories together, the review gets slower and trust drops. A reviewer who cannot tell whether the file is being clarified or broadened will often default to caution.

A simple rule of thumb

If the missing work can be defended using the evidence and scope boundary already submitted, it likely belongs in a revision. If the packet needs new evidence to justify a broader request, it is probably a new scope issue and should be handled as such.

That discipline helps both sides. Contractors avoid muddy packets, and reviewers can process the request faster. PactPack bakes that distinction into its pricing, coverage gate, and included-revision boundaries so the buyer knows what is inside the fixed price before payment starts.