Recruiting a volunteer is hard. Everything after the yes is where you actually keep them.
Here’s what usually happens once someone agrees to help. They’re keen on the day they sign up, and then there’s a gap. They wait to hear what’s next, the forms trickle in over email one at a time, and the training they needed lands after their first shift instead of before it.
By the time anyone checks in, the spark has gone out. Nobody did anything wrong. There just wasn’t a process to carry them from “I’m in” to “I know what I’m doing.”
That stretch is onboarding, and most nonprofits run it by hand. This post covers how to build it on the WordPress site you already run, using Gravity Forms to collect the information a volunteer needs to provide, Gravity Flow to route the checks and schedule the induction, and Gravity SMTP to make sure the welcome emails land.
One thing to be clear about up front: this is onboarding people you’ve already accepted. Recruiting, interviewing, and screening happen before this point and are their own topic. This picks up the moment someone becomes a yes and carries them to a confident first shift.
The nonprofits this works for
If your volunteers need more than a signup form before they can start, this is for you. How much more depends on the role, which is why a one-size process struggles:
- Hospice and care organizations – Volunteers who sit with patients or visit people at home are in a position of real trust. You need references and ID on file, a background check done, and safeguarding training completed before their first visit, and none of it can be skipped.
- Youth mentoring and tutoring programs – Anyone working with children has to clear a background check and finish training before they’re matched with a young person. The sequence makes sure that order never gets reversed.
- Food banks and community pantries – These often onboard volunteers in waves before a big distribution or the holidays. The checks are lighter, so the priority is speed and warmth. Collect emergency contacts and a waiver, send the orientation details, and get people rostered quickly.
- Conservation and community groups – Event and project volunteers need emergency contacts, a bit of induction detail about the site, and a friendly introduction to the team lead they’ll work under on the day.
The shape is the same every time. Someone has said yes, and the job now is to get them ready, checked where the role calls for it, and made to feel part of the team before they show up. Some roles need a lot before that first shift and some need very little, and good onboarding bends to fit both.
Where volunteer onboarding breaks
In practice, onboarding tends to fall apart in four places:
- The silence after “yes” – Enthusiasm peaks the day someone is accepted, and that’s often when nothing happens. Every week of quiet makes it less likely they’ll ever start, and you rarely find out why.
- Paperwork trickles in over email – Agreements, emergency contacts, references, and copies of ID get chased one message at a time, and the coordinator is the only person who knows what’s still outstanding.
- Checks get skipped or done late – Background checks and role-specific training are the steps you cannot miss, and they’re the easiest to lose track of when everything is manual. A volunteer slipping into a client-facing role before their check clears is the gap that keeps a safeguarding lead up at night.
- Everyone is onboarded identically – The volunteer stuffing envelopes and the volunteer visiting patients go through the same process, which is either far too much for one or dangerously too little for the other.
The fix is one process that bends to fit the role. Each new volunteer fills in a single form that asks for exactly what their role requires, and the checks that role calls for happen in the right order, before the first shift rather than after it. In between, a series of scheduled emails keeps them informed and welcomed, so the gap between saying yes and showing up never goes quiet.
The onboarding form (Gravity Forms)
The volunteer fills in one form, and you send them the link once they’re accepted. The link already carries the role they’ve joined, so the form only asks for what that role requires.
Set the role before the volunteer opens the form – Gravity Forms can fill in a hidden field automatically, so the setup is one form with a hidden role field, embedded on a separate page for each type of role. When your coordinator accepts a new volunteer, they send the link that matches the role, and the volunteer opens a form that already knows which one they’re joining. They never see the field or have to choose anything, which matters, because the role decides everything that follows.
Ask each role for what it needs – Because the role is set when the form loads, conditional logic can show each volunteer only the fields that apply to them. Someone joining a mentoring role is asked to upload photo ID, name two referees, and agree to a background check. Someone helping at a weekend event is just asked for a photo for their volunteer badge. It’s the same form doing both jobs, and nobody has to send in a passport scan to hand out water at a fun run.
Cover the agreements and the practical details – Use the Consent field for the things every volunteer signs, like a code of conduct or photo permission. If you need a real signature on a waiver, the Signature Add-On (included with the Elite and Nonprofit licenses) lets volunteers sign on any device. Then add the small things, like availability, t-shirt size, or dietary needs for the induction, so nobody is chasing them the week of the first shift.
Routing the checks (Gravity Flow)
Once the form is in, Gravity Flow takes over. The role arrived with the submission, so the workflow knows which path each volunteer belongs on. This is the part a form on its own can’t do.
The heart of it is routing by role. Roles that need vetting branch to a compliance step, and roles that don’t go straight to the welcome. A youth mentoring role routes to a background check before anything else happens, while an event volunteer never touches that branch.
The compliance step is assigned to whoever owns vetting. It holds the volunteer there until that person confirms the background check is clear and the references check out, then marks them cleared to continue. To be precise about what this does: Gravity Flow records the check and won’t let the volunteer move forward without a sign-off, but it doesn’t run the check, and it isn’t your safeguarding policy. It supports the process you already have, and the judgment stays with your people.
A second step lets the coordinator assign a buddy or team lead, so the volunteer arrives to a named person rather than a room of strangers. Pairing people up is one of the cheapest ways to keep a volunteer, and building it into the sequence means it happens every time.
Two notes from experience. Keep the compliance branch as strict as your policy requires, and send anything ambiguous to a human rather than trying to automate the decision. And build the first version with one simple role, get that path working end to end, then add the vetted roles.
The welcome sequence (Gravity Flow and Gravity SMTP)
This is the part that decides whether a volunteer sticks around. Everything above gets them ready, and this is what makes them feel wanted.
Gravity Flow can schedule steps around a date, so instead of sending everything at once, you can time a series of emails around the volunteer’s start date. A warm welcome the day they’re cleared, a “what to expect” email a few days before their first shift, an introduction to their buddy, a reminder to finish any online training. That steady contact covers exactly the window when volunteers usually go quiet.
Gravity SMTP makes sure those emails arrive. It routes your WordPress email through a transactional service with delivery logs, so a welcome doesn’t sit in a spam folder while you assume it was read.
Tone matters as much as timing. These emails should sound like a person who’s glad the volunteer is coming, not a system processing an entry. Name the coordinator they can call, tell them where to park, say what to wear. Those small details are what turn a nervous first-timer into someone who comes back.
What this doesn’t do
A few limitations:
- It’s onboarding, not recruitment – Advertising roles, taking applications, and deciding who to accept all happen before this build begins. It picks up once someone is a yes.
- It doesn’t run your background checks – The workflow routes a volunteer to the check and records the sign-off, but the check happens with your provider, and the safeguarding policy behind it is yours.
- It isn’t a volunteer management system – Shift scheduling, hours tracking, and rota management are what dedicated platforms are for. This build carries a new volunteer from accepted to ready, and that’s it.
The volunteer who comes back
A volunteer’s first few weeks decide whether there’s a second month. Someone who was welcomed the day they joined, told what to expect, checked where their role required it, and introduced to a real person walks into their first shift feeling part of something. Someone who filled in a form and heard nothing for three weeks often doesn’t walk in at all.
That work is the same every time, which is exactly what a workflow is for. Build the sequence once, on the site you already have, and every volunteer moves through it feeling looked after, while your coordinator gets back to the part only a person can do, which is making people feel welcome.
If your organization is a registered nonprofit, you can get started with all of the functionality in Gravity Forms by purchasing the Gravity Forms Nonprofit license.
Already using Gravity Forms? You have half of this built. Gravity Flow and Gravity SMTP add the rest. Check out Gravity Flow pricing to get started, or try a personalized demo to see a time off workflow in action.
Newsletter
If you want to keep up-to-date with what’s happening on the blog sign up for the Gravity Forms newsletter!
"*" indicates required fields
