Plot with guest house: entry, distance, zone plan
12–15 sotok plot with guest house: separate routes, parking, quiet and shared zones. Percentages for a FormSpace plan.
Short answer: a plot with guest house on 12–15 sotok needs two logical entrances, not two chaotic paths: shared entry, separate routes to main and guest house, privacy buffers. The mistake is placing the guest house at the gate without parking and a quiet zone — guests and hosts clash from day one. Below: 9 zones with % for ~13 sotok and transfer to FormSpace.
Two-generation logic: plot for two generations. Here the focus is a separate guest building and distance.
Who this is for
| Parameter | Recommendation |
|---|---|
| Area | 12–15 sotok (1200–1500 m²), reference ~13 sotok |
| Buildings | Main house + guest 40–80 m² |
| Scenarios | Long guest stays, rental, relatives |
| Parking | 2–3 spaces, turning at entry |
| Privacy | Guests do not cross hosts’ bedroom/kids zone |
| Maintenance | 6–10 hours per month |
| Style | Functional, clear service zones |
Zoning scheme
Reference for ~1300 m², guest house in depth or to the side, not at gate.
| # | Zone | ~% | ~m² | Content |
|---|---|---|---|---|
| 1 | Entry / turning | 10 | 130 | Shared entry, 2–3 parking spaces |
| 2 | Main house / terrace | 12 | 156 | Hosts’ parade zone |
| 3 | Shared terrace / table | 8 | 104 | Joint dinners |
| 4 | Guest house | 10 | 130 | Separate entrance, quiet yard at porch |
| 5 | Guests’ quiet garden | 8 | 104 | Bench, shade — not through kids zone |
| 6 | Lawn and play | 18 | 234 | Shared turf, view from both terraces |
| 7 | Utility / service | 10 | 130 | Shed, bins — behind main house |
| 8 | Buffer planting | 14 | 182 | Hedges between houses and neighbours |
| 9 | Service paths | 10 | 130 | Loop: entry → both houses → utility |
Total: 100% ≈ 1300 m².
Distance main ↔ guest house: 15–25 m direct or via buffer — enough privacy without “two plots”.
Flow diagram
[Gate] → [Parking]
├→ [Main house / terrace] → [Shared terrace] → [Lawn]
└→ [Service path] → [Guest house] → [Quiet garden]
↘ [Utility]
Materials
| Element | Recommendation | Avoid |
|---|---|---|
| Entry | Pavers or gravel with edging | Single narrow drive without turning |
| Path to guest | Gravel 1.2 m, lighting | Route through hosts’ bedroom |
| Terraces | Same palette, different scale | Two incompatible styles at façades |
| Buffer | Hedge 1.5–2 m | Solid wall without light |
| Guest yard | Mulch, stone, compact paving | Large lawn at guest entrance |
| Parking | Hard surface, not on lawn | Guest cars on turf |
Palette: 2–3 materials, repeat at both houses for plot unity.
Typical mistakes
- Guest house at gate — noise, headlights, no privacy.
- Single entrance through hosts’ kitchen — guests “live in the corridor”.
- No parking for second guest car — cars on lawn.
- Shared lawn without buffer — mow/play conflicts.
- Utility by guest porch — smell, noise, bins visible.
- Visual without plan — plan in one evening first.
Build it in FormSpace
| Step | Block | Action |
|---|---|---|
| 1 | 1.1 | Brief: guest house, parking, privacy |
| 2 | 1.2 – 1.3 | Underlay, ~1300 m² boundary |
| 3 | 1.4 | Both houses, entry, trees |
| 4 | 1.5 | 9 zones, guest as separate polygon |
| 5 | 1.6 | Paths, terraces, buffers |
| 6 | 1.7 | Check: house distance, parking 2–3 spaces |
FAQ
Where to place guest house?
In depth or on side line, with own porch and short path from parking — not at gate.
Second gate needed?
Rare on 13 sotok. Path fork after parking is enough.
Shared or separate terrace?
Shared 8% for dinners + small terrace at guest house — privacy compromise.
Renting guest house?
Add 14% buffer and service path without crossing hosts’ zone.
Summary
Guest house plot = shared entry, separate routes, 15–25 m distance, buffers. Two houses — one scheme, not two random yards.
Start now: create a project in FormSpace and lay out both houses in blocks 1.4 and 1.5.
Published:
Volodymyr Vybornyi
Landscape designer, founder of https://formspace.design/
Writes about landscape design, business, and modern computer-aided landscape planning tools, including AI.