What it does
Actions
The single thing an inspector most wants to see working. A finding raised, given to somebody, dated, done — and checked by somebody other than whoever did it.
Actions come from everywhere: an assessment finding, a failed check, a defect on a certificate, an incident, a legal update, or somebody just noticing something. All of them land in one list with an owner, a priority and a date.
Completing an action does not close it. It moves to awaiting verification, and the product refuses to let the person who did the work be the one who verifies it. That separation is what turns a task list into evidence.
An open urgent action pulls its regime to red on the register and the dashboard, even when every document is in date — because that is the honest reading of the situation.
What it does not do
The boundary, stated plainly, because you will find it eventually and it is better to find it now.
- Verification is a person confirming they checked. DutyHub records the claim and who made it; it cannot inspect the work.
- An action nobody raises does not exist. The product surfaces gaps in the duties it knows about, not problems nobody noticed.