VBS Registration Pro – Documentation

VBS Registration Pro is a structured event registration plugin for WordPress that manages kids registration, volunteer signups, payment collection, automated email workflows, exports, seasonal separation, and operational event organization from a single WordPress site.

It is built for churches that want complete control over their event data without depending on an outside SaaS registration platform.

This page documents how the plugin works conceptually so churches can evaluate fit, workflow, and administrative overhead before purchase or deployment.

01 Product Scope & Intent

VBS Registration Pro is a seasonal registration system built specifically for churches managing Vacation Bible School and similar structured events. It is designed around three core principles:

  1. Local data ownership — all data lives in your WordPress database, not a third-party cloud.
  2. Clear lifecycle state management — every registration has a defined, trackable status at all times.
  3. Predictable seasonal separation — each event year is logically isolated to keep records clean and reporting accurate.
Scope BoundaryVBS Registration Pro is not a replacement for a full church management system (ChMS). It is purpose-built for event registration, payment handling, volunteer coordination, and communication within a defined seasonal event cycle.

02 System Architecture Overview

The plugin operates as a modular system inside WordPress. Each component handles a distinct responsibility and communicates through internal hooks and filters.

📅Season Controller
👧Kids Registration Module
🙋Volunteer Registration Module
⚙️Status Engine
💳Payment Gateway Layer
Stripe & PayPal
📧Email Automation Engine
📣Bulk Communication Engine
🧩Groups & Crew Assignment Layer
📤Export & Reporting Module

Data residency: All registration and volunteer data is stored entirely in your WordPress database. No external CRM or cloud database is used. Payment processors are contacted only during transaction processing and confirmation — they do not retain your registration records.

03 Seasons System

A Season represents a specific event cycle (e.g., VBS 2026). Seasons are the top-level organizing structure of the entire plugin. Every registration — kids and volunteer — is stamped with the active season at the time of submission.

The Season system guarantees:

  • Registrations from different years never mix in reports or lists
  • Historical data is fully preserved when a new season is created
  • Admin reporting stays clean and season-specific by default
Only one season is active at a time. Changing the active season does not delete or alter existing records. New submissions are stamped with the new season; prior submissions remain exactly as stored. Seasons are logical partitions — not database resets.

Typical season lifecycle: Create a new season before registration opens → set it as active → all submissions are attributed to it → when the event ends, create next year’s season and switch → prior season data remains fully accessible for reference, reporting, or export.

04 Data Model

The system manages two independent record types. Kids registrations and volunteer records are stored separately and do not share data.

4.1 Kids Registrations

Each form submission creates one parent-level registration record. That single record can contain multiple children. The structure stores:

  • Parent name, email, and phone
  • One or more child entries (name, age/grade, and any per-child fields)
  • Emergency contact information (if enabled in settings)
  • Custom form field data (any fields you’ve added)
  • Season label
  • Registration status
  • Payment metadata — amount, transaction ID, payment method (if applicable)
  • Created and updated timestamps

Payment totals are calculated per child. A family registering three children will have one registration record with a combined total reflecting all three.

4.2 Volunteer Registrations

Volunteer records are completely independent from kids registrations and do not interact with the payment system.

  • Contact information (name, email, phone)
  • Selected role(s)
  • Availability windows
  • Optional T-shirt size
  • Season label
  • Submission timestamp

4.3 Groups & Crew Assignments

The plugin also maintains an organizational layer for groups, crews, classrooms, or rotation teams. This is separate from the family registration record and exists to support event operations after registration is complete.

  • Children can be assigned into named groups or crews for the active season
  • Groups may include visual identifiers such as labels or colors for easier roster handling
  • Group ordering can be controlled for printouts, dashboards, and operational flow
  • Leader or helper assignments can be tied to a crew when your event structure requires it
  • Assignments are used for rosters, check-in visibility, attendance review, and day-of-event organization

In practice, this means registration collects the child data first, and the groups/crews system organizes those children into workable teams for classrooms, rotations, or welcome desk operations.

4.4 Parent Permission Slips & Volunteer Policy Acknowledgments

The plugin includes two separate compliance-style acknowledgment layers: one for parents registering children and one for volunteers serving at the event. These are intentionally handled as distinct parts of the system because they solve different operational and legal needs.

