A prospective student finds the right class, clicks Register, and disappears. It is tempting to assume they lost interest. They may instead have reached a fee they did not expect, become stuck uploading a document, or discovered that the clinical schedule conflicts with work.
Students abandon registration when the process leaves an important question unanswered or makes the next step too difficult. Common issues to investigate include unclear costs, schedule uncertainty, excessive form fields, mobile problems, payment errors, and confusing confirmation messages. Your own data is needed to determine which problems matter at your school.
Do not treat every unfinished form as a lost sale. Some people are still comparing programs or gathering information.
Start with evidence from your own registration journey
Baymard's checkout research identifies issues such as unexpected costs, lack of trust, and complicated checkout in ecommerce. Those findings offer useful hypotheses for a school to test. They are not a measured abandonment rate for CNA enrollment or training-school registration.
Map your own steps: program page, cohort selection, contact information, requirements, payment, and confirmation. Record where an applicant leaves or encounters an error, using appropriate privacy controls.
Separate a form submission from a confirmed enrollment. If those events are mixed together, staff may think the process is working while students remain stuck before the final step.
1. Make costs clear before the form begins
Show the total program charge, what is included, and what may be paid separately. Explain the amount due today and the remaining obligation if installments are available.
A “from” price can confuse applicants if nearly everyone must pay additional required fees. A deposit should be labeled as a deposit, with a clear explanation of what it reserves.
Test the page with someone unfamiliar with your school. Ask them to explain the total cost and the next payment. Their answer can reveal ambiguity more quickly than a staff discussion.
2. Explain the full schedule
A student may be able to attend evening theory classes but not daytime lab or clinical activities. Put material schedule requirements where people can see them before making a financial commitment.
Identify what is fixed, what is assigned later, and what the student must be available for. If a placement is conditional, explain the condition accurately.
Do not hide crucial scheduling details in a document that appears only after checkout. That may produce completed forms and disappointed students rather than successful enrollments.
3. Ask for information at the right stage
Review every field. What decision does it support, who uses it, and when is it actually needed?
You may need substantial documentation before participation in a healthcare program. That does not necessarily mean every document belongs in the initial inquiry form.
The W3C's accessible forms guidance recommends clear labels, instructions, error feedback, and requesting information necessary for the process. Apply those principles while preserving requirements that genuinely belong at the current stage.
If later steps require documents, tell the applicant what to prepare and when. Reducing surprise is as important as reducing the number of fields.
4. Test the experience on a phone
Have someone complete the process with a phone using an ordinary connection. Do not guide them through each screen.
Watch for small controls, hidden error messages, unreadable policy text, awkward date selection, and uploads that fail without explanation. Test keyboard navigation and relevant assistive-technology behavior as part of accessibility review.
If the session expires, can the person recover? If they must leave to find a document, is the next step clear? A save-and-return function may help where supported, but do not advertise it unless it works in your actual setup.
5. Treat payment and enrollment as connected events
A successful charge followed by an unclear registration state is especially frustrating. Test what happens when a payment succeeds, remains pending, fails, or the browser is closed before returning to the school site.
The confirmation should explain what has happened: application received, payment received, seat reserved, or enrollment confirmed. Those phrases should correspond to actual states in your process.
Give students a way to contact the school with a reference number. Staff should be able to investigate without asking them to repeat the entire application or pay again.
6. Offer help without turning uncertainty into pressure
If an applicant has provided appropriate permission for follow-up, use a helpful message focused on resolving the problem.
For example:
Hi Jordan, this is the admissions team at your training school. If you still need help choosing a cohort or completing registration, reply with your question or contact our office. We can explain the schedule, requirements, and payment options.
Adapt the sender and channel to your actual process and consent requirements. Do not imply you observed private browsing behavior or that a seat is nearly gone unless you can substantiate it.
Make it easy to stop further messages. A student who has chosen another program should not have to argue with an automated sequence.
Measure one clear funnel
Use a defined cohort and time period. A simple starting calculation is:
Completion rate = confirmed registrations ÷ valid registration starts × 100.
If 60 people begin registration and 42 confirm within your defined measurement window, the completion rate is 70%. This is a fictional example, not a benchmark.
Decide how you handle repeat attempts, staff-assisted entries, bots, and students who return later. Otherwise, the calculation can change because tracking changed rather than because the experience improved.
Then review drop-off by step and device, plus error reports and admissions questions. Never put sensitive student or payment details into analytics events.
Run one useful improvement at a time
Choose the most plausible problem and make a focused change. For example, clarify all mandatory fees before the first form, then review whether applicants ask fewer cost questions and whether completion changes.
Small schools may not have enough traffic for a reliable A/B test. In that case, combine a before-and-after review with observed usability sessions and staff feedback. Be cautious about attributing every change to the redesign; seasonality and cohort demand also matter.
Frequently asked questions
Is every abandoned registration recoverable?
No. Some people are researching, are not eligible, or cannot attend the schedule. Aim to remove avoidable friction and help suitable applicants make informed decisions.
Should we remove all required fields?
No. Keep necessary requirements, explain them, and collect them at the right stage. A shorter form that leaves staff unable to process the enrollment creates different problems.
Should we offer discounts to everyone who leaves?
First identify the obstacle. A discount does not fix a broken upload, an unsuitable schedule, or an unclear clinical requirement.
Review the journey from the student's side
Steams Online's class registration tools include customizable forms and payment options. Your school's configuration and instructions determine much of the student's experience.
Request a walkthrough using a real program scenario. Follow the entire path from program selection to confirmation, including what staff see when a student needs help.
