Overview
A Certification that lapses unnoticed pulls a qualified person out of a RideOps position or blocks a Checklist mid-shift. The fix is to make expiry a leading indicator — surfaced and acted on weeks ahead, not discovered after the fact. Mobaro gives you four complementary levers for this. This article covers how to combine them.
Why this matters: When a Certification expires, the User immediately loses the linked Competency and any access it gated. Catching "expiring in 30 days" is an action item; catching "expired" is already a problem. Build your process around the leading indicator.
The four levers
Lever | What it does |
Automatic renewal reactivation | A Certification flagged Mark as due for renewal reactivates its Certification Process on the renewal date, so the User can simply retake it. |
Competency Overview widget | A live Dashboard matrix of Users vs Competencies, color-coded by status — the at-a-glance view of who's expiring. |
Certification Center | Each User sees their own upcoming renewals in the mobile app. |
Build renewal into the Certification
The most reliable lever is the one that needs no monitoring: when you create or edit a Certification (or set it on a Certification Process), enable Mark as due for renewal and set a relative expiration. On the renewal date, the associated Certification Process reactivates automatically in the User's Certification Center, prompting them to retake it before the Certification lapses. See Gaining and managing Certifications.
Best practice: Use relative expiration (e.g. 1 year from completion) on recurring Certification Processes. Renewal cadence is then baked into each User's own anniversary rather than a shared calendar deadline.
Watch the Competency Overview widget
Add the Competency Overview Widget to a Dashboard for the team or Location you're responsible for. It renders a User × Competency matrix color-coded by status, so a glance tells you who's current, who's expiring soon, and who's lapsed. See Competency Overview Widget.
Best practice: Pair the widget with an owner — a person who reviews it on a set cadence (weekly is common) and kicks off renewals. A widget nobody owns drifts into wallpaper.
Let Users see their own renewals
Each User sees their upcoming renewals in the Certification Center in the mobile app, where anything expiring soon is flagged. Encourage staff to check it and complete reactivated Processes early. See Using the Certification Center in the mobile app.
Frequently asked questions
Q: Can Mobaro send an alert the moment a Certification is about to expire?
A: The proactive, pushed mechanism is a scheduled report of expiring Certifications emailed via a Notification Rule, plus automatic renewal reactivation. Use those rather than expecting a per-Certification countdown alert.
Q: What's the least-effort way to prevent lapses?
A: Enable Mark as due for renewal with relative expiration on your Certification Processes. The Process reactivates itself on each User's renewal date with no manual monitoring.
Q: What happens if a Certification lapses anyway?
A: The User loses the Competency and any access it gated until it's renewed — by completing the Process again or an admin re-issuing it. See Gaining and managing Certifications.
Q: Which window should I report on — 30, 60, or 90 days?
A: Match it to how long renewal takes. If retraining needs scheduling weeks ahead, report on 60–90 days; for a quick self-assessment refresh, 30 is often enough.