Camp Roster Readiness: What to Verify Before Each Session Starts
- A camp roster is ready when every expected camper has the correct booking, group, schedule, and required reviews completed under the camp’s own process.
- Use distinct status labels such as requested, submitted but not reviewed, needs correction, and reviewed, because a submitted form is not an approved form.
- Reconcile totals before chasing items: in the fictional example, 32 confirmed registrations stay 32, not 35 with cancellations or 36 with waitlist entries.
- Keep sensitive details in restricted records, give every unresolved item an owner, and repeat the checks for late bookings and transfers after sign-off.
A camp roster is ready for the next session when each expected camper has the correct booking, group, schedule, and required reviews completed under the camp’s process. A name on a registration list is only one part of that check.
The goal is to give the opening team a current, usable record and a clear route for unresolved issues. This guide focuses on that administrative handoff. It does not replace your camp’s safety, health, safeguarding, or check-in procedures.
Build the camp roster from one session, not the season
Build the working roster from the specific session’s confirmed registrations. Include its dates, location, operating hours, and the time the roster was last checked.
Exclude canceled bookings from the active list while preserving their history. Check recent session transfers both ways: a camper moved out should leave this session’s active roster, and a camper moved in should appear with the correct start date.
Some children may attend several weeks. Reusing their information can be convenient, but each session still needs an accurate booking and review of any changes.
Separate optional schedules such as early arrival or extended care. A camper registered for the base day should not automatically appear on every add-on roster.
Use form status labels that show the next action
A single “complete” checkbox can conceal several different states. Use a small set of labels that your team understands.
| Status | Meaning | Next action |
|---|---|---|
| Not requested | Staff have not issued the relevant request | Confirm whether it applies and assign it |
| Requested | The family has been asked to provide the item | Follow up through the approved channel |
| Submitted, not reviewed | An item arrived but has not been checked | Route it to the authorized reviewer |
| Needs correction | A reviewer identified a specific gap | Explain the necessary correction privately |
| Reviewed | The responsible reviewer completed the required check | Record reviewer and review date |
| Not applicable | This requirement does not apply to this booking | Record the reason under camp procedure |
Avoid treating “submitted” as “approved.” A file may be unreadable, refer to the wrong session, or need a specialist’s review.
The table is a workflow suggestion. Your camp decides the actual requirements and who is qualified to review each one.
Build the roster checklist from your camp’s requirements
Typical administrative categories to review include:
- Confirmed session and location
- Agreed daily schedule and add-ons
- Current guardian contact route
- Required permissions and acknowledgments
- Pickup information under the camp’s process
- Required health-related review by authorized staff
- Payment status and any authorized arrangement
- Group assignment and staff handoff
- Outstanding questions or approved exceptions
Do not turn that list into a universal packet of mandatory forms. Programs differ. NYSDEC, for example, publishes both general camp forms and forms for particular locations or sessions. Its page also specifies how certain materials are handled at arrival. Those instructions apply to DEC camps, not every day camp. NYSDEC registration and forms information
Establish your own requirements with the appropriate program leaders and authorities. Where health information is involved, the administrative team should track the review state without making medical decisions.
Keep a readiness register separate from sensitive details
The management view needs to answer “What is unresolved, and who owns it?” It usually does not need to reproduce a camper’s medical history.
A restricted-access readiness register can use:
| Record | Example |
|---|---|
| Camper reference | C-104 |
| Session | North Science, July session |
| Open item | Session-specific permission requires review |
| Status | Submitted, not reviewed |
| Assigned reviewer | Authorized program lead |
| Next action | Complete review or request correction |
| Review deadline | Camp’s actual preparation deadline |
Keep the underlying documents in the approved system with appropriate access. Do not attach the entire camper file to a general staff email or duplicate it into several spreadsheets.
The FTC’s business guidance recommends collecting only information needed for the business and limiting access to people who need it for their work. Apply that principle when deciding what belongs in a roster, readiness register, or staff handoff. FTC guide to protecting personal information
Retention and disposal should follow your camp’s approved requirements; this checklist does not set a retention period.
Reconcile roster totals before chasing missing items
Suppose a fictional session report shows:
- 32 confirmed registrations
- 30 campers assigned to groups
- 2 confirmed campers awaiting group assignment
- 3 canceled bookings retained in history
- 4 separate waitlist entries
The active session count is 32. It should not become 35 because canceled records remain visible, 36 because waitlist entries are included, or 39 if both are added. The same distinctions underpin a camp enrollment report by session.
The two unassigned campers belong in the exception queue. They should not disappear from the expected-arrivals count.
Now compare related schedules. If nine campers purchased extended care, check that all nine appear in the appropriate add-on record. Do not rely on staff remembering a note in the family’s invoice.
These checks find administrative inconsistencies. They do not establish that the session meets staffing or capacity requirements, which need their own review.
Send a specific missing-item message
Subject: One preparation step for [camp session and dates]
Hi [guardian name],
We’re preparing for [session and dates]. Our record shows that [specific item] still needs [submission or correction].
Please use [approved secure link] by [date] to complete the step. If you have already submitted it, contact [camp contact] so we can check the record.
Please do not email sensitive health or payment information. Use the approved channel above, or contact us for help accessing it.
[Staff name]
Check the status immediately before sending. A message asking for an item already submitted can be avoided by reviewing the queue and the correct account first.
If a reviewer needs a correction, identify the issue clearly without disclosing sensitive details in the email subject or a shared thread.
Prepare the opening-team handoff
Give authorized staff the information they need for their role through the camp’s established system. Confirm that they can access it before the session starts.
The administrative handoff should identify:
- The current roster version or last refresh time
- Expected campers and schedule variations
- Newly approved transfers or late registrations
- Unresolved items and the person handling each
- Who can make an exception or registration decision
- How corrections will reach the opening team
Sensitive care information should reach the appropriately authorized staff through the established health and safety process. Do not omit necessary care information merely to keep a general roster brief; route it correctly.
A printed roster, if required, should be handled and stored under the camp’s privacy procedures. Staff need to know when an updated version replaces it.
Handle late changes without losing the review trail
A roster can be reviewed on Friday and become outdated before Monday. Assign ownership for changes after the main review.
For a late booking or transfer, repeat the applicable checks rather than treating the earlier session sign-off as covering the new camper. Record what changed, who reviewed it, and who was notified.
If an issue remains at arrival, follow the camp’s escalation and admission procedures. Front-desk staff should not improvise health approvals, eligibility exceptions, or payment arrangements to clear the queue.
What a “ready” camp roster should mean
Record the administrative handoff as complete when the booking list is reconciled, the team has current information, and every unresolved item has an owner. Keep a camper with an unresolved required item marked pending until the authorized reviewer makes the decision required by the camp’s process. Completing the handoff does not itself clear that camper to attend.
Bloomily for camps brings session registrations, camp groups, and forms into its camp workflow. During an evaluation, ask staff to demonstrate a fictional camper whose form is submitted but still awaiting review. That case shows more than a screen containing only completed records.