Project evidence · controlled publication · privacy safe

Show the project thinking. Publish the evidence only when it is real.

Apollo separates completed-project evidence from representative applications and planning frameworks. A page becomes a case study only when the underlying project facts and permission to publish are verified.

Evidence class stated Customer privacy protected Outcomes require project evidence

PUBLIC LIBRARY6Controlled public evidence/framework records

VERIFIED CASE STUDIES0Published only when project facts and approval support them

PLANNING FRAMEWORKS6Non-customer decision and procurement models

Evidence standard

Four public evidence classes. Different proof requirements.

This prevents concept imagery, supplier references or useful planning material from being accidentally presented as an Apollo customer result.

Verified case study

A real project may be named only when the project facts, supplied scope and publication approval are verified. Outcomes must be supported by the project record rather than inferred from product capability.

None currently published

Anonymised project evidence

A real project can be described without customer identity or precise location only when the underlying facts are documented and the anonymised publication is approved.

Representative application

Shows how a product or system may be used. It is not presented as an Apollo customer installation and must not imply a measured project outcome.

Planning framework

A non-customer decision or procurement model. It can explain what should be reviewed, but it cannot be described as a completed project or customer result.

Public project library

Evidence and frameworks with the status stated.

The current public library contains planning frameworks only. That is deliberate: useful decision guidance is published now, while customer project claims remain behind the verification gate.

1 matching records

Council park recreation package framework — Councils & public realm

Planning framework

01Councils & public realm

Council park recreation package framework

A non-customer procurement framework for councils planning courts, modular pump tracks, sports lighting, VAKTAR AI cameras, shade and CIVARO public-realm systems within one park or recreation brief.

Evidence basisApollo procurement model · non-customer frameworkReviewed 15 Sep 2026

What this record reviews

Community outcome and target users
Lifecycle, maintenance and accessibility interfaces
Technology, lighting and operating policy
Staging, public-space design and local approvals

Framework value

Separates supplied recreation systems from local public-space design, civil works and statutory responsibilities while preserving a staged expansion pathway.

CIVARO Public Realm Public Realm Knowledge CIVARO Project Brief Builder

Internal evidence stays internal

Private project records do not belong in public frontend code.

Customer names, exact locations, quotations, drawings, contact information and internal project files stay outside this public evidence register. If a future project is approved for publication, only the approved evidence record is added here.

Case-study gate

A real project can move public only after verification.

A public completed-project case should identify the supplied scope, distinguish Apollo supply from local works, document the project facts used in the story and record permission for the level of identification being published.

Technical evidence standard

Have a similar project?

Start with the real site conditions, not a case-study assumption.

Build a project brief Use Project Tools