
A link saved in a purchasing file is not much help if the installer cannot find the relevant instructions.
A building product arrives with a code, a label and a link to technical information. The purchasing team has ticked the documentation box. On site, however, the installer needs to know which instructions apply to this product, in this location, as part of this design.
The gap is usually not a lack of documents. It is the absence of a clear connection between the product, the approved work and the information people need.
Start with an exact match
New Zealand’s building product information requirements apply to designated products and place obligations on specified suppliers, including manufacturers and importers. MBIE’s guidance explains that framework. The availability of information does not, by itself, establish suitability for every proposed use.
For a project file, identify the exact product and version supplied. Keep the relevant installation, use and maintenance information alongside the design details that rely on it. Where the delivered item differs from the specification, stop the administrative assumption that it is automatically interchangeable and seek the required assessment.
Use plain filenames or a short index that a foreperson can navigate. A folder full of documents called “technical-final” makes it unnecessarily difficult to select the right one.
Put information at the decision point
The person checking a delivery needs identifying details. The installer needs current instructions and relevant design information. The owner later needs maintenance and operating information. One large undifferentiated download does not serve each of those purposes well.
Agree who maintains the project copy and how updates are communicated. Avoid treating a saved document as permanently current when the supplier has issued a relevant revision; also preserve the record of what applied to the product actually installed.
Ask installers whether the information is accessible in the conditions where they work. A system that requires several logins and reliable reception may fail at the point it is most useful. Provide an appropriate controlled alternative where needed.
A product-information process is successful when a worker can find the right instruction, a reviewer can understand the selected product and an owner can maintain it later. Collecting documents is only the first part of that job.