Request Project PricingPublic Realm & Development · Specification guide
A strong public-realm specification defines what the product must do, what evidence is current and where supplier responsibility ends. That creates a cleaner basis for procurement than relying on appearance or a manufacturer catalogue alone.
Describe use, capacity, exposure, material expectations, maintainability and interfaces before freezing the exact product. This makes tender comparisons more meaningful and reduces late substitutions based only on visual similarity.
Dimensions, materials, warranties, test reports and certifications should be tied to the exact current product where those claims matter. Generic family statements should not be used as model-specific proof.
Foundations, civil works, accessibility, electrical work, installation, local engineering and approvals should be separately assigned unless they are explicitly included in the supply contract.
Cleaning, inspection, spare parts, replacement access, finish maintenance and future expansion can materially affect whole-of-life value and should be reviewed alongside capital cost.
Record the approved model, finish, dimensions, options, technical documents and revision at each stage. Future replacements and project phases should refer back to that controlled record.
Reference this resource
Link to the live page rather than a saved copy so readers reach the current Apollo planning resource and its latest product and planning links.
apollonzglobal.com/knowledge-centre/public-realm-development/specifying-public-realm-councils-developersApollo NZ Global. Specifying Public Realm Products for Councils & Developers. apollonzglobal.com/knowledge-centre/public-realm-development/specifying-public-realm-councils-developersReference & source policy Move from knowledge to project