Construction planning guide

Metal Roofing ITP Preparation and Inspection Records

Prepare metal-roofing inspections by roof zone, sheet system and approved detail. Join support readiness, sheet fixing and flashing interfaces to the actual design and manufacturer information, with evidence retained before details become concealed.

Scope of this guide

Building metal roof sheets and defined associated components and flashing interfaces. Structural design, roof drainage design, tile/slate roofs, membranes, solar equipment and specialist access-system design are separate packages unless explicitly scoped with their governing documents.

Collect the files that control this package

Input to reviewWhat to identify
Roof layout and system selectionIdentify slopes, zones, sheet profiles, material/finish, support system and approved drawing revisions.
Design and fixing detailsProvide the actual project fixing, side/end lap, penetration and flashing details and approved product instructions.
Support readiness and safety interfacesIdentify structural/support release evidence and the project’s separate access and fall-protection procedures.
Under-sheet and adjoining workLocate insulation, sarking/under-sheet components, services, wall junctions and drainage-interface responsibilities.
Inspection and completion requirementsIdentify evidence needed before concealment, project-defined tests if any, defect treatment and as-built/product handover records.

Map the inspection sequence to the actual work

Keep roof-support readiness separate from installing under-sheet components, setting out and fixing sheets, and completing flashings. Refer each check to the detail for its actual zone or junction. A delivery docket identifies the received sheet but cannot demonstrate that a lap or fastener arrangement matches the project design.

Check the scope and adjoining responsibilities

Fixing spacing, wind-related design requirements, lap dimensions and flashing geometry must be taken from the approved project system and details. Do not derive them from a public example or an installer training unit. A quality inspection also does not replace the project safety plan or authority to access the roof.

Keep an unresolved requirement visible

The roof plan shows a new penetration but the provided flashing detail covers a different profile. Identify the roof zone, penetration, profile and the two document locators; request the applicable approved detail and keep that interface open.

Record the affected step and location, source documents and revisions checked, precise decision requested and the project role or route assigned to resolve it. Incorporate an authorised response with its reference and revise the affected plan and record. Do not hide the gap behind “as per standard”.

Use the blank fields already matched to the plan

Use Roof zone / grid for the boundary, Structure release ref. for support readiness, Fixing / lap detail locator for the installation basis, and Penetration / junction locator with Approved flashing detail ref. for weathering interfaces. Keep concealment photographs and defect dispositions retrievable.

The public package downloads include both the plan and its matching blank records in Excel, Word and PDF. The browser editor changes the plan; it does not collect site observations or perform tests. Use a repeatable record for each actual event and preserve original reports and photographs under the project procedure.

Separate results from authorised decisions

The ITP holds planned requirements. The inspection record holds actual observations, results and evidence. The project procedure assigns who reviews a discrepancy, authorises treatment, releases a contractual point and accepts a handover. Keep their names, dates and decision references distinct.

Use the cross-package register to index the current plan and actual event records. If a departure is identified, link the NCR to the affected work and requirement, the authorised disposition and any required recheck before closure.

Request project-specific drafting for this work

Send the existing project files and required client form with one clearly defined package and its interfaces. The named roofing service also supports a customer-defined scope beyond this public baseline when the required controlled sources are supplied.

The service is USD 99 per defined package, delivered within 24 hours after payment and complete usable required project files. It prepares the ITP and matching blank records; design decisions, actual inspections/tests, commissioning, approvals and certification remain with their assigned project parties.

Fictional package mapping example

Illustrative workflow only. No real site result, numerical acceptance requirement, test outcome or authorised release is represented.

  1. Identify the fictional roof bay and the approved sheet-profile selection.
  2. Map the fixing row to the supplied bay detail and keep the penetration flashing as a separate interface check.
  3. Record the missing applicable flashing detail as an open design/interface decision.
  4. Name photographs, product batches and the eventual project release reference without entering a fictional site result.

Before issuing the plan

Sources and their limits

Public sources explain the planning topics below. Confirm their jurisdiction, contract context and applicable edition; use controlled project documents for the actual requirements.

Related resources