Build Project BriefClimate & Global Projects · Technical evidence authority guide
A project is not technically controlled simply because a supplier sends a folder of certificates. The useful document set is the one that matches the exact quoted product, current configuration, project stage and destination requirement. Build the document register deliberately and keep claims inside what the evidence actually supports.
List the documents the client, consultant, contractor, receiving team and installer actually need. Separate design information, product evidence, manufacturing records, installation information, freight documents and handover records so missing items remain visible.
A large unstructured folder can hide important gaps more easily than a short controlled register.
Record model, material, dimensions, finish, factory, test standard and document date where these affect applicability. A test or certificate should not be assumed to cover another configuration simply because the product looks similar.
When applicability is uncertain, identify the gap for technical review rather than converting it into a website or quotation claim.
Manufacturer test reports, calculations, drawings and certificates can support a local professional's review, but they do not automatically create approval in every destination. Local building, structural, fire, electrical, accessibility and statutory requirements remain jurisdiction-specific.
The project team should identify which local professional or authority accepts, reviews or supplements the supplied evidence.
Project drawings should identify revision, date, status and approval responsibility. Changes to dimensions, loads, openings, finishes, hardware or site interfaces after approval should trigger a controlled review before manufacture continues.
Shop drawings are only useful when the project team knows which version is current.
Structural steel, façades, glass, grandstands and other significant systems may require more formal material, welding, inspection or production records than lower-risk catalogue products. Define the expected record before production rather than requesting an undefined quality pack after dispatch.
Where third-party inspection is used, preserve the inspection scope and release record with the project file.
Packing lists, crate or bundle IDs, photographs, serial or batch references where relevant, spare-part lists and shipping documents help the receiving team connect physical goods to the approved project information.
For remote projects, clear identification can materially reduce installation delay and replacement risk.
Installation instructions, commissioning information where applicable, maintenance guidance, warranty conditions, spare components and service contacts should reflect the final supplied system. Generic brochures are not a substitute for final project information.
Name who will hold the final record after handover and how replacement parts will be identified later.
Comparison reference
Use this as a starting structure. Not every project needs every document, and additional jurisdiction-specific evidence may be required by the local project team.
| Planning criterion | Design & technical | Manufacturing & quality | Logistics & receiving | Handover & lifecycle |
|---|---|---|---|---|
| Typical records | Approved drawings, product data, calculations where applicable, test reports, certificates and material / finish information. | Material certificates where relevant, welding / QC records, inspection reports, sample or mock-up approvals and production release records. | Packing list, crate / bundle IDs, freight documents, delivery instructions, receiving and damage-inspection record. | Installation / commissioning information, maintenance guide, warranty, spare-parts list and service contacts. |
| Main applicability check | Does the evidence apply to the exact model, size, material, factory and project configuration? | Does the record relate to the manufactured batch or project and the agreed QC scope? | Can the receiving team identify what arrived, what is missing and where each package belongs? | Does the handover information describe the final supplied system rather than a generic family? |
| Local responsibility | Local professionals confirm jurisdiction requirements, code application and any additional evidence needed. | Project / consultant team defines any local inspection or release obligations beyond manufacturer QC. | Importer / receiver manages customs, local receiving, unloading and inspection as assigned by the quotation. | Owner / operator and local specialists manage maintenance, inspections and statutory operating responsibilities. |
| Common failure | Certificate folder is large but does not match the quoted product. | QC is requested only after production, with no agreed hold points or records. | Crates arrive without clear identification or a controlled packing record. | Manuals and warranty documents do not match the final configuration or are not transferred to the operator. |
The project specification, destination requirements and written quotation determine which documents are required and which party is responsible for providing or reviewing them.
Reference this resource
Link to the live page rather than a saved copy so readers reach the current Apollo planning resource and its latest controlled product links.
apollonzglobal.com/knowledge-centre/climate-global-projects/international-project-documentation-technical-evidence-guideapollonzglobal.com/knowledge-centre/climate-global-projects/international-project-documentation-technical-evidence-guide#comparison-matrixMove from knowledge to project