Overview
Mobaro's Certifications are only useful if the right people know, in real time, who's certified, who's expiring, and who's overdue. This article covers how to build a compliance reporting view of your Certification data — answering the questions a safety lead, ops manager, or auditor would actually ask, using the surfaces Mobaro already provides: the Certifications module, the Competency Overview Widget, Report Templates, and the API for anything ad-hoc.
Why this matters: Certifications that exist in the system but aren't reported on don't protect anyone. The point of tracking a Certification is being able to say, on demand, "every operator working this attraction this morning is currently qualified" — and to flag the cases where that isn't true before they show up to work, not after an incident.
Required access: To view all Certification data and build the dashboards described here, you need Super User access or a Role with Certifications: View (read), plus Dashboards: Modify if you'll be assembling new dashboards. Editing Certifications themselves requires Certifications: Modify.
Questions a compliance dashboard should answer
Before you build anything, lock in the questions the dashboard needs to answer. Most operations need some combination of:
Who is currently certified for X? — the simplest question, used for shift planning and audit response.
Who is expiring in the next 30 / 60 / 90 days? — the question that drives proactive renewals before they become problems.
Who has never been certified for a required Certification? — gaps in onboarding or transfers.
Who is overdue? — Certifications that have already lapsed, in active operation. The most urgent slice.
What's the compliance rate for a Location, User Group, or Role? — the rolled-up KPI for leadership reporting.
Audit trail — who certified whom, when, and via which Certification Process? Required for inspections and incident review.
Best practice: Write these questions down, with the audience for each, before you start building. A dashboard that answers six clear questions for three distinct audiences is far more useful than a single sprawling view nobody reads.
Where Certification data lives in Mobaro
Mobaro surfaces Certification data in four primary places. Each is suited to a different job:
Surface | Best for |
Certifications module | Day-to-day list view of all User Certifications — search, filter by User or Cert, manually update individual records. |
Competency Overview Widget | Visual matrix of Users vs. Competencies/Certifications. The right tool for "who in this team is certified for what" at a glance. |
Report Templates | Periodic exports — weekly compliance summaries to leadership, monthly audit packs, etc. |
Mobaro API | Custom or ad-hoc reporting — any cross-system integration, BI tool feed, or one-off compliance pull. |
The Certifications module
The Certifications page in the Mobaro Backend is the source of truth for individual records. Use it for direct lookups ("does Dana hold X?"), to manually grant or revoke a Certification, or to investigate a single User's history. It's the wrong tool for population-level questions — for those, dashboards and reports are faster.
The Competency Overview Widget
The Competency Overview Widget renders a User × Certification matrix, color-coded for compliance status. This is the single most useful surface for shift-level compliance views: a Location lead can see at a glance which of their crew is current on the required Certifications. See Competency Overview Widget for setup details.
Report Templates
For recurring compliance reporting — weekly email digests, monthly audit packs — Report Templates let you save a configured report and run it on a schedule. The right tool when the same compliance question gets asked every cycle. See Creating and using Report Templates.
The Mobaro API
For custom reporting that goes beyond what the built-in widgets and templates cover — feeding a BI tool, joining Certification data with HRIS data, building one-off compliance audits — pull the data directly via the Mobaro API. See Getting started with the Mobaro API and the Mobaro API parameter reference.
Building a compliance dashboard
Pick the right widgets
For a Certification compliance dashboard, the workhorse is the Competency Overview Widget. Add additional widgets to surface the questions you locked in earlier. Resist the urge to add widgets just because they look interesting; every widget should answer a question.
Filter aggressively
A dashboard that shows every Certification across every team is a wall of data nobody acts on. For each dashboard you build, scope the filters to a specific audience:
A Location lead dashboard filters to that Location's Users and the Certifications relevant to that Location.
A safety leadership dashboard rolls up across Locations to compliance rates, with drill-down available.
A compliance/audit dashboard surfaces gaps and overdue records in a list, sorted by severity.
Share with the right audience
Once a dashboard is built, share it with the team who needs it (and only that team). Use Dashboard Templates if you have many similar audiences (one per Location, for example) — see How to set up dashboard templates. For periodic delivery to people who won't open the dashboard themselves, configure a Report Template that emails the export.
Note: Dashboards reflect live data — when a Certification is granted or expires, the dashboard updates. Reports are snapshots at the moment the export runs. Use dashboards for in-the-moment decisions, reports for cycle-driven reviews.
Common reporting patterns
Pre-shift compliance check
Audience: Location leads, opening managers.
Question: Is everyone scheduled to work this attraction today currently certified?
Setup: Competency Overview Widget filtered to the Location and the day's User Group, with required Certifications listed. Pin to a shared dashboard or display in the supervisor's office before park open.
Hire-cohort tracking
Audience: Onboarding leads, training managers.
Question: Of the Users hired in the last 30 days, who's completed which required Certifications?
Setup: Filter to recently created Users and check Certification status against a defined "required for new hires" list. Best as an API-driven export joined with HR start-date data, since Mobaro doesn't natively segment by hire-cohort.
Best practices
Build for questions, not data
A dashboard is a tool for answering specific questions. Define the questions, then design the visuals. The reverse — picking pretty widgets first and figuring out what they show later — produces dashboards nobody trusts.
One audience per dashboard
A single dashboard that tries to serve Location leads, leadership, and compliance officers ends up serving none of them well. Build separate dashboards for each audience, even if they share underlying data.
Make expiration a leading indicator, not a lagging one
"Who's expired" is a problem report. "Who's expiring in 60 days" is an action item. Build your dashboards around the leading indicator — expiring-soon — and the lagging indicator becomes the exception, not the norm.
Best practice: Pair every dashboard with a clear owner. The owner is responsible for keeping the filters current as Locations, User Groups, and Certifications evolve. An ownerless dashboard slowly drifts out of date — the data is right, but the filters are wrong, and trust erodes.
Anti-patterns to avoid
Watch out for these common pitfalls in compliance reporting:
The "everything dashboard" — every widget, every filter, every Certification on one screen. Nobody will use it.
Reporting only on lapsed Certifications — by the time you're reporting expiries, you're behind. Lead with expiring-soon, not expired.
Manual one-off pulls as the only path — if you're answering the same compliance question every week, that's a Report Template, not a manual export.
Confusing visibility with action — a dashboard sitting on a TV in the break room isn't compliance reporting; it's wallpaper. Pair the dashboard with a person and a process for acting on what it shows.
Skipping the audit trail — when an inspector asks "how do you know that operator was certified that day," you need a date-stamped record. Don't rely on the live dashboard for historical questions; archive periodic reports.
See also
How to create a Certification Process — for how Certifications get earned in the first place.
Gaining and managing Certifications — for the User-side flow and admin overrides.
How does Mobaro manage the visibility and retention of user certifications? — for the data lifecycle behind compliance reporting.
Competency Overview Widget — the workhorse widget for compliance dashboards.
Creating and using Report Templates — for recurring exports and scheduled delivery.
How to use the dashboard — dashboard fundamentals.
How to set up dashboard templates — for replicating dashboards across many audiences (e.g., one per Location).
Getting started with the Mobaro API — for custom or BI-tool reporting.
Frequently asked questions
Q: Can a single dashboard show compliance across multiple Locations?
A: Yes. For very different audiences (one Location lead vs. a regional director), build separate dashboards or use Dashboard Templates rather than overloading a single view.
Q: Can I show only the Users who actually work at a given Location?
A: Yes — filter the Competency Overview Widget by Group membership. For Users who work at multiple Locations, decide whether you want them to appear on each Location's dashboard or only their primary; configure the filter accordingly.
Q: What happens to historical Certifications when a User leaves the organization?
A: That depends on your retention configuration. See How does Mobaro manage the visibility and retention of user certifications?. For audit purposes, archive a Report Template export periodically rather than relying on the live system to retain departed-User data indefinitely.
Q: Can compliance dashboards drive notifications when something expires?
A: Dashboards themselves are visual — they don't push notifications. Use Notification Rules to push proactive alerts (e.g., "Certification X expires in 30 days for User Y") in parallel with the visual dashboard. See your Notifications collection for setup.