Buyer’s guide
Evaluate continuing education software one real class at a time.
An evidence-first checklist of 32 prompts for comparing how any product handles a noncredit class—from the first schedule decision through registration, delivery, completion, and reporting.
How to score
Score evidence, not presentation polish.
Give each prompt a 0, 1, or 2 after the vendor shows the workflow. Keep nonnegotiable requirements separate, so a high average can’t hide a critical gap.
Score 0
No current evidence.
Unavailable, only described, or dependent on an unnamed future plan.
Score 1
Partial or conditional.
Covers part of the job, needs configuration, or relies on a manual handoff with an owner.
Score 2
Shown end to end.
Demonstrated in the current product, including the difficult state or exception.
01
Continuing Education operating fit
Start with the domain model. A product can look polished and still force CE work into credit-term assumptions, disconnected event tools, or staff-owned spreadsheets.
Can the vendor demonstrate one class from initial setup through verified outcome?
Evidence to requestA current-product review using one consistent course, section, session, learner, payment, attendance, and completion record.
Does the product distinguish a reusable course from a scheduled section and its individual sessions?
Evidence to requestCreate one course, schedule two sections with different dates or locations, and open the session-level delivery view.
Can staff operate short-run, rolling, evening, weekend, and one-time offerings without a semester-first workaround?
Evidence to requestConfigure a representative offering on your real calendar and show how dates, registration, and closeout follow it.
Does the workflow preserve human judgment for consequential exceptions?
Evidence to requestShow a publish decision, payment exception, refund review, or completion exception with an owner, reason, and recorded outcome.
02
Catalog and learner decision
Adult learners often decide quickly and outside office hours. The catalog must explain the actual section clearly without exposing the complexity of the back office.
Can the public catalog carry the college’s identity and program structure?
Evidence to requestA configured institution homepage and catalog with the college name, palette, programs, featured content, and approved public copy.
Does the decision page show the section facts a learner needs before paying?
Evidence to requestDates, session schedule, location, modality, availability, price, prerequisites, materials, policies, and next steps on one responsive page.
Can learners choose interests and find a relevant class on phone and desktop?
Evidence to requestSelect learner interests, inspect the matched recommendations and explanation, then search and filter the catalog at mobile and desktop widths using keyboard-only navigation and visible focus.
Do published details come from the same section record staff operate?
Evidence to requestChange an approved section fact, preview the public page, publish it, and show how staff can trace the public result back to its source.
03
Noncredit registration and payments
Registration is a capacity, identity, payment, and communication workflow—not a button that hands the learner to an unrelated checkout screen.
How does the product protect a seat while the learner completes checkout?
Evidence to requestA timed seat hold plus a capacity test showing what two learners see when they compete for the last place, join the waitlist, receive a time-limited offer, and let an expired offer move to the next learner.
Can card payment be retried safely without creating duplicate charges or enrollments?
Evidence to requestA successful payment and a failed-payment recovery showing idempotency, enrollment state, payment state, and section counts.
Do staff see the enrollment and its financial state in one operating view?
Evidence to requestOpen registration activity, locate the learner, and trace confirmation, payment, promo-code validation and redemption, balance, and follow-up state.
Can staff review a refund and reconcile the resulting records?
Evidence to requestA complete refund case with policy context, funding-source detail, approval or denial, payment update, decision note, and reconciliation result.
04
CE operations and exceptions
The daily value of an operating system appears when a class is incomplete, a deadline is close, or an exception requires a person to decide what happens next.
Can staff see what is required before a class is published?
Evidence to requestA readiness view separating blockers from optional follow-up across schedule, room, instructor, public content, capacity, operational custom fields, and other institution-defined facts.
Are lifecycle changes controlled and understandable after learners enroll?
Evidence to requestMove a section through representative states and show the guards, consequences, owner, reason, and history for a material change.
Do worklists lead staff to the record and action that resolve the issue?
Evidence to requestStart from a registration, payment, refund, attendance, or closeout exception and complete the follow-up without reconstructing context elsewhere.
Can permissions reflect distinct CE staff responsibilities inside one institution?
Evidence to requestShow role-aware access for an administrator, CE staff member, instructor, and learner, including a denied action and its safe result.
05
Instructor delivery and attendance
Most CE instructors need the roster, schedule, attendance, and required closeout inputs—not the full administrative system.
Does the instructor see only assigned classes and delivery-relevant information?
Evidence to requestSign in as an instructor and open assigned sections, class logistics, sessions, and roster without institution-wide staff access.
Can attendance be recorded for each session with the states the program uses?
Evidence to requestEnter present, absent, excused, and tardy records across multiple sessions and review the resulting class status.
How are missing, late, or corrected attendance records handled?
Evidence to requestLeave attendance incomplete, show the instructor reminders for missing attendance plus the CE work queue, then test an edit-window rule, a locked record, and the supported correction or escalation path.
Is the instructor-to-CE-office handoff visible before closeout?
Evidence to requestSubmit any required grade or outcome input and show how staff identify incomplete delivery work and resolve an exception.
06
Completion, certificates, and reporting
A learner outcome is credible when the institution can trace it to completion evidence, issue it reliably, and report the underlying activity.
Can completion be reviewed from attendance and any required grade input?
Evidence to requestA closeout view showing the supporting records, the completion decision, an exception, who resolves it, and the resulting learner transcript record.
Is the certificate created only after the completion record is confirmed?
Evidence to requestComplete a learner, trigger durable PDF generation, verify the certificate record, and show the learner’s download path.
Can a third party verify the certificate without seeing the full education record?
Evidence to requestScan the certificate QR code and inspect the public verification page, invalid-token behavior, and fields intentionally withheld.
Do operational reports reconcile to the class and learner records beneath them?
Evidence to requestReview enrollment, attendance, instructor, revenue, refund, and certificate-related records, then test CSV export plus any required state workflow such as Iowa ICSPS validation and spot-check source rows.
07
Data boundaries, access, and accessibility
Institutional review should test the controls that separate colleges, restrict sensitive records, and let learners and staff complete essential work.
How is institution scope enforced beyond the page URL?
Evidence to requestArchitecture and test evidence for tenant checks at the authenticated request, query, and database layers, including a cross-tenant denial.
Where can student education records travel—and where are they prohibited?
Evidence to requestA data-classification map covering the database, identity, payments, storage, email, search, analytics, logs, and support handling.
How are identity, institution membership, roles, and permissions reviewed?
Evidence to requestSign-in and role-assignment flows, permission checks on sensitive actions, access removal, and an audit trail of material changes.
What current accessibility evidence covers public and authenticated workflows?
Evidence to requestWCAG 2.1 AA targets plus keyboard, focus, responsive reflow, reduced-motion, automated-rule, and manual assistive-technology results.
08
Implementation and operating readiness
A strong product can still fail when responsibilities, evidence, support, and launch conditions remain implicit. Make the operating plan part of the evaluation.
Does the first pilot use a representative class with named success criteria?
Evidence to requestA written scope naming the program, class, learner journey, staff workflows, outcomes, owners, acceptance criteria, and decision date.
Are vendor configuration and college responsibilities separated clearly?
Evidence to requestA responsibility matrix for identity, content, programs, locations, roles, payments, policies, test data, approvals, support, and communication.
Will the college rehearse the whole lifecycle before opening registration?
Evidence to requestA test plan and results for browse, checkout, payment failure, refund, instructor work, attendance, completion, certificate, email, and reporting.
Does the readiness review produce an explicit decision and unresolved-work record?
Evidence to requestA named go, no-go, or follow-up decision covering product evidence, institutional readiness, support, rollback, owners, due dates, and open requirements.
Turn the checklist into a decision record.
Add the 32 scores for a maximum of 64, then list every score of 0, every nonnegotiable requirement, and every conditional score with its owner and due date. The total is a comparison aid—not a substitute for security, accessibility, legal, finance, or institutional approval.
Ask each finalist to repeat the same representative-class review. Record what the current product showed, what needs configuration, and what remains unresolved.