Online Class Registration: Requests, Approval, and Waitlists

Online class registration should tell a family what they have submitted and what happens next. A request, an approved place, a waitlist entry, and a paid enrollment are different states. Calling all four "registered" creates avoidable confusion.

This guide is a practical setup checklist, not a promise of a particular increase in enrollment. Start with your school's approval and payment rules, then choose software that can represent them.

Define the enrollment decision

Decide whether a suitable applicant can enroll immediately or needs staff review. Write down who checks eligibility, capacity, required documents, and payment. Identify which checks the software actually enforces and which staff must perform.

An available place on a public page is not a reservation. Two families may submit at the same time. The enrollment operation must check capacity again when a place is confirmed.

Use distinct messages for each result:

Request received: the school has the application; no place is promised.
Approved: the school has confirmed enrollment.
Waitlisted: the request is waiting under a clearly explained queue policy.
Closed or withdrawn: the request is no longer being considered.

Keep the form and payment process specific

Ask only for the information needed at this stage. Explain where families can supply additional documents through the school's approved process. Do not treat a general notes field as a waiver-signing or medical-record system.

If payment is required, demonstrate the complete flow before buying software: successful payment, failed payment, duplicate submission, cancellation, and refund. Check whether payment reserves a place, follows approval, or remains entirely separate. A software subscription paid by the school is not a tuition payment made by a family.

Tell families about charges and cancellation terms before they commit. The software must support the policy you actually intend to operate; a generic booking form is not proof that it does.

Choose the waitlist behavior deliberately

A waitlist can work in different ways. One system may automatically enroll an eligible applicant; another may send an offer with a deadline. Those policies have different staffing and communication needs.

Define whether staff must approve a request before it can move forward. Decide what happens when the class closes, capacity changes, a family withdraws, or the school reaches a subscription limit. Test the queue with multiple applicants, not just one.

Set up the ProgresslyAI workflow

ProgresslyAI currently implements registration requests with staff approval. It does not collect tuition or complete a waiver during registration.

Create an active weekly class, assign its schedule, and set a roster capacity where needed.
Enable online registration for the selected class.
Open Registrations and copy the public registration-page link to your website.
Submit a test request with a student name, contact name, and contact email. The public form does not require an account.
Review the request as staff. Approve enrollment, approve a waitlist place, or close the request.
Check the class roster and the registration email status after the change.

Approved waitlist requests can promote in queue order when eligible roster and plan places open. Unreviewed requests do not automatically enroll. The current flow does not send a time-limited offer for the family to accept.

Registration changes queue email updates. Check delivery status and investigate failures; a queued or provider-accepted message does not prove the family received it.

New pending and waitlist emails include a private review link valid for 30 days. Opening it does not withdraw the request: the recipient must explicitly confirm withdrawal. Confirmed enrollments require contacting the school about cancellation. Treat these private links as confidential.

Test before publishing your registration link

Use synthetic applicants and a test class. Verify a normal approval, a full class, two competing approvals, approved waitlist promotion, withdrawal, and a closed class. Check the result from a phone and from the staff dashboard.

A registration approval does not by itself create a family portal account. Staff can link and invite a parent separately. Verified linked parents can then access the permitted records for their students.

The current public page supports one student request at a time, with up to 12 owner-defined questions in total. Each question can apply to all classes or 1 to 100 selected classes; applicants see the questions for their chosen class. Short answers, long answers, choices, and yes/no responses can be required or optional. A follow-up can appear when one earlier choice or yes/no answer matches, including chains of follow-ups. Hidden answers are not submitted. Requests retain their original questions, rules, and submitted answers when the school changes its form. This does not provide compound AND/OR rules, numeric conditions, signed waivers, age or prerequisite enforcement, sibling discounts, term booking, an embedded widget, or a multi-child checkout. Use the school's established process for any required work that is not supported.

Measure the process you run

Count requests received, requests approved, waitlist entries, and confirmed enrollments separately. Track the elapsed time from request to staff decision and investigate requests left without a response. Compare periods with similar programs and capacity; a change in enrollment alone does not establish that a new form caused it.

ProgresslyAI does not currently provide a website conversion funnel or abandoned-registration analytics. Use an appropriate separate measurement process if those are required.

Starting with a free school

Starter is free for up to 25 students and 1 instructor seat. Pro costs USD $49/month for up to 200 students and 5 instructor seats. Business costs USD $99/month with unlimited students and instructor seats. AI reports require a paid plan; retention insights require Business. Review the plans and included features before choosing.

Create a test school on Starter and verify the approval workflow before moving a live intake process. See the registration feature page and current plans.