Maintenance program
Preventive maintenance schedule builder
Paste an asset list, set how often each one needs servicing, and get a dated schedule plus the assets nobody has scheduled at all.
This browser is not saving anything, so your list will be lost when you leave. Private browsing usually causes this.
Paste your assets
One asset per line, copied straight from a spreadsheet or an export. Columns are read in order: name, location, category, cadence. Only the name is required, and a header row is ignored.
Assets
| Asset | Location | Category | How often | Last done | Services | Remove |
|---|
Schedule
Building a PM schedule that survives contact with the floor
Most PM schedules fail for one of two reasons. Either everything was set to the same cadence because that was quicker than thinking about it, or the schedule was built once and never adjusted as assets proved themselves reliable or otherwise.
Start with what the asset costs you when it stops
Cadence should follow consequence, not age or purchase price. An asset with a spare on the shelf and an hour to swap it can run closer to failure than one with a four-week lead time, even if they are identical machines. Work out which assets you cannot afford to lose, schedule those properly, and accept that some of the rest are run-to-failure whether or not anyone has written that down.
Find the assets nobody scheduled
The coverage gap list is the part worth acting on first. An asset with no PM does not appear in a PM compliance figure, because it is never late. That means a plant can report high compliance while a meaningful share of its equipment sits outside the program entirely, and nobody notices until one of them stops.
Watch the month the work lands in
The services-per-month row usually shows a spike wherever the start date was set, because everything anchored to the same day comes due together. Staggering the start of a few large groups spreads the same work across the year without changing a single cadence.
Frequently asked questions
How often should a PM run?
Start from the manufacturer interval, then move it based on what you see. If an asset keeps failing between services the interval is too long; if inspections keep finding nothing wrong, it is too short and you are spending labor to confirm good news.
Criticality matters more than age. A pump with a spare sitting on the shelf can run to failure. The one with no spare and a four-week lead time cannot, whatever the nameplate says.
What counts as an uncovered asset?
Anything with no PM scheduled against it at all. These are worth finding because they are invisible in a PM compliance figure: an asset with no PM is not late, it is absent, so the number looks fine while the risk sits outside it.
Set an asset to Not scheduled here and it shows in the coverage gap list rather than being dropped.
Why is my monthly PM not every 30 days?
Because a month is not 30 days, and treating it as one adds roughly an extra service a year. A quarterly PM anchored on 31 January falls on 30 April here, not on day 121. Cadences under a month are counted in days; everything from monthly up moves by calendar month and clamps to the end of short ones.
Does this connect to my CMMS?
No. It runs entirely in your browser and has no account. Paste an asset list from any spreadsheet or export, build the schedule, and take it away as CSV.
Inside UpKeep, the PM Coverage Planner does this against your live asset register and writes the PM plans back, so the schedule you agree is the schedule that runs.
Can I use this to level out workload?
To see it, yes. The services-per-month row shows where the schedule stacks up, which is usually a spike in whichever month everyone picked as a start date. Staggering the start dates of a few large groups flattens most of it.
Run this against your real asset register
The PM Coverage Planner in UpKeep does this on your live assets: it finds what has no PM, builds the plans with cadence and due times, and writes them back so the schedule you agree is the one that runs.