A step-by-step template for creating a PM schedule that actually gets executed — with the right tasks, the right frequency, and an owner for every line item.
Complete one worksheet per asset. A PM schedule that is not tied to a specific asset with specific context is a template, not a maintenance plan. This profile establishes the baseline you need to make good frequency decisions in Section 2.
☐ Yes — attached or on file ☐ No — not available from OEM ☐ Unknown — needs research
A criticality-1 asset (easily bypassed, low production impact) may be a run-to-failure candidate. A criticality-5 asset with no redundancy should be PM'd conservatively — err toward over-maintenance until you have failure history to calibrate against. The PM Playbook includes a full criticality scoring matrix.
Build one row per PM task. Each task should be specific enough that two different technicians would perform it the same way and reach the same pass/fail conclusion. Vague tasks ("check motor") are not PM tasks — they are reminders to improvise.
| Task # | Task Description | Skill Level | Est. Time (min) | Parts / Materials | Frequency | Basis (Cal / Use / Cond) | Pass / Fail Criteria | Owner |
|---|---|---|---|---|---|---|---|---|
| 1 | ||||||||
| 2 | ||||||||
| 3 | ||||||||
| 4 | ||||||||
| 5 | ||||||||
| 6 | ||||||||
| 7 | ||||||||
| 8 | ||||||||
| 9 | ||||||||
| 10 |
Use this decision table when you are unsure how to set the interval for a task. The goal is to start with a defensible frequency and then refine it based on actual results — not to find the perfect interval on the first try.
| Condition | Recommended Frequency Approach | Notes |
|---|---|---|
| Known wear item with OEM specification | Follow OEM interval as starting point | Adjust only if you have documented failure data showing a different interval is appropriate. Deviating from OEM requires a written rationale. |
| Known wear item without OEM specification | Use failure history average, minus 20% as a safety margin | If MTBF is 6 months, set PM at 5 months. No failure history? Use the conservative estimate row below. |
| No failure history available | Start conservative — PM at 50% of expected life or monthly, whichever is shorter | Run 2–3 PM cycles, observe findings. Adjust interval after each cycle based on condition at PM time. If item always looks new at PM, extend the interval incrementally. |
| Degradation is detectable before failure (vibration, temperature, wear measurement, oil analysis) | Move to condition-based monitoring — set inspection frequency, not replacement frequency | Define the trigger threshold that initiates a repair. Calendar-based replacement of a condition-detectable item wastes parts and labor. |
| Failure has minimal consequence (non-critical, easily replaced, redundancy available) | Document run-to-failure as an intentional decision | RTF is a valid maintenance strategy — but it must be a deliberate choice, not a default. Set a minimum spare parts stock level and a replacement time standard so the team is prepared when failure occurs. |
Set a calendar reminder to review each asset's PM frequency after every 3 PM completions. Ask: was anything found at PM that indicates the interval should be shorter? Was nothing ever found, suggesting the interval could be longer? A PM schedule that never gets updated is a PM schedule that will drift out of calibration over time.
Run through this checklist before putting the schedule into your CMMS or assigning any work orders. Every "no" is a gap that will cause problems in execution — either missed tasks, inconsistent results, or schedule overload.
Track these metrics for the first 90 days of a new or revised PM schedule. The goal is to establish a baseline and catch problems early — before poor execution becomes an entrenched habit. Review this table at the end of each month.
| Period | Scheduled PM Count | Completed On Time | Completed Late | Skipped / Deferred | Repeat Failures During Period | Notes |
|---|---|---|---|---|---|---|
| Month 1 | ||||||
| Month 2 | ||||||
| Month 3 | ||||||
| 3-Month Total |
On-time % = (on time ÷ scheduled) × 100 |
High deferral rate: Schedule is overloaded, tasks are taking longer than estimated, or production windows are too narrow. Revisit task times and crew capacity before month 2. Repeat failures despite PM completion: PM tasks may not be addressing the actual failure modes — revisit task content, not just execution. High "completed late" rate: Scheduling logic needs adjustment — tasks may be landing on the wrong shift or overlapping with other workload peaks.
This worksheet gives you the structure to build one PM schedule for one asset. The PM Playbook gives you a complete, implementation-ready system: failure mode analysis templates, criticality scoring, multi-asset scheduling logic, compliance tracking dashboards, technician training guides, and audit checklists — everything needed to run a professional PM program from the first work order to the quarterly review.
Learn more about the Preventive Maintenance Playbook →Companion article: uptimesystemshub.com/articles/pm-scheduling/ · © 2026 Equipment Uptime Systems. For single-organization use. Not for redistribution.