PM Schedule and Checklist Templates You Can Reuse

Search for a preventive maintenance schedule template and you get a thousand download pages, almost all of them gated behind a form, and almost all of them useless: a grid of empty cells with month headings and no explanation of what belongs in a row, what the columns are for, or how the thing survives contact with a real maintenance team. After twenty-two years of building and rescuing PM programs inside CMMS, CAFM and EAM systems, I can tell you that the format is the easy part. What separates a schedule that runs a site from a spreadsheet that gets abandoned in April is the discipline encoded in the columns. So this article gives you the templates as real tables you can copy, and next to every column an explanation of what it is for and the specific mistake I see teams make with it.

The message up front: a PM program needs six artefacts, not one. An asset register (what you own), a job plan library (what gets done), an annual master schedule (when, across the year), a weekly work plan (who, this week), a compliance tracker (what you must prove), and a maintenance log (what actually happened). Most teams build only the annual schedule, which is why their program looks organised on paper and falls apart in execution. Build all six, even if they start as six tabs in one workbook.

1. The six artefacts, and why one spreadsheet is not enough

The single most common structural mistake in a young PM program is trying to make one sheet do every job. Someone builds a big grid with assets down the side and months across the top, ticks the cells where work is due, and calls it the maintenance schedule. It looks like control. It is actually a plan with no execution layer, no task detail, no evidence trail and no history, which means it can tell you what should have happened but never what did.

The six artefacts split along two axes: static reference data versus time-based planning, and plan versus record. Keeping them separate is what lets each one stay simple.

A note on scope before we start: this article gives you the planning and tracking artefacts. It deliberately does not give you the inspection checklists themselves, the line-by-line task lists for an air handling unit, a distribution panel, a pump set or a generator. Those live in a companion piece, preventive maintenance checklists, templates and examples. Use that article to fill the task detail, and this one to schedule, assign and prove it. If you are earlier in the journey and still deciding what your PM program should cover at all, start with the complete guide to preventive maintenance.

2. Template 1: the asset register (minimum viable columns)

Everything else depends on this. You cannot schedule maintenance on an asset you have not identified, and you cannot prioritise it without knowing what it serves. The failure mode here is almost always the same: someone starts with sixty columns because the CMMS data template has sixty columns, the population effort collapses under its own weight, and eighteen months later the register is forty percent complete and nobody trusts it. Start with the twelve columns below. They are enough to run a PM program. You can add depth later, on assets that earn it.

3. Template 2: the PM job plan (task template)

A job plan is the reusable definition of one PM task set, written once per asset class and frequency, then attached to every asset in that class. It is the artefact that stops your schedule from becoming a list of vague instructions like "service AHU". Two headers and a task table are all it needs.

The task rows themselves follow a five-column pattern. The reading and limit columns are what turn an inspection from a tick-box exercise into data you can trend.

4. Template 3: the annual PM master schedule

This is the artefact people mean when they ask for a preventive maintenance schedule template. Its job is to answer one question: across the next twelve months, in which period is each PM due, and is the resulting workload evenly spread? One row per asset and job plan combination, with period columns across.

I strongly prefer week numbers to months. Months hide the problem: "March" can mean a comfortable spread or forty jobs all landing in the last three days. Weeks force the levelling conversation.

The two summary rows at the bottom are the whole point of the template. Without them you have a calendar. With them you have a capacity plan, and you can see before the year starts which weeks are overloaded.

5. Template 4: the weekly PM work plan

The annual schedule says what is due. The weekly plan makes it happen. This is the artefact most missing from the templates you find online, and the reason so many annual schedules produce a growing backlog instead of completed work. It converts due dates into assignments, with the access, parts and permits resolved in advance.

The rule I would give any planner: the weekly plan for next week should be finalised and issued before the end of this week, with every row either ready to execute or explicitly flagged as blocked. A plan issued on Monday morning is not a plan, it is a list of surprises.

Note that this template assumes you distinguish PM work orders from corrective, emergency and project work. If your numbering does not separate those, the whole measurement layer collapses, because you cannot compute a PM compliance figure or a planned-versus-reactive ratio. The conventions are in work order types in a CMMS.

6. Template 5: the PM compliance tracker

Compliance tracking is a different question from scheduling, and conflating the two is a common and expensive mistake. The schedule asks "when is it due". The tracker asks "can we prove, to an auditor or a client, that the obligation was met within its window, and where is the evidence". Statutory and contractual items belong here even if they also appear on the annual schedule.

Two external references worth anchoring your obligation list against: the SFG20 building maintenance standard for building services task content and frequencies, and ISO 55001 for asset management systems if you are working towards a formal management system. For fire and life safety items in particular, the relevant NFPA codes set inspection, testing and maintenance frequencies that your local authority will usually reference directly. Always confirm against the local jurisdiction's requirements, which in the Gulf region frequently sit on top of the international code rather than replacing it.

7. Template 6: the maintenance log and history record

The log is the artefact that makes everything else improvable. Without a maintenance history you can schedule, assign and complete work forever without ever learning anything from it. With one, you can see which assets consume the most labour, which PM tasks never find anything, and which failures keep coming back.

