Learning delivery
Built for a bad connection
Delivery & Engagement
The class, and the register that reconciles to it
Live sessions on your timetable, joined from the course, with an attendance register and a regularisation request for the day it was wrong.
live · 20 API routes
What it does
Sessions and joining
On the timetable, in the course, in the learner’s own list.
An attendance register
Per session and per course, with rules that define what counts.
Regularisation
A learner disputes a mark; somebody with the authority decides; both are recorded.
How it actually works
Attendance rules are data, not code
What counts as present — minutes attended, joined-by time, whether a late join is partial — is configuration per institute. A hard-coded threshold is the fastest way to make a product unusable for the second customer.
The permission keys it adds
A sample. Each is a real key in the catalogue, described for a school administrator rather than an engineer.
live.session.viewlive.session.joinlive.attendance.viewlive.regularization.decide
Who holds it
- Teacher
- Student
- Institute Admin
The shipped role templates that hold it by default. Each is a copy you own and can edit — nothing in the code reads a role's name.
And what it does not
Naming these here is cheaper for both of us than discovering them in week six of a pilot.
What this does not do yet
Naming these is cheaper for both of us than discovering them in week six.
- A meeting-provider adapter — you paste a Zoom, Meet, Teams or Jitsi link
- Recording ingestion
- In-class polls
Related
Batches & enrolment
Cohorts, timetables and a waitlist that moves
Start on the free tier. Bring your spreadsheet.
A hundred seats, twenty-five courses and no conversation. If you would rather see it driven by someone who knows it, that takes twenty minutes.
Or open the sandbox (opens in a new tab) and click around first. No form.