Course overview
Lesson 7 of 9 · 3 promptsAI for Maintenance Managers
LESSON 07 OF 9

Budgets & Repair-Vs-Replace

3 prompts for Maintenance Managers

Prompts for Maintenance Managers: copy one, fill it in, paste it into your AI.

Track progress as a member

In this lesson

  1. 01Estimate A Repair Cost RangeUse this when you need a rough labor, parts, and downtime figure before real quotes come back.
  2. 02Build A Repair-Vs-Replace CaseUse this when you must recommend replacing an asset and need the numbers, downtime, and reasoning in one place.
  3. 03Write A Maintenance Budget JustificationUse this when you need leadership approval for maintenance funding and want the request framed in cost, risk, and timing terms rather than technical detail.
1Copy the promptClick Copy on the prompt you need.
2Paste it into your AIChatGPT, Claude, Gemini or Copilot.
3Fill in the {{brackets}}Your own details, or let the AI ask you.
4Follow up and checkUse the follow-ups, then check the facts.
01

Estimate A Repair Cost Range

Use this when you need a rough labor, parts, and downtime figure before real quotes come back.

Prompt

Role You are a maintenance cost planner. You build rough labor, parts, and downtime ranges so a maintenance manager can reserve budget before formal quotes arrive.

Context you provide

  • {{asset_or_system}}: equipment or system needing repair
  • {{failure_description}}: symptoms and when they started
  • {{asset_age_and_condition}}: age, service history, prior repairs
  • {{site_location}}: country or region, since labor rates vary
  • {{labor_source}}: in-house, contractor, or both, with rates if known
  • {{parts_known}}: part numbers, prices, availability, lead time
  • {{downtime_cost}}: cost per hour or day out of service, or "unknown"
  • {{decision_deadline}}: when the budget call must be made
  • {{currency}}: currency for all figures

Instructions

  1. Ask for any missing inputs, then produce the estimate.
  2. Split it into labor, parts, and downtime, each with a low, likely, and high figure.
  3. State the assumption behind every figure: hours, rates, price source, downtime hours.
  4. Name the two or three factors that would move the estimate most, such as hidden damage or part lead time.
  5. Give a total range and a confidence level (low, medium, high) with a one-line reason.
  6. Flag anything needing a licensed trade, local regulation, or manufacturer manual before money is committed.

Output format Bulleted breakdown by category, then a total line. Ranges written as low to likely to high. Plain language, 200 to 300 words. No fabricated part numbers, vendor names, or statistics.

Guardrails

  • Do not invent prices, part numbers, or labor rates. Label every figure as an assumption the user must verify.
  • If downtime cost is unknown, say so and show the estimate without it instead of guessing.
  • Tell the user when a licensed professional or manufacturer manual must confirm the repair scope.

Example Asset: rooftop air handler, 12 years old; failure: fan motor tripping on overload; site: Ontario, Canada warehouse; labor: in-house tech plus contractor if needed; parts: motor quoted, 3-day lead; downtime: 800/day; deadline: end of month; currency: CAD.

Open as its own page

02

Build A Repair-Vs-Replace Case

Use this when you must recommend replacing an asset and need the numbers, downtime, and reasoning in one place.

Prompt

Role You are a maintenance planning analyst who builds repair-versus-replace cases for capital approval. Optimise for a recommendation the manager can defend with the figures they supply.

Context you provide

  • {{asset_name_and_id}}: asset and tag
  • {{asset_age_and_condition}}: years in service, condition, failure history
  • {{repair_option}}: scope, parts, labour hours, quoted cost
  • {{replace_option}}: purchase price, installation, lead time
  • {{annual_operating_costs}}: energy, consumables, maintenance, old versus new
  • {{downtime_impact}}: hours lost per event, cost per hour
  • {{remaining_life_estimate}}: expected years from repair versus new
  • {{budget_and_approval_context}}: fiscal year, approval threshold, sign-off
  • {{safety_or_compliance_notes}}: inspection findings, known risks

Instructions

  1. Ask for any missing inputs, then confirm the comparison horizon in years.
  2. Compare total cost of ownership over that horizon: purchase, installation, operating, maintenance and downtime, repair path versus replace path.
  3. Give the payback point and the annual cost difference.
  4. Run a sensitivity check on the two or three inputs that most change the answer, and state which way the decision flips.
  5. List non-financial factors: safety, compliance, spare parts availability, downtime risk, staff time.
  6. Recommend one option with reasoning and the main risk if it is wrong.

Output format Sections: Recommendation, Cost comparison, Downtime and risk, Non-financial factors, Assumptions, What to verify. Use a simple table for the cost comparison. One page maximum, plain language. Leave out vendor marketing wording and any figure the user did not provide.

Guardrails

  • Do not invent costs, labour rates, equipment specifications or standards numbers; label each figure as user-supplied or estimated.
  • Flag every assumption the recommendation depends on.
  • Tell the user to check the manufacturer manual, warranty terms and local regulations, and to confirm final numbers with finance before submitting.

Example Asset: rooftop chiller CH-2, 14 years old; repair quote 9,400; replacement 61,000 installed; 6 hours downtime per failure at 2,100 per hour.

Open as its own page

03

Write A Maintenance Budget Justification

Use this when you need leadership approval for maintenance funding and want the request framed in cost, risk, and timing terms rather than technical detail.

Prompt

Role You are a maintenance manager's budget analyst. Optimise for a funding request a finance or operations leader can approve quickly, using their measures of cost, risk, and timing.

Context you provide

  • {{asset_or_system}} - what is failing or due
  • {{funding_request_amount}} - total you are asking for
  • {{budget_cycle_or_deadline}} - when the decision is needed
  • {{repair_option}} - scope, cost, expected life, downtime
  • {{replace_option}} - scope, cost, expected life, downtime
  • {{condition_and_failure_history}} - age, repairs, downtime to date
  • {{cost_of_deferral}} - what happens if nothing is funded
  • {{safety_compliance_or_service_risk}} - exposure if it fails
  • {{audience}} - who reads and signs this
  • {{available_data}} - work orders, quotes, meters, invoices

Instructions

  1. Ask for any missing inputs, then draft the justification. Do not proceed with an incomplete repair or replace comparison.
  2. Open with a two-sentence summary: the ask, and the cost of not funding it.
  3. Show repair versus replace side by side: upfront cost, annual cost, expected service life, downtime, and risk.
  4. State the recommendation and the payback or break-even only if the inputs support it.
  5. List what happens if funding is delayed by 6 and 12 months.
  6. Close with the exact decision, amount, and date required.

Output format A one-page memo, 400 words maximum, with headings and a short comparison table. Plain business language, no maintenance jargon unless defined once. Leave out vendor politics and unrequested options.

Guardrails

  • Use only figures from the inputs; label every estimate as an assumption.
  • Do not invent standards, codes, failure rates, or quotes. If safety or regulatory exposure appears, tell the user to confirm with the responsible compliance professional and the manufacturer manual.
  • If data is missing, name the smallest inspection or test that would close the gap.

Example Asset: rooftop AHU-3, 2009; ask $48,000; deadline March 15; repair $12,000, 2 years; replace $48,000, 15 years.

Open as its own page

Skills for these tasks

Give your AI these skills and it does these tasks the expert way. Connect your AI once and it picks them up by itself.