Parent Waiver / Permission Slip

  • Can be enabled as its own step in the kids registration flow
  • Displays waiver text separately for each child in the registration
  • Requires the parent to agree for each child before submission
  • Stores the exact waiver text presented at the time of agreement
  • Captures an acceptance timestamp for each child’s waiver acknowledgment

The default waiver language covers permission to participate, emergency medical authorization, photo/video release, liability release during normal event activities, and confirmation that medical and allergy information is accurate and current.

Volunteer Policies & Safety Acknowledgment

  • Can show a church-supplied safety or child protection policy document link
  • Requires the volunteer to acknowledge that they have read and understand the policy
  • Stores a policy acknowledgment timestamp when the volunteer checks the box
  • Can also collect background-check authorization
  • Can collect medical or allergy notes relevant to volunteer service

When enabled, the volunteer form presents a clear Child Safety & Protection Policy section with a PDF link and a required acknowledgment checkbox before the form can be submitted.

This makes the plugin more than a simple signup form. It also functions as a documented intake system for parental permission, volunteer policy awareness, and safety-related acknowledgments tied to the active season.

05 Registration Lifecycle

Each kids registration moves through a clear sequence:

1
Parent submits the registration form
→
System validates the form and creates the registration record
2
If the event is free, the registration is marked Active immediately
3
If payment is required, the registration is created as Pending until payment is confirmed
4
After payment confirmation, the status becomes Paid
5
Confirmation emails are sent based on the final state

This lifecycle ensures the system always knows whether a family has merely submitted the form, successfully paid, or still requires follow-up.

06 Status Engine

Every registration exists in a trackable status state. This makes filtering, reporting, and communication consistent.

Active
Pending
Paid
Cancelled

Why this matters: bulk email, exports, and admin follow-up can all be filtered by status. Example: you can contact only pending families to remind them to complete payment, or export only paid registrations for final attendance planning.

07 Payment Processing Architecture

If you enable paid registration, the plugin supports direct integration with:

Stripe Checkout PayPal

The plugin does not depend on WooCommerce or a third-party e-commerce layer. Payments are handled directly inside the registration workflow.

1
Registration is created with a Pending status
2
User is redirected to the chosen payment gateway
3
Gateway confirms successful payment via webhook / callback / IPN
4
The plugin records transaction metadata and updates the registration to Paid
5
Confirmation emails are triggered
ImportantIf a family completes payment but the registration remains Pending, the issue is usually not the form itself — it is the gateway callback, webhook delivery, or IPN communication that failed.

08 Permissions, Safety & Policy Flow

The plugin does not treat permission slips or volunteer policies as generic notes. They are built into the live form workflow so that acknowledgments happen during submission rather than later through a disconnected paper process.

1
Parent completes the registration details for one or more children
2
If the waiver feature is enabled, the form adds a dedicated waiver step before final review
3
A unique waiver card is shown for each child, and the parent must agree separately for each child
4
The resolved waiver text and acceptance state are stored with the registration data
5
On the volunteer side, the form can require acknowledgment of your posted Child Safety & Protection Policy before submission
Why this mattersChurches often need proof that permission, medical authorization language, media release language, or volunteer policy language was actually presented and acknowledged during signup. This plugin is structured to collect those acknowledgments inside the form flow instead of relying only on offline paperwork.

Because the parent waiver text is configurable, each church can adapt the wording to its own ministry policies and legal review preferences. The volunteer policy area is also configurable and can point to the church’s own PDF policy document while preserving a checkbox acknowledgment in the volunteer record.

09 Email Automation Engine

VBS Registration Pro includes a built-in transactional email engine. It can send:

  • Parent confirmation emails
  • Admin notification emails
  • Payment-based confirmations after successful payment
  • Waitlist or follow-up emails depending on configuration

Email messages are controlled from the plugin settings and support dynamic values through merge tags.

{parent_name} {children_names} {event_name} {event_date} {registration_id} {payment_status}

This allows non-technical admins to personalize messages without editing code.

10 Bulk Communication Engine

The plugin includes a bulk email tool for targeted communication to parents or guardians based on filters. Typical uses:

  • Send reminders to families with Pending registrations
  • Send event info only to Paid or Active registrations
  • Announce schedule changes to all families in the active season

Bulk communication is separate from automatic transactional emails. This keeps system-generated confirmations and manually sent announcements clearly distinct.

11 Export & Reporting

Exports are read-only outputs of your stored data. They do not modify records. Available formats:

