Installed Systems Explained
Metal Roof Proposal and Scope System
Use this practical system to compare a metal roofing proposal line by line, separate verified requirements from field decisions, document a clean closeout, and keep property-specific discoveries under written change control.
A metal roof proposal and scope system is a written map defining the installed assembly: it identifies measured roof areas, removal assumptions, deck review and repairs, the named roof system and underlayment, flashings and ventilation interfaces, site protection and cleanup, permit responsibility, change authorization, and closeout records.
Key takeaways
- A proposal is useful when it states what is included, excluded, assumed, and subject to written change—not merely a roof area and product name.
- Measurements must account for roof planes, slopes, valleys, walls, penetrations, edges, and access conditions; field verification remains essential.
- Deck repairs, concealed conditions, and permit requirements need a documented decision path because they cannot always be settled before removal.
- Closeout should preserve the installed-system record: product data, approved changes, permit evidence when applicable, care information, and the controlling written warranty.
What should a metal roof scope include to be checkable?
A dependable proposal separates the roof covering from the entire installed system. Read it for a traceable sequence: measured existing roof, removal or recover decision, substrate review, water-shedding layers, metal roof system, perimeter and penetration details, ventilation interface, site protection, cleanup, and handoff. The International Residential Code (IRC) treats metal roof panels as a roof covering with explicit requirements for support, slope, attachment, and wind resistance; a proposal should show how the project will address the parts that apply.[1]
A city or county may set the permit path and amendments. Louis City describes permits as legal authorization tied to its adopted codes, and Illinois directs code questions to the city, village, or county official because local codes and amendments matter.[5][6] The proposal should state the jurisdiction to verify, not assume a universal rule.
| Scope topic | A usable proposal states | Confirm before signing |
|---|---|---|
| Measurements | Roof planes, features, access assumptions, and measurement basis | That valleys, walls, penetrations, and transitions are identified |
| Removal and deck | Existing-layer assumption, removal method, deck-review trigger, and repair authorization path | How concealed deterioration or structural concerns will be documented |
| Roof assembly | Standing seam or stone-coated steel system, underlayment, attachment, trim, and accessories | That the selected system suits verified slope and substrate conditions |
| Flashing and ventilation | Named edge, wall, valley, penetration, ridge, intake, and exhaust interfaces | Which details are included and which require field verification or another trade |
| Permits and changes | Permit roles, inspection coordination, exclusions, and written change-order process | Local jurisdiction requirements and authority to approve added work |
| Cleanup and closeout | Protection, debris removal, final cleanup, documents, care information, and warranty records | What record the owner receives and which written warranty controls |
How are roof measurements documented before ordering materials?
The measurement record should identify each roof plane, pitch or slope, ridges, hips, valleys, rakes, eaves, sidewalls, headwalls, chimneys, skylights, plumbing vents, dormers, and transitions. It should also flag access constraints, steep or high areas, gutters or guards to be addressed, and existing rooftop equipment. A total roof area without those features is insufficient for checking trim quantities, flashing labor, or the difference between simple and complex geometry.
Treat aerial measurements, field measurements, and final order quantities as related but distinct records. The proposal can state the measurement basis and expected verification step; it cannot honestly guarantee that concealed geometry or substrate conditions are known before removal. Property-specific judgment includes whether a feature can be reused, needs relocation, or requires another trade. Record that judgment in a site note or approved change rather than silently substituting an assumption.
How does the proposal define removal, deck review, and repairs?
The scope should say whether existing roofing will be removed, how many layers are assumed, what happens to underlayment and flashings, and how debris will be managed. It should name the deck-review trigger: after removal, the installer examines exposed sheathing and related conditions before the new assembly conceals them. Under the IRC, metal roof panels are fastened to wood structural panels, solid lumber sheathing, or spaced lumber sheathing unless the covering is specifically designed for spaced supports.[1] That makes the actual substrate relevant, not incidental.
A clear allowance or unit-price method is better than pretending unseen deck repairs are already quantified. The written process should describe how deterioration, inadequate fastening, unsafe access, or structural concerns are documented, who may authorize additional work, and what work pauses pending a decision. A proposal is not a structural engineering report; if field observations indicate a structural issue, the next step may be evaluation by a qualified professional rather than an installer-created solution.
Should the proposal name the complete roof assembly or just the metal?
Specify whether the selected Bishop's system is Standing Seam Metal Roofing or Stone-Coated Steel Shingles, then identify the profile or panel/shingle series, finish or color selection, substrate approach, underlayment type, attachment method, trim family, and required accessories. Standing seam and stone-coated steel are not interchangeable scopes: their fastening patterns, layout, accessory sequence, and low-slope limits may differ. The manufacturer installation instructions for the exact system should be the installation baseline, alongside applicable code.[2][3]
The scope should not promise an unsupported slope, wind performance, or accessory compatibility. Instead, it should identify the roof slopes and conditions to be checked against the chosen product documentation. Manufacturer manuals are especially important at starts, ends, laps, vents, and transitions, where a generic material description does not establish the installed detail. If a product, color, or accessory changes before installation, document whether that change affects related trim, lead time, price, or warranty paperwork.
How should flashing and ventilation be coordinated in the scope?
List the edge-metal and flashing interfaces rather than writing only “flashing as needed.” Typical decisions include eaves, rakes, ridges, valleys, roof-to-wall transitions, chimney or skylight details, pipe penetrations, vents, and equipment curbs. The metal-roof manufacturer’s approved details determine how those parts overlap, fasten, and shed water within a particular system. EDCO’s roofing installation guide, for example, directs installers to follow manufacturer recommendations for vents and metal flashings.[3]
Ventilation must be scoped as an attic or roof-assembly decision, not as a default add-on. The National Roofing Contractors Association notes that ridge ventilation is most effective as part of a balanced system and links balanced ventilation to managing moisture, heat buildup, and deterioration risk.[4] Verify present intake and exhaust, air sealing, insulation configuration, blocked paths, and whether a ridge detail is compatible with the selected roof system. Those observations are property-specific and may call for a separate ventilation plan.
Who is responsible for permits and handling change orders?
Assign permit responsibility in writing: who verifies the jurisdiction, prepares or submits information, pays required fees, posts the permit if issued, requests inspections, and retains records. Louis City requires a project address and plans at the application stage and explains that review depends on project specifics.[5] In Illinois, residential jurisdictions with adopted codes can have local amendments, although local structural standards must meet the state-described IRC baseline beginning in 2025.[6] Neither source makes a permit outcome predictable for every property.
A change order should be the decision record for discoveries or owner requests that alter scope, materials, timing, or price. Common triggers include deck repairs, hidden water damage, code-official comments, ventilation changes, additional penetrations, solar or snow-retention coordination, and accessory substitutions. Require a description, the reason, drawing or photo support when useful, cost and schedule effect, and written owner authorization before the affected work proceeds, except for narrowly defined emergency protection.
How should the job be closed out and documented?
Before work begins, the proposal should say how landscaping, siding, driveways, windows, and attic contents will be protected where applicable, as well as how staging, debris, magnetic nail collection, and final site cleanup will be handled. Cleanup language should be specific enough to set expectations but should not disguise existing property damage or work by other trades as roofing responsibility. Photographing relevant pre-existing conditions and the completed roof makes the record more useful if questions arise later.
At closeout, request the final scope and approved changes, product identification, manufacturer care information, permit and inspection documents when applicable, and warranty documents. Bishop's states a 50-year warranty, but the current written warranty controls every term, eligibility condition, exclusion, remedy, and transfer rule. Bishop's also offers financing; financing terms belong in their own current documents rather than being implied by the roof scope. A complete file helps an owner distinguish a product document from a workmanship or project record.
When it fits
- You want to compare metal-roof proposals by installed scope rather than by a single total or product label.
- Your roof has valleys, walls, penetrations, additions, or access constraints that merit a feature-by-feature plan.
- You need a clear method for deck discoveries, permit coordination, and owner-approved changes.
- You are choosing between Standing Seam Metal Roofing and Stone-Coated Steel Shingles and want the selected system documented precisely.
When it may not fit
- You need an engineering assessment of framing, settlement, or other structural conditions rather than a roofing scope.
- You expect a pre-removal proposal to fix the exact quantity of concealed deck repairs without a documented contingency.
- You want one generic permit answer for all Missouri and Illinois jurisdictions instead of verifying the property’s local authority.
- You are seeking an asphalt, tile, wood, or other non-metal system; Bishop's is a residential metal-only specialist.
Educational guidance only; it is not a quote, contract, engineering opinion, legal advice, code determination, permit approval, or warranty. Actual scope depends on the property, selected product, manufacturer instructions, governing local requirements, and a written agreement. Current written financing and warranty documents control their terms.