What is a conditional camp registration form?

A conditional form asks a follow-up question only when an earlier answer calls for it. Report an allergy and the severity and action-plan fields appear; say a camper takes medication and the form asks about dosage, timing, and self-carry. Families who don't ride the bus never see the pickup-stop questions. The form stays short for each family while staying complete for the ones who need every field.

Why do flat registration forms produce bad data?

A long form that shows every question to everyone has two costs. Parents abandon or rush it, so it comes back half-done, and a flat form can't tell 'not applicable' from 'forgot,' so you chase answers you didn't need and miss ones you did. Short forms that ask only what applies come back more complete and more accurate.

Which branches does a camp registration form need?

Five branches cover most camp forms: allergy reported leads to severity and action plan, medication at camp leads to dosage and timing, a swim activity leads to a swim-level question, bus transportation leads to pickup-stop details, and a returning camper hides the fields you already hold. Each shortens the form for families it doesn't apply to and asks complete follow-ups of the ones it does.

How does Camp Runner keep branched answers usable?

Each branched answer maps to its place on the camper record — an allergy lands as structured medical data, not free text in a comments box. The form builder also flags any branch that can never fire before the form goes live, so you fix it in the builder instead of discovering a missing answer weeks into registration.

Conditional camp registration forms: a practical guide

A camp registration form has to ask a lot of questions. The medication ones, the allergy ones, the swim-level ones, the transportation ones — and that’s before the waivers. Put all of them on one form for every family, and you get a 60-field wall that parents scroll past and fill in carelessly. The follow-up questions that matter most are buried among the ones that don’t apply.

Branching fixes this. A conditional form asks the right follow-up only when the previous answer calls for it — short for the family who doesn’t ride the bus, complete for the family who does. This is a practical guide to building one: why a flat form costs you clean data, how branching works, the branches every camp needs, and where the answers land.

Why a flat form costs you clean data

A long, flat form has two costs, and they compound.

The first is completion. Every extra field a parent scrolls through is a chance to abandon the form or rush it. A form that shows all 60 questions to everyone — including the 30 that don’t apply — reads as a chore, and chores get half-done at 11pm the night before the deadline.

The second is data quality, and it’s the worse one. When a parent has to skip past fields that don’t apply, they make mistakes: they answer a medication-dosage question for a child who takes no medication, or leave a swim-level field blank that you needed. A flat form can’t tell “not applicable” from “forgot,” so you end up chasing answers you didn’t actually need and missing ones you did. Short forms that ask only what applies come back more complete and more accurate. Branching is how you get short without losing the questions that matter.

How branching works

The rule model is simpler than it sounds: a field appears when an earlier answer meets a condition. Nothing more exotic than “show this when that.”

You set a condition on a field — show the severity question when the allergy question is answered yes. While a parent fills out the form, the registration form evaluates those conditions live as they type. The severity field stays hidden until the allergy answer turns it on, then appears in place. The parent only ever sees the questions their own answers call for.

That’s the whole mechanic. A field, a condition on an earlier answer, and live evaluation as the form is filled in. Stack a handful of those rules and a form that would be 60 flat fields becomes a short path that branches only where each family’s situation requires.

The branches every camp needs

Five branches cover most of what a camp form has to ask. Each is a small pattern you can build the same way.

Allergy reported → severity and action plan. When a parent reports an allergy, show the severity question and the action-plan fields. The family with no allergies never sees them; the family that needs them gets the full set.
Medication at camp → dosage, timing, self-carry. When a parent says their camper takes medication at camp, branch into dosage, schedule, and whether the camper self-carries. These are the questions your health staff actually need, asked only of the families they apply to.
Swim activity selected → swim-level assessment. When a camper signs up for a swim activity, ask for the swim level. No swim, no swim-level field cluttering the form.
Bus transportation chosen → pickup-stop questions. When a family chooses bus transportation, ask which stop and any pickup details. Families driving their own camper skip it entirely.
Returning camper → skip what we already have. When the camper is returning, hide the fields you already hold from last year and ask only what’s changed. The returning family isn’t re-typing what the system already knows.

Each branch does the same two things: it shortens the form for the families it doesn’t apply to, and it asks complete follow-ups of the families it does.

Catch a broken branch before parents do

Branching has a failure mode: a rule that can never fire. You delete a field that another field’s condition referenced, or you write two conditions that contradict each other, and now there’s a branch that will never show — silently. The parent never sees it, you never collected the answer, and you find out when the data’s missing.

The Camp Runner form builder checks for this before the form goes live. It flags a branch that can never show — a rule pointing at a field you removed, or a condition that contradicts itself — at build time, so you fix it in the builder instead of discovering it in a parent’s missing answer three weeks into registration. You preview the branched flow exactly as a parent will see it, confirm each branch fires, and ship a form you’ve already watched work.

Where the answers go

A branched answer is only useful if it lands somewhere structured. This is where a real camp registration system separates from a general form tool.

When a parent answers a branched medical question, that answer maps to the right field on the camper record — the allergy lands as structured medical data, not a line of free text in a comments box. The same holds for transportation, swim level, and the rest: the form builder resolves each field to its place on the camper record, so a branched answer is queryable, sortable, and able to surface a missing form on its own. You’re not collecting prose you’ll have to re-read and re-key. You’re collecting structured data that the rest of the system can act on the moment it arrives.

That’s the payoff that a standalone form can’t give you. The branch doesn’t just keep the form short — it routes each answer to where the camper record needs it.

Building your first branched form

You can build a working branched form this week. Here’s the short version.

Start flat, then cut. List every question, then mark which ones only apply to some families. Those are your branch candidates.
Build the trigger fields first. The allergy yes/no, the medication yes/no, the activity picker, the returning-camper check. These are the answers your branches hang off of.
Add one branch at a time. Set the condition — show the severity field when the allergy answer is yes — and preview it. Confirm it appears and disappears as you change the trigger.
Preview as a parent, twice. Once as a family the branch applies to, once as a family it doesn’t. Both paths should feel short and complete.
Let the builder check it. Before you publish, confirm there are no flagged branches — no rule pointing at a deleted field, no condition that can’t fire.

Start with the five branches above and you’ll have covered most of what a camp form needs. The form gets shorter, the data comes back cleaner, and your health staff stop chasing answers a flat form let parents skip.

A flat form is the enemy of completion and clean data; branching is the fix. Branching forms are one piece of camp registration software that holds together at scale. If your registration is still stitched together from general-purpose tools, the forms seam is one of several — the full picture is in where Jotform and Stripe camp registration breaks.

Join the waitlist to build next season’s registration on branching forms — and if you’d rather see one run first, the registration features show a branched flow end to end.