Volunteer hour requirements are one of those policies that sound simple at a board meeting and get complicated by the second week of the season. Set the number too low and the same six families carry everything anyway. Set it too high and you spend the season fielding hardship emails. Write the policy vaguely and you'll relitigate it at every pickup.
Here's how to set a requirement that's fair on paper and in practice — and one you can actually enforce without becoming the villain of the group chat.
Start from the work, not from a round number
Most clubs pick a number that sounds reasonable — "ten hours per family" — and hope it covers the season. Do the math the other direction instead.
List the events and jobs that genuinely require volunteers: home games, concessions, tournaments, setup and teardown, photo day, the year-end banquet. Estimate the volunteer-hours each one needs, total them, and divide by the number of families.
Take a soccer club with 80 families. Ten home game days needing 8 volunteers for 3 hours each is 240 hours. A weekend tournament needs another 150. Add 60 for miscellaneous events and you're at 450 hours — about 5.5 hours per family. That's your requirement, maybe rounded to 6 with a little slack. If your math says you need 14 hours per family, that's not a requirement problem; that's a sign your program is trying to run too many volunteer-hungry events.
When the number is derived from real work, you can explain it. "We need 450 hours to run the season and there are 80 of us" lands very differently than "the board decided on ten."
Make it per-family, with the right escape valves
Per-family (not per-parent, not per-child) is the standard for good reason: it's the unit people actually budget time in. But a bare number isn't enough. Decide these up front and put them in writing:
- Who can work the hours? Most clubs allow any adult connected to the family — parents, grandparents, an older sibling over 16 for appropriate roles. The wider you draw the circle, the fewer hardship cases you'll handle.
- Do multi-child families owe more? Common answers: a flat family rate regardless of kids, or a modest bump per additional child (6 hours for one, 8 for two or more). Pure multiplication — 6 hours per kid — punishes exactly the big families that are already stretched thin.
- What counts? Be explicit. Scheduled shifts count. Board service counts (usually generously). Driving your own kid to practice does not. Ambiguity here is where most disputes are born.
- Is there a buyout? Some families genuinely cannot give time and would rather give money. A buyout option (covered in depth in its own decision) keeps the requirement honest for everyone else, but it needs careful pricing so volunteering doesn't become the budget option only.
Enforceability lives and dies on tracking
A requirement you can't measure is a suggestion. Before the season starts, you need answers to three questions any family might ask:
- How many hours do we have so far?
- Which shifts did they come from?
- How many do we still owe?
If answering those takes you twenty minutes of spreadsheet archaeology, the requirement will quietly collapse around midseason — families stop trusting the numbers, and you stop wanting to defend them.
This is where doing it digitally pays for itself. When shift signups, arrival check-ins, and hour credits live in one system, every family's balance is current without anyone doing data entry on Sunday nights. HometownLift's volunteer tools track hours per family automatically as shifts are worked and checked in, and families can look up their own balance — which means the question "how many hours do I have?" stops arriving in your inbox at all.
Decide the consequence before you need it
The hardest part of a requirement isn't setting it; it's the family that ends the season at 2 of 6 hours. Decide now, in the calm of preseason, what happens — because deciding case-by-case in May guarantees inconsistency and resentment.
Workable consequences, roughly in order of teeth:
- A deposit check collected at registration, returned (or torn up) when hours are met, cashed if they aren't. Clear, self-enforcing, and very common.
- A fee invoiced for unmet hours at a stated rate per hour.
- Registration hold for next season until the balance is settled.
Whatever you choose, pair it with grace built into the policy itself: a midseason reminder when a family is behind pace, an explicit hardship process handled privately by one designated person, and a cutoff date late enough that a busy family can still catch up at the spring tournament.
The goal of the consequence is not revenue. It's making sure that the family who worked six Saturdays isn't subsidizing the family who worked none. Say that sentence out loud at the parent meeting — it's the entire moral case for the policy, and almost everyone accepts it when it's framed that way.
Communicate it like a contract, run it like a community
Put the requirement in registration materials, have families acknowledge it when they sign up, and mention it once at the season kickoff. Then stop talking about it like a rule and start talking about it like logistics: "We still need four people for Saturday's gate" recruits better than "remember, you owe hours."
A requirement is the floor, not the culture. The clubs that thrive are the ones where the requirement exists, is tracked honestly, is enforced predictably — and is mostly invisible, because people are signing up anyway.
The bottom line
Derive your hour number from the actual work divided by actual families. Define who can work, what counts, and what happens at zero — in writing, before the season. Track hours in a way families can check themselves, enforce the consequence you announced, and handle hardship privately and generously. Fair, visible, predictable: that's a requirement that holds up from August to May.
When you're ready to make hour tracking automatic instead of a spreadsheet chore, see how HometownLift handles volunteer scheduling and hours.