8. What to measure from these templates

Six artefacts built properly give you five measures almost for free. Report these monthly and you will know whether the program is working, which is more than most sites can say.

PM yield is the one most people have never calculated and the one that changes the most decisions. If a quarterly task has run 400 times and never once produced a finding or a follow-up, you are paying for it with nothing to show. That is the evidence you need to extend the interval or delete the task. The broader measurement frame sits in the FM KPI framework.

9. Making these work in Excel or Sheets without it collapsing

If you are going to run this in a spreadsheet, a few mechanical decisions determine whether it survives its first year.

• One workbook, six tabs, one direction of reference. Register, JobPlans, AnnualSchedule, WeeklyPlan, Compliance, Log. References flow one way: the schedule looks up the register and the job plans, never the reverse. Circular lookups between tabs are how these files become unmaintainable.
• Asset ID as the only join key. Never join on asset name. Names get edited; IDs must not. Lock the ID column.
• Closed lists for every categorical field. Asset class, criticality, trade, work type, status. Use data validation against a hidden Lists tab. This single step prevents most of the data quality problems that make the file unreportable later.
• Dates as real dates, in ISO format. Store 2026-09-24, not 24/09/26. Mixed regional date formats in a shared file are a reliable source of silent error, particularly in a multinational team.
• The log is append-only. New rows at the bottom, existing rows never edited. If a correction is needed, add a row noting the correction. An editable history is not a history.
• One person owns the file. Shared editing on a planning workbook produces conflicting versions within weeks. Technicians submit completions to the owner, or via a form that appends to the log; they do not type into the workbook.
• Version the file by date, keep an archive. PM-Master-2026-W39.xlsx, with last month's copies retained. When someone asks what the plan said in March, you need to be able to answer.

10. When to graduate from spreadsheets to a CMMS

I will say something the software industry does not: a spreadsheet PM program, run with discipline, outperforms a badly implemented CMMS. I have walked into sites with a well-regarded EAM system where compliance reporting was fiction, and sites running a single careful workbook where the plant was in genuinely good condition. The tool is not the variable. Discipline is.

That said, there are real thresholds beyond which the spreadsheet stops being the constraint-free choice and starts costing you more than the software would. These are the signals I would actually use.

A useful rule: if you can tick three or more of those rows, the spreadsheet is now costing you more in planner time and lost data than a light CMMS would cost in licence fees. If you can tick one, stay where you are and get the discipline right first, because the single best predictor of a successful CMMS implementation is having run a disciplined manual process before it.

On tool choice, the honest position is that the small-team end of the market is genuinely good now. MaintainX, Limble, Fiix, UpKeep and eMaint will all run a few hundred assets with mobile execution competently and at a cost that a single planner's recovered time justifies. The enterprise platforms, IBM Maximo, Hexagon EAM, Infor EAM, SAP PM and Planon, are a different proposition entirely: more capable, considerably more implementation effort, and only warranted when you have the asset base, the integration requirements and the internal ownership to sustain them. Shortlists for both ends are in best CMMS for small teams and the CMMS buyer shortlist.

11. A four-week rollout sequence

Building all six artefacts at once is how this stalls. The order below is the one I would recommend, and it produces something usable at the end of every week rather than something complete only at the end.

Then review at ninety days, not at twelve months. Look at estimate accuracy, PM yield and the blocked-reason column in the weekly plan. Those three tell you where the plan is wrong while there is still time to fix it. The programme-level framework for that review cycle is in preventive maintenance plans and programs.

The idea to walk away with

The template is not the program. What makes a preventive maintenance schedule work is the small number of fields that force a decision: criticality, so you know what matters; estimated hours, so you can level the load; a ready flag, so unready work is not issued; a follow-up work order reference, so findings become action; and an actual-hours field, so the plan learns from reality. Every one of those is a discipline wearing the costume of a column. A beautiful grid without them is a document. A plain grid with them is a maintenance program.

And the six artefacts are six because they answer six different questions. When a site tells me its PM program is not working, the diagnosis is usually not a bad schedule. It is a missing weekly plan, or a log that says "done", or a compliance obligation tracked nowhere. Build all six, keep each one simple, and the program holds.

Final thoughts

Copy these tables into a workbook, put your own assets in them, and resist the urge to add columns. The most common way a PM spreadsheet dies is not neglect, it is ambition: someone adds twenty fields that nobody has time to populate, the file becomes half empty, and half-empty data is data nobody trusts. Twelve register columns, a dozen job plans, a levelled annual grid, a weekly plan issued on Friday, a tracker for the obligations you must prove, and an append-only log. That is a complete preventive maintenance system, and it will run a building well.

For the inspection task content to drop into those job plans, the asset-by-asset checklists are in preventive maintenance checklists, templates and examples. And if you get to the point where the spreadsheet is genuinely the constraint rather than the discipline, that is a good problem: it means the program is working well enough to have outgrown its tooling.

Related reading: Preventive maintenance: the complete guide, PM checklists, templates and examples, How to build a PM schedule, Asset criticality classification, Work order types in a CMMS, Best CMMS for small teams.