Who it's for
Four groups, judging the same platform on four different things.
A director approving a training platform and an instructor building a course in it are not asking the same question. Neither is the support staff member managing a roster, or the student trying to finish a module before Friday. Each case is made on its own terms below.
For decision-makers
Institutional leadership
Directors, deputy chiefs and the people accountable for what a training organization can prove it did.
- One platform, not a stack. Scheduling, authoring, assessment, certification, reporting and administration are one application with one access model. There is nothing for IT to stitch together and nothing to keep in sync between systems.
- Access provisioning stops being a project. Placement in the hierarchy grants scope. There is no separate permissions matrix maintained alongside your org chart, and therefore no second version of it to fall out of date.
- Deployable entirely inside your boundary. No public internet dependency at runtime, no external data repository, no vendor-hosted tenancy. Closed and air-gapped networks are the design target rather than a supported edge case.
- A complete audit trail. Every enrollment, grade, certificate and administrative action is attributable and timestamped, including who approved an enrollment and when.
- Certification you can stand behind. Certificates are issued automatically on genuine completion and are independently verifiable by code. Browse mode exists precisely so that credit means something.
- Integration when you want it, not before. Active Directory sync, external student records sync and SCORM completion export are built in and inert until pointed at real infrastructure.
The evaluation question
"What am I actually buying?"
A single application covering the whole training lifecycle, running on infrastructure you control, with an access model that mirrors the organization you already have.
What is available on request
A detailed feature walkthrough, technical documentation, and a full deployment and security handoff guide. A pilot can be scoped against your own courses and your own structure rather than a demonstration dataset.
For practitioners
Instructional designers & instructors
The people who build the courses and teach them — and who will be in the platform every working day.
- Eleven block types, learned once. Rich text, image, video, link, popup, quiz embed, survey embed, file download, knowledge check, embedded page and tabs — available on every page of every course. The set is deliberately finite.
- A visual map of what you have built. The Build page lays out the whole structure of modules and pages, so the shape of a course is something you can see rather than reconstruct from a list of titles.
- Version history on everything authored. Materials, videos, surveys and scheduled reports each keep a full history. View any earlier version, and revert to it.
- Your review progress, kept separate. Author review progress tracks the pages you have actually opened and checked while building. It is provably distinct from student completion — different storage, different computation, different markup.
- Schedule from the calendar itself. Click a day to create a course or a session with the date already filled in.
- Gate a course on readiness. Mark a survey as the course's pre-course questionnaire and get a charted, exportable picture of the cohort's baseline before day one — from everyone, not just the people who replied to an email.
- Publish for graduates without touching the course. Mark a module alumni-only and it leaves the course entirely, appearing instead on the site-wide Alumni page for certificate holders.
The daily question
"Will this get in my way?"
Content libraries default to the courses you actually work on. Navigation is consolidated into Library, Authoring and Admin menus. Nothing you author is lost, and nothing requires a second tool.
For administrators
Course support staff & registrars
The people who run the roster, chase the paperwork and answer the question when an audit asks it.
- Nine live roster fields per person. Alternate first and last name, organization, personnel level, and approval tracking — who approved an enrollment and when — shown identically on the roster and the course detail page.
- Waitlists you actually control. When a course fills, students join a waitlist. Seats are filled deliberately by course staff, never by an automatic promotion nobody decided on.
- Reference spreadsheets kept as a history. The roster document library stores workbooks against a course, readable in the browser and downloadable — and uploading one changes nobody's enrollment.
- Schedules released on time. Weekly PDFs compute their own release dates from the course start, with a per-week override for anything that breaks the rhythm. Staff schedules stay staff-only.
- Reports that arrive without being asked for. Recurring scheduled reports, filterable by course or group, delivered by email on a flexible interval.
- Archiving that can be undone. Tidying up the catalog never means losing the record of who took what.
The audit question
"Can we show our work?"
Approval tracking is a live roster field rather than a mail thread. Certificates are verifiable by code. Every administrative action is attributable and timestamped. The answer to an audit is a page, not a reconstruction project.
For learners
Students
The largest group by far, and the one least willing to be trained on how to use a training platform.
- Enroll from the catalog. Sign up, and if a course needs approval you are held as Pending until course staff approve you. If a course is full you join a waitlist rather than hitting a dead end.
- Know where you are. A module-level progress bar shows every module marked not started, in progress or complete, alongside an overall completion bar. Both reflect real, verified progress, and both compute from the same figure.
- Choose how you are taking the course. Credit mode follows the course as designed and earns credit and a certificate. Browse mode lets you explore freely for review or preview. The choice is made once and then locked.
- Never guess what is required. Required prompts are clearly marked and confirmed with a checkmark once opened. Optional ones are there for context and do not block you.
- This week's schedule, this week. Each week's schedule appears when that week arrives. The calendar shows when your courses run and when classes meet.
- Something after the finish line. Once you hold your first certificate, the Alumni page gathers content published for graduates of every course you have completed, grouped by course.
The learner question
"What do I have to do next?"
The progress bar answers it on every page, and it is the same number the instructor sees. Nothing about your standing in a course requires asking someone.
Next step
Tell us which of these you are.
A walkthrough is considerably more useful when it is pointed at the part of the platform you will actually live in.