A preventive maintenance schedule template for a small shop (with a worked example)
Most small shops do not skip preventive maintenance because they do not believe in it. They skip it because the schedule lives in someone's head, or in a spreadsheet nobody opens until a machine is already down. A good PM schedule fixes that by turning "we should grease that conveyor sometime" into a dated, owned, repeatable task. This guide gives you a copyable preventive maintenance schedule template, shows you how to set the intervals — the part everyone gets wrong — and walks the whole thing through a worked example for a 12-machine plant.
What a PM schedule actually is
A preventive maintenance schedule is a list of recurring maintenance tasks, each tied to a machine, an interval, and the date it is next due. That is the whole idea. It is not a maintenance history, and it is not a work-order system — it is the forward-looking plan that tells you what to do this week before anything breaks.
The schedule answers three questions at a glance: what needs doing, on which machine, and by when. If your current "schedule" cannot answer "what is due this week" without someone thinking hard, it is a wish list, not a schedule. The template below is built to answer that question in one sort.
The columns your template needs
Open a new workbook and make one sheet called PM Schedule. Every PM task is one row — a single machine can have several rows, one per task at its own interval. Resist the urge to add columns you will not maintain. These six are the working template:
Make the Next due cell a formula, not a hand-typed date. If Last done is in column D and the interval in days is in column C, then =D2+C2 keeps the schedule honest — every time someone updates the last-done date, the next-due date moves itself. Typed due dates drift the moment a PM gets done early or late, and a schedule you have to re-key by hand is a schedule that quietly goes stale.
Two optional columns earn their keep once you have more than a few machines: an Owner (who is responsible, by name or role) and Parts (the filter, belt, or consumable the task needs, so you can stage it beforehand). Add them when the basic six are running cleanly, not before.
How to set the interval — the part everyone gets wrong
The interval is where PM schedules live or die. Set it too long and you are running to failure with extra paperwork. Set it too short and techs start skipping PMs because half of them are not really due, which trains everyone to ignore the schedule. There are three honest ways to pick one:
Where to get the first number: start with the manufacturer's recommendation if you have the manual, then adjust from your own failure history. If a machine keeps breaking before its PM comes due, shorten the interval. If PMs consistently find nothing wrong, lengthen it. That feedback loop is why the schedule and your downtime history belong next to each other — a recurring breakdown in the log is the clearest signal that an interval is wrong. For how the two records divide the work, see maintenance log vs downtime log.
- Time-based. Every N days or weeks, regardless of use. Right for anything that degrades on the calendar — rust, rubber aging, lubricant breakdown, annual inspections. Simple to track, so it is where most shops start.
- Runtime-based. Every N run-hours or N cycles. Right for wear that tracks usage, not time — a press run two shifts a day needs its hydraulic service sooner than one run two days a week. Requires that you capture run-hours, from the HMI, a cycle counter, or your production log.
- Condition-based. When a measured signal crosses a threshold — vibration, temperature, oil analysis, a pressure drop across a filter. The most precise, but it needs sensors or routine checks, so reserve it for your few critical, expensive machines.
A worked example: a 12-machine stamping and machining shop
Here is a real-shaped slice of a PM schedule for a shop running 12 machines across stamping, machining, and plant utilities. Each machine has one to four PM tasks; this is the subset due soonest, as of 2026-11-16, sorted by next-due date:
The value is in the Next due column doing the planning for you. Filter the sheet to the next seven days and you get this week's list: Press 1, the robot weld cell, CNC mill 2, and Conveyor A, all due on or before 2026-11-23 — 3.0 hours of planned work. That is a number a supervisor can actually fit around production — not "do all the PM," which never happens, but "slot three hours in across the week."
Add up the schedule the same way and you get the shop's standing PM load. Divide each task's hours by its interval in days, multiply by seven, and sum the column. For the eight tasks above, that comes to about 2.1 hours a week: 1.25 hours from the two weekly tasks, about 0.4 from the two monthly tasks, and about 0.5 from the four longer-interval tasks. Run the same sum over every row on your own sheet. Knowing that number is the point: a weekly PM load is a staffing decision you can make on purpose, instead of discovering it as unplanned downtime at the worst possible moment. The whole case for that trade — plan a little now or pay a lot later — runs through the real cost of a breakdown; if you want to put a dollar figure on it, see how to calculate the cost of unplanned downtime.
Reading the schedule every week
A PM schedule is a weekly habit, not a quarterly document. The routine that keeps it alive is short:
That last point is the honest feedback loop. If the overdue list keeps growing, you have told the schedule to do more maintenance than you have hands for — fix it by lengthening non-critical intervals or adding capacity, not by ignoring the red.
- Monday, sort by next due. Pull the tasks due in the next seven days. That is your week's PM plan, with hours attached.
- Stage the parts. Anything with a filter, belt, or consumable in the Parts column gets pulled from stores before the tech walks to the machine. Half of "we ran out of time" is actually "we ran out to find the part."
- Update last-done the day it is finished. The moment a PM is complete, set its Last done to today. The formula moves Next due forward on its own, and the task drops off this week's list and reappears when it is due again.
- Watch for overdue. Any row where Next due is in the past is a missed PM. A short list of overdue items is normal; a long one means your intervals are too aggressive or you are understaffed for the load you have set.
When the spreadsheet stops being enough
For a dozen machines and one person who owns the file, this template is genuinely good. It starts to strain in predictable places. The due-date formulas depend on every person updating the right cell, and techs on the floor rarely have a laptop open mid-shift, so last-done dates drift to end of day or end of week. Runtime-based intervals mean nothing unless someone keys in run-hours. And the schedule sits in its own tab, disconnected from the downtime log — so when a machine breaks, nobody checks whether a PM was overdue, which is exactly the question worth asking. If you are tracking stops in a spreadsheet too, the free downtime tracking Excel template is the companion to this one.
When you hit those walls, the method stays the same and the tool changes. HelpFab's preventive maintenance keeps one PM per machine and task, and sorts them into a live queue — Breakdowns, Overdue, Available, and Coming up — that techs work from a phone on the floor. Each PM becomes available before it is due (the default early-start window is 25% of the interval, and you can change it), so a tech can knock it out while the machine is already stopped for something else. The next due date then counts from the day the work was done. You can also set a downtime type to create a maintenance request when an operator logs it, so a breakdown from the downtime log reaches the queue without being typed in twice. One limit to know before you move: HelpFab schedules PMs on the calendar — weekly, monthly, quarterly, or yearly — so run-hour and condition-based tasks stay on your sheet. The spreadsheet is the right place to start; the tool is where you go when the spreadsheet can no longer keep up with the shop.
> Free: we'll set up your PM schedule for you. HelpFab is running a free preventive maintenance setup offer. Send your machine and maintenance list in any format — our template, your own spreadsheet, PDFs, or phone photos of a binder or whiteboard — and we load your machines and PM schedule into HelpFab, then walk you through it on a short handoff call. It's free, limited to the first 10 shops, up to 25 machines each. The same page has this template as a ready-made workbook you can download. See the free PM setup offer for details.
Copy this and run one this week
Make the sheet, add your six columns, and fill one row per PM task for your two or three most important machines — the ones that stop production when they go down. Set each interval from the manual or your own failure history, make the Next due cell a formula, and on Monday sort by due date to get your week's list. Then do the quiet, boring thing that separates shops that fight fires from shops that don't: when a task is done, update the date, and let the schedule tell you what's next.