What Would Happen to Your Plot If You Had to Stop Coming

Here's a question nobody asks when they're excited about a new growing project, but everybody eventually needs the answer to: what happens when life gets in the way?

Because it will. Someone's kid gets sick. Someone's shift pattern changes. Someone has a bad month, or a bad year, and the last thing they can face is a plot of courgettes going to seed while they can't get out of bed. Most community growing schemes aren't built for this. They're built for the version of you that shows up every Saturday, enthusiastic, reliable, improving. The moment you stop fitting that version, the system usually has no answer for you — just a waiting list of people who'd "actually use it," and a quiet, polite nudge to give your plot up.

We think that's backwards. If a project only works for people who are already doing fine, it was never really for the people who need it most.

So here's roughly how we'd want it to work, in a Rooted Common Ground Farms space, if you had to stop coming.

Nobody takes your plot the week you go quiet. There'd be no three-strikes policy, no automatic reallocation after a fixed number of missed sessions. A plot going a bit wild for a stretch isn't a crisis — it's just weather and time doing what they do. Someone on site, or in the wider Rooted network, would keep an eye on it: enough watering to keep things alive, nothing more demanding than that. Not because you owe anyone an explanation for being absent, but because the land can hold steady while you can't.

Coming back wouldn't require an account of where you've been. This is one of the places where "trauma-aware" stops being a word on a page and becomes an actual design choice. A lot of people who'd benefit most from a space like this have already had enough of justifying their absences — to employers, to services, to themselves. We don't want a reappearance to feel like walking back into a room where everyone clocked that you left. The plot's still there. The kettle's still on. That's the whole welcome.

If genuinely too much time passes, there'd be an honest conversation, not a silent cut-off. At some point, if a plot has gone untouched for long enough that it's clearly not coming back into use, someone would reach out directly — not a form letter, an actual person asking how you're doing and whether you want help getting back into it before anything changes. The land getting used by someone else isn't a punishment; it's just what land held in trust does when it's not being asked to sit empty. But that decision happens with you, as a conversation, not to you, as a notice.

Your spot in the place doesn't depend on your plot. Having a growing space is one way to belong here, but it isn't the only one, and losing it wouldn't mean losing your place. You could come back to help in the shared beds, sit in on a session, or just be around, long before you're ready to take on your own patch of ground again. Belonging here was never meant to be conditional on productivity.

Underneath all of this is the same belief that runs through everything Rooted does: people aren't broken, the systems that are supposed to catch them usually are. A system that drops you the moment you stop performing "reliable" isn't really support — it's a filter dressed up as one. We'd rather build something that assumes, as a baseline, that the people using it are whole humans with unpredictable lives, not volunteers to be managed for consistent output.

This is still a proposed network — none of this is running on actual ground yet, and we're not pretending otherwise. But it's exactly the kind of detail worth getting right on paper before there's soil to test it on, because the small, unglamorous policies are where trauma-aware either means something or doesn't. Anyone can put "trauma-informed" in a mission statement. The test is what happens on the Tuesday you don't show up.

A garden doesn't ask what's wrong with you before it lets you dig. We don't think it should ask anything of you for the weeks you can't, either.