Regulations with responsible persons
Act, ordinance, DGUV regulation, standard, permit or internal directive — company-wide or per site, with a responsible person and deputy, source and summary. A regulation that does not apply stays in the register with its reasoning: that decision matters to an auditor as much as the applicable one.
Obligations whose status is computed
An obligation is linked to a maintenance template (DGUV V3, UVV, BetrSichV, ZÜS, fire extinguishers, drinking water), an instruction topic or a credential from the driver file. The status follows from the linked objects — fulfilled, due soon, overdue — with counts. None of it is retyped or maintained twice.
Manual obligations with evidence
What no module records — the risk assessment, the appointment of the data protection officer, the notification to the health authority — gets a due date and a recurrence. Evidence with date, note and document moves the due date by the interval.
Review interval instead of a change feed
There is no legal change service and no warranty on a regulation's currency. Instead, each regulation is re-read against the linked source at its interval and confirmed with "Reviewed"; changes are recorded as a history with a valid-from date. What is overdue is on the dashboard.
Starter catalogue without professional review
Around 17 regulations for fleet, workshop and buildings — ArbSchG, BetrSichV, DGUV V1/V3/V68/V70, StVZO § 29, FZV, GefStoffV, lifts, 1. BImSchV, TrinkwV, fire protection, GDPR — with typical obligations that are bound to the existing maintenance templates on apply. Explicitly without professional review: the operator checks every entry against the source.
Reminders and reporting
Due obligations and upcoming reviews are date sources of the workflow automation: e-mail or notification X days ahead, with tokens for obligation, regulation and responsible person. The "Legal register" report lists every obligation with its status as CSV, Excel or PDF — the list you hand an auditor.