Most school software stores data. This one is designed around a single question: when an inspector asks what happened, can you prove it? Every decision below follows from that.
Hour records are the compliance surface a regulator inspects, and the hardest thing to make correct after the fact.
UPDATE and DELETE on an hour entry are refused by a Postgres trigger, not by application code that someone could bypass. A developer who writes an update against a recorded value gets an error, not a silently rewritten legal record.
A correction inserts a new row carrying a mandatory reason and a reference to the row it replaces. The original stays, marked void, and both remain visible for the life of the record.
A conditional session — one where the split depends on how the day actually ran — will not save without a note explaining what decided it. An uninterpretable record is refused at the door.
No hour total, monthly cap, or exam gate is written into the software. They live as rows with effective dates and a source note, and the interface shows that note beside the value. We flag; we do not decide.
When an inspector asks for records, the difference between “here is a read-only view for that date range” and “give us three days to export spreadsheets” is a feature a school will pay for.
Quizzes release as students progress and objective items are marked instantly. What is not automated is the part that matters.
Multiple choice, true/false, and matching — the large majority of items. Instant feedback, and the lesson to reread.
Scenario questions get an AI-drafted score that an instructor confirms or overrides. A draft is never a result.
Every safety-critical item, and every practical assessment. A student can answer 95% correctly and still fail because they got the bloodborne-pathogen question wrong — and the platform will refuse to record that as a pass, whatever the total says.
No software can watch someone shave a client with a straight razor. That stays an instructor, every time.
Each school sets its own name, mark, and colours. Those colours become the application’s colours at runtime, so there is no per-tenant stylesheet and nothing to maintain.
A school’s students never see Amplifi anywhere. That is the whole promise, and the product is built so it cannot accidentally be broken — a school with no uploaded mark falls back to its own initial, never to ours.
Their own record only. Progress, lessons, hours, and results. They cannot see another student, and they cannot see instructor material.
Assigned cohorts. Records and verifies hours, grades assessments, teaches from the instructor edition. No edit rights over history.
The whole school. Enrolment, staff, branding, reporting, and granting auditor access when an inspection comes.
Read-only, scoped to named students and a date range, time-boxed with a hard expiry. Sees nothing without a live grant.
Amplifi staff. Not a member of any school. Reading a school's data requires naming that tenant, and every such read is separately audited.
It is the part that decides whether software like this is worth having.