Most companies have a volunteer program. Most of those programs are used by the same quarter of the workforce every year. CECP’s Giving in Numbers survey, which draws on more than 650 multi-billion-dollar companies, reports that 25% of employees on average take part in company volunteer programs, and that the people who volunteer and the people who give are largely the same people. If your employee volunteer participation is stuck, the problem is almost never that your employees do not care. It is that the program was designed for the 25% who would show up anyway.
We work with People teams on the operations side of talent, and the pattern repeats: the volunteer calendar is full, the participation number does not move, and nobody can say why. This post is the diagnostic we run. Three numbers to pull first, then seven causes, each with a specific fix. We use the Koenig Childhood Cancer Foundation’s Crazy Socks gift bag event as the worked example throughout, because its format happens to remove four of the seven causes at once.
Diagnose first: the three numbers to pull
Before changing anything, pull three numbers for your last two or three events. They take an afternoon and they tell you which cause to fix first.
Reach. If this is under 80%, the announcement is not getting to most of the company, and Cause 3 is your problem.
Appeal. Low here points to Causes 1, 2, 5, and 6: timing, the shape of the ask, leadership, and the story.
Friction. If people sign up and do not show, Cause 4 (logistics) is eating your program.
One more number if you have it: how many employees used your volunteer time off code in the HRIS this year. We covered how to set that code up in our guide to a volunteer time off program. A generous VTO policy with single-digit usage is the clearest sign that the barrier is not permission. It is everything else on this list.
Cause 1: The event sits outside work hours
The problem. Saturday morning at a food bank, a weeknight at a shelter, a 6 am 5K. The event asks employees to trade personal time, childcare, or a commute for the company’s community goals.
The impact. The only people who say yes are the ones who already volunteer on weekends. You reinforce the 25% and never meet the 75%.
The fix. Put the primary event inside the workday, on a workday, and treat it like an all-hands. Managers block the time, not employees. If the workday version has to be shorter, make it shorter. A 90 minute on-site event at 2 pm on a Thursday will outdraw a full Saturday every time, and it does more for team cohesion because the people in the room are actual teammates, not a self-selected club.
Cause 2: The ask goes to individuals, not teams
The problem. A company-wide email with a sign-up link. Every recipient makes a private decision, and the default private decision for a busy person is to do nothing.
The impact. Sign-up rates in the low single digits, a lot of “I meant to,” and a program that looks unpopular when it was never really offered.
The fix. Invite teams, not people. Each manager gets a headcount to fill and a slot on the calendar. The decision becomes social (“our team is doing the 2 pm session”) rather than individual (“should I sign up?”). This is the single highest-leverage change on the list. It also gives you Number 1 in the diagnostic for free, because you know exactly who was asked.
Cause 3: The announcement only reaches the usual 25%
The problem. The opportunity is posted on the giving platform, the CSR Slack channel, and the intranet page. All three are read by people who already volunteer. CECP’s finding that volunteers and givers overlap by more than 11 percentage points is the same ceiling seen from the data side: the program keeps talking to itself.
The impact. Reach (Number 1) is far lower than the People team assumes. We have seen teams discover that fewer than half the company ever saw the invitation.
The fix. Route the invitation through the channels people cannot ignore: the manager’s team meeting, a calendar hold sent from the manager, and the HRIS or ATS onboarding task list for new hires. The giving platform is where people log hours, not where they discover events.
Cause 4: Logistics land on the employee
The problem. Drive across town. Sign a waiver. Complete a background check. Bring your own gloves. Find parking. Each step is small. Together they turn a yes into a no-show.
The impact. Attendance (Number 3) drops well below sign-ups, and the people who drop are disproportionately parents, commuters, and anyone with a packed afternoon. Which is most of the 75%.
The fix. Prefer partners that bring the event to you. When the nonprofit handles supplies and setup and the activity happens in your own conference room or cafeteria, the only logistics an employee faces are walking down the hall. This is the reason we keep pointing People teams at the Crazy Socks format (more on that below): KCCF coordinates the supplies and setup and brings the event on site.
Cause 5: No leader is visibly in the room
The problem. The executive sponsor writes the announcement email and skips the event. Everyone notices.
The impact. Employees read the real priority from what leaders do with their calendar, not from what they say in an email. If the VP is not there, the two hours look optional, and optional loses to the inbox.
The fix. Book leaders into a session before you announce anything, and put their names on the calendar invite. One senior leader assembling bags at the same table as a first-year analyst does more for participation than any incentive program. Recognition afterward matters too, but presence during matters more.
Cause 6: The cause has no story
The problem. “Join us for our annual day of service” describes an activity, not a reason. Employees are asked to give time to an abstraction.
The impact. Even people who attend leave without a memory of why it mattered, so they do not talk about it, and next year’s invitation lands cold.
The fix. Choose partners where a real person can tell the story in the room. Crazy Socks builds this into the format: founder Elana, a childhood cancer survivor who battled Ewing’s sarcoma at age seven, shares why the project exists before the team starts building. The idea came from her own treatment, when the dull hospital socks came to represent the monotony and sadness of those days. Employees who hear that write different notes into the bags than employees who were handed a task sheet.
Your People team runs the program. We keep the systems behind it running.
If your team also owns ICIMS, we can look at how your onboarding tasks, hiring manager workflows, and reporting are configured and show you where adoption is being lost. One client cut application time by 75% after a redesign.
Book a discovery callCause 7: Nothing is measured, so nothing improves
The problem. The program reports one number a year, usually total hours, and it is compiled by hand from the giving platform.
The impact. Total hours can go up while participation goes down, because the same 25% volunteer more. Leadership sees a healthy chart. The People team cannot explain why the culture survey says otherwise.
The fix. Report the three diagnostic numbers per event, plus unique participants as a share of headcount for the year, plus VTO code usage from the HRIS. Put them on the same dashboard as your other People metrics. If your team lives in ICIMS, the same discipline you apply to ICIMS recruiting reports applies here: define the number, name the owner, review it on a cadence.
The worked example: KCCF Crazy Socks
The Koenig Childhood Cancer Foundation’s Crazy Socks project delivers gift bags to hospitalized children battling cancer. More than 105,000 gift bags and more than 315,000 items have been distributed to children across the United States and beyond. For a People team, the event runs in three steps, in KCCF’s own words: KCCF coordinates (supplies delivered, setup handled), Elana inspires (the founder shares the why), and the team builds (participants write notes of hope and assemble the bags).
Map that against the seven causes and you can see why we use it as the example. It runs on site during work hours (Cause 1). It is booked as a team event by design (Cause 2). It lives on the manager’s calendar, not a platform listing (Cause 3). KCCF handles the logistics (Cause 4). The story is told in the room by the person it happened to (Cause 6). Causes 5 and 7 are still on you: get your leaders in the room and count the three numbers.
Everything a People team needs to plan it is on the KCCF Crazy Socks page, including a downloadable brochure and the contact details for the corporate program (join@thekccf.org). If you are still deciding between formats, our earlier guide to corporate volunteer event ideas compares the common options side by side.
A 30 day plan to move employee volunteer participation
Week 1. Pull the three numbers for your last events and VTO code usage from the HRIS. Decide which cause you are fixing first.
Week 2. Pick one on-site, work-hours event and book two leaders into it before anything is announced.
Week 3. Give every manager a headcount and a session. Send the calendar hold from the manager, not from the People team.
Week 4. Run it, count invited, signed up, and attended, and publish the three numbers internally the same week.
Most of our client work is ICIMS consulting for talent acquisition teams, and the People leaders we work with tend to own both the hiring system and the culture programs around it. The same principle holds in both: adoption follows design. A program nobody uses is not a people problem. It is a configuration problem, and configuration can be fixed in a month.
Frequently asked questions
Adoption follows design, in volunteer programs and in ICIMS
On a discovery call we will walk through how your ICIMS onboarding tasks, hiring manager views, and reports are set up, and tell you which configuration changes would move adoption fastest. One client saw 90% fewer support tickets in 90 days.
Book a discovery call
