What it does
One calendar
Every date the product knows about, in one place: document reviews, certificate expiries, recurring checks, statutory deadlines and action due dates.
Dates arrive from everywhere — a fire risk assessment review, a gas certificate expiry, a weekly alarm test, a DSAR deadline, an action somebody accepted. Left in their own systems they are ten lists, and the one nobody checks is the one that matters.
Everything lands in one table, so a single view answers "what is due in the next thirty days" across every regime and every building.
There is a subscribable feed, so the dates appear in Outlook or Google Calendar alongside everything else somebody actually looks at.
What it does not do
The boundary, stated plainly, because you will find it eventually and it is better to find it now.
- The feed is read-only. Moving a date has to happen in DutyHub, because the date usually has a reason attached to it.
- A calendar link stays valid indefinitely rather than expiring, because a calendar client re-fetches forever and a broken feed is worse than no feed. Treat the URL as a credential.