How it works
A certificate says someone clicked.
Every compliance platform issues a certificate when someone finishes a course. A certificate is a PDF. It proves someone clicked through some slides — not who actually did the work, not what they saw, not whether the record still says today what it said the day it was signed. LaborGenie issues something different: an attestation record, built so that altering or deleting it after the fact is exactly as detectable as forging it in the first place.
How a record gets made
Two refusals, built in.
Two things the platform refuses to do, on purpose. One binds at registration, the one door all curriculum passes through; the other binds at signing, the one moment a record is made. Neither can be routed around by the catalog, the job-role picker or the request button, because all three go through the same door.
A clinic and a vendor serving clinics carry inverse obligations — one obtains business associate agreements, the other signs them; one notifies patients, the other notifies its client. LaborGenie records which kind of organization you are and refuses to register a track scoped to the other kind. A clinic put on the business-associate track would be taught the inverse of its own duties and then attest that it understood them. That is refused at the door.
Binds at registrationYour Security Official's name, your incident hotline, your breach-notification window fill in as the learner reads and freeze verbatim into the attestation. While any value the text quotes is still blank, the platform will not sign. An unfinished setup can't produce a legal record that says someone was told to call a hotline nobody named.
Binds at signingA completion can require two signatures, not one.
Some compliance completions carry more weight with a manager's acknowledgement in the record — not as a formality, but as a second point of accountability. Organizations can require a countersignature: the completion lands in a review queue on the manager's own console, and the training record carries two signatures before it's considered closed.
The countersignature is its own signed record, chained to the completion it acknowledges. The same append-only rule applies — a manager acknowledgement cannot be removed or edited after the fact any more than the completion it covers can.
A certificate that proves itself.
When someone completes a track, they receive a certificate they can share. Anyone who receives it can verify it — no account, no login, no call to customer service required.
Every certificate carries a verification link. Open it and the verifier checks the attestation record directly — name, track, completion date, curriculum version hash. Organizations opt in per-tenant; individuals control whether their own certificate is shareable with a revocable consent flag that deliberately sits outside the signed attestation, so it stays revocable even after it's been shared.
This is what “independently verifiable” means in practice: the proof does not depend on LaborGenie's uptime, our word, or our continued existence.
Credential tracking in the same system.
Tracking external licenses and certifications alongside training records, with 90, 60, and 30-day alerts before anything lapses.
Every person's profile carries two clearly separated records: the verified training record (platform-attested completions) and tracked external credentials — state licenses, DEA registrations, board certifications, COI, CAQH attestations. External credentials are recorded as claims with document evidence, never presented as platform-verified, and never entering the attestation chain.
The separation is the selling point. A platform that blends self-reported credentials with verified training records makes both worse. Here they live side-by-side, clearly labeled, on the same dashboard, without laundering one into the other.
Every record remembers exactly what it covered.
Curriculum changes over time — a new CFR citation, an updated procedure, a policy correction. LaborGenie snapshots the exact content hash of the version each person actually completed, and freezes an organization’s own placeholder values — its policies, its officers, its locations — into the attestation at the moment of signing. Update the curriculum next quarter, and last quarter’s records still say, provably, what they said when they were signed.
An evidence pack, not a login you have to trust
When it's time to answer an auditor — or a curious board member — export the organization's evidence pack and run it through the standalone verifier. It re-derives every hash in the chain independently. If a record was altered or removed, the break shows exactly where. Retained six years, matched to HIPAA's own documentation rule.
Product preview — illustrative attestation rows, not a real tenant's records.
Studio
The AI that drafts your video cannot publish it.
Studio is where an organization builds its own training video. Create a project, upload the procedures you actually run on, and Genie drafts a storyboard from them — a headline, the narration and a slide grammar for each point. It renders with your logo, your colours and your organization's name on the slide, and it stays login-gated and streamed like every other module video.
That sentence describes the code, not the interface. The generator reads a project to authorize, reads the documents it was given, calls the model and returns a draft. It has no path to the stored storyboard, never inserts a render and never publishes — and a test in the platform's own suite bans every write verb, and any import of the write actions, from that file. A gate that says “the UI asks first” is one refactor from being skipped. This one cannot be.
Your documents are treated as data, never as instructions — the first rule the model is given — and the second rule is to invent nothing: no citation, regulation number, deadline or penalty that isn't in your material. Every drafted segment is shown in full before an author accepts it, and the model's own notes render above the segments, which is where a gap in the sources, an unsupported claim or an attempted injection gets reported. Generated narration becomes content a workforce attests to under a tamper-evident record, so the gate had to be the kind that can't be forgotten.
- Calls no mutating database method — .insert( .update( .upsert( .delete( are banned from the file
- Imports nothing from the write actions
- Checks staff role, tenant pause and rate limit before the model is called
- Treats source documents as data, never instructions — the first rule, before anything else
- Invents nothing: no citation, regulation number, deadline or penalty absent from the sources
- Validates the model’s reply before returning it
Assignment, not a spreadsheet.
A roster comes in as a CSV or a live connection. Each person resolves to a job-role bundle — the tracks and role add-ons that apply to them today. Move someone from front desk to billing and their obligations move with them on the next pass, not at next year’s renewal.
Termination doesn’t erase the record.
Guarded account deletion refuses to destroy anything load-bearing — training records, attestation chain entries, audit events, manager countersignatures, or export logs. An organization can revoke someone’s access without destroying the evidence that they trained. The record is retained for as long as the organization’s account exists, matched to HIPAA’s six-year documentation rule.
Compared fairly
Comparing platforms? Compare the record.
Two competitors with different shapes. Each comparison says what they do well, where we aren't comparable, and the one question a feature list can't answer.
Learning, credentialing operations and policy management as one purchase, with a large accredited library. LaborGenie doesn't out-bundle it. It changes what the completion record is.
Read the comparison → Traliant sells the library.Cinematic, whole-workforce compliance video, sold to HR. Ours isn't cinema, and the page says so. What it can do is name your officers, draft from your procedures, and sign into a record.
Read the comparison →