Nonprofit·Cleveland, QLD·2025
Redlands Landcare Network
Volunteer rosters that aren’t a Facebook thread
Planting-day signups work for people who are not on Facebook
Client
Incorporated association: one paid coordinator (Maree, three days a week), a volunteer committee, and a few hundred members who show up unevenly. Council grants pay for plants; labour is volunteer.
Engagement
Low-budget site and roster. Committee signed IA in one evening meeting. Maree is the publisher. We trained two backup volunteers in case she is on leave.
Duration
5 weeks
A volunteer network on the Redlands coast was organising planting days in a Facebook group and a spreadsheet only one person could unlock. We gave them a small public site, a roster the coordinators share, and a signup that does not require a Facebook account.
- Nonprofit
- Volunteers
- Webflow
Starting point
Event details lived in a Facebook group older members refused to join. The spreadsheet of ‘who said they’d come’ sat on Maree’s laptop. Wet-weather cancels were a post that half the group never saw. Grant acquittals asked for attendance numbers Maree reconstructed from memory.
Challenge
Budget was a council digital grant, not a marketing department. The committee wanted it to look like a community group, not a startup. Nobody would learn a heavy CMS.
Approach
Public pages for upcoming days, how to join, and where the money goes. Signup writes to Airtable; Maree marks attended after the day. Wet-weather sends one email to the signed-up list. CMS fields are named in plain English. We spent an hour with two backups clicking ‘duplicate event’.
How it ran
Discovery through launch — emphasis changes by client; this is how this one actually went.
- 1
Discovery
Sat in the committee meeting. Listed what Facebook was actually doing for them.
- 2
IA & grant facts
What funders need to see. What volunteers need on a Saturday morning.
- 3
Build
Webflow CMS, Airtable, confirmation email, mobile check on Maree’s phone.
- 4
Training
Two backups duplicate an event live. Printed one-pager on the fridge in the shed.
- 5
First live day
We were on-call for the first planting Sunday. One field renamed after people called it ‘the creek day’.
What we shipped
- Public events site Maree can update
- Signup without a Facebook account
- Shared roster and attendance export
- Wet-weather email to the signed-up list
Outcomes
- →People without Facebook can still sign on for a Sunday
- →Maree exports attendance for grant acquittals instead of reconstructing it
- →Wet-weather cancel reaches the people who said they were coming
Stack
- Webflow (public site + CMS for events)
- Airtable (roster, wet-weather cancel)
- Email confirmation (not another Facebook event)
- Council grant logo block Maree can swap
Constraints
- Grant-sized budget — no custom app
- Must stay editable by non-technical backups
- No member paywall in this phase
What actually worked
Naming CMS fields the way Maree already talked. A beautiful ‘volunteer OS’ would have died in week three.
From the room
“I can send the grant officer a list that did not come out of my head. That is the win.”
— Maree Walsh, coordinator
Related work
More case studies
Live productSafety & compliance SaaS · Sydney, Australia
Vouchd
Safety & compliance checklists teams actually finish on site
Allied health · Ryde, NSW
Harbour Physio
Bookings that don’t die in the lunch-hour voicemail
Trades · Preston, VIC
Northside Electrical Group
Job status without ringing every van