The system of record that has to still be there in ten years.
An enterprise learning platform is judged on the day it is bought and on the day it is audited. wizBank 8.0 has been running the compliance spine of large enterprises for twenty-five years, across more than ten million registered learners. This page describes what is actually inside it — UpLearn LMS, MetaSim, Kora, and the evidence machinery around them — and where an LMS stops and a capability system begins.
25 years
Enterprise learning engineering, from before the category had a name
10M+ learners
Registered across wizBank platforms worldwide
4 core systems
UpLearn LMS, MetaSim, Kora, and the compliance spine
Deploy your way
SaaS, private or hybrid, with data residency you control
Four systems that share one record.
A learning platform that cannot answer "is this person currently qualified to do this work" is a content library with a login. wizBank is built the other way round: the record is the product, and the four systems below are the ways of writing to it and reading from it.
UpLearn LMS
The learning system of record. Enrolment, assignment, due dates, renewal cycles, assessments, attestations, licences, exception handling and a complete audit trail — across business units, brands, legal entities and jurisdictions. It is deliberately boring in the best way: it does the unglamorous work so that the interesting work can happen elsewhere.
MetaSim
Business and sales simulation. Learners make decisions in a modelled environment, live with the consequences, are scored against a rubric, and are walked through a structured debrief. It exists because behaviour does not change from a video, and because competence under pressure is not the same thing as comprehension in a classroom.
Kora
Knowledge management. Maintained, versioned, findable, citable organisational knowledge — with the relationships between policy, process, product and evidence kept intact, so a learner or an agent is pointed at the current version rather than the one someone uploaded last year.
The compliance spine
Regulatory assignment rules, evidence capture, expiry and escalation, recertification, regulator-ready reporting and evidence export. This is the layer clients buy wizBank for, and the layer that has been hardened by twenty-five years of being asked the awkward question.
The LMS in numbers
Who can do what, and how you know that is still true
Employees, partners, digital employees
Never claimed, claimed, demonstrated, currently valid
A certificate is evidence of attendance, not capability
Four evidence states, and only the last one is useful for a decision
If your LMS cannot distinguish between these four, it is storing course history rather than capability. That distinction is the whole design problem.
Never claimed
No record at all. Most of your workforce on a given capability sits here, and most organisations do not know it.
Claimed
A self-declaration, or a completion record. Useful for finding the population; not evidence of capability.
Demonstrated
Completed a real task from their own domain to a stated standard, assessed by someone who knows the domain.
Currently valid
Demonstrated, in scope, within its validity period, with no conflicting change since. This is the only state you can make decisions on.
What the platform does, stated concretely.
No abstraction. These are the mechanisms an enterprise actually configures, and the reason a compliance officer signs off on the system rather than tolerating it.
| Capability | Mechanism | What it replaces |
|---|---|---|
| Regulatory assignment | Rules keyed to role, location, entity, activity and event — a new hire, a role change, a new regulation, a product launch | Annual campaigns assembled by hand and tracked in spreadsheets |
| Renewal & recertification | Cycles with configurable windows, reminders, grace handling, escalation to line managers and to compliance | A shared spreadsheet of expiry dates that one person maintains |
| Evidence capture | Per-learner record of completion, assessment score, material version, attestation and date | Folders of signed PDFs named by a person who left two years ago |
| Multi-jurisdiction & multi-language | Per-jurisdiction regulatory variants of the same course, with local language versions and local assessment rules | One global course, one PDF of local addenda, and a lot of judgement |
| Audit trail | Immutable event history: who was assigned what, by which rule, on which date, with which result | Reconstructing the position of a year ago from email |
| Reporting | Coverage and completion by team, site, role, entity and jurisdiction; exportable evidence packs | A weekly report that measures clicks, not competence |
| Integration | SSO, SCIM, HRIS, talent and assessment systems over REST API and webhook, with a documented data model | Scheduled CSV exports that are wrong by the time anyone reads them |
What the LMS is actually for, once it holds capability
Each of these is a decision the business needs to make. An LMS that only stores completions supports none of them.
| Capability | What the LMS records | What it enables |
|---|---|---|
| Record of capability | Who has demonstrated what, when, in what scope, with what validity period | Deciding who may be given which authority, and who may supervise an agent |
| Role and authority mapping | What each role requires, and at which authority tier | Delegation decisions: which decisions a role may delegate to an agent |
| Training assignment and completion | What was assigned, to whom, and whether it was completed | Compliance evidence — and, more usefully, a capability gap signal |
| Partner and external records | External personnel with access to your process, and their training state | Evidence about your whole ecosystem, not just your payroll |
| Agent capability records | Each digital employee's curriculum, performance record and evaluation threshold | Managing agents as capability assets rather than software |
| Audit and compliance record | Continuous, retrievable evidence over a defined period | Answering a regulator or auditor without a reconstruction project |
Continuing professional development, treated as evidence rather than a certificate.
In Hong Kong and in several financial jurisdictions, continuing development is an obligation with a deadline and a regulator who asks. Most organisations satisfy it by counting hours. Counting hours is necessary and insufficient: the question a regulator is really asking is whether the person is current, and the question your audit committee is really asking is whether you can prove it for every individual in a population that changes weekly.
wizBank handles CPD as an assignment problem with a deadline rather than a log. Hours are derived from completed, assessed activity. Provider and activity approvals are recorded. Expiry is enforced. Where a professional body's requirements are more specific than a generic scheme, they are configured as their own rule set with their own cycle, and the same individual can sit under several schemes at once without the records colliding.
- Activity-based recording — a course, a simulation, an internal workshop or an external event, each mapped to a recognised activity type
- Cycle management — per-jurisdiction annual or multi-year cycles, with pro-rata handling for joiners and leavers
- Gap detection — who is short, by how much, and what will close the gap before the deadline
- Evidence export — per-person, per-cycle, in a form a professional body or auditor will accept
- Simulation counts as activity — because assessed, coached practice is the strongest evidence of professional currency that a regulated firm can hold
Our learning business has its own headquarters in Hong Kong, where CPD and regulatory training are the daily reality of the business. That depth is what we bring to a client operating elsewhere — it is a capability asset, and it is why the Hong Kong market is one line of one group rather than the whole of the company.
Ten million learners, read carefully
That figure is the size of the operational footprint — registrations, records, assessments, certificates and audit trails carried. It is not a claim that ten million people were transformed by us, and we will not let it be presented that way.
It proves scale of operation
Twenty-five years of renewal cycles, expiries, migrations and audit requests handled without losing the trail.
It proves the record model
A population of that size and that turnover exposes any weakness in the data model within months. There is no place to hide a bad record at that volume.
It does not prove your outcome
Your capability result depends on your content, your assessment and your population. We measure those; we do not transfer a headline number.
What the TMS does that the LMS does not
The LMS records what happened. The TMS decides what should happen next. Most organisations have the first and think they have both.
Skills taxonomy
A shared vocabulary of capability, aligned to roles and to the authority tiers in your operating model. Without it, a skills gap analysis produces a list of course requests rather than a capability plan.
Gap analysis
Where demonstrated capability falls short of what the operating model requires. Done against the taxonomy and the authority map rather than against a training budget.
Succession and pathways
Who is being prepared for a role that requires authority they do not yet hold — including the supervisor and agent-owner roles that did not exist three years ago.
Investment decisions
Which capability gaps cost the business most, and whether the answer is training, process redesign, or accepting the gap. Not every gap is a training gap.
Learning management and capability management are different jobs.
Conflating them is the most common architectural mistake in enterprise learning. One runs the learning. The other runs the capability — and capability is what a strategy actually depends on.
| Concern | LMS (UpLearn) | Capability management (TMS) |
|---|---|---|
| Core question | Has this been delivered, and can we prove it? | Can this population do the work, and can we prove it? |
| Unit of record | Learning activity — enrolment, completion, attempt | Capability — role, level, evidence, validity |
| Primary owner | Learning and compliance functions | Capability owner, usually the business line |
| Time horizon | Campaign, course, cycle | Multi-year, with decay and re-validation |
| Output | Completion rates, coverage, evidence packs | Capability baselines, gaps, sequencing, workforce plans |
| Data owned | Learning events, content, assessment results, attestations | Capability profiles, role definitions, assessment instruments, agent records |
| Typical question | "Are we compliant across every jurisdiction?" | "Can this business still operate if we lose a third of the team?" |
How they connect in wizBank. The LMS produces the events, the scores and the attestations. The capability layer consumes them, applies them against a role and a standard, and produces the profile, the gap and the decision. Neither replaces the other, and an organisation that buys only the LMS will keep answering the first question well and never get to the second.
LMS or course catalogue — the distinction that decides the budget
You can buy a course catalogue cheaply and still lack a capability system. The difference is not features; it is whether the record supports decisions.
- Content organised by subject
- Completion is the primary record
- Currency is a publishing concern
- Cannot answer who is qualified for what
- Value measured in seats consumed
- Static — it describes the past
- Content organised by role and authority
- Demonstrated capability is the primary record
- Currency is a validity-period concern
- Can answer who is qualified for what, and when that was last true
- Value measured in decisions enabled
- Dynamic — it describes the organisation now
Where it runs, and how it talks to everything else.
Enterprise learning fails on deployment and integration far more often than on features. Those are the two things we spend the most time on, and the two things we will not let a client discover late.
Deployment models
SaaS for speed and for populations that need to be online quickly. Private deployment where records carry regulatory weight and data residency is non-negotiable. Hybrid where the learner population is distributed but the record of assessment must stay inside the perimeter. Multi-tenant where the organisation has genuinely separate entities, and separate where they only look separate on an org chart.
Data residency
Where the records live is a decision the client makes, and it is a decision with consequences for cross-border transfer, for local regulator expectations and for internal audit. We document what is stored, where, and how it moves, before contract rather than after it.
Identity & provisioning
SSO and SCIM against your identity provider, so that joiners, movers and leavers are reflected in enrolment and certification without a reconciliation step. Learner accounts are provisioned from the HR record, and deprovisioned when it changes.
Integration surface
REST API and webhooks for HRIS, talent, assessment and business systems, plus the content standards your authors already use: SCORM and xAPI for tracking, with the content itself hosted or delivered as you prefer.
Why learning is the foundation of an agentic business, not a line item
This is the single idea that separates our enterprise learning business from a training vendor. An agentic business needs three populations taught, and only one of them currently is.
- Learning is for employees
- Courses are assigned by an L&D system
- Completion is the metric
- The LMS is a compliance archive
- External partners are somebody else's problem
- Software is deployed, not onboarded
- Learning covers every capability carrier — employees, partners, and digital employees
- Capability is assigned by role and authority, not by department
- Operating evidence is the metric, not completion
- The LMS is a governed semantic store the agents reason over
- Partner enablement sits inside the same system, with its own records
- Digital employees are onboarded with a curriculum and given a performance record
Six questions that tell you whether you need a real LMS.
If the answer to three or more of these is yes, a course library with a login will not get you there. It is a short list because the underlying requirement is a single one: a defensible, current, per-person record of competence.
Do your regulators ask for evidence by person?
If the answer is a population-level summary, a report is enough. If it is "show us the training record of this named individual, on this date, against this material version", you need a per-learner evidence model with an audit trail behind it.
Do you operate in more than one jurisdiction?
Multiple legal entities, licences or regulators means the same course has different required content, different assessment rules and different cycles. A single catalogue with a global completion rate cannot represent that.
Do you deploy agents into the same processes?
Then the record must hold agents as well as people: an agent version with a knowledge set, an evaluation result, a permission scope and an expiry. A human-only LMS will need a second system bolted on later, and the two will disagree.
Do you rely on external partners in your process?
Partner populations need certification records, tiering and expiry visible to you — with delegated administration, because you will not administer a vendor's roster by hand.
Is your population changing faster than your campaign cycle?
High turnover, project staffing, seasonal operations — if the population on the ground next month is not the population on the register today, assignment rules have to be event-driven rather than annual.
Do you need CPD, licence or certification tracking?
Anything with an expiry date and a professional consequence is a workflow problem, not a report problem. It needs renewal logic, escalation, and the ability to answer "who is currently valid" instantly.
And the two that disqualify a course library outright. If a material change in policy, product or regulation has to reach a defined population by a defined date and be provably received, you need assignment rules and an evidence trail. If you have to demonstrate that a specific individual was competent on a specific date for a specific purpose — an audit, a tender, a client assurance questionnaire — you need a per-person record. Neither of those is a reporting feature. They are the product.
Five questions that tell you whether a learning system is actually working
Five yes-or-no answers. Three or more yes means the foundation is real. Fewer means the learning system is a reporting tool rather than a capability system — and an agentic business cannot be built on that.
- Can you name who can do what, and how you know that is still true this month?
- Does a regulator or auditor get an answer from records you already hold, or do you assemble it?
- When a policy changes, can you identify everyone affected and what they must retrain?
- Do external partners who touch your process appear in the same system as your employees?
- Do your digital employees have a training record, or only a version number?
We do not sell a course subscription.
A content subscription is a good product with a different business model, and we are not going to pretend our platform is one. What we will not do is license a catalogue and let you believe you now have a learning system.
Our platform carries your content, your assessments, your certifications and your evidence. That is more work to set up and it is more expensive per seat, and it is the reason the record is worth something when someone asks. If you want breadth of content for a modest price, buy a content vendor and pair it with a compliance system — it is a legitimate architecture, just not ours.
We also do not run a course marketplace on your catalogue, and we do not let auto-generated content into a regulated programme without the same review, versioning and assessment controls as anything else.
If the requirement is evidence of competence across a regulated population, thousands of courses will not satisfy it. We will say that during the conversation rather than after the pilot.
Material that changes behaviour or conveys regulatory obligation needs an owner, a version, a review date and an assessment attached. Generation can help produce drafts; it does not confer the review that makes content safe to certify against.
Completion is a system event. We report proficiency, evidence completeness and validity, because those are the numbers that hold up under questioning.
Building a defensible per-person record across a population takes configuration, content and assessment work up front. A cheap deployment that produces a weak record is a cost you will pay twice.
Four honest questions before you buy or replace an LMS
Four questions. A system that answers no to the first or second cannot support an agentic business, however good its course catalogue is.
- Can it hold records for people who are not your employees — partners, contractors, suppliers?
- Can it hold a record for an agent, with a performance history and a validity period?
- Can it distinguish attendance from demonstrated capability, and evidence both separately?
- Can your risk function get a regulator-ready answer from records it already holds?
What this page answers
Every topic below is covered in the sections above, and each links to the page that goes deeper on it.
Bring your evidence request, not your feature list.
Tell us the question a regulator, an auditor or a customer has asked you that you cannot currently answer. We will show you exactly how wizBank would produce that answer on your population, and where it could not — a two-week working session, no commitment.