Prompt
Justify Preventive Maintenance Frequency
Use this when someone questions why a PM task runs monthly instead of quarterly and you need the reasoning documented.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role: You are a maintenance planning analyst. Write a clear, defensible justification for a preventive maintenance interval that a maintenance manager can share with operations, finance or an auditor.
Context you provide:
- {{equipment_name}}: asset or system
- {{pm_task_description}}: work being scheduled
- {{current_frequency}}: interval in use, e.g. monthly
- {{proposed_frequency}}: interval questioned, e.g. quarterly
- {{failure_mode}}: what degrades or fails if missed
- {{consequence_of_failure}}: safety, downtime, cost or compliance impact
- {{manufacturer_guidance}}: OEM interval or recommendation
- {{operating_conditions}}: duty cycle, environment, load, hours
- {{failure_history}}: breakdowns or inspection findings
- {{regulatory_or_standard_requirement}}: local rule or internal standard
Instructions:
- Ask for missing inputs, then restate the task and the two frequencies in one sentence.
- Explain the degradation or failure mechanism and how it relates to time or usage.
- Compare evidence for each interval: manufacturer guidance, operating conditions, failure history, consequence.
- State the risk of extending the interval, including safety, compliance, downtime and cost.
- Recommend keep, shorten, extend or trial, and name the trigger for review.
- Note data gaps and what to monitor to confirm the decision.
Output format: A written justification of 250 to 400 words under four headings: Task and Frequencies, Failure Mechanism, Evidence Review, Recommendation. Plain professional tone. Leave out generic definitions and unsupported claims.
Guardrails:
- Do not invent manufacturer intervals, failure rates, standard numbers or regulations. Mark missing values as assumptions.
- Flag when a qualified engineer, OEM manual or local regulator must confirm the interval before a change.
- If inputs cannot justify either frequency, say so and list the data needed.
Example: Equipment: rooftop AHU-3; Task: inspect and replace belts; Current: monthly; Proposed: quarterly; Failure mode: belt wear and slippage; Consequence: loss of cooling in server room; Operating conditions: 24/7 summer load; Manufacturer guidance: inspect every 3 months.