PROJECT SEVENTEENBalclutha project assembly

ASSEMBLY FLOOR

The seven-bay assembly

A good project can move forward, loop back or stop. The assembly exists to expose uncertainty before goodwill turns into an unsafe promise.

ASSEMBLY FLOORA linked sequence, not a checklist race

A project can return to an earlier bay whenever a new fact changes the picture.

The seven bays

Each bay asks five working questions and provides detailed notes inside the Android app.

01

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.

02

Define — build a scope that can be handed over

Write one outcome, finite tasks, explicit exclusions and a change-control decision.

03

Partner — make every handoff visible

Separate the requesting partner, site controller, project lead, specialist authority and receiving owner.

04

Make Ready — lock conditions before arrival

Use prompts for authority, safeguarding, public movement, inclusion, weather, competence and handover.

05

Act — run an adaptable work line

Brief in view, open one controlled zone and keep pause authority legible.

06

Hand Over — return the place and next decision

Walk the full edge, account for temporary controls and name any unfinished condition.

07

Learn — debrief without scores

Keep one process, change one friction point and carry one question into the next Listen stage.

The evidence lanes

Better preparation keeps unlike information apart.

P

Partner statement

What the authorised partner has actually asked for, including corrections and boundaries.

O

Direct observation

What an adult can see or measure without guessing another person's circumstances.

I

Crew idea

A proposal that remains a proposal until the right owner accepts it.