Overview
Redlist route templates (also called work order templates) come in three types: Fixed, Dynamic, and Manual. Each type controls how work orders are generated for technicians. This article explains what each type does and how to choose the right one for your situation.
Accessing Route Setup/Templates
From the navigation, click Lubrication Routes, then click Route Setup/Templates.
Understanding Fixed Routes
A Fixed Route generates work orders on a set recurring schedule. All tasks on the route are included in every work order — the route's schedule controls when work orders generate.
When to use Fixed:
You want work orders to generate automatically on a predictable schedule
You have a fixed set of tasks that appear on every work order generated from this template
You need task due dates to match the work order's due date
You have an ERP integration that requires a completed work order with all tasks included
How Fixed routes work:
When the last task on a work order is completed, the work order closes
The next work order generates based on the Work Order Generation settings configured on the route
All tasks are included every time — individual task frequencies do not filter tasks in or out of a Fixed route
Task due dates on the work order match the work order's due date
Frequency settings (configured on the route):
The Frequency section controls how often work orders generate and when the next one is due. It has two parts:
Frequency — Set how often the work order generates (every X Days, Weeks, Months, or Years). Enable Specific Day to pin generation to a particular day of the week or month. Enable Additional Frequency to also trigger generation based on Miles/km or Hours.
Work Order Generation — Two settings that control next work order behavior:
Calculate next work order due date from — Choose whether the next due date is calculated from the last work order's due date or the last work order's completed date.
Last work order's due date — Use when the schedule itself is what matters. If a route is due every Monday and technicians finish it on Wednesday, the next one is still due the following Monday. The calendar never drifts. Best for routes with regulatory, contractual, or compliance deadlines where consistency of interval is required.
Last work order's completed date — Use when the clock genuinely resets after completion. If an oil change is performed today, the 90-day interval starts today — not from when it was originally scheduled. Best for condition-based maintenance where early or late completion changes when the work is next needed.
Create a new work order when — Choose one of three options:
Create a new work order only when the current work order is completed — The next work order does not generate until all tasks on the current one are finished.
Create a new work order automatically after the current work order is past due and never ignore previous work orders — Generates a new work order on schedule when work orders are being completed on time. If a work order goes past due without being completed, the next one still generates and the previous one stays open — it is never automatically ignored or skipped.
Create a new work order automatically after the current work order is past due. Ignore all work orders before the current work order that do not have any reactive tasks — Same as above, but clears out older work orders that have no reactive tasks.
Understanding Dynamic Routes
A Dynamic Route runs continuously and pulls in tasks based on each task's individual due date. Instead of all tasks appearing every time, tasks enter and exit the route as they come due. Tasks can also appear during their compliance window — the period before their due date when early completion is allowed.
When to use Dynamic:
You have the same task on multiple routes and don't want technicians completing it more than once in the same period — Dynamic tracks when each task was last completed and won't show it again until it's due
You want task schedules driven by actual completion dates, not work order dates — if a task is completed early, the next due date shifts accordingly rather than staying fixed to the calendar
You want to prevent technicians from over-maintaining equipment — Dynamic routes ensure no task is completed before it is actually needed
You want to give your team the option to get ahead of their work — the compliance window brings tasks into view before they are due, so technicians can be aware of what's coming up
How Dynamic routes work:
Each task drives its own schedule — tasks show up on the work order when their individual due date arrives, based on each task's frequency setting
Technicians only ever see tasks that are currently due or within their compliance window
The work order stays open continuously — tasks enter and exit as they come due
Understanding Manual Routes
A Manual Route stays completely inactive until a user with the appropriate permissions deliberately generates it. It never creates a work order on its own and is never visible to technicians until triggered.
When to use Manual:
Tasks can only be performed during a planned shutdown or scheduled downtime
You want full control over exactly when technicians see and complete this work
How Manual routes work:
No work order is created until a user clicks Generate from the route list
The route template stays inactive between generations — no overdue flags, not visible to technicians
Each time Generate is triggered, the user sets the due date for that specific work order
Understanding Routes Generated from Programs
If you need to run the same maintenance routine across a large number of assets, a PM Program saves you from building each route one by one.
You set up your maintenance tasks once inside the program. Then you add your assets. Redlist automatically creates a dedicated set of work order templates for each asset based on what you built — so every asset gets its own maintenance schedule without you having to configure each one manually.
When you need to update the maintenance routine, make the change at the program level and it applies to all linked routes automatically — no need to update each one individually.
Routes managed by a PM Program display a Linked to Program badge on their profile. If a specific asset needs a different configuration, you can unlink it from the program — it will stop receiving updates and you can make whatever changes that asset requires.
When to generate routes from a Program:
You have the same maintenance routine that applies to many assets and don't want to build each route individually
You want updates to the maintenance routine to automatically apply across all assets at once
How routes generated from Programs work:
You set up the maintenance structure once inside the program — sections, components, tasks, and work order templates
You add assets to the program and Redlist creates a dedicated set of work order templates for each asset based on your configuration
Changes made at the program level apply to all linked routes automatically
If a specific asset needs a different configuration, unlink it — it keeps its current settings and stops receiving program updates
How to Create a Fixed Route
From Route Setup/Templates, click Create.
Under Route Type, select Fixed.
Enter a Name for the route (required).
Select a Board (required).
Optionally set Last Completed On, Next Due, Asset, Region, and Notes.
In the Frequency section, configure how often the work order generates and how the next due date is calculated.
Click Save.
How to Create a Dynamic Route
From Route Setup/Templates, click Create.
Under Route Type, select Dynamic.
Enter a Name for the route (required).
Select a Board (required).
Optionally set Region and Notes.
Click Save.
NOTE: Last Completed On, Next Due, and Asset are not available on Dynamic routes. The Activate, Reactivate, and Print buttons on the route profile are also not applicable to Dynamic routes.
How to Create a Manual Route
From Route Setup/Templates, click Create.
Under Route Type, select Manual.
Enter a Name for the route (required).
Select a Board (required).
Optionally set Last Completed On, Next Due, Asset, Region, and Notes.
Click Save.
NOTE: The Activate, Reactivate, and Print buttons on the route profile are not applicable to Manual routes. Use the Generate button from the route list instead.
How to Generate a Manual Route
Manual routes do not generate work orders automatically. Generation must be triggered manually each time the work should run.
From Route Setup/Templates, locate the manual route in the table.
In the Actions column, click Generate.
In the modal, set a Due Date for the work order.
Click Generate.
If a work order from this route is already open, the modal shows the existing work order name and current dates. Update the New Due Date and New Planned Start if needed, then click Save Due Date.
How to Change the Route Type on an Existing Route
From Route Setup/Templates, open the route.
On the General tab, locate the Route Type field.
Select the new route type.
Click Save.
Use Cases
Weekly conveyor lubrication — Fixed
A maintenance team lubricates conveyor bearings every Monday. The tasks are the same every week. A Fixed weekly route is created. Each Monday a work order generates with all tasks included. When the last task is completed, the work order closes and the next one generates according to the route's frequency settings.
Preventing repeated work across routes — Dynamic
A technician completes a monthly task on Monday as part of a monthly route. On Wednesday, a quarterly route generates that includes the same task. Because it is a Dynamic route, the task does not appear — it was just completed and is not due again. Without Dynamic routes, the task would show up on both work orders regardless of when it was last done, leading technicians to repeat work that didn't need to be done.
Mixed-frequency equipment program — Dynamic
The same pump requires a weekly oil check, a monthly filter inspection, and a quarterly oil change. One Dynamic route is created covering the pump. Each time technicians open the route, only the tasks currently due or within their compliance window appear. The technician completes everything in one pass without visiting the pump three separate times.
Planned shutdown maintenance — Manual
A facility shuts down twice a year for scheduled maintenance. During these windows, technicians perform oil changes and component repacks that cannot be done on running equipment. A Manual route is created with all shutdown tasks. The route is invisible during normal operations — no overdue flags, no unwanted work orders. When a shutdown begins, a user clicks Generate, sets the due date, and technicians see the work order immediately.
Troubleshooting
Issue: The Route Type field is not visible on the creation form.
Solution: The Route Type field appears at the top of the creation form, above the General fields. If you are editing an existing route, Route Type is found on the General tab.
Issue: The Activate, Reactivate, and Print buttons are disabled on a route.
Solution: These buttons are not applicable to Dynamic or Manual routes. For Dynamic routes, work orders generate automatically as tasks come due. For Manual routes, use the Generate button from the route list. If the route is Fixed and the buttons are still disabled, check whether the page is still loading.
Issue: A Generate button does not appear for a route in the Actions column.
Solution: The Generate button only appears for Manual routes. Fixed and Dynamic routes generate work orders automatically and do not have this button. Confirm the route type by opening the route and checking the General tab.
Issue: A program route is showing a Linked to Program badge and cannot be edited independently.
Solution: Program routes receive updates from their linked PM Program. To edit the route independently, click Unlink from Program on the route profile. To edit the source template instead, click Edit Program.
Summary
Fixed, Dynamic, and Manual routes each control how and when work orders are generated. Fixed routes run on a set schedule with the same tasks every time. Dynamic routes run continuously, pulling in tasks as they come due. Manual routes stay inactive until triggered — ideal for shutdowns and downtime work that should never appear during normal operations.