plot.eco

Design patterns · Pattern 5 · v0.1.1

Make participation able to change something

Draft, not reviewed Drafted with AI help from the owner's brief (22 Oct 2026); examples sourced 22 Oct 2026. Not yet reviewed.

The problem

The problem

Consultation often arrives after the design is fixed. People are asked for comments they can see make no difference, and the record of what they said, and why it was or wasn't taken up, disappears.

The pattern

The pattern

Open the questions that are still open, early, and say which ones are. Record each request, the response, and whether the design changed. Give a standing group a real decision over something specific (the public edge, the planting, the hours), with a budget.

What it changes on the ground

  • A published list of what is still open to change
  • Each request recorded with its response and outcome
  • A community advisory group with a decision over a named element
  • A budget that group controls

What makes it credible

One , traced step by step. Each step needs its own evidence.

  1. 1

    Existing condition

    What was decided before consultation began

  2. 2

    Proposed change

    The open questions and the group's remit, published

  3. 3

    Delivered work

    Requests, responses and design changes, recorded

  4. 4

    Maintained condition

    The group meeting and deciding, minuted

  5. 5

    Measured result

    Changes to the design that came from the community, counted

Examples elsewhere

  • Officeparken · Høje-Taastrup, Denmark

    What the source establishes
    The landscape architect says the design leaves room for the community to shape what comes next.
    “allowing the community itself to influence future uses – for example through the addition of playgrounds, further planting, or new gathering spaces”
    Gottlieb Paludan Architects (on gottliebpaludan.com), 2025-09-16 · stored as s/WS4F-A3
    The question it raises here
    What part of this facility's surroundings could a community group decide, with a budget?
    Not checked
    The company's or designer's own account, stored by PLOT on 22 Oct 2026 and not yet reviewed by a person; nothing here is independently checked. How the community's influence works in practice isn't in this source.

Questions to take to a design discussion

  • What can still change, and what can't?
  • Where is each request and its answer recorded?
  • Does any group decide anything, with a budget?
  • What changed because people asked?

Applies to: data centre · Where: anywhere · Version 0.1.1