Recruit volunteers with clear roles, honest time commitments and a short form
People rarely decline to volunteer because they don't care. They hold back because they can't tell what they'd be doing, for how long, or whether they're qualified. A volunteer sign up page that answers those three questions for each role, then asks for a few details, recruits far more reliably than "we'd love your help". Anticode builds the page and sends each sign-up straight to whoever coordinates.
Describe roles, not a cause
The cause is why people arrive; the role is why they sign up. Instead of one general appeal, list each role as its own short card with the same five facts. People scan for the one that fits their week.
| Role | What you'd do | When | Commitment | Needs |
|---|---|---|---|---|
| Warehouse sorter | Check dates and sort donations into crates | Tuesday or Thursday, 10:00 to 13:00 | One shift a fortnight | Able to lift light boxes |
| Delivery driver | Drop parcels to homes in the town | Saturday mornings | Two Saturdays a month | Full licence, own car, mileage paid |
| Welcome desk | Greet visitors and take referral details | Weekday afternoons | Weekly, three months minimum | Patience; training given |
| Event helper | Set up and run the winter appeal collection | One weekend in December | One-off | Nothing |
Include at least one one-off role. Many people won't commit to a weekly slot until they've tried you once.
Be honest about what's involved
- Time, including the hidden time. Training sessions, induction, travel to the site.
- Checks. If a role involves children or vulnerable adults, say a background check is required and that you arrange it. Where it applies (a DBS check in England and Wales, for example), name it.
- Costs. Whether expenses or mileage are reimbursed.
- Accessibility. Whether the site has step-free access, and whether roles can be adapted.
- Age limits. If under-18s can help, and on what terms.
This is also what reduces no-shows. A volunteer who knew exactly what Saturday involved is more likely to turn up for it.
The form: five questions or fewer
The first form is an expression of interest, not an application. Ask for name, email, phone, the roles they're interested in, and when they're usually free. Anticode's built-in contact form only has name, email and message, so a form with these fields is a custom form tied to a site function (up to 30 plain-text fields); or keep the contact form and list the questions above it. Leave references, emergency contacts and health information for later, once someone has spoken to them, and collect those through your organisation's proper process rather than a public web form.
Say right above the form what happens next: "Our volunteer coordinator, Priya, will call you within a week to arrange a short induction." A name and a timescale make the sign-up feel received.
Getting sign-ups to the coordinator
On Anticode, each sign-up is saved to the project, sealed at rest with AES-256-GCM, and can be emailed to the coordinator. Connectors then send it wherever the team works. Two setups suit most volunteer programmes:
- A shared spreadsheet
- The Google Sheets connector adds a row per sign-up through an Apps Script web app. Add columns for "called", "inducted" and "first shift" and you have a simple volunteer pipeline. Airtable or Notion work the same way if the team prefers them.
- A team channel
- A Slack, Discord or Telegram message for each sign-up, so whoever is free can pick it up quickly. Useful before a big event when volunteers are needed this week, not next month.
Each submission is sent to a connector once, without retries, so keep the email copy on. The dashboard's access log records the last 200 reads, exports and deletes of form data, which helps if someone asks what happened to their details. The form submissions to Google Sheets guide shows the setup, and the volunteer sign-up process covers what happens after.
Building the page
Describe the organisation and the roles: "a volunteer sign up page for Eastgate Food Share with four roles, their times and what each needs". The Architect asks a few questions where they change the page, then the design engine builds it. Because a site that collects personal data can't be published until the account owner and the person publishing have two-factor sign-in turned on, you'll be asked to set that up first. That's a sensible requirement for volunteer details. Anticode also writes a Privacy Policy for the site from what the form collects; check it fits your organisation's own policy.
What the page won't handle
- No shift rota or scheduling. Volunteers can't pick slots from a calendar, and there's no staff rota feature. Use a rota tool once people are on board.
- No volunteer accounts or hours logging. There are no logins on published sites.
- No automatic reply to the volunteer. Anticode can email the coordinator; replying to the volunteer is done by a person or by a tool connected through a webhook.
- No document uploads. Collect certificates or ID through your own secure process.
Questions people ask
Can I use the booking calendar for volunteer shifts?
It's built for appointments: it refuses double-booked slots, so only one person can take each time. That doesn't fit shifts needing several volunteers, and there's no rota feature.
Where should the volunteer page live?
Linked from your main navigation or footer, with its own address you can share in posters and posts. It can be a section of a larger site or a small site of its own.
How do I stop the form being spammed?
Keep the form short, avoid publishing the coordinator's personal email address on the page, and check new rows before acting on them. The guide on stopping contact form spam covers more.