Apollo NZ GlobalBuild Project Brief

Public Realm & Development · Specification guide

Specifying Public Realm Products for Councils & Developers

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.

Planning guidance — final supplied configuration remains project-specific.
Public-sector recreation and infrastructure used as a procurement planning reference
01

Specify the function before the brand

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.

02

Use current evidence

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.

03

Separate product supply from site works

Foundations, civil works, accessibility, electrical work, installation, local engineering and approvals should be separately assigned unless they are explicitly included in the supply contract.

04

Write lifecycle into procurement

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.

05

Keep a controlled project record

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.

Move from knowledge to project

Apply this guidance to the actual site.

Open the project brief checklist Build Project Brief