Sample project: an illustrative engagement built to show my process, not a client engagement. Willow Creek Family Resource Center is invented, and so are its volunteers, programs, grants, and figures.
Overview
In this sample, Willow Creek runs a food pantry, a weekend tutoring program, and seasonal volunteer drives, supported by two part-time staff and a rotating roster of roughly 40 volunteers. The engagement brings visibility and consistency to operations without adding complexity a small team cannot sustain.
The situation
Volunteer coordination lived almost entirely in the program director's head and a series of group text threads. Shift sign-ups, supply orders, and grant reporting deadlines were tracked across whatever tool happened to be open at the time: a paper sign-up sheet, a shared spreadsheet nobody remembered to update, or a sticky note on the office door.
A grant report deadline was nearly missed when the person responsible for compiling program outcome data assumed someone else was handling it. Volunteer no-shows were common because reminder communication was inconsistent, and new volunteers often received a different onboarding experience depending on who happened to train them.
What I built
- Volunteer trackerOne live view of every shift: program area, date, onboarding status, and an automatic confirmation status.
- Onboarding and shift coordination SOPThe repeatable process that gives every volunteer the same experience, whoever delivers it.
- Onboarding checklistOne page covering intake, orientation, and sign-off, identical for every volunteer.
- Reminder scheduleWho reminds whom, and when, so nothing depends on one person's memory.
- Grant reporting calendarEvery funder deadline with an internal due date set ahead of it, and one named owner each.
- Monthly report templateA one-page board and grant update that pulls straight from the tracker.
The tracker, in this sample
7Scheduled shifts
4Confirmed
1Confirm now
2Needs onboarding
Volunteer coverage snapshot as of September 22, 2026. Status is calculated automatically: Needs Onboarding if onboarding is incomplete, Confirm Now if the shift is within 2 days, otherwise Scheduled.
| Volunteer | Program area | Shift | Onboarded | Status | Notes |
| Maria Alvarez | Food Pantry | Sep 23 | Yes | Confirm now | Regular Saturday volunteer |
| Devon Price | Tutoring | Sep 25 | Yes | Scheduled | |
| Sam Okafor | Food Pantry | Sep 21 | No | Needs onboarding | First shift, onboarding pending |
| Lena Whitfield | Event Support | Sep 30 | Yes | Scheduled | Fall drive setup |
| Devon Price | Tutoring | Oct 2 | Yes | Scheduled | |
| Sam Okafor | Food Pantry | Sep 24 | No | Needs onboarding | Onboarding scheduled before this shift |
| Maria Alvarez | Food Pantry | Sep 30 | Yes | Scheduled | |
The plan
Every reminder has a trigger, a time, a channel, and one named owner, so a shift or a report never depends on someone remembering it.
- 2 weeks beforeOpen shifts posted
Shifts go into the tracker and volunteers are told they can sign up. Owner: Project Coordinator.
- 5 days before a first shiftOnboarding check
If onboarding still shows No, the Volunteer Lead schedules orientation before the shift.
- 48 hours beforeConfirmation
A text asks the volunteer to confirm. No reply by the next morning triggers a call. Owner: Project Coordinator.
- Morning ofSame-day reminder
Arrival time, location, and who to ask for.
- ImmediatelyNo-show or gap
The gap is flagged in the tracker and coverage is adjusted the same day. Owner: Volunteer Lead.
- Every Friday, then monthlyLogging and reporting
Volunteer hours and program outcomes are logged weekly. On the first business day of the month, the monthly report is drafted from the tracker for the program director to review.
Grant reporting, with an internal date ahead of every deadline
Grant reporting calendar as of September 22, 2026. Reminders go out 30, 14, 7, and 2 days before each due date.
| Report | Funder due | Internal due | Data source | Owner | Status |
| Regional Food Bank Network: Q3 distribution report | Oct 15 | Oct 8 | Pantry shifts and outcomes in the tracker | Program Director | In progress |
| Community Foundation: annual impact report | Nov 15 | Nov 8 | Volunteer hours and program outcomes, all programs | Program Director | Upcoming |
| State literacy grant: interim tutoring report | Dec 1 | Nov 24 | Tutoring shifts and learner outcomes in the tracker | Volunteer Lead | Upcoming |
Risks and how they were handled
This engagement's risks sit in the operating documents rather than a separate log, because each one is handled by a standing rule:
- A report deadline slips because two people assume the other owns it. Every report has one named owner and an internal due date a week ahead of the funder's.
- A volunteer no-shows. Confirmation 48 hours out, a same-day reminder, and a call when there is no reply by the next morning.
- A new volunteer starts without orientation. The tracker blocks a first shift until onboarding is marked Yes, and the Volunteer Lead is prompted 5 days out.
- Coverage disappears on the day. Gaps are flagged in the tracker immediately and coverage is adjusted the same day.
- Reporting data has to be reconstructed. Hours and outcomes are logged every Friday, so compiling a report is a filter and a review, not a rebuild.
What a client would receive
- A live volunteer and program tracker the program director can update in seconds.
- A written SOP for onboarding and shift coordination, with named roles.
- A one-page onboarding checklist, identical for every volunteer.
- A reminder schedule with a trigger, a channel, and an owner for each step.
- A grant reporting calendar and a monthly report template that pull from the tracker.