Parks and Recreation teams are being asked to support youth with more complex needs, often with seasonal staff and limited time to prepare. In our recent 30-minute session, CampDoc and Traction Rec focused on a practical question: what changes reduce last-minute surprises while still keeping the experience simple for families?

This recap highlights the three core takeaways from the webinar and translates them into concrete steps you can use with your current workflow.

Across Parks & Rec, staff are seeing more youth arrive with medical, behavioral, dietary, and mental or emotional health considerations that materially affect supervision and planning. When those needs are not known until check-in, teams end up making decisions in the parking lot, not in a planning meeting.

One of the most consistent themes we hear is the staffing mismatch: youth needs can feel “medical-grade,” but the people delivering care day-to-day are often seasonal, non-medical staff who are still learning your basic procedures.

That reality creates a predictable temptation: collect less information to avoid being overwhelmed. The webinar’s position was the opposite. Collecting too little can create risk and put staff in a reactive posture. The goal is not more data. The goal is better decisions, made earlier, with clearer information.

1) Segregate your data to optimize for user experience and security

When registration systems became digital, many departments tried to put everything into one place because that was the easiest path away from paper. That approach made sense at the time. It is also where many teams now feel friction. Segregation can mean separate systems, separate modules, or strict role-based access that keeps sensitive health information out of general registration workflows.

A key distinction shared in the session is between:

• PII (personally identifiable information): operational and contact information your broader team may need, like name, address, phone, enrollment, and payment history

• PHI (protected health information): the health and care details that should be limited to a small group on a need-to-know basis, such as medications, allergies, dietary restrictions, immunization records, and relevant behavioral or mental health history

The practical rule discussed was simple: the moment PHI is attached to a participant’s name, the risk category changes, and it becomes much harder to justify broad access. Privacy requirements vary by agency and state, but the operational best practice is the same: limit access and protect sensitive health details.

This is not only about compliance. It also protects families from unnecessary exposure. One scenario discussed was a front desk staff member looking up a refund and accidentally seeing sensitive notes they do not need to see.

What this looks like in practice

• Keep registration fast and focused on what is truly needed to enroll (the “search, find, register” experience).

• Store and manage health information in a dedicated environment that is designed for restricted access and stronger controls.

• Set permissions so health details are available to the few people who need them, not everyone with a login.

This separation supports both sides of your operation: families move through registration quickly, and sensitive information stays protected.

2) Advocate for continuous visibility of participant information

Many teams do not review health information until right before the program starts, or even on the first day. In the webinar, that “day-one review” was called out as a frequent cause of bottlenecks and surprises.

Two common problems came up:

Paper-based workflows

• Illegible or incomplete forms create a time pressure decision: decipher it, chase the parent, or ignore it.

• Check-in becomes a choke point instead of a smooth handoff.

Digital workflows with “gatekeeping”
Some digital setups do not show staff any data until every field is completed and the parent clicks submit. The webinar framed that as a blind spot: the information may exist, but you cannot see it early enough to act.

A reality many departments experience today is brute-force follow-up. Lots of calls, lots of chasing, and low response rates.

The recommended shift was continuous visibility, meaning staff can see information as it is entered, spot red flags, and route follow-up to the right person before check-in day.

Why it matters operationally
Early visibility supports staffing decisions. If a child’s information indicates they may need additional support, you have time to plan, hire, adjust ratios, or coordinate accommodations instead of improvising on day one.

3) Structure questions to limit interpretation errors

This portion of the session was direct: many forms create “data overload” by using open text fields for critical information, then expecting seasonal staff to interpret what it means.

That was described as the unstructured data problem: families can type anything, in any format, which makes the information hard to parse and hard to act on.

The solution is not a longer form. It is a better one.

Structured data techniques discussed

• Replace broad prompts with specific, decision-friendly questions

• Use conditional logic and drop-downs to remove guesswork

• Ask for the detail that changes your response (for example, “mild swelling” versus “anaphylaxis”)

• Keep a small space for “anything else we should know,” but do not rely on it for the items that drive safety decisions

A practical example you can borrow
Instead of:

• “List any allergies.”

Use a structured sequence:

• “Does the participant have allergies?” (Yes/No)

• “Select allergen type(s).”

• “What happens with exposure?” (mild symptoms / severe symptoms / anaphylaxis)

• “What should staff do?” (EpiPen / inhaler / notify guardian / other)

This turns “information” into “instruction,” which is what seasonal staff actually need.

Here is a straightforward exercise you can use to evaluate your current forms and workflow.

Step 1: Registration experience check

• Can families find the program quickly and register without hunting for medical details at the moment of payment?

• Are you collecting only what you truly need at enrollment?

Step 2: Visibility check

• When do staff first see health information in a usable format?

• Are you waiting for 100 percent completion, or can you review as families enter information?

Step 3: Interpretation check

• Do critical questions rely on open text boxes?

• Could a seasonal staff member read the responses and know what to do without guessing?

Step 4: Segregation check

• Is PHI limited to the staff who truly need it?

• Would front desk or finance staff ever encounter sensitive health details while doing routine work?

The “standard of care” conversation is not about collecting everything. It is about building a workflow that gives your team the right information, at the right time, in a format they can act on, while keeping sensitive details protected. That is how you reduce day-one surprises without turning registration into a paperwork event.

If you would like to talk through how this looks in your current setup, CampDoc and Traction Rec can share examples of workflows we see working well in Parks & Rec today.

If any of the three shifts above hit a nerve, you have two good options, depending on what you need right now.

1) Watch the recording

The session is 30 minutes and stays focused on process decisions Parks & Rec teams can act on, including:

• how to keep registration fast while segregating health information for better security

• how to build continuous visibility so you are not blind until check-in day

• how to structure questions so seasonal, non-medical staff are not forced to interpret vague notes

👉Register to watch the recording

2) Talk through your current workflow

If you’d rather skip the recording and get straight to your department’s setup, our team can help you map a practical “registration-to-health” workflow based on what you run today. This is most useful if you’re trying to reduce day-one surprises, tighten access to sensitive information, or clean up forms that have grown over time.

👉 Get in touch