Build a preventive maintenance schedule for my equipment
A maintenance plan that sets tasks and intervals per asset, balances workload, and tracks compliance.
The prompt
Help me build a preventive maintenance (PM) schedule.
Equipment list: [ASSET | type | age | how critical (high/med/low) | hours of use per week]
Manufacturer recommendations: [PASTE OR SUMMARIZE, if available]
Failure history: [common breakdowns, downtime, repair costs]
Maintenance resources: [technicians, hours available, outside contractors]
Production windows for maintenance: [e.g. "weekends", "between shifts"]
Do this:
1. Rank assets by criticality (impact of failure on safety, output, quality) and condition.
2. For each asset, list PM tasks: task | interval (time- or usage-based) | duration | skill needed | parts. Use manufacturer guidance where given; otherwise propose intervals and mark them [CONFIRM WITH MANUFACTURER].
3. Spread the tasks into a 12-month calendar that fits our maintenance hours and production windows, avoiding pile-ups in one week.
4. A daily or weekly operator checklist (clean, inspect, lubricate) for simple tasks operators can own.
5. Metrics to track: PM completion rate, overdue PMs, unplanned downtime, mean time between failures.
6. Where failure history suggests condition-based checks (vibration, temperature, wear measurements) would beat fixed intervals.
Safety-related tasks (lockout/tagout, guarding, pressure systems, lifting equipment) may have legal inspection requirements; flag them and tell me to confirm with a qualified person.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Projects & Operations prompts
What to fill in
- PASTE OR SUMMARIZE, if available
- common breakdowns, downtime, repair costs
- technicians, hours available, outside contractors
- e.g. "weekends", "between shifts"
- CONFIRM WITH MANUFACTURER
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Turn different teams' views into one cross-functional action planCombines input from several teams into one plan with shared goals, clear owners per team, handoffs, and dates.
- Turn company goals into a quarterly operations planA quarterly plan that translates company priorities into operations objectives, initiatives, metrics, and owners.
- Set up a preventive maintenance schedule for my fleetA PM program by vehicle class with service intervals, inspection checklists, parts planning, and downtime scheduling.
- Write a project closure reportFormally closes a project: results vs. objectives, handover, open items, and lessons.