Know your VBS volunteers are safe, staffed, and ready.
VBSReady turns a church volunteer spreadsheet into a deadline-ready packet: cleared helpers, missing training, role coverage, conflict flags, reminder drafts, and parent-safe rosters before VBS week starts.
Landing-page validation only. Early users share redacted/status-only data; no sensitive background-check reports required.
vbs readiness packet
84 volunteers · 11 missing · 3 rooms short
Pre-K room
Two cleared helpers, one youth volunteer needs adult pairing
Games station
No lead assigned for Wednesday afternoon
Check-in desk
All helpers trained; allergy notes hidden from public roster
Coordinator summary
Every missing item points to a volunteer, role, day, and next message so the coordinator can fix the roster without rebuilding another spreadsheet.
Narrow customer
Children's-ministry and VBS coordinators at small churches who already have volunteer registrations in Excel, Google Forms, email, and church-system exports.
Paid problem
The week before VBS, one unclear helper status can become a staffing gap, safety concern, parent-confusion moment, or late-night coordinator scramble.
Landing test
The waitlist tests whether coordinators will share a redacted spreadsheet for a concierge readiness packet before buying a seasonal product.
Day-in-the-life pain
The sheet says 84 volunteers. It does not say whether Monday morning is safe.
A coordinator exports form responses, copies them into a roster, checks who can serve with kids, remembers who still needs training, splits family members across rooms, prints sign-in sheets, and answers the same “am I scheduled?” questions. The problem is not collecting names. It is knowing which names are cleared, assigned, shareable, and ready before children arrive.
Input
Upload the volunteer spreadsheet, Google Form export, or registration CSV that already has names, roles, availability, training notes, and background-check status.
Readiness checks
VBSReady groups volunteers by role and day, flags missing safety status, youth-volunteer constraints, classroom coverage gaps, duplicate records, and people who still need a coordinator nudge.
Output
A VBS-week packet: safe / missing / blocked board, role rosters, parent-safe exports, reminder drafts, sign-in sheets, and a coordinator summary for the ministry lead.
Current workaround and why it breaks
A spreadsheet can collect names, but it becomes fragile when status fields, role assignments, availability, youth-volunteer limits, room ratios, training requirements, and shareable exports all change at once. The failure mode is not a prettier table; it is a coordinator discovering the gap during volunteer check-in.
Features tied to the evidence
A readiness packet, not another church suite.
Spreadsheet import first
Start from the Excel or Google Sheet already used by the coordinator. No church-management migration required for the first packet.
Safe / missing / blocked lanes
Separate cleared volunteers from people missing training, background-check status, availability, or parent/guardian constraints.
Role and room coverage
Show which rooms, days, and stations are understaffed before the Sunday-night panic begins.
Parent-safe exports
Create teacher, check-in, and room-lead versions that hide fields not needed by every helper.
Concierge readiness packet
Early users get one redacted spreadsheet review and a VBS-week packet before a full product is built.
Community evidence
The evidence points to a spreadsheet-to-roster wedge.
The sources are public issue trackers and public discussion, summarized without unnecessary usernames. Reddit was searched first for this run, but direct Reddit endpoints were blocked, so this page cites only accessible evidence.
GitHub Issues · VBS volunteer spreadsheet
A VBS organizer describes volunteer registrations being collected and managed in a manual spreadsheet named VBS 2026 Volunteer Registrations (Final).xlsx, then asks for a structured app flow to remove manual entry.
Open source →
GitHub Issues · VBS setup from Excel
The same VBS workflow starts from an Excel volunteer tracker, which points to a practical migration need: import the sheet coordinators already trust and turn it into readiness checks.
Open source →
GitHub Issues · volunteer / NGO operations
Volunteer organizations are described as struggling with volunteer records, schedules, campaigns, communications, and coordination. That corroborates the broader operations pain while VBSReady stays narrower.
Open source →
Hacker News · why small teams stay in Sheets
Operators build CRMs and dashboards in Google Sheets when vertical software is unavailable, too expensive, or seat-priced. The landing test leans into spreadsheet compatibility instead of forcing a suite migration.
Open source →
Objections
Designed for the coordinator who does not want another platform before VBS week.
Why not Planning Center or ChurchTrac?
Those suites can be excellent, but the evidence points to coordinators whose operating truth is still a seasonal spreadsheet. VBSReady is a preflight packet, not a full church database.
Why not keep the spreadsheet?
Sheets hold rows, but they do not reliably answer whether every classroom is staffed, every helper is cleared, every conflict is visible, and every export is safe to share.
Is background-check data too sensitive?
The validation version asks for redacted or status-only data. The product promise is readiness visibility, not storing sensitive reports.
Will small churches pay?
That is exactly what the waitlist tests: whether a deadline-driven, seasonal packet is valuable enough before building a full SaaS workflow.
Validation plan
Join if you would test one redacted roster review.
Early waitlist users get a human-reviewed VBS readiness packet from a redacted sheet. Demand is validated if coordinators submit real spreadsheet shapes, identify missing checks worth paying for, and ask to reuse the packet for the next event.