A Certification Process links a training Checklist to a Competency, then awards that Competency automatically when a User finishes, with optional reviewer sign-off and a built-in expiration. Set it up once, assign it to Users, and Mobaro tracks every User's progress for you.
You'll need to be a Super User or have Competencies: Administrate to create and manage Certification Processes.
How it works
Once a Process is running, each Assignee moves through the same path:
An Assignee starts the Process, if they hold any required prerequisite Competencies.
They complete the linked Checklist.
If
Require Validationis on, a Reviewer approves or rejects the completed Checklist.On approval, or on completion if validation isn't required, the Competency is awarded with its expiration.
The User now holds the Competency wherever it's required: gated Schedules, RideOps Operator and Attendant Positions, and more.
For the bigger picture of how Competencies, Certifications, and Processes fit together, see Utilizing Competencies.
Create a Certification Process
In the Mobaro Backend, expand Competencies, click Certification Processes, then click + Create.
Give the Process a Name (e.g. Loader Training), then choose the Awarded Competency and the training Checklist. Add Required Competencies only if a User must already hold something to be eligible.
Note: A Process's Required Competencies are prerequisites a User needs to start. That's different from a Schedule's Required Competencies, which gate access at execution time. Same name, different layer, and only active Competencies count.
Under Assignees & Reviewers, add the Users or User Groups who can run the Process, then add one or more Reviewers. Toggle Require Validation on if a Reviewer must sign off before the Competency is awarded.
Best practice: For safety-critical certifications, keep Require Validation on and make domain experts the Reviewers. Without it, finishing the Checklist alone awards the Competency, with no second pair of eyes.
Under Competency Expiration, choose Never, At an exact date (a shared deadline for everyone), or Relative to Process completion (a duration from each User's own completion date).
Best practice: Use Relative to Process completion for recurring training, so each User's renewal clock starts when they actually finish.
Click Save. The Process joins the Certification Processes list, ready to assign.
Monitor progress
The Certification Processes list shows every Process and where each Assignee stands:
Status | Meaning | What to do |
Awaiting completion | Eligible, but hasn't finished yet. | Follow up with reminders or scheduled training. |
Completed | Finished and, if required, validated. Competency awarded. | Nothing. Held until expiration. |
Existing Certification | Already holds the Competency another way. | Nothing. No duplicate is issued. |
Best practice: Build a Dashboard widget for Certifications and check it weekly to check for due for renewal or expired certifications.
Want to see this end to end? Utilizing Competencies walks through the same Loader Training setup, from a new hire's first day through renewal.
Frequently asked questions
Process prerequisites vs. Schedule requirements, what's the difference?
A Process's Required Competencies are prerequisites to start. A Schedule's Required Competencies gate access to that Schedule's Checklists at execution time (with Restrict access on). Same field name, different layer.
What happens if a Reviewer rejects a Checklist?
The Assignee stays in Awaiting completion and can re-run the Process after addressing feedback. The Competency isn't awarded until a Reviewer approves.
If I edit the Process later, do existing Certifications change?
No. Existing Certifications keep their original expiration and Competency. Edits only affect new completions.
How do I stop using a Process?
Edit it and remove all Assignees, which stops new runs. Certifications already awarded keep their expiration and stay valid until they lapse normally.