Community parks coordination, when you've also got a day job

It’s 11

on a Tuesday night. You’ve got the kids down. You’re sitting up in bed with your phone, building the rota for Saturday’s invasive species clearing. Three new sign-ups came in via the WhatsApp group while you were at your actual job today. Two more replied to the Mailchimp newsletter saying they’d love to come but only if it’s not raining. Someone messaged the Facebook page asking whether eight-year-olds can come along. You haven’t replied to any of them yet.

You’re not getting paid for any of this. You’ll be at your actual job at 8

tomorrow morning.

You already know, in some sense, what a post like this is going to say. That information shouldn’t live in five places. That you need a successor. That a better signup process would help. You know. The reason none of it has happened isn’t ignorance. It’s that fixing it requires effort on top of the effort you’re already doing, and every minute spent designing a system is a minute not spent on the thing the system is meant to support.

So let’s be honest about that up front. Nothing good happens without effort. Building a workable coordination setup for a community parks group is a real piece of work — a long weekend, probably, broken across two or three weekends in practice. Someone has to do it. If the someone is you, the question is whether it’s worth it.

Here’s the case for yes. The effort you’re putting in now resets every week. The chair-at-11

problem is the same problem next Tuesday and the Tuesday after. The setup you build once does its own running afterwards. You’ll still be coordinating, but from fewer places, with fewer surprises, and in less time. The point isn’t to eliminate the work. It’s to do it once instead of every week.

What follows is what “minimal” actually looks like for a community parks group. Not the simplest possible system, which is what you have now and which is breaking. The smallest system that actually holds.

Five things, and only five

A community parks group needs five pieces of operational infrastructure to coordinate itself reliably:

1. One operational channel where decisions live.
2. One acquisition funnel that everyone joins through.
3. One signup tool used the same way every event.
4. One records sheet for who’s cleared for what and who does what role.
5. One shared folder for documents that aren’t for everyone.

That’s it. Five. Used the same way every time. Most groups have something like ten to fifteen separate places where coordination is happening, and that’s why coordination is hard.

Going through them in turn.

The operational channel

Pick one place where the operational decisions of the group actually live. This is the channel you message first, every time, when something matters: workdays going ahead, workdays cancelled, kit arriving, council enquiries, a new tool stored in the new shed.

For most community parks groups in 2026 this is going to be WhatsApp, and probably a WhatsApp Community with a couple of linked groups (one for everyone, one for the committee). The reason isn’t that WhatsApp is good. It’s that it’s where the regulars actually pay attention. People check it. They reply. Push notifications work. That’s the whole bar, and it’s a higher bar than most other channels clear.

Things that are not the operational channel: your Facebook page (where new people find you), your Mailchimp newsletter (where members who don’t use WhatsApp hear from you once a month), your website (which exists for Google), the committee email thread (where formal decisions get recorded). All of these matter. None of them is where Saturday gets cancelled.

Naming the operational channel out loud, on the committee, is half the work. The chair messages WhatsApp first when it rains. Always WhatsApp first. Everything else is downstream.

The funnel

If WhatsApp is where decisions live, then everyone who’s going to act on those decisions has to be in WhatsApp. That sounds obvious. The reason it doesn’t happen is that there’s no single path to membership. People get added via whoever recruited them, in whatever channel that person uses, and a third of your active members are only on Facebook because that’s where they found you.

The fix is a single funnel. Every path into the group ends with the same form, and the form ends with the WhatsApp invite link.

In practice: your Facebook page links to the same signup form that your website links to that your Mailchimp newsletter links to that the QR code on the noticeboard at the park entrance links to. The form captures name, email, and which programmes they want to hear about. The confirmation page and the confirmation email both contain the WhatsApp link. The chair stops adding people manually. New volunteers are in WhatsApp before their first workday, not after.

This is the part that prevents the rainy-Saturday scene where someone drives twenty minutes because she saw the workday on Facebook and was never added to WhatsApp. She’d have been added at signup. She’d have got the cancellation message at 6

like everyone else.

A Google Form pointed at a Google Sheet does this for free. So does almost any signup tool. The mechanism is less important than the rule: one form, one path, every time.

The signup tool

This is the one piece of the system where doing it on a phone in fifteen-minute windows actively hurts you, because what you need is a signup that runs itself.

What that means concretely: a tool where you post a workday once, where members sign themselves up without asking you, where they can see who else is coming, where they get a reminder the day before, and where you can message everyone signed up without copying names into WhatsApp by hand. When someone drops out, they un-claim the slot themselves. When the workday is full, it shows as full. When it rains, you message the signed-up group from inside the same tool.

The piece that matters most is the last one. Every time you find yourself copying names between a signup tool and a chat app, the chair-at-11

problem is reappearing under a new name. So the rule of thumb when choosing is: signup and messaging in the same place.

The tool that does this most directly for community parks groups is Zelos. You post the workday, members claim a slot themselves, and the chat lives inside the same workspace, so when Saturday gets cancelled at 6

