The software demonstration looks impressive. The dashboard is tidy, the charts are colorful, and the presenter moves quickly. Then you ask how to handle a student who changes cohorts after paying a deposit, and the answer becomes much less specific.
A CNA school software demo should follow real student and staff tasks from inquiry through completion. Use the same scenarios with each vendor, record what was demonstrated, and distinguish working features from configuration, custom development, and future plans.
The best demo checklist helps your team evaluate fit—not simply remember which presentation looked best.
Prepare five fictional records before the call
Use invented information instead of exposing real student records during vendor evaluation.
- An applicant who has asked about an evening cohort but has not registered.
- A student who has paid a deposit and needs an installment plan.
- A student with a document awaiting review before a required activity.
- An employer sponsoring several learners.
- A student who missed a session and needs an approved make-up process.
Choose scenarios that matter to your actual programs. Send the vendor the agenda beforehand and ask them to show the workflow using their current product.
1. Follow an inquiry into registration
Ask the presenter to create a lead, assign responsibility for follow-up, and move the person toward the correct cohort.
Then view the registration experience from a phone-sized screen. Can the applicant understand the schedule, cost, prerequisites, and next step? What happens when the class is full?
Record whether the system keeps a single student identity or creates duplicates as the person moves through the process. Ask how staff resolve an accidental duplicate without losing the payment or academic record.
2. Review documents and readiness
Upload a harmless sample file and ask an authorized staff member to review it. Check how another staff member knows whether it was merely received or actually accepted.
Ask how requirements differ by program or cohort. Can the school identify missing items and who must follow up? If a document expires or requires correction, what does the student see?
Do not accept “compliance tracking” as a complete answer. Ask which requirements can be represented, who approves them, and what evidence the school can retrieve. Software does not confer state approval on a program.
3. Reconcile tuition and payment plans
Run the deposit example all the way through:
- Create the charge and explain what is included.
- Record the deposit and show the remaining balance.
- Add an agreed installment schedule.
- Show a pending, completed, and failed payment.
- Make an authorized adjustment and inspect the record.
- Produce a receipt and an outstanding-balance report.
Ask which actions occur in the school software and which occur in the payment processor. Confirm gateway compatibility, fees, refund responsibilities, and how transactions are reconciled.
For sponsored students, ask the vendor to distinguish the learner from the payer. A generic payment button is not enough to demonstrate sponsor invoicing.
4. Test classroom, lab, and clinical records
Bring your approved reporting categories and a sample requirement. Ask whether the system tracks attendance status, actual time, and required categories separately.
Demonstrate a late arrival, an absence, a make-up session, and an authorized correction. Ask whether the history shows who changed the record and why.
Do not assume that checking “present” produces an acceptable hour record. For nurse aide programs, federal training requirements distinguish training requirements that must be reflected in your program's approved approach. Your jurisdiction and program may impose additional conditions.
5. Review learning and completion decisions
Ask an instructor to open a course, review submitted work, grade a sample, and identify a learner who needs attention.
Then inspect how completion is determined. Are attendance, assessment, and other requirements handled appropriately? Can a certificate be withheld until the authorized person confirms eligibility?
Ask how a certificate is corrected or reissued. If the vendor mentions badges, verification, or interoperability, request a demonstration of those exact capabilities rather than assuming all digital credentials work the same way.
6. Inspect permissions, records, and exit options
Use separate administrator, instructor, and student views. Confirm that each role sees the information it needs and that sensitive information is restricted appropriately.
The FTC's Start with Security guidance emphasizes limiting data access and evaluating service-provider security. Translate that into specific vendor questions about authentication, backups, incident notification, staff access, and your own configuration responsibilities.
Also ask what happens if you leave. Request sample exports for student details, financial records, attendance, documents, and academic history. Confirm formats, costs, timing, and what is not included. “You own your data” is helpful only if you can retrieve it in a usable form.
Use a simple demonstration scorecard
For each requirement, record the evidence and assign one status:
- Demonstrated: The current product completed the task during evaluation.
- Needs configuration: Supported, but your setup and responsibilities need confirmation.
- Needs an integration or extra service: A separate dependency or charge applies.
- Planned: Described as a future capability, with no assumption of present availability.
- Not supported or unresolved: The requirement remains a gap.
Give each requirement an importance rating before the demo: essential, useful, or optional. One missing essential function can matter more than a long list of attractive extras.
If you use numeric scores, keep the formula simple and preserve the notes behind each score. A total without evidence can hide an important limitation.
Finish with an implementation conversation
Ask who imports data, configures payment settings, trains staff, and checks the first cohort. Confirm the timeline and what your team must provide.
Discuss support using a realistic scenario: a student cannot register shortly before a class starts. How is the issue reported, what support hours apply, and what escalation is available under the proposed plan?
Request a written summary of the package, recurring charges, one-time work, usage fees, and any commitments made during the call.
Frequently asked questions
Should the school evaluate software in a trial?
When available, a trial can help staff repeat the important tasks themselves. Use approved test data and define success criteria before starting.
Is a CNA-specific product always the best option?
The label alone does not establish fit. Evaluate the actual workflows, program requirements, implementation support, and total cost.
Should future features count toward the decision?
Record them separately. Base operational readiness on what you can use and verify now, with any future commitments clearly documented.
Use the same checklist when evaluating Steams Online
Steams Online brings registration, student records, billing, and learning management into its training-school platform.
Schedule a demonstration and bring your fictional scenarios. Ask the team to show your essential tasks, identify configuration needs, and explain any gaps before you make a decision.
