Overview
Downtime templates let you predefine common downtime scenarios so operators can log them in seconds on RideOps, instead of typing the details each time. Templates keep downtime reporting consistent and improve data quality — and you can control, per template, whether starting that downtime creates an Assignment (making it blocking or non-blocking).
Users must be Super Users or have Organization: Administrate to create and manage downtime templates.
Why this matters: Operators hit the same downtime events over and over — weather delays, sensor trips, lift stops. A template makes those one tap to log with the right category, so downtime gets recorded consistently in the moment instead of written up vaguely after the fact.
Create a downtime template
Open downtime templates
In the Mobaro Backend, go to Configuration > Downtime to view existing templates, then click + to open the template builder.
Fill in the general details
On the General tab, set what operators see and what gets pre-filled:
Name — what the operator sees in RideOps (e.g. Lift Stop – Low).
Description (optional) — extra context that appears in the downtime log.
Downtime category (optional) — classifies the event (e.g. Mechanical, Weather, Staffing).
Limit to (optional) — restrict the template to a specific Location or Location Group.
Color — visually differentiates the downtime type in RideOps.
Best practice: Use short, consistent names so operators can pick the right option fast — e.g. Lift stop – high, Lift stop – low.
Set the Assignment creation policy
On the Assignment configuration tab, choose how this downtime type handles work:
Inherit — follows your account's global Assignment-creation setting.
Create — an Assignment is created when the downtime starts (a blocking downtime).
Do not create — no Assignment (a non-blocking downtime).
Note: Choosing Create reveals extra settings — assignee User Group, priority, and categories — so you can define exactly what gets created. The global default is set in Configuration > Downtime; see Getting started with Downtime.
Best practice: Use Create for downtime that always needs follow-up (maintenance, safety, inspections) and Do not create for informational or temporary holds (weather, planned pauses). For the blocking vs non-blocking behaviour on the floor, see Managing Downtime and uptime from the mobile app.
Using downtime templates in RideOps
Once set up, operators see templates when starting a new downtime in RideOps. Selecting one pre-fills the fields, logs the category and description automatically, and applies the template color for visibility. Operators can still start downtimes manually without a template.
Frequently asked questions
Q: Can I use the same template across all Locations?
A: Yes. Leave Limit to blank and it's available globally in RideOps.
Q: Can I make location-specific templates?
A: Yes — use Limit to to scope a template to a Location or Location Group.
Q: Can I disable Assignment creation for a specific downtime type?
A: Yes. On the template's Assignment configuration tab, set the policy to Do not create.
Q: How do I keep my account's existing behaviour?
A: Set the policy to Inherit so the template follows your global setting.
Q: Are templates required to start a downtime?
A: No — operators can always start one manually. Templates just make it faster and more consistent.