Step 03
Technical and Compliance Verification
Documentation belongs to a system and a configuration, not to a manufacturer. Verification means matching the paperwork to what is actually being supplied.
What the work involves
- —Identifying the standards that govern the project in its destination market
- —Requesting manufacturer test reports and certification for the specified configuration
- —Checking that the documentation matches the system, size and build-up being supplied
- —Flagging gaps to the project team before procurement proceeds
What the project team receives
- —A documentation set traceable to the supplied configuration
- —Early identification of any compliance gap
Why it matters
Test reports travel badly. A report can be genuine, current and entirely irrelevant to the configuration being bought, because it covers a different size, frame depth, glass make-up or opening type. Verification is the step that establishes whether the documentation actually describes what will be delivered.
Destination markets govern, not the market of manufacture. What a building authority in the United States, Canada or a specific European country will accept is a matter of the standards named in the project documents, and those requirements differ by jurisdiction.
Who it serves and where it fits
- —Architects and specifiers who have to demonstrate compliance to a client or authority.
- —Contractors assembling submittal packages for approval.
- —Developers whose financing or insurance depends on documented performance.
- —It sits between award and production, and again whenever a configuration changes.
How it reduces procurement risk
- —Documentation is checked against the configuration being supplied, not against a similar one.
- —Gaps are raised while there is still time to re-test, re-specify or re-source.
- —Claims that cannot be evidenced are not carried into the project.