What this guide solves
Search results and reference articles can explain concepts, but they cannot automatically establish that a location, configuration or product is compliant, suitable or approved. This guide separates what was learned from what a project must still prove.
Four-step verification workflow
- Define construction and location: record use, geometry, roof state, attachment, enclosure and exposure.
- Match evidence to the question: regulations, calculations, tests, installation records and maintenance evidence serve different proof tasks.
- Confirm with the accountable party: authorities, designers, manufacturers and inspectors confirm only within their scope.
- Retain traceable records: preserve edition, date, configuration, issuer, project identity and limitations.
Evidence path by topic
| Question family | Confirm | Stronger evidence to retain | What general content cannot establish |
|---|---|---|---|
| Types and history | Actual roof movement, attachment and enclosure | Measured drawings, photographs and the local authority's classification path | A product name or visual resemblance does not establish the legal or structural category. |
| Materials | Specified grade, finish system, exposure and compatible fasteners | Product traceability, mill or treatment records, finish data and project warranty terms | A generic material label does not establish grade, durability or suitability for the exposure. |
| Anatomy and components | Geometry, connection, load-transfer and drainage details at every interface | Approved details, manufacturer instructions and installation records | A rendering or component list does not establish an assembled system's load or water path. |
| Engineering | Site actions, continuous load path, foundations, connections and supporting structure | Project-specific site data, calculations, approved drawings and inspection records | A general table, calculator or article is not a project design or approval. |
| Climate-responsive design | Wind, rain, snow, heat, exposure class, drainage capacity and control fail-state | Local climate data, declared test scope, project design documents and commissioning records | One rating or laboratory result does not establish whole-system performance in every configuration. |
| Planning and codes | Jurisdiction, adopted edition, local amendments, use, site constraints and permit pathway | Written authority guidance, current adopted text and project permit documents | A model code, national guide or neighboring approval does not establish local permission. |
| Use and maintenance | Installed model, environment, service history, current condition and safe access | Manufacturer instructions, dated logs, photographs and competent inspection where risk warrants | A calendar interval or warranty period does not establish present condition or remaining life. |
Evidence strength is not applicability
An official code, consensus standard or laboratory report can be a strong source, yet jurisdiction, edition, specimen, configuration, boundary conditions and responsibility still need checking. A higher source tier does not make a document automatically applicable to every project.
Boundary: This is an editorial verification method—not engineering design, legal advice, product certification, a permit decision or independent external review.
Review source tiers and scope · Use the product evidence checker · See the public evidence gaps