Overview
A Certification Process automates the lifecycle of a Competency: it ties a training Checklist to a Competency, optionally requires reviewer validation, awards the Competency on completion, and sets the expiration. Once configured, you assign it to Users (or User Groups), and Mobaro tracks each User's progress and handles the Competency award without manual entry. This article covers the full setup: creating the Process, configuring assignees and reviewers, setting expiration rules, and monitoring progress.
Users must be Super Users or have the following Role to create and manage Certification Processes:
Competencies: Administrate
Why this matters: Manually awarding Certifications doesn't scale. For any credential awarded more than once — annual training, periodic re-certifications, role onboarding — a Certification Process is the right tool. The Process tracks award dates, expiration, and renewal automatically, and removes the risk of someone forgetting to add a Certification when training is complete. For a broader overview of how Competencies, Certifications, and Certification Processes fit together, see Utilizing Competencies.
How a Certification Process works
A Certification Process is built from these components:
Component | What it does |
Awarded Competency | The Competency granted to a User on completion. |
Checklist | The training or assessment Checklist Assignees must complete. |
Required Competencies (prerequisites) | Competencies a User must already hold to be eligible for the Process. Optional. |
Assignees | The Users or User Groups who can run the Process. |
Reviewers | Users who validate completed Checklists before the Competency is awarded. Required when |
Competency Expiration | When the awarded Competency expires — never, a fixed date, or relative to completion. |
End-to-end, the runtime flow runs like this:
An Assignee starts the Process (if they hold any prerequisite Competencies).
They complete the linked Checklist.
If
Require Validationis ON, a Reviewer reviews the completed Checklist and approves or rejects it.On approval (or on completion, if validation isn't required), the Awarded Competency is granted to the User with the configured expiration.
The User now holds the Competency for any gating uses — Schedules with Required Competencies, RideOps Operator or Attendant Positions, etc.
Creating a Certification Process
1. Open Certification Processes
In the Mobaro Backend, expand Competencies in the navigation and click Certification Processes.
2. Start a new Certification Process
Click + Create.
3. Configure General Settings
In the editor, fill in the following fields:
Name— A descriptive name (e.g., Loader Training).Awarded Competency— The Competency the Process grants on completion.Checklist— The training Checklist Assignees must complete.Required Competencies(optional) — Any prerequisite Competencies a User must already hold to be eligible.
Note: Required Competencies on a Process are prerequisites — a User must hold them to start. This is different from a Schedule's Required Competencies, which gate access to that Schedule's Checklists. The fields are named the same but apply at different layers: Process prerequisites are before the Process runs; Schedule requirements are at execution time.
Heads-up: Users must hold active prerequisite Competencies to start a Certification Process. Expired or deleted Competencies don't qualify.
4. Set Assignees and Reviewers
Under Assignees & Reviewers, add the Users or User Groups who can run the Process. Add one or more Reviewers to validate completed Certifications. Optionally toggle on Require Validation to require a Reviewer's signoff before the Competency is awarded.
Best practice: For safety-critical certifications, leave Require Validation ON and assign Reviewers who are domain experts — senior trainers, supervisors, or compliance leads. Without validation, completion of the Checklist alone awards the Competency, with no second pair of eyes on the work.
5. Set Competency Expiration
In the Competency Expiration section, choose how long the awarded Competency stays valid:
Never — The Competency does not expire.
At an Exact Date — A fixed expiration date (e.g., December 31, 2027). Useful for fixed-term regulatory certifications that all holders share a deadline for.
Relative to Process Completion — A duration measured from the date the User completes the Process (e.g., 1 year). Most common for recurring training where each User's expiration tracks their personal completion date.
Best practice: Use Relative to Process Completion for recurring training. It builds renewal cadence into the Competency itself, so each User's expiration is tied to when they actually completed the Process — not a calendar-wide deadline that may not align with their personal training schedule.
6. Save
Click Save. The Process appears in the Certification Processes list, ready for Assignees to run.
Monitoring progress
Open the Certification Processes list to see every Process and the status of each Assignee. The progress view groups Assignees into three categories:
Status | Meaning | What to do |
Awaiting Completion | The Assignee is eligible but hasn't completed the Process yet. | Surface for follow-up — notifications, in-person reminders, or training scheduling. |
Completed | The Assignee has completed the Process and (if required) been validated by a Reviewer. The Competency is now awarded. | No action — the User holds the Competency until expiration. |
Existing Certification | The Assignee already holds the Awarded Competency through some other Certification (manual entry or another Process) and doesn't need to run this one. | No action — the User counts as held. No duplicate award is issued. |
Best practice: For recurring training programs, build a Dashboard widget filtered to Certifications expiring in the next 30 days for the Awarded Competency. Reviewing it weekly lets you re-assign the Process to Users approaching expiration before their Certification lapses.
Example: configuring Loader Training
Scenario
You want to set up a Certification Process that awards the Loader Competency to new ride Loaders after they complete training, with a 1-year expiration. This is the configuration side of the worked example in Utilizing Competencies — building the Process that drives Maria's onboarding experience.
Setup
The Loader Competency exists.
A Loader Training Checklist exists — training content plus signoff questions.
A Senior Loaders User Group exists, configured as Reviewers.
A New Hires User Group exists, configured as Assignees.
Result
You create the Process with these settings:
Name: Loader TrainingAwarded Competency: LoaderChecklist: Loader Training ChecklistRequired Competencies: (none — no prerequisites for a new hire)Assignees: New Hires User Group
Reviewers: Senior Loaders User Group
Require Validation: ONCompetency Expiration: Relative to Process Completion, 1 year
Outcome:
Maria (in New Hires) starts the Loader Training Process and completes the Checklist with her trainer.
A Senior Loader reviews and approves the Checklist.
The Loader Competency is awarded automatically with a 1-year expiration.
Eleven months later, Maria's Certification appears in the renewal Dashboard. The training team re-assigns the Process to her, and she completes a refresher to renew before lapse.
Frequently asked questions
Q: What's the difference between Required Competencies on a Process and on a Schedule?
A: Same field name, different layer. A Process's Required Competencies are prerequisites — a User must hold them to start the Process. A Schedule's Required Competencies are gating — a User must hold them (and the Schedule must have Restrict access ON) to act on Checklists from that Schedule.
Q: What happens if a Reviewer rejects a completed Checklist?
A: The Process status stays in Awaiting Completion for that Assignee. They can re-run the Process — typically after addressing the Reviewer's feedback. The Competency isn't awarded until a Reviewer approves a completed Checklist.
Q: Can the same User be an Assignee and a Reviewer on the same Process?
A: Technically possible, but not recommended — it defeats the purpose of validation. Best practice is to keep these roles separate so Reviewers act as a genuine second pair of eyes.
Q: If I edit the Process settings later, do existing Certifications change?
A: Existing Certifications keep their original expiration and Awarded Competency. Edits only affect new completions going forward.
Q: Can I award the same Competency through more than one Certification Process?
A: Yes. A Competency can be awarded by any number of Processes — useful when there are multiple paths to the same qualification (e.g., direct training versus a transfer credential from another park).
Q: How do I stop using a Certification Process?
A: Open the Process from the list and edit it. Removing all Assignees stops new runs. Existing Certifications awarded by the Process aren't affected — they keep their expiration and stay valid until they expire normally.