Community use
Describe intended users, activities and routes, along with any consultation or stakeholder priorities already identified.
Bring together the public use, stakeholder needs and procurement requirements. Identify the decisions, documents and review responsibilities early so the canopy proposal can be developed around the actual project process.

A public-space project can involve users, asset managers, designers and procurement teams. A shared brief gives each group a consistent view of the purpose, site constraints, scope and information needed before a decision is made.
Describe intended users, activities and routes, along with any consultation or stakeholder priorities already identified.
List the submission requirements, evaluation needs and decision dates supplied by the project team.
Identify the responsible professionals, approval process, operating team and documents required at handover.
Agree the problem the shade project is intended to address and the users it should serve.
Provide a clear document list and scope so the proposal responds to the intended review stage.
Include operation, maintenance access and handover requirements alongside design and delivery.
Share what is available and mark approximate information. We will use it to clarify the next questions and the support your project needs.
Discuss this project →Yes. State the stage, available information and the decision the team needs to make. Any assumptions should be identified so an early discussion is not confused with a final engineered proposal.
Do not assume them. Provide the project requirements and identify the responsible parties. Available documents, contractual arrangements and local review needs are confirmed for the specific scope.
Send your project brief. Overseas on-site personnel can be arranged; responsibilities and installation scope are agreed for each project.
Request a project quote →Share the intended use, approximate dimensions and what you need us to help with.