Listen — start with the community signal
Ask who is authorised to describe the need, what success would make easier and which detail still needs direct confirmation.
ASSEMBLY FLOOR
A good project can move forward, loop back or stop. The assembly exists to expose uncertainty before goodwill turns into an unsafe promise.
A project can return to an earlier bay whenever a new fact changes the picture.
Each bay asks five working questions and provides detailed notes inside the Android app.
Ask who is authorised to describe the need, what success would make easier and which detail still needs direct confirmation.
Write one outcome, finite tasks, explicit exclusions and a change-control decision.
Separate the requesting partner, site controller, project lead, specialist authority and receiving owner.
Use prompts for authority, safeguarding, public movement, inclusion, weather, competence and handover.
Brief in view, open one controlled zone and keep pause authority legible.
Walk the full edge, account for temporary controls and name any unfinished condition.
Keep one process, change one friction point and carry one question into the next Listen stage.
Better preparation keeps unlike information apart.
What the authorised partner has actually asked for, including corrections and boundaries.
What an adult can see or measure without guessing another person's circumstances.
A proposal that remains a proposal until the right owner accepts it.