Program Use Considerations

Signup / Registration Options

With Byga, you have various choices depending on the specific program.

Custom Form with Payment: If the program is a one time event (e.g., a weekend ID camp) that does not need grouping as a team for an ongoing schedule or ongoing team communication a Byga Custom Form may be sufficient.
Shareable Link Registration: If the program has more than a one time event, players can be grouped into one or more teams to leverage team schedules and communication. In this case the Shareable Form- based Registration is recommended.
Invite Based Registration: For competitive programs with tryouts, the Invite-based Registration is recommended.

Consider the following team management / schedule / communication functions when setting up a Program.

Decide if you prefer the specific Program families have Byga web and / or mobile app or neither.
Provide a link to the club’s Byga site.
Provide a link to FAQ: https://www.byga.net/parent-portal-faq
Provide recommendations on when to contact their team coach vs club contact.
Provide norms on whether families should message their team or only coach / manager. Should there be another club person listed as manager for backup.
Provide information on what if any additional information should be added to player profile (e.g., proof of residency).
Do you want the schedule to be added to the team, so a cancellation will notify the families of changes, etc.

While there are differences in various camps. The following are some recommendations in the form design for session based camps.

Each session should be its own question.
If the player has paid for a session → add the player to that team.
If the player wants to add a session, submit another form.
If each session is a separate question, the thank you email will summarize the sessions. If including the sign up fees in the message, the language should state that these are the fees for selected sessions but the paid invoice is the confirmation of payment.
If on the waitlist, you will be notified to pay.
If coming off the waitlist (especially if it impacts the price), have them submit a new form.
If using a lot of waivers, avoid redoing waivers when adding sessions, consider using a data collector to keep data collection separate from session signups.
Make sure any pools desired for messaging or export are possible based on the form questions.
Include a second player contact option in the form.

For more information, please reference Programs Registration Management