What it does
Staff without accounts
A bar's Saturday crew, an agency steward, a volunteer. They need to confirm they have read the evacuation procedure. They do not need a login.
Acknowledgement goes out as a link with an expiry and a use limit. The person opens it, reads the current approved version, and confirms — and the record keeps the exact text they were shown, not a reference to a document that has since changed.
Where there is real training content, DutyHub uses the platform's course player and records the score. Where there is not, the acknowledgement is the record.
Requiring an account for everybody who has to confirm reading a procedure is the wrong product and the wrong bill. It is also why most organisations do not have the evidence.
What it does not do
The boundary, stated plainly, because you will find it eventually and it is better to find it now.
- A link records that somebody with the link confirmed. It is not identity verification, and for a casual workforce that is the appropriate trade — but it is a trade, and you should know you are making it.
- Links expire and are use-limited by design, so a forwarded link stops working rather than being reusable for ever.