Training delivery platform
Training delivery,and the record thatproves it happened.
Plans, hours, evidence and reviews in one place, with everyone who needs to sign actually signing. You decide how it all works.
Everything a programme needs, in one place.
Most providers run enrolment in one system, delivery in a second, hours in a spreadsheet and reviews in a document template. The joins are where the evidence goes missing.
Learning plans
Set a programme up once. Everyone who joins it gets their own copy, dated from the day they actually start.
Guided learning hours
Learners log their time as they go and their coach signs it off, so nobody is reconstructing a year from memory in June.
Evidence and marking
Work comes in, gets marked, and goes back with reasons if it needs more. None of it lives in somebody's inbox.
Skills assessment
Learner and coach score the same things separately. Where they disagree is what the next conversation is about.
Progress reviews
Everyone writes their part before the meeting, so the meeting can be a conversation instead of a form-filling exercise.
Reporting
Click any number and you get the records behind it. Nothing on a report is a figure somebody typed in.
Learning plans
A plan built from your programme, not a curriculum you bend around.
A programme is a template you build once: months, modules, activities, what each one is due by and what counts as finishing it. Copy it for the next cohort and change only what is different.
- Due dates work off the day each learner starts, so nobody rebuilds a plan per cohort
- An activity will not go for marking until it has the evidence it asks for
Module 6 · Conversion optimisation
- Submitted
A/B testing fundamentals
Digital learning · due 10 Jul
- In progress
Run a live A/B test
Assignment · due 24 Jul
- Not started
Landing page critique
Assignment · due 31 Jul
- Referred
Build a campaign dashboard
Referred 26 Jun · 1 of 2 evidence
Guided learning hours
Hours logged in seconds, checked against the work they belong to.
A learner enters hours and minutes and that is exactly what gets stored. No decimals quietly rounding, and no argument in twelve months about how a total was arrived at.
- Logged from a phone, because that is where most of the working day happens
- Submitted and verified are different states, and both stay on the record
verified of 450:00 planned
28:00
awaiting verification
- Verified
- Awaiting verification
- Monthly target
Evidence and skills
Sending work back is part of the system, not an email nobody can find.
When a coach sends something back they have to say why, and that note sits on the activity where the learner is already working. The earlier version stays too.
- Feedback lands where the work is, not in a thread the learner has to go looking for
- Self and coach assessments sit side by side and are never averaged into one score
- K1Audience segmentationselfcoach
- K3Data protection and consentselfcoach
- S1Campaign planningselfcoach
- B2Seeks and acts on feedbackselfcoach
Where the two disagree, the gap is the conversation. K3 and S1 are flagged for the next review.
Progress reviews
Two dates on every review, and three people on the record.
The date it has to happen by and the date everyone actually sat down are different things, so they are different fields. Conflating them is how a review looks compliant and is not.
- How often reviews happen, and what is in them, is yours to set
- Once signed, a review can be added to but never quietly edited
Sections complete
Scheduled 14 Aug, two weeks inside the compliance deadline. Personal development and goals still open.
- Elena Rossi · LearnerSigned
- Marco Bianchi · Learning coachSigned
- Sofia Lindqvist · Workplace mentorAwaiting
Progress against plan
Drift shows up in month three, not at the end.
Everyone has a target that moves with how long they have been on programme. The only thing a caseload review needs to look at is the gap between where someone is and where the marker sits, and it is the same gap on all three screens.
- learners on this coach's caseload
- submissions waiting to be marked
- reviews due in the next fortnight
Progress complete, against elapsed-time target
- Tomas Novák
- 58%
- Elena Rossi
- 42%
- Aisha Benali
- 44%
● On track · 3 points ahead of target
▲ At risk · 13 points behind, 7 submitted and unmarked
■ Behind target · 28 points behind with 4 items unmarked
The vertical marker is the target for each learner’s point on programme. Figures are from the demonstration data set, not a customer.
Built for every side of a programme, including the one that usually gets ignored.
Employers are the most neglected users in this category. They are the ones who have to sign, so they get a view worth signing from.
Training providers
Everything from first contact to final assessment, with a caseload that puts whoever is slipping at the top.
Universities
Run the work-based half of a programme properly, instead of tracking it in a spreadsheet nobody trusts.
Colleges
Different cohorts on different routes, all measured against the same idea of what progress means.
Employers
See what someone actually did this month, and sign what you need to sign in about two minutes.
Health and public sector
Long programmes, short courses and continuing development, all leaving the same kind of trail behind them.
Employability providers
Case management that produces a record a caseworker can put in front of anyone who asks.
“A learner, a coach and a workplace supervisor agreeing on progress in writing, on a schedule, is what stops people drifting.”
Yours to shape
The way you run programmes is a setting, not a feature request.
How often reviews happen, what is in them, how many hours a programme needs, how long it runs, what the documents say. All of it lives in your workspace and you change it yourself, without waiting for us to ship anything.
- Your data, wherever you need it
- An EU region, your own servers, or somewhere else entirely. Where it lives is your decision, not a condition of using us.
- Your words, not ours
- Interface language and every role label. If your coaches are called training coordinators, that is what the platform calls them.
- Accessible because it has to be
- WCAG 2.2 AA, a keyboard path through every workflow, and nothing where colour is the only thing telling you what happened.
We would rather show you than tell you.
A demo runs about forty minutes and covers the learner, coach and employer views of the same programme. Bring the awkward question about your own delivery model; that is the useful part.
What it covers
- How you deliver now, and where the evidence currently lives.
- The three roles walked through a programme shaped like one of yours.
- A written note of what would need configuring and what we would build.