ACADEMY / BUILD

Grow legal

Grow legal

The paperwork side of taking over a lot or a rooftop. Boring until it isn't.

BUILDHOST6 MIN READ

Every square metre of a city belongs to someone - a person, a company, a housing association, or the municipality. Before you put a single bed on it, find out who, and get permission in writing. A friendly verbal yes from a building manager evaporates the moment they change jobs. An email is enough; a one-page agreement is better. Guerrilla growing has its romance, but a garden you can be evicted from overnight isn't a garden, it's a performance.

For vacant lots, the owner is usually findable through the municipal land registry. Many cities actively want temporary use of empty lots - it cuts their maintenance costs and looks good - and some have formal interim-use or community garden programs with leases for a token rent. Ask the city's parks or urban planning department directly. The worst case is a no; the common case is 'fill in this form.'

Rooftops are a different animal, and the issue is weight. Wet soil runs roughly a tonne per cubic metre, and most roofs were engineered for snow and the occasional maintenance worker, not thirty raised beds after a rainstorm. Before anything heavier than a few pots goes up, you need the building owner's permission and, for any serious setup, a structural engineer's sign-off on load capacity. This isn't bureaucratic decoration - roofs fail, and when they do it's catastrophic. Spread weight near load-bearing walls and columns, use lightweight substrate mixes, and keep paths clear.

Water access makes or breaks a site. Hauling cans up four flights gets old by week two. Negotiate tap access as part of your permission - offer to put a meter on it and pay the usage. No tap available? Rain barrels under any downpipe you're allowed to touch, and design the garden around mulch and drought-tolerant planting from day one.

Then there's the neighbor layer, which no permit covers. Introduce yourself to the people whose windows face the site before the first session, not after the first complaint. Tell them what you're doing, give them a way to reach you, and mean it when you say they're welcome. A neighbor who got a heads-up and a bag of tomatoes is an ally. A neighbor who found out from the noise is a case file. This matters double for anything involving sound - the sound-setup guide covers that side.

Know the local limits before you test them. Cities differ wildly on what's allowed: open fires and barbecues, structures above a certain height, beehives, chickens, selling produce, events with amplified music. None of this is knowable in general - the only real advice is to check your municipality's actual rules, and when in doubt, ask the relevant office before doing the thing. Asking first reads as responsible; asking forgiveness reads as a reason to shut the whole site down.

Last one: insurance and liability. If you're hosting sessions where the public shows up and swings tools around, find out whether the landowner's insurance covers it or whether your crew needs its own liability policy - some community garden programs include this in the lease. It's the least raveyard paragraph in this whole academy, and it's the one that keeps the gates open.

Field Notes

  1. 01Permission in writing. Verbal agreements leave with the person who made them.
  2. 02Wet soil: ~1 tonne per cubic metre. Roofs need an engineer's sign-off.
  3. 03Negotiate tap access early. Hauling water gets old by week two.
  4. 04Meet the neighbors before the first session, not after the first complaint.
  5. 05Local rules vary wildly. Check your municipality, ask before you act.

Learned it? Now do it.

Theory is cheap. Find a session near you and put your hands in it.