Everything a department needs to grow its people, in one place.
The learning plane turns a department’s idea of good work into skillsets, programmes, teams, learning paths, evidence and assessments — and keeps every step where the people responsible for it can see it.
Say what good looks like, once, for the whole department.
A department publishes a skillset — the skills it values and what each level of them means — and a programme, the weeks of work that get somebody there. A draft of either can be written for you from a brief, and edited before it is published.
Skillsets with levels
Criteria grouped by skill, each with the levels a person can be at, so an assessment has a shared language and a member knows what the next level asks.
Programmes in weeks
A programme is weeks of sections and tasks with the hours they take. Publishing it is deliberate; a new version leaves paths already started untouched.
A draft to start from
Where a model is configured, a lead writes a brief and reads a drafted skillset or programme back, to keep, cut or rewrite. Nothing is published without a person.
Invite by name. Know where somebody stands from day one.
A team is the people who work together, with a lead and its mentors. An administrator invites a person; the person answers a few questions about themselves on first sign-in — their department’s and the organization’s own — and again whenever a head or an administrator asks; it stays with their record and sits side by side before the first path is started.
Invitations that expire
Each invitation is a private link that works once, can be sent by mail, revoked or reissued, and respects the organization's domains, where it has any.
What they say about themselves
The member’s own answers, question by question — to their department’s questionnaire and the organization’s own — when they join and whenever they are asked again, kept with their record for them and for the people who follow their work. Nobody scores it.
Roles of your own
The roles the platform means everywhere, and roles an organization defines on top: additive, organization-wide, and never able to take a responsibility away.
A programme becomes one person’s weeks.
Starting a path lays the programme out from a kickoff date, a week at a time, each week closing on its day. Each week is a task, and each task carries what was asked, what was shown, and what the reviewer said.
Weeks that speak up
A week warns two days before it closes and on the day; a lead can extend a closed week or reschedule a task, and the path shows the change.
Evidence, kept safe
Documents, images and text are scanned before they are stored and handed out only to the people entitled to the task. Nothing is ever shared by link.
Repositories on demand
A GitLab assignment provisions a repository from your template, invites the learner, and snapshots what was pushed for the review.
One programme, one result, written when the work is done.
The assessor, usually the team’s lead, gives each capability of the skillset the programme teaches a level and, where it helps, a note, all on one page, then publishes the result — the levels and notes, the feedback, and any targets and next steps — which is what the person reads and what completes their path.
Private until published
A member sees a result when it is published, never a draft and never the assessor's private notes. Publication is in the audit history with who and when.
Where you stand, drawn
A result reads as a picture: a bar per area, strengths and what to grow next, and every capability with its level and note — never one grade. It keeps the names it was published with, and a correction is a revision that keeps the earlier one.
Reports, in bounds
Leads and administrators read progress across their teams and organization; nobody reads across a boundary they are not responsible for.
Run every organization from one place, without being inside any of them.
A separate console for platform administrators: organizations, their first administrators, platform access, the platform’s own audit history — and break-glass support that has to be granted, for a reason, for a day at most, with the organization’s administrators told.
Ready to see it with your own team?
Tell us about your department and how your people learn today. We will show you how the learning plane fits, and set up your first organization with you.