What it does
The register
One row for every duty you carry, on every building you carry it for. Green because an approved document is in force and in date — not because somebody ticked a box.
A register is built by answering questions about a premises, not by choosing from a menu. You describe the building — what it is used for, how many people, whether anybody sleeps there, whether there is gas, a lift, a kitchen — and the applicability rules put the duties that follow onto the register.
Status is computed. A duty is green when the thing that satisfies it exists, has been approved by somebody entitled to approve it, and has not expired. It goes amber when a review or a check is coming due, and red when it has passed or when an urgent action against it is still open.
The one status a person can set by hand is "not applicable", and it requires a written justification. Everything else is derived, because a status somebody can type is a status somebody will type on a busy afternoon.
What it does not do
The boundary, stated plainly, because you will find it eventually and it is better to find it now.
- It reflects what you have recorded. A duty satisfied by a certificate nobody uploaded is red, correctly, and DutyHub cannot tell the difference between not done and not recorded.
- Applicability rules are written by us and reviewed by retained professionals. They are a starting point for your own judgement, not a legal determination about your organisation.
- A duty nobody has written a rule for will not appear. The gap report exists to make that visible rather than to pretend the list is exhaustive.