Capability template for people and HR
Volunteer shift options
A volunteer lead gets draft shift options once an event's availability replies are in: each role's needs set against who volunteered, the requirements on record and the shifts already confirmed, with every uncovered position shown. The lead checks and confirms; nothing is assigned or sent.
Listed under
Add it to a workflow in the Fully Powered Planner, beside the teams and roles that will run it. Book a fit call
The outcome
The replies are in and the lead can see the whole event on one page. For every shift and role, the page shows how many places are needed, how many are already confirmed, how many are waiting on an answer, and which volunteers could take what is left. Two draft options follow, one that fills places in a set order until no more can be filled (not a guaranteed maximum) and one that gives each volunteer a single shift, so the lead can see what each choice costs in gaps.
The gaps are never hidden. A place nobody can take is shown as uncovered, with the reason. A volunteer whose requirement is not on record is shown as a possibility to check, never as cover. Interest is not qualification, and a pending confirmation is not a confirmation.
The lead still decides. The template rates, ranks and turns away no one, places nobody for good and contacts no volunteer. Suitability, assignments and every conversation with a volunteer stay with the lead.
Who starts the work, and when
The volunteer lead starts it when the availability replies for an event have come in and some places on the role list are still open. It runs again when a late reply arrives, when someone withdraws or when the role list changes. The lead reviews both options, adjusts them and confirms assignments with volunteers directly. Event staff and program delivery read the result once the lead has settled it.
What they supply
- The event's role list: for each shift, its date and hours, each role, how many places are needed and any requirement for the role.
- The availability replies: for each volunteer, the date, the hours they offered, the roles they chose, the most shifts they will do and any note they wrote.
- The qualification records you already keep, such as a food handler card or a completed training, with each record's status and expiry.
- The assignments already made, confirmed or still pending.
- A few settings: the event name, today's date and a default limit on shifts per volunteer.
What comes out
One page in a fixed order. The places still to fill, with the volunteers who could take each. Two draft options, each showing who is placed where, what is left uncovered and why, and which volunteers are not placed. Then the flags that need a person: pending confirmations, hours that do not cover a shift, requirements not on record, volunteers' own notes, and questions only the lead can settle. Volunteers appear by the code and name in your files, and no contact details are repeated.
An invented example
Illustrative example with invented data. Marrow Creek Community Meals is an invented nonprofit, and the event, the volunteers, the codes, the cards and every figure below are invented. The volunteers are written as a code and a first name with an initial. First come the inputs the volunteer lead supplied, in full, then the page the capability returned.
The inputs
SETTINGS
Event: Autumn Neighbor Supper
Volunteer lead: Noor Hale
Today: Tuesday 10 November 2026
Default shift limit per volunteer: 2
ROLE LIST (roles.csv)
shift_id,event_date,shift_start,shift_end,role,positions_needed,requirement
S1,2026-12-05,09:00,12:00,Setup crew,3,
S1,2026-12-05,09:00,12:00,Kitchen helper,2,Food handler card
S2,2026-12-05,12:00,15:00,Serving line,3,Food handler card
S2,2026-12-05,12:00,15:00,Greeter,2,
S3,2026-12-05,15:00,17:00,Cleanup crew,3,
AVAILABILITY REPLIES (availability.csv)
volunteer_id,volunteer_name,event_date,available_from,available_to,roles_interested,max_shifts,note
V01,Alma R.,2026-12-05,09:00,17:00,Setup crew;Cleanup crew,2,
V02,Bruno T.,2026-12-05,09:00,12:00,Setup crew;Kitchen helper,1,
V03,Cleo M.,2026-12-05,09:00,15:00,Kitchen helper;Serving line,2,
V04,Dev K.,2026-12-05,12:00,17:00,Greeter;Serving line;Cleanup crew,2,
V05,Esme L.,2026-12-05,09:00,11:30,Setup crew,,Can only stay until 11:30
V06,Farid N.,2026-12-05,12:00,17:00,Serving line,1,
V07,Greta P.,2026-12-05,09:00,17:00,Setup crew;Greeter;Cleanup crew,3,Prefers not to work two shifts back to back
V08,Hugo S.,2026-12-05,12:00,17:00,Greeter;Cleanup crew,2,
V09,Ivy D.,2026-12-05,09:00,15:00,Serving line;Kitchen helper,2,
V10,Jonas B.,2026-12-05,15:00,17:00,Cleanup crew,1,
V11,Kira O.,2026-12-05,,,,,Away that weekend
QUALIFICATION RECORDS (qualifications.csv)
volunteer_id,qualification,status,valid_until
V03,Food handler card,Confirmed,2027-03-31
V04,Food handler card,Confirmed,2027-06-30
V06,Food handler card,Confirmed,2026-11-30
V09,Food handler card,Pending,
ASSIGNMENTS SO FAR (assignments.csv)
volunteer_id,shift_id,role,status
V07,S2,Greeter,Confirmed
V08,S3,Cleanup crew,Pending
The output
VOLUNTEER SHIFT OPTIONS: Autumn Neighbor Supper, Saturday 5 December 2026
For: Noor Hale, volunteer lead. Prepared Tuesday 10 November 2026 from 5 role rows (13 places), 11 availability replies, 4 qualification records, 2 assignments (1 confirmed, 1 pending). Default shift limit: 2 stated. Limit not stated for: V05. Nothing has been assigned or sent.
Places to fill
S1 Saturday 5 December 09:00-12:00, Setup crew (no requirement): needed 3, confirmed 0, pending 0, to fill 3. Could take it: V01 Alma R., V02 Bruno T., V07 Greta P.
S1 Saturday 5 December 09:00-12:00, Kitchen helper (Food handler card): needed 2, confirmed 0, pending 0, to fill 2. Could take it: V03 Cleo M.
S2 Saturday 5 December 12:00-15:00, Serving line (Food handler card): needed 3, confirmed 0, pending 0, to fill 3. Could take it: V03 Cleo M., V04 Dev K.
S2 Saturday 5 December 12:00-15:00, Greeter (no requirement): needed 2, confirmed 1, pending 0, to fill 1. Could take it: V04 Dev K., V08 Hugo S.
S3 Saturday 5 December 15:00-17:00, Cleanup crew (no requirement): needed 3, confirmed 0, pending 1, to fill 2. Could take it: V01 Alma R., V04 Dev K., V07 Greta P., V10 Jonas B.
Totals: needed 13, confirmed 1, pending 1, to fill 11.
Order used: S1 Kitchen helper (1 could take it), S2 Serving line (2), S2 Greeter (2), S1 Setup crew (3), S3 Cleanup crew (4).
Option 1: Fill as many places as the order allows
S1 09:00-12:00, Setup crew: placed V01 Alma R., V02 Bruno T., V07 Greta P. Confirmed already: none. Pending: none. Uncovered 0.
S1 09:00-12:00, Kitchen helper: placed V03 Cleo M. Confirmed already: none. Pending: none. Uncovered 1. Why: V03 is the only volunteer who chose it and could take it, and V03 already holds the one place drafted here; V02 and V09 are under "Requirement not on record".
S2 12:00-15:00, Serving line: placed V04 Dev K., V03 Cleo M. Confirmed already: none. Pending: none. Uncovered 1. Why: V06 and V09 are under "Requirement not on record".
S2 12:00-15:00, Greeter: placed V08 Hugo S. Confirmed already: V07 Greta P. Pending: none. Uncovered 0.
S3 15:00-17:00, Cleanup crew: placed V10 Jonas B., V01 Alma R. Confirmed already: none. Pending: V08 Hugo S. Uncovered 1, of which pending 1. Why: the last place is held for V08's pending confirmation.
Covered 10 of 13 places (confirmed 1, drafted 9). Uncovered 3, of which pending 1.
Not placed in this draft: V05 Esme L., hours do not cover; V06 Farid N., requirement not on record; V09 Ivy D., requirement not on record; V11 Kira O., replied not available.
Option 2: One shift each
S1 09:00-12:00, Setup crew: placed V01 Alma R., V02 Bruno T. Confirmed already: none. Pending: none. Uncovered 1. Why: V07 could take it but is at the limit (confirmed for S2 Greeter); V05 chose it but the hours do not cover the shift.
S1 09:00-12:00, Kitchen helper: placed V03 Cleo M. Confirmed already: none. Pending: none. Uncovered 1. Why: V03 is the only volunteer who chose it and could take it, and V03 already holds the one place drafted here; V02 and V09 are under "Requirement not on record".
S2 12:00-15:00, Serving line: placed V04 Dev K. Confirmed already: none. Pending: none. Uncovered 2. Why: V03 is at the limit; V06 and V09 are under "Requirement not on record".
S2 12:00-15:00, Greeter: placed nobody. Confirmed already: V07 Greta P. Pending: none. Uncovered 1. Why: V04 is at the limit; V08 is at the limit (pending for S3).
S3 15:00-17:00, Cleanup crew: placed V10 Jonas B. Confirmed already: none. Pending: V08 Hugo S. Uncovered 2, of which pending 1. Why: V01, V04 and V07 are at the limit; one place is held for V08's pending confirmation.
Covered 6 of 13 places (confirmed 1, drafted 5). Uncovered 7, of which pending 1.
Not placed in this draft: V05 Esme L., hours do not cover; V06 Farid N., requirement not on record; V07 Greta P., limit reached; V08 Hugo S., limit reached; V09 Ivy D., requirement not on record; V11 Kira O., replied not available.
Flags for the volunteer lead
Pending confirmations: V08 Hugo S., S3 Cleanup crew.
Hours do not cover the shift: V05 Esme L. offered 09:00-11:30; S1 Setup crew runs 09:00-12:00, 30 minutes longer.
Requirement not on record: V02 Bruno T., S1 Kitchen helper needs a Food handler card and no record exists. V06 Farid N., S2 Serving line: card Confirmed but valid until 2026-11-30, before the event. V09 Ivy D., S1 Kitchen helper and S2 Serving line: card status Pending.
Back-to-back shifts in an option: Option 1: V03 Cleo M., S1 Kitchen helper then S2 Serving line. V07 Greta P., S1 Setup crew then V07's confirmed S2 Greeter. V08 Hugo S., S2 Greeter then V08's pending S3 Cleanup crew. Option 2: none.
Notes from volunteers, as written: V05 Esme L.: "Can only stay until 11:30". V07 Greta P.: "Prefers not to work two shifts back to back". V11 Kira O.: "Away that weekend". The notes have not been applied to either option.
Roles named that are not on the role list: none.
Replied, not available: V11 Kira O.
Over-filled places: none.
Questions for the volunteer lead
1. V08 Hugo S. is pending for S3 Cleanup crew. Is that confirmed or released? Option 1 also places V08 in S2 Greeter, the shift before it.
2. V07 Greta P. wrote "Prefers not to work two shifts back to back". Option 1 places V07 in S1 Setup crew, which ends when V07's confirmed S2 Greeter shift begins. Is that acceptable to V07, and to you?
3. V05 Esme L. can stay only until 11:30. Is a shorter stay acceptable for S1 Setup crew?
4. V02, V06 and V09 have no usable Food handler card on record. Can any record be confirmed before 5 December? S1 Kitchen helper and S2 Serving line each have one place uncovered in Option 1.
Draft for Noor Hale's review. Nothing has been assigned, confirmed with a volunteer, sent or changed in any record.
Where it fits
- People and HR, because the work is matching people to places, with the lead keeping every decision about them.
- Operations and process improvement, where an event's day is made to work with the people who offered.
- Nonprofits, where events run on volunteers and the replies arrive in a pile.
- Education, for school and college events staffed by parents, alumni and students.
- Government, for community events run by a public office or library.
- Established businesses, for organizations that hold the same events year after year.
- Growth & scaling, when the volunteer list outgrows what a lead can hold in their head.
It is not the event plan, which plans the event itself, and it is not the employee onboarding plan, which welcomes someone who has already joined. The service roster options work in headcounts for paid staff; this one works with named volunteers and the offers they made.
What has to change for your company
Rename the roles and shifts to match your events. List the requirements you actually set and where each is recorded. Decide your default limit on shifts per volunteer and whether a volunteer may work two shifts that touch. Decide who confirms assignments and in what words, since the template writes no message to volunteers. Agree how late replies and withdrawals reach the lead. Keep contact details out of what you paste. The template reads files you supply and needs no connection to your volunteer database, so it runs in the AI product your team already uses.
What has been checked
Fully Powered AI wrote this capability template. It was editorially reviewed on 10 November 2026. It was tried once on its invented example in Claude on 10 November 2026; the record of that run is published with it. Edits made after that run have not been run again: Option 1 was renamed, its overlap rule now also excludes a volunteer whose drafted shifts overlap, the date style and the rules for "Limit not stated for", "limit reached" and shared questions were settled, and the example was corrected to match. Its acceptance tests 2 to 14 are proposed and have not been run. It has not yet been tested in a client environment. It has not yet been tested as a packaged version in ChatGPT, Claude, Copilot or Gemini.
Testing in your environment means running it on a past event whose staffing you already know, with cases written in advance: a reply that covers only part of a shift, an expired card, a volunteer with a note about back-to-back shifts, a pending confirmation and a renamed column. The lead checks every place against the files before anyone is asked to confirm.
The full capability template
Everything above is the outline. The complete capability template is the working version: the roles, the inputs, the procedure, the exceptions and stop conditions, the output format, the reviewer checklist, the acceptance tests, the instructions for an AI assistant and what to customize for your company. It comes with a download and the link to its folder in Fully Powered’s public repository.
Free with an account. Sign in by email: no password and no card.
Next step
Put this capability to work for your team: on your plan, or built with you in a sprint.
Build this in a sprint
In a sprint, Fully Powered adapts this capability template to your rules, proves it on your own work and puts it in the hands of the roles that own it.
Two ways to begin: