Read a detailed text description
Five linked blocks run from project address and site facts to legal classification, adopted design basis, product-specific evidence and final approval or inspection records. Feedback arrows show that a mismatch in configuration, location or assumptions must be resolved rather than skipped by relying on a generic certificate.
Key takeaways
- A certificate needs scope and configuration.
- Project drawings must match the site.
- Operating limits belong in the contract.
On this page
Identify the exact system
Record manufacturer, system family, model, revision, bay dimensions, height, roof type, alloy or material grades, finish, motors, sensors, screens and accessories. A certificate for a related family is not evidence until its scope clearly includes the supplied configuration.
Separate six evidence classes
Keep marketing literature, standards or certificates, laboratory reports, engineering calculations, project-specific drawings and installation/commissioning records as distinct files. Each answers a different question. A test report does not locate foundations; a project drawing does not prove the tested performance claimed in a brochure.
Official standard hub for US structural actions including wind, snow, rain, seismic and load combinations.
Interrogate headline ratings
For wind, snow, rain, corrosion, fire or electrical claims, record the standard and edition, test method, specimen, pass criterion, operating state, limitations and issuing body. Verify the document directly with the issuer where possible. A logo without a report or directory entry is not enough.
Close the handover loop
The final package should include approved drawings, as-built changes, concealed-work photographs, anchor and foundation records, drainage and control tests, manuals, maintenance intervals, spare-parts list, warranties and responsibility contacts. Define which limitations the owner must actively manage.
Official directory for aluminum standards, alloy data and errata.
Build an indexed, internally consistent evidence package
Register each document's issuer, identifier, revision, date, language, applicable model, claimed performance, exclusions and verification route. Mark it as marketing, standard, certificate, test report, calculation, drawing, instruction or warranty so unlike documents are not treated as equivalent evidence. Then cross-check model names, member sections, bay sizes, roof state, motors, anchors and limitations across the entire package. A valid document can still be irrelevant when it covers another configuration, while individually credible files can form an incoherent submission when their assumptions differ.
Evidence-package consistency check
Different files must describe one supplied system.
| Checkpoint | Define | Retain |
|---|---|---|
| Performance | What was tested/calculated? | Scope and limits |
| Configuration | What is supplied? | Model and revision |
| Project | Does it match the site? | Drawings and criteria |
| Handover | Can it be maintained? | Records and manuals |
Primary sources and scope
Official standard hub for US structural actions including wind, snow, rain, seismic and load combinations.
Official directory for aluminum standards, alloy data and errata.
Official abstract establishing a lifecycle framework from briefing and design through maintenance, replacement, reuse and disposal.
US model-code provisions for residential patio covers; only applicable where adopted.
Cite this page
Pergola Wiki Editorial Team. “Product evidence and procurement checklist.” Pergola Wiki. Reviewed 24 July 2026. https://pergola.wiki/articles/product-evidence-checklist/