, the message goes to exactly the people who’d signed up, without you typing anyone’s name. The free plan covers unlimited members and up to 25 active workdays at a time, which is enough headroom for how a parks group actually operates. It’s built in Estonia and GDPR-compliant by default, which matters if you’re a UK or EU group holding a membership list. Workspaces are invite-only with no public directory — by design — so members aren’t exposed to anyone outside the group, and all messaging is admin-supervised, which is the right shape for a group that includes minors at children’s events. Native iOS and Android apps mean the coordinator’s phone is the actual office, which it was going to be anyway.

If you want to look at the wider field: SignUpGenius is the established web-form signup, free and ad-supported. Doodle handles one-off polls better than recurring rotas. Spond is popular with UK sports clubs and works for parks groups too. Any of them will handle the basic signup; what they don’t give you is the messaging in the same place, which is the step you’re trying to stop doing by hand.

The wrong choice is the spreadsheet shared via Google Drive, because it requires the coordinator to maintain it by hand, and that’s the chair-at-11

problem you’re trying to solve.

Whatever you pick, the rule is the same: every workday goes up the same way. Same template, same fields, same lead time. Members learn the rhythm. Their muscle memory becomes part of the system.

The records sheet

Compliance is the part where “we’re all friends” stops being enough. Working with under-18s requires a current background check. Chainsaw use requires documented training. Pesticide handling requires certification. None of this goes away because the group is a volunteer-run charity with very little in the bank, and none of it can be remembered in the chair’s head.

Build one sheet. One row per active member, columns for the things that matter: background check status and expiry date, first aid certificate, chainsaw certificate, pesticide certificate, role on the committee if any, deputy if any. Update it when something changes, which for any one person is roughly twice a year.

The point of the sheet isn’t admin theatre. It’s that when the parent volunteer offers to lead a small group of children on the bug hunt, you don’t have to make a thirty-second decision in front of an eight-year-old. You’ve already made it. The signup for the children’s session was visible only to people with current background checks; she either signed up in advance, or she’s helping with something else today.

If the signup tool you’ve picked supports filtering signup visibility by tags, this enforcement happens automatically: you tag members as “DBS-cleared” or “chainsaw-cleared” and the relevant signups only appear to people with the right tag. If it doesn’t, you check the sheet before each event. Annoying, but better than the alternative.

The records sheet is also where role descriptions live, alongside who currently holds them and who their deputy is. Not the constitutional description: what the membership secretary actually does, every quarter, in practice. This document is the most boring thing the group will produce. It’s also the thing that lets a successor exist, because the successor can read it and know what they’re walking into.

The shared folder

Everything else — meeting minutes, the constitution, insurance documents, the equipment inventory, photos for the newsletter, the risk assessments — lives in one Google Drive folder with a clear top-level structure. Six subfolders, no more. Everyone on the committee has access. The chair doesn’t need to be the keeper of any of it.

This isn’t the part of the system that breaks first, but it’s the part that breaks worst. The committee that doesn’t have shared access to its own paperwork is one resignation away from a crisis.

The small core

None of the above replaces the people. Most community parks groups are kept alive by a small handful of volunteers whose ongoing presence holds the whole thing together: the retired teacher who knows where every tool is stored, the chair who’s been chair for six years, the treasurer who’s been doing the accounts since 2017, the volunteer who quietly turns up to every workday and makes the tea. Without them, the group doesn’t run for a year. Sometimes it doesn’t survive their absence at all.

Better systems reduce the load on these people. They don’t replace them, and pretending they do is how groups end up with a polished signup tool and no chair.

If you’re reading this, you’re probably one of the small core, or you’re sitting next to one. Two things matter more than any system you build.

First, look after the people who are already doing the work. Identify them, by name, on the committee. Thank them publicly at the annual meeting. Ask them what they actually want from the group, not just what the group needs from them. Notice when they’re getting tired, and have the conversation before they have to start it.

Second, start looking for the next ones, gently and now, not when the current ones step down. They’re already coming to workdays, usually quietly, often less than the regulars, but consistently. Give them a small defined job. One workday to run. The kit list for a season. The newsletter for one issue. People who are going to grow into the small core almost always start by being given something specific to own.

This part isn’t system design. It’s the actual work of community parks volunteering, and it’s the part the system exists to give you time for.

What this is honestly going to cost

A weekend, broken across two or three weekends. The annoyance of migrating people who liked the old way. A committee meeting where you have to argue for it. A few months of lower-grade chaos while everyone learns the new rhythm. Some people who don’t make the move and quietly drift off, which is sad, and some of whom would have drifted off anyway.

What you get back is the Tuesday night where you don’t have to build the rota by hand because it built itself. The rainy Saturday where you message one channel and everyone gets the message. The new volunteer who’s already in WhatsApp the first time you meet her. The committee meeting where the deputy chair can actually deputise, because the role is written down. The annual meeting where stepping down doesn’t feel like the group might not survive it.

The work doesn’t disappear. It moves. From every Tuesday night to one long weekend, once. From your head to a sheet anyone can read. From the chair to a structure that doesn’t depend on the chair. That’s the whole point of doing it.

Someone has to do the thing. If it’s you, it’s worth doing once.