Highstage eQMS — Training & Compliance

Prove your training compliance on any date. Not just today.

Every person, every controlled document, one live state — with the evidence, the dissent and the excusals an auditor will actually ask to see. No status-chasing, no spreadsheet reconciliation the night before.

Highstage brandmark
Overall compliance, due soon, overdue and people at risk

States that reflect reality, not a filing cabinet

Not "assigned" and "done". Six states track exactly where a person stands against their deadline right now — and every obligation is in exactly one of them at any moment.

OpenNot yet due, nothing outstanding.
Due SoonInside the warning window — 7 days by default.
OverduePast deadline with no valid, current evidence.
FulfilledSigned, understood, still inside the interval.
ExcusedConfirmed leave — the clock is held, not ignored.
RefresherWas fulfilled; the retraining interval has elapsed.
Retraining

Two kinds of retraining, correctly separated

Most systems conflate "a document changed" with "time to re-attest". Highstage keeps them distinct: a new-version grace period gives people time to catch up when a document is revised, while a separate retraining interval handles scheduled re-attestation — annual SOP refreshers, for example.

An auditor can see exactly which trigger fired, and when.

Trigger — new versionMAN00001 v1 → v2. Grace period starts; deadline set from the release date.
Trigger — retraining interval12 months since last fulfilment. Moves to Refresher; the document is unchanged.
Plan coverage row showing overdue, due soon and refresher counts
Dissent

"I do not understand" is a record, not a lost checkbox

Dissent is built in and weighted equal to "I understood" — and it does not silently satisfy the obligation. It routes straight to the document's author and stays visible in an admin queue until someone follows up.

Nothing unclear gets buried, and the unclear document gets fixed.

OPEN DISSENTS 3 awaiting author response
MAN00002 v2 — User Manual, USStep 4.2 contradicts the work instruction.
NOT FULFILLED
SOP00114 v5 — Complaint handlingEscalation owner unclear for weekend intake.
NOT FULFILLED
SOP00051 v2 — Design transferAuthor replied; revision in review.
IN PROGRESS
Signature integrity

Integrity you can prove, not just claim

Every signed record carries a cryptographic hash of its own signature fields, taken at the moment of signing. Anyone can recompute it later and verify the record hasn't been altered since — proof, rather than a log saying somebody clicked "sign".

SIGNED RECORD
DocumentMAN00001 v2 Signed byHSADMIN Timestamp2026-07-28 09:14:02 CET ResponseRead and understood
SIGNATURE HASH 9f2c41ab7d0e58c3b6a1f0d94e7c25b8a3f61d0c9e84b752a0c6df31e59b7a44 Recompute at any time — a mismatch means the record changed.
Time Machine

Audit any date, not just today

Reconstruct compliance exactly as it stood — or will stand — on any chosen date: what evidence existed, which excusals were actually confirmed by then, what the deadlines were. Drag the date.

Today
Compliance as of
31 Jul 2026
Jan 2026MarMayJunTodaySepNov 2026
Overall compliance 21%
11Overdue
0Excused
0Refresher
Today. An urgent push from CAPA-0042 added seven obligations this week, each with a stated reason and a second-person confirmation.

Speed where you need it, controls where an auditor looks

A genuine two-person control on urgent training

A CAPA, an NCR or an audit finding can push training immediately, skipping formal plan approval. But the creator can never confirm their own push, and every push carries a stated reason.

Excusals that don't quietly create risk

Leave doesn't only pause the clock. When it ends, deadlines shift forward by the length of the absence — so returning staff aren't instantly flagged overdue for time they were never at fault for.

Ownership stays where it belongs

A one-time corrective retrain never quietly takes over someone's long-term recurring plan. The original plan and interval are left untouched — corrective action and standing process stay separate.

Against a spreadsheet and a folder of signed PDFs

THE QUESTION
SPREADSHEET + EMAIL
HIGHSTAGE eQMS
Who is overdue right now?
Chase managers, rebuild the sheet
Live count, per plan and per person
A document was revised — who must re-read it?
Manual mail-out, no deadline trail
Grace period starts automatically, trigger recorded
Someone didn't understand it
A reply in an inbox, if at all
Dissent record, routed to the author, still not fulfilled
Prove the record wasn't edited afterwards
File timestamps, and trust
Recomputable signature hash
Show compliance on the day of the incident
Reconstruct by hand from old exports
Time Machine — pick the date
Highstage User
"The auditor asked what our training status was on the day of the deviation. It took us one field, not one week."
— Quality Manager, [Medtech]

Live in a quarter, not a project year

WEEKS 1–2 · MAP Job functions and document scope We map who must read what, and set grace periods and retraining intervals per document type.
WEEKS 3–6 · CONFIGURE Migrate existing evidence Historic signatures load with their original dates, so the Time Machine reaches back before go-live.
WEEKS 7–10 · GO LIVE Audit dry-run with your QA team We run the questions an auditor asks, against your real data, before anyone external does.

Questions we get

Does dissent block the document?No. It blocks that person's obligation from counting as fulfilled and notifies the author. The document stays in force until its owner acts.
Can we set different grace periods per document type?Yes — per document type or per plan, alongside the warning window that drives Due Soon.
What happens to training that was already signed elsewhere?Historic evidence migrates with its original signing dates, so past states reconstruct correctly.
Who can confirm an urgent training push?Any authorised approver other than the person who created it. The reason given is stored on the record.

See it against your own SOPs

Bring one plan and one revision history. We'll show you the state on any date you pick.

Talk to us