Preventive maintenance schedule template for real production windows

What belongs in a PM schedule template

A preventive maintenance schedule is not a wish list. It is a repeatable plan that answers: which asset, what work, when it is due, who owns it, and whether the plant can actually release the machine.

Every useful row should include:

• Asset identity — machine / line / location, not a vague area nickname
• Task name — specific enough that two technicians do the same job
• Trigger — calendar interval, runtime/meter, or event-based (after changeover, after sanitation)
• Estimated duration — honest minutes, not aspirational ones
• Parts and tools — what must be on hand before the window opens
• Allowed window — which production or sanitation stop this fits into
• Owner role — who claims the work when it is due
• Completion rule — due PM becomes a work order, not a checkbox in a binder

If a field does not help the floor finish the job, drop it. Template bloat is how PM becomes theater.

For how PM fits among reactive and predictive work, see [maintenance types explained](/guides/maintenance-types-explained). For plant-level PM strategy, see [preventive maintenance for plants](/guides/preventive-maintenance-for-plants).

Sample template fields (copyable)

Copy these fields into a sheet or CMMS schedule. One row = one PM task on one asset.

• Asset ID / name
• Asset criticality (A / B / C or similar)
• PM task title
• Task steps / checklist (short — see sizing below)
• Trigger type (calendar / meter / event)
• Frequency or meter interval
• Next due date / next due reading
• Estimated duration (minutes)
• Required parts (part numbers + qty)
• Required tools / PPE
• Allowed production window (e.g., Friday changeover, nightly sanitation)
• Assignee role / default owner
• Last completed date
• Last completed by
• Notes / failure mode this PM prevents
• Active? (yes/no — park tasks you are not ready to staff)

Example row (illustrative):

• Asset: Packaging Line 2 — sealer
• Task: Inspect and clean sealing jaws; check thermocouple reading
• Trigger: Calendar — weekly during Friday changeover
• Duration: 25 minutes
• Parts/tools: cleaning kit, spare thermocouple on hand
• Owner: Packaging tech lead
• Window: Friday changeover only

How to choose frequencies without theater

Frequencies should come from three inputs — not from copying an OEM PDF blindly:

1. OEM / vendor guidance — starting point for safety-critical and warranty-sensitive items
2. Failure history — shorten intervals where the same wear failure keeps returning; lengthen where history is clean
3. Real windows — if the line only releases for 30 minutes on Fridays, a 90-minute “monthly” PM will be skipped forever

Start with critical assets and the failure modes that already cost you downtime. Expand coverage after compliance is real. A short schedule that finishes beats a thick schedule that everyone ignores.

Sizing checklists so they finish

Long checklists look thorough and die on the floor.

• Prefer 5–12 steps that a tech can complete in the estimated window
• Split oversized jobs into separate PM tasks with their own triggers
• Put “nice to inspect” items on a lower frequency instead of bloating every visit
• Require parts readiness before the window — not mid-task scavenger hunts
• Measure percent finished on time, not percent of tasks written

If technicians routinely skip the last half of a checklist, the template is wrong — not the crew.

From template → CMMS work orders

A static template becomes maintenance when due items convert into owned work orders:

1. Schedule the PM on the asset in the CMMS
2. When due, generate a work order with the checklist, parts, and window
3. Someone claims, starts, and completes the job with notes
4. History stays on the asset for the next review

That loop is what separates a living PM program from a spreadsheet calendar. Corivo is built to schedule PM on assets and turn due work into owned jobs so compliance is visible.

Downloadable template note

A downloadable sheet/CSV lead-magnet version of this field list is coming soon. Until then, copy the bullet fields above into your own workbook, rewrite frequencies against your production windows, and move critical rows into a CMMS as soon as you are ready to own due work.

Common PM template mistakes

• Ignoring production windows — calendar-perfect tasks that never get a stop
• Boiling the ocean — building a full-plant library before critical assets finish reliably
• Checklist theater — 40 steps nobody completes, then marking PM “done”
• No parts linkage — planned work that stalls for missing consumables
• No owner — “maintenance” as a group instead of a claimable job
• Never converting to work orders — the template stays a document, not a system of record

Build the smallest template that protects your noisiest assets, prove finish rates for two weeks, then expand. That is how PM schedules earn trust on the floor.