Preventive Maintenance Schedule Template (Buildings and Equipment)
Copy a free preventive maintenance schedule template and checklist for buildings and equipment, with a worked example and an AI prompt to fill it in.
For Operations and Managers

What is a preventive maintenance schedule template?
A preventive maintenance (PM) schedule template is a table that lists every asset you maintain, the task to perform on each, how often, who does it, when it was last done and when it is next due. It turns "we should check that" into a dated, assigned job. The version below works for buildings (HVAC, plumbing, fire and life safety, roofs) and for equipment (pumps, compressors, forklifts, production machines). Copy it into Excel or Google Sheets and fill it in.
TL;DR
- A PM schedule has five working parts: an asset list, a task list per asset, a frequency, an owner, and a "next due" date that calculates itself.
- Start from the manufacturer's manual, then layer on code requirements and your own failure history. Never start from a generic internet list alone.
- Group tasks by frequency (daily, weekly, monthly, quarterly, annual) so one technician round covers many assets at once.
- AI can draft the first version in minutes if you paste in your asset list and manual excerpts, but you must verify every interval against the manual and local code.
- Track completion, not just the plan. A schedule nobody closes out is a wish list. Log date done, who, what was found, and parts used.
- Review the schedule twice a year. Move tasks that find nothing to a longer interval, and tasks that keep finding problems to a shorter one.
What goes in a preventive maintenance schedule?
Every row in the schedule answers six questions: what asset, what task, how often, who, when last, when next. Everything else is optional detail that helps with planning or audits.
Here is the minimum, and what each column is for.
| Column | What it holds | Why it matters |
|---|---|---|
| Asset ID | A unique tag, like RTU-03 or PMP-12 | Prevents "which pump?" confusion |
| Asset name | Plain description | Readable by anyone |
| Location | Building, floor, room or zone | Lets technicians plan a route |
| Task | One specific action | "Inspect" is vague; "Check belt tension and wear" is a task |
| Frequency | Daily, weekly, monthly, quarterly, semiannual, annual | Drives the due date |
| Interval | Number of days or months | Lets the spreadsheet calculate |
| Trigger | Calendar or meter (hours, cycles, miles) | Some equipment wears by use, not time |
| Assigned to | A person or team | An unowned task does not get done |
| Est. time | Minutes or hours | Used to balance workload |
| Last done | Date | Source of truth for the next date |
| Next due | Formula | Shows what is coming or overdue |
| Status | Scheduled, due soon, overdue, done | Filterable at a glance |
| Reference | Manual page, code or SOP | Proves why the task exists |
| Notes | Findings, parts used | Feeds the next review |
Copy this preventive maintenance schedule template
Paste this header row into a spreadsheet, one tab called Schedule.
Asset ID | Asset | Location | Task | Frequency | Interval (days) | Trigger | Assigned to | Est. time (min) | Last done | Next due | Status | Reference | Notes
Then add two helper formulas. In Google Sheets or Excel, if "Last done" is column J and "Interval (days)" is column F:
- Next due (column K):
=J2+F2 - Status (column L):
=IF(J2="","Not started",IF(K2<TODAY(),"Overdue",IF(K2-TODAY()<=7,"Due soon","Scheduled")))
For monthly tasks you can store the interval as 30, or use =EDATE(J2,1) to land on the same day next month. Pick one approach and use it everywhere.
Add conditional formatting: red for "Overdue", amber for "Due soon". Add a second tab called Assets with one row per asset: ID, make, model, serial number, install date, warranty end date, location, and a link to the manual. Add a third tab called Log where each completed job gets a new row: date, asset ID, task, technician, time spent, findings, parts used, and whether a follow-up repair was raised.
Keeping the Log separate from the Schedule matters. The Schedule shows what is planned; the Log is your history, and your history is what you use to adjust intervals later.
What should a preventive maintenance checklist include?
A good checklist is short, specific and tickable. Each line names a component and a pass condition, so two different technicians would reach the same conclusion. Below is a starting set grouped by frequency. Treat these as prompts, not rules. The manufacturer's manual, your insurer, your warranty terms and local code decide the actual interval.
Building systems checklist
Weekly or monthly
- Walk the plant rooms and mechanical spaces: look for leaks, unusual noise, odors, vibration, and anything stored that should not be there
- Check emergency lighting and exit signs for illumination (the test button or a visual check)
- Visually inspect fire extinguishers: in place, accessible, pin and tamper seal intact, gauge in range
- Check HVAC filters and replace if loaded
- Inspect restrooms and kitchens for slow drains, dripping fixtures, and running toilets
- Check parking lot and exterior lighting for burnt-out lamps
- Review building management system alarms and clear or escalate
Quarterly
- Inspect HVAC condensate drains and pans for blockage
- Check belts, bearings and motor mounts on air handlers and fans
- Test backup generator under load or per the manufacturer's run schedule
- Inspect roof drains, gutters and downspouts for debris
- Check door closers, hinges and access control hardware
- Inspect water heater and boiler visible components, relief valves, and venting
Semiannual
- Service heating and cooling equipment before each season
- Clean coils and check refrigerant and electrical connections (qualified technician)
- Test sump pumps and backflow components where fitted
- Inspect exterior walls, sealants, windows and caulking
Annual
- Fire alarm, sprinkler and extinguisher inspections by qualified or licensed providers, as required by your local fire code
- Elevator inspection and certification as required by your jurisdiction
- Roof inspection after winter and after major storms
- Electrical panel inspection, including thermal imaging if your policy calls for it
- Backflow preventer testing where required
- Review of the whole schedule against incidents and repairs from the past year
Equipment checklist (generic, adapt per machine)
Before each shift or daily
- Visual check for leaks, loose guards, damaged cords or hoses
- Check fluid levels (oil, coolant, hydraulic)
- Confirm safety devices work (e-stops, interlocks, alarms)
- Listen for abnormal noise and note abnormal temperature or vibration
Weekly or monthly
- Lubricate points per the lubrication chart
- Check belt tension and chain condition
- Clean or replace air and fluid filters
- Check tire or track condition on mobile equipment
- Inspect batteries and terminals
Quarterly to annual
- Calibrate gauges, sensors and controls
- Replace wear parts on a schedule (seals, bearings, belts)
- Test electrical connections and motor condition
- Full inspection against the manufacturer's service interval
- Update the asset record with hours, repairs and condition
Any task that involves energized electrical work, pressure vessels, confined spaces, or stored energy needs lockout/tagout and a qualified person. Put that requirement in the Notes column so it is never left to memory.
How do you fill in the template? A worked example
Take a three-story office building with one rooftop air handling unit, one gas boiler, a standby generator, and a shared air compressor in the basement workshop. Two technicians, plus a contractor for specialized work. Here is what a filled-in schedule might look like. The intervals are illustrative; yours come from your manuals.
| Asset ID | Asset | Location | Task | Frequency | Interval (days) | Assigned to | Est. time (min) | Reference |
|---|---|---|---|---|---|---|---|---|
| RTU-01 | Rooftop air handler | Roof | Inspect and replace filters | Monthly | 30 | Tech A | 30 | OEM manual, filter section |
| RTU-01 | Rooftop air handler | Roof | Check belts, bearings, condensate drain | Quarterly | 90 | Tech A | 60 | OEM manual |
| RTU-01 | Rooftop air handler | Roof | Full service, coil cleaning | Semiannual | 180 | HVAC contractor | 180 | Service contract |
| BLR-01 | Gas boiler | Basement plant room | Visual check, pressure and temperature readings | Weekly | 7 | Tech B | 15 | Site SOP |
| BLR-01 | Gas boiler | Basement plant room | Combustion and safety device inspection | Annual | 365 | Licensed contractor | 240 | Local code, insurer |
| GEN-01 | Standby generator | Exterior pad | Run test, check fuel, oil, coolant, battery | Monthly | 30 | Tech B | 45 | OEM manual |
| CMP-01 | Air compressor | Workshop | Drain condensate, check oil level | Weekly | 7 | Tech A | 10 | OEM manual |
| CMP-01 | Air compressor | Workshop | Replace air filter, check belt | Quarterly | 90 | Tech A | 45 | OEM manual |
| FIRE-ALL | Fire extinguishers | All floors | Visual inspection and tag check | Monthly | 30 | Tech B | 40 | Fire code, SOP |
Three habits make this schedule easier to run.
- Bundle by location and frequency. Tech A's monthly roof visit covers RTU filters and anything else on the roof, so the climb happens once.
- Separate in-house from contractor work. Contractor rows still live in your schedule, with the contractor named as owner, so you see when visits are due and can check that they happened.
- Stagger heavy weeks. If every quarterly task falls on the first Monday, you get a crunch and nothing else gets done. Offset start dates by asset or floor.
Can AI build my preventive maintenance schedule?
AI is good at the slow part: turning a pile of asset names and manual excerpts into a structured first draft. It is poor at knowing your local code, your warranty terms or your site's quirks. Use it to draft, then check.
Paste the following into ChatGPT, Claude, Gemini or your company's approved AI tool. Replace the bracketed parts. Do not paste confidential data your company forbids sharing; asset names and general descriptions are usually fine, but check your policy.
You are helping a facilities/maintenance team build a preventive maintenance (PM) schedule.
Site: [type of site, e.g. 3-story office building, 40,000 sq ft, in [region]]
Team: [number of technicians, in-house skills, which work is contracted out]
Asset list:
[Paste asset list: ID, name, make/model, location. One per line.]
Manufacturer guidance (excerpts from manuals, if available):
[Paste maintenance sections. Say which asset each belongs to.]
Output a table with these columns:
Asset ID | Asset | Location | Task | Frequency | Interval (days) | Trigger (calendar or meter) | Suggested owner (in-house or contractor) | Est. time (min) | Source of the interval
Rules:
1. Use the pasted manufacturer guidance as the source for intervals wherever it exists, and quote the section.
2. Where no guidance is pasted, propose a typical interval and label it "ASSUMPTION, verify".
3. Keep each task to one specific action, not "inspect".
4. Flag any task that normally requires a licensed or certified provider, or lockout/tagout.
5. After the table, list the assets where you lacked information and the questions I should answer.
6. Do not invent code citations. If a task is likely regulated, say "check local code" instead.
What to check in the AI's answer
- Every interval against the manual. Anything labelled ASSUMPTION needs a source before it goes in the schedule.
- Regulated tasks. Fire protection, elevators, boilers, pressure vessels, backflow and electrical inspections have legal requirements that vary by jurisdiction. Confirm with your authority having jurisdiction, insurer or licensed contractor.
- Warranty conditions. Some warranties require specific service intervals or documented service. The AI does not know yours.
- Missing assets. Models tend to produce neat, plausible lists and quietly skip the odd item: the roll-up door, the dock leveler, the sump in the corner.
- Made-up specifics. If it quotes a standard, part number, torque value or fluid grade you did not give it, treat it as unverified.
Where not to trust AI
Do not use AI output as the final word on safety procedures, torque or pressure settings, electrical work, or anything legal or compliance-related. Use the manual, the qualified contractor and your safety team. Also be careful with AI-assisted interval cuts: a model cannot tell you that a task is safe to skip.
A second useful prompt, once you have a few months of data in your Log tab:
Here is our maintenance log for the last [6/12] months: [paste rows].
Identify:
1) tasks that were done on schedule and found nothing every time (candidates for a longer interval),
2) assets with repeated findings or breakdowns (candidates for a shorter interval or a closer look),
3) tasks that were frequently late and why that might be.
Give me a short list of recommended changes, with the evidence for each. Do not recommend removing any task that is regulatory or safety-related.
How often should preventive maintenance be done?
There is no universal answer, and anyone who gives you one is guessing. Three inputs set the interval, in this order:
- Regulation and insurance. If a code or your insurer requires an inspection at a set interval, that is the floor.
- The manufacturer. The manual lists service intervals, often by calendar time or by running hours, whichever comes first. Follow it, especially during warranty.
- Your own history. If a unit runs in a dusty or humid environment, filters clog faster. If a monthly check has never found a thing in two years, consider moving to quarterly. Make that call from log data, and write down why.
Use meter-based triggers (hours, cycles, miles) for equipment whose wear depends on use, like forklifts, compressors and generators. Use calendar triggers for things that degrade with time or have to be checked regardless of use, like extinguishers, roofs and sealants.
How do you keep the schedule from falling apart?
Most PM programs fail from neglect, not bad design. A few practices keep yours alive.
- One owner for the schedule. Someone reviews overdue items every week, in a standing 15-minute meeting or a Monday check.
- Close the loop. A task is not done until the Log row is filled in. Make "findings" a required field, even if the answer is "none".
- Turn findings into work orders. When a PM check finds a worn belt or a leaking valve, raise a repair ticket right away and reference the asset ID.
- Track a few numbers. Percent of PM tasks completed on time, count of overdue tasks, and repairs found during PM versus breakdowns. Those three tell you whether the program is working.
- Review twice a year. Add new assets, retire old ones, adjust intervals, and check that contractor visits really happened.
- Keep the paper trail. Auditors, insurers and warranty claims all ask for records. A dated log with names is much stronger than memory.
Should you build your own maintenance tracker instead of using a spreadsheet?
A spreadsheet is a fine start, and for a handful of assets it may be all you need. It gets awkward when several people update it, when you want automatic reminders, or when technicians need to close out jobs from a phone on the roof. At that point, many teams buy a maintenance management subscription, or build a small tool of their own. With Remy, you describe the tracker in plain English (an asset register, recurring tasks with owners, a "due this week" view, a completion form for technicians, and email reminders for overdue items) and it builds and deploys a working web app with sign-in and roles. It is mobile-responsive, not a native phone app. You own the code, and the plan is a flat monthly fee with AI usage billed at cost.
Frequently Asked Questions
What is the difference between preventive and predictive maintenance?
Preventive maintenance happens on a fixed schedule, by time or usage, whether or not anything seems wrong. Predictive maintenance uses condition data, such as vibration, temperature or oil analysis, to decide when work is needed. Many sites run mostly preventive maintenance and add predictive monitoring on their most critical or costly equipment.
Can I use Excel or Google Sheets for a PM schedule?
Yes. For a small site or a limited number of assets, a spreadsheet with an asset tab, a schedule tab and a log tab works well. Add the next-due and status formulas above and conditional formatting. Consider moving to dedicated software when you have multiple technicians, a need for mobile work orders, or compliance reporting.
How do I decide which assets to include first?
Start with anything that is safety-critical, legally required to be inspected, expensive to replace, or whose failure would stop operations. Add the rest in waves. A short schedule that is actually followed is more useful than a complete one that nobody opens.
Who should write the checklist for each machine?
Start with the manufacturer's maintenance section, then have the technicians who work on the machine edit it. They know which steps are skipped, which are unclear and which are missing. Have a supervisor or safety lead review any step involving hazardous energy, chemicals or confined spaces.
How long should a PM task take?
Estimate from the first few times it is done, then update the figure from the Log. Include travel, setup, lockout and cleanup, not just the hands-on work. Realistic time estimates are what make the weekly workload plan believable.
Useful for
How we source, write, and correct our articles. Editorial standards
Related articles

Vendor Evaluation Template: A Software Scorecard You Can Copy

SOP Template You Can Copy, Plus an AI Prompt to Fill It In

Three-Way Match: How to Do It, Step by Step
