Draw relationships before repeating a building type
Place arrival, private accommodation, shared functions, landscape, staff support, service access and quiet areas on one relationship map. Focus on what needs to connect, separate or remain adaptable.
Do not begin with a copied plan. Repetition can multiply a weak relationship just as easily as a strong one, so the site logic must be reviewed before any record is duplicated.
| Constraint | Evidence | Decision boundary |
|---|---|---|
| Site zone | relationship question | project input |
| Shared function | operating purpose | programme owner |
| Service route | coordination dependency | reviewer |
| Building record | documented fact | decision status |
Separate arrival, guest movement and service circulation
Trace how visitors arrive and orient themselves, how daily movement reaches private and shared areas, and how staff, maintenance and deliveries move. Mark conflict points as questions for the site team. Include after-hours and changeover scenarios so the route hierarchy is tested under different operating conditions without predicting a final design.
The canvas does not prescribe roads, dimensions or landscape solutions. Those decisions require site information, local review and professional coordination.
Make each phase work as a complete operating state
For every proposed phase, list the functions, access, services and management routines that must already work. Identify dependencies on later work instead of assuming the final arrangement exists from the start.
Phasing language does not prove supplier timing or project delivery. It is a developer-owned sequence that must be tested against reviewed scope and evidence.
How QHOME can assess a modular-village enquiry
Use documented project examples only for the relationships they actually show. QHOME can review the site-system brief and identify verified product information for further discussion, while the new site's programme and local context remain separate.
A written next step can state what QHOME is able to confirm, what the project team must provide and which questions remain open. It cannot promise a village portfolio, site outcome, delivery programme or commercial result.