Your procedures. Not a generic course library.
New-hire onboarding built on the documents your site actually runs on, with results a supervisor can trace.
What you are trying to do
Onboard new hires against the current revision of a procedure, not last year’s deck.
Keep each organisation’s material isolated at the database level.
Produce a record that names what was assessed and against which document.
What this rests on
- Answers cited back to your own material, with the instructor one tap away when the material does not cover itOn our go/no-go benchmark every answer retrieved the right passage, carried a valid citation and stayed inside the material, and every out-of-scope question routed the learner to the instructor rather than a guess — against 54.2% for handing the model the whole document.
- Every procedure step and rubric criterion carries a reference back to the document it came fromA criterion with no source reference is refused before it can be saved. Not a warning — a rejection.
- Competency is scored by rules against an approved rubric, not by a language model’s opinionForty-one automated checks, including a deliberate break to prove the checks can fail. The model records what it observed; the rubric decides the mark.
- Each institution’s data is isolated at the database level, not by application codeTen checks run as a real signed-in user, so the database’s own access rules are genuinely exercised rather than assumed.
- Data export, erasure and guardian consent are implemented and testedExport, erasure and guardian consent each ship today and are driven through a real browser before release.