📊 CSV Export

  • Optimized for spreadsheet use
  • Roster management and mail merges
  • Importable into Excel, Google Sheets, or ChMS
  • One row per child or per registration (depending on export type)

📄 PDF Export

  • Formatted for printing and sharing
  • Check-in sheets and summary reports
  • Volunteer assignment printouts
  • Group and crew rosters for teachers, leaders, or check-in teams
  • Single-record and bulk export options

All exports respect the active season filter and status filter. Always verify your filter selections before exporting to ensure you’re pulling the correct data set.

12 Administrative Controls

The admin panel provides full control over registrations, volunteers, configuration, communication, and group organization from within the WordPress dashboard.

That includes the ability to build crews after registration opens, assign children to those crews, and use those assignments in printed rosters and operational workflows.

Registration Management

  • View, search, and filter all registrations
  • Filter by season and status
  • View full registration detail per family
  • Manually update registration status
  • Delete individual records
  • Run exports from list view

System Configuration

  • Payment gateway setup (Stripe & PayPal)
  • Email template customization
  • Season creation and management
  • Group and crew creation, ordering, and assignment
  • Volunteer role definitions
  • Parent waiver text and enable/disable controls
  • Volunteer policy link, checkbox text, and acknowledgment controls
  • Custom form field configuration
  • Registration open/close controls
Deleting RecordsDeleting a registration record removes it permanently, including all associated child entries and payment metadata. Payment history at Stripe or PayPal is not affected — those records remain in your gateway account. Admin actions do not delete gateway-side history.

13 Data Ownership & Security

Because the plugin runs entirely inside your WordPress install, your church retains direct control over registration data, volunteer submissions, and exportable records.

  • No third-party SaaS dashboard owns your data
  • No monthly cloud platform lock-in is required for core registration functions
  • Your normal WordPress backup strategy also protects your event records
Security note: while the plugin stores your event data locally, payment card data is not stored in WordPress when Stripe or PayPal are used correctly. Sensitive card handling remains at the payment gateway.

14 Common Failure Scenarios

The most common support issues fall into a few predictable categories:

  • Emails not sending: usually a hosting email deliverability problem, not a registration storage failure
  • Payment completed but status still Pending: usually a webhook/IPN callback issue
  • Wrong season selected: new registrations were created under an older active season
  • Exports missing records: filters were set to the wrong season or status
  • Parents cannot submit registration: the waiver step is enabled and one or more child waiver boxes were not checked
  • Volunteer form will not submit: the policy acknowledgment or background-check authorization field is required and incomplete
Troubleshooting tip: if a payment shows as successful but the registration is still Pending inside WordPress, do not assume the customer failed to pay. First confirm whether the payment actually went through at the gateway. Check your gateway dashboard first. If the payment is confirmed there, the issue is webhook/IPN delivery. You can manually update the status to Paid from the admin while resolving the root cause.

15 Maintenance & Updates

Plugin updates are designed to be non-destructive. They preserve all of the following:

  • All registration records (kids and volunteer)
  • All season data and season labels
  • All configuration settings (payment keys, email templates, form fields)
  • All export history and custom fields
  • Waiver settings and volunteer policy settings

Best practice checklist before every update:

  1. Back up your WordPress database
  2. Review the update changelog for any breaking changes or required configuration steps
  3. Update during a low-traffic window (not the day registration opens)
  4. After updating, verify payment gateway settings are intact
  5. Test one free registration and one paid registration end-to-end
  6. Confirm webhook/IPN endpoints remain active and reachable

16 Intended Use

VBS Registration Pro is purpose-built for:

  • Annual VBS registration (paid or free)
  • Seasonal structured church events with defined start/end cycles
  • Volunteer coordination tied to a specific event season
  • Group and crew organization for classrooms, rotations, and check-in flow
  • Small to mid-size church event programs that need clean, isolated registration data year over year
Not a ChMS replacement. VBS Registration Pro is not designed to manage ongoing membership, recurring giving, small groups, or general church database functions. It is purpose-built for seasonal event registration. For full church management needs, it is intended to complement — not replace — a dedicated ChMS platform.

Looking for more?

Need Events, Contributions & Online Giving?

If your church needs to track contributions, manage giving records, or handle online donations and general events beyond VBS — check out the Church Contributions, Events & Giving Records Plugin for WordPress. It’s built for the same WordPress-native, church-owned-data philosophy and pairs naturally alongside VBS Registration Pro.

View the Plugin →