A PM schedule controls when a PM task recurs. When you add a schedule to a PM template, Limble generates the PM task on the timing you set, so recurring maintenance goes out on its own without someone creating it each time.

You can add a schedule when you build a PM template or add one to an existing template later. Each template holds its own schedule, and you can turn a schedule on or off without deleting it.

There are three schedule types: time-based, usage-based, and threshold-based.

When you pick a type, the schedule shows only the fields that particular type needs, so you can set the timing that applies.

1. Time-based schedules repeat on a calendar interval. You also set the time of day the task generates and the date the schedule starts.

2. Usage-based - repeats after the asset runs a set amount of usage (e.g., run hours or cycles).

3. Threshold-based - generates a PM when an asset reading goes above a set value, below a set value, or between two values. This works well for sensor readings like temperature or vibration.

If a new reading shows that more than one usage-based or threshold-based PM was missed, Limble generates all of the missed PMs at once.

Some maintenance doesn’t follow a single cycle. You can add more than one schedule to a PM template, and each schedule generates tasks on its own timing.

For example, an inspection PM can run monthly and also have a threshold-based schedule that generates the same PM when a temperature reading goes above 90°F.

To add another schedule, open the PM template and click Create schedule. On the PM templates page, the Schedule column shows how many schedules a template has.

A schedule is either active or inactive.

Advanced options change how a schedule handles timing beyond its basic interval.

Turn them on in the Advanced options section when setting up a PM schedule.

The advanced PM schedule options only work with specific schedule types and plans.

Stack PMs generates a new PM on schedule, even if the previous PM is still open.

When stack PMs is off, Limble waits for the open PM task to be closed before generating the new task.

Most PMs don't need stacking, but it helps with high-frequency checks.

For example, if a technician checks fridge temperatures every 2 hours and misses the 2-hour check, stacking still assigns the 4-hour check.

To set it up, read Keep PMs generating while earlier PMs are open.

Reschedule on PM completion sets the next PM based on the date the last PM was completed, not the date it was planned. This keeps the time between PMs consistent, even when work is done early or late. It only works with daily schedules.

For example, a 30-day calibration PM is due April 30 but completed on April 15. The next PM is scheduled for May 15.

To set it up, read Schedule the next PM from its completion date.

Skip occurrences stops a PM from generating every set number of times, so it doesn't overlap with a larger PM that covers the same work.

For example, a quarterly PM can skip the occurrences that land on the same dates as your annual and semi-annual PMs.

By default, a usage-based PM is scheduled from the usage logged when the last PM was completed. Schedule at regular intervals generates PMs at fixed points instead, so late work doesn't push future PMs later.

For example, a car gets an oil change every 3,000 miles, and the 12,000-mile PM is completed at 12,750 miles:

You can combine a daily time-based schedule with a usage-based schedule so a PM generates on time or usage, whichever comes first.

For example, a vehicle gets an oil change every 90 days or every 3,000 miles. When a PM from either schedule is completed, both schedules reset.

This setup uses Reschedule on PM completion, so it’s available on Premium+ and Enterprise plans.