Overview
Downtime templates let you predefine common downtime scenarios so operators can log them quickly in RideOps. Templates help keep downtime reporting consistent, reduce manual entry, and improve data quality.
With this update, you can also control whether starting a downtime should create an assignment — per downtime template.
Why use downtime templates?
Operators often encounter repeatable downtime events—like weather delays or sensor trips. A downtime template pre-fills key details so downtime can be logged in seconds instead of entered manually.
Downtime templates help your team:
Maintain consistent downtime reporting
Reduce ambiguity when selecting downtime categories
Improve overall data quality and reviewability
How to create a downtime template
To create or manage downtime templates, you’ll need admin access to Configuration in the Mobaro Backend.
Navigate to downtime templates
Go to Configuration in the Mobaro Backend, then open the Downtime area to view existing downtime templates.
Click + to create a new template
Select + to create a new downtime template. This opens the downtime template builder.
Fill out the general details
On the General tab, configure what operators will see and what will be pre-filled when they log downtime:
Name: What the operator will see in RideOps (example: “Lift Stop – Low”).
Description (optional): Extra context that appears in the downtime log.
Downtime category (optional): Helps classify the event (example: Mechanical, Weather, Staffing).
Limit to (optional): Restrict the template to a specific location or location group.
Color: Helps visually differentiate the downtime type in RideOps.
Tip: Use short, consistent naming for templates (e.g., “Lift stop – high,” “Lift stop – low”) so operators can pick the right option quickly.
Configure assignment creation per downtime template
Use the Assignment configuration tab to control whether starting this downtime type should create an assignment.
Open the assignment configuration tab
In the downtime template builder, select the Assignment configuration tab.
Choose an assignment creation policy
In Assignment creation policy, pick one of the following:
Inherit: Uses your account’s global assignment creation behavior.
Create: An assignment will be created when the downtime is started (a blocking downtime).
Do not create: No assignment will be created when the downtime is started (a non-blocking downtime).
Note: If you select Create, additional assignment settings will appear so you can define exactly what gets created for that downtime type (for example: assignee user group, priority, and categories).
Recommendation: Use Create for downtime types that always require follow-up work (maintenance, safety, inspections). Use Do not create for informational or temporary downtime where no action is needed (weather delays, planned holds).
Using downtime templates in RideOps
Once templates are set up, operators will see them when starting a new downtime in RideOps. Selecting a template:
Pre-fills downtime fields
Logs the category and description automatically
Applies the template color for visibility
Frequently asked questions
Q: Can I use the same template across all locations?
A: Yes. Leave Limit to blank and the template will be available globally in RideOps.
Q: Can I create location-specific templates?
A: Yes. Use Limit to to assign a template to a single location or location group.
Q: Can templates be edited after they’re created?
A: Yes. Select the edit (pencil) icon next to an existing template to update it.
Q: Are templates required to start a downtime in RideOps?
A: No. Operators can still start downtimes manually, but templates significantly speed up the process.
Q: Can I disable assignment creation for a specific downtime type?
A: Yes. Open the template, go to Assignment configuration, then set Assignment creation policy to Do not create.
Q: How do I keep the old behavior?
A: Set Assignment creation policy to Inherit so the template follows your account’s existing (global) behavior.