Administration and enrolment
Course, programme and term set-up, rule-based enrolment by department, role or year group, waitlists, bulk changes from a spreadsheet, and delegated administration so faculty or line managers handle their own groups.
Education · Learning management
Commission a learning management system built around how your institution enrols, teaches and evidences learning: cohorts and terms, standards-based content, gradebooks, mandatory training records and the identity and records systems it must talk to. We start from your administrators’ real workload, then build the platform that removes it.
SCORM, xAPI and LTI handled as first-class content
Enrolment synced from your SIS or HRIS
Completion evidence that stands up to an audit
Deliverables
Course, programme and term set-up, rule-based enrolment by department, role or year group, waitlists, bulk changes from a spreadsheet, and delegated administration so faculty or line managers handle their own groups.
Cohorts that start and finish on fixed dates, rolling self-paced intakes, sections with their own instructors, and release rules that open modules on a date or after a prerequisite is met.
Import and launch of SCORM 1.2 and 2004 packages, an xAPI statement endpoint or connection to an external learning record store, and LTI 1.3 so third-party tools open inside a course with grades passed back.
Weighted categories, rubrics, late and resubmission rules, moderation and second marking, grade release controls, and export in the format your registry or SIS expects.
Assignment of mandatory courses by role, due dates and recertification intervals, manager escalation for overdue items, and a tamper-evident completion history with the content version each learner actually took.
Dashboards and scheduled exports by organisation unit, course and cohort, covering progress, attainment and overdue training, with row-level permissions so each manager sees only their people.
Early decisions
Student and employee identities normally live in a SIS or HRIS. We decide which fields the LMS may change, how often sync runs and what happens when someone transfers, leaves or returns before building enrolment.
Legacy SCORM libraries, xAPI for tracking learning outside courses, and LTI tools each carry their own runtime work. We inventory your existing content and tools and support what you actually hold first.
SAML or OpenID Connect against your identity provider, plus a role model mapping staff, students, instructors, managers and external learners to permissions, is settled before any screen is designed.
Faculties and departments, business units and locations, or partner organisations for an external training provider drive enrolment rules, reporting scopes and delegated admin, so the hierarchy is modelled early.
Regulated sectors may need to show who completed which version of which course and when. We agree the evidence fields, retention periods and data protection obligations, which depend on your jurisdiction and sector.
Engagement
With registry, L&D or training operations staff we walk through a full cycle: term or intake set-up, enrolment, teaching, assessment, results or certification, and the reports requested at each step.
SSO, SIS or HRIS sync and the organisation hierarchy are built and proven with real data before course features, because every later screen depends on who the learner is and where they sit.
Existing SCORM packages, question banks and completion records are imported and checked, so learners do not lose transcripts and auditors can still see past compliance evidence.
A single faculty, business unit or client programme runs a real cycle on the platform while we tune enrolment rules, gradebook settings and reports, then the remaining units follow and your team takes over the code.
Fit
Institutions with unusual programme structures, multi-tenant client training or approval workflows that a packaged LMS cannot express without workarounds are the strongest case for a custom build.
If most of your administrators’ time goes on moving data between the LMS, the SIS or HRIS and finance, owning the integration layer usually matters more than any learner feature.
Training providers delivering accredited or mandatory courses to client companies need per-client branding, enrolment, reporting and invoicing that generic tools rarely combine.
Healthcare, financial services, construction and other regulated employers needing defensible records of who completed what, and when, benefit from controlling how those records are stored.
Alternatives
If people discover and buy courses themselves on their phones, the build centres on the catalogue, payments and engagement rather than administration.
Open registerWhen your needs match a standard multi-course LMS, starting from our reference product is quicker than a bespoke platform.
Open registerTutoring marketplaces, assessment start-ups and parent-facing school apps are wider edtech builds with their own shape.
Open registerLearners spend a few minutes a week in a learning management system. Administrators, instructors and managers live in it. The quality of an institutional LMS is decided by how quickly a term can be set up, how few manual corrections enrolment needs, and how easily someone can answer an auditor’s question about a named employee.
That is why we start discovery with the people who run the system rather than the people who take courses, and why integration with the record systems is built before the course pages.
Most organisations arrive with years of SCORM packages, a few xAPI experiments and several LTI tools faculty depend on. Supporting those standards properly means implementing their runtimes, not just accepting the upload. A course that launches but fails to report completion is worse than one that refuses to load, because nobody notices until the compliance report is wrong.
For mandatory training, the record matters as much as the learning. A useful completion entry says who completed it, which version of the content they saw, the score and when the recertification falls due. If the course is later updated, earlier completions must still point to what was actually taken.
We design that history to be append-only and exportable, and agree retention with your data protection lead, since rules on how long learner data is kept vary by country and sector.
At handover your team receives the source, infrastructure definitions, the integration mappings for each record system and the runbook for the start of each term or intake. Adding a department or a new content tool is then a configuration and development task your engineers can carry out themselves.
FAQ
In most cases, yes. SCORM packages are imported and launched in a player that implements the runtime API. We test your actual library during migration because authoring tools interpret the standard differently and some packages need small fixes.
Not necessarily. The LMS can include a statement endpoint for its own content, or forward statements to an external learning record store if you already run one or want analytics from outside the LMS.
A scheduled or event-driven sync reads joiners, movers and leavers from the system of record and applies your enrolment rules. Changes made in the LMS that conflict with the source are flagged rather than silently overwritten.
Yes. External learners can be held in their own organisation units with separate sign-in, branding and reporting, so a training provider or a university short-course unit can serve them alongside internal users.
Related services
For the sync services that keep enrolments, grades and completions consistent with your SIS, HRIS and finance systems.
Open registerWhen attainment, progression or training compliance needs to sit alongside other institutional data in one reporting layer.
Open registerFor hosting learner records with the access controls, logging and encryption your data protection obligations call for.
Open registerPrimary sources
Dated official documentation, standards, and research that support the factual claims on this page.
The standard for launching external learning tools inside an LMS and returning grades.
Specification for recording learning experiences as statements in a learning record store.
How to read this page
Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.
Next decision
Define outcomes, constraints, evidence, rights and handover before delivery begins.
Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.