Certificates, competencies and expiries
Compliance software lives or dies on how it models the paperwork. Mustr keeps it simple: one list of competency types, defined by you, used everywhere.
Your competency list
Competencies are whatever your work depends on: first aid, working at heights, a site induction, a machine ticket. Each one is either renewing, with an expiry date that gets tracked and chased, or one-off, verified once and current forever, which is how inductions and some licences behave. You define the list during onboarding, usually straight from the competency matrix you already keep, and it becomes the shared language of the whole system: client requirements, role requirements and worker certificates all point at it.
Recording and verifying
Certificates arrive two ways: workers upload their own from their phones, or the office records them directly. Either way a certificate isn't trusted until an administrator verifies it, so the status you roster against is one a human has checked. Verified, pending and expired states are visible on the worker, on the matrix view across your whole workforce, and inside every booking check.
The 60-day window
Anything expiring inside the next 60 days shows on the dashboard, most urgent first, with one-click reminder emails to the worker. Sixty days is enough runway to rebook a course, sit it and upload the new cert before anything lapses. The renewal arrives, gets verified, and the worker never drops out of eligibility.
When something does expire
The worker isn't removed from the roster or their existing confirmed shifts; you're told, loudly. What changes is the future: no new bookings onto shifts that require the expired competency until it's renewed. That's the blocking behaviour, and it's the difference between an awkward conversation this week and a non-compliant worker on site next month.
See the compliance engine page for how requirements attach to clients, roles and shifts, or book a demo with your own matrix.