Skip to main content
Skip to download form

Free downtime cost tracking log

Jump to download form ↓

Enter your email below to download this downtime cost tracking log as a ready-to-use PDF.

Free downtime cost tracking log (PDF-ready). Capture lost production, repair, parts, contractor and safety costs by incident. ISO 14224 aligned.

Jarrod Milford

Jarrod Milford

Commercial Director

Updated 15 May 2026

Updated 15 May 2026

How to use: download the PDF, print or complete digitally on any device.

  • PDF format, ready to print or fill on screen
  • Use as-is or customise to suit your operation
  • Go digital in MapTrack for photos, alerts and audit trails

Download free PDF template

FreePDFUpdated May 2026

Get your free template

Enter your email to download the downtime cost tracking log as a free PDF. No sign-up required to use it.

Rated 4.9 on G2Rated 4.9 on Capterra
Your info is secure. No spam, ever.

These templates are free general guides provided as-is. They do not constitute legal, safety or compliance advice. You are responsible for ensuring any form meets your specific workplace obligations, industry standards and applicable regulations.

G2 rating 4.9 out of 5Capterra rating 4.9 out of 5

Trusted by teams across Australia and New Zealand

We respect your privacy. Unsubscribe anytime.

Used by construction, mining and field service teams

Saunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuiltDraintechGenusAxis Services GroupRIXDFES Western AustraliaSaunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuiltDraintechGenusAxis Services GroupRIXDFES Western Australia

What is a downtime cost tracking log?

A downtime cost tracking log is a structured register used to capture the full financial impact of every unplanned downtime event on an asset, production line or facility. Rather than recording only the visible cost of a breakdown (labour hours and parts pulled from the storeroom), the log captures the six cost components that together make up the total cost of unreliability: lost production, internal labour, parts and consumables, contractor and hire, safety and quality consequence, and customer impact. Each row records one downtime event, the asset, the failure mode, the duration in hours, the six cost components calculated against an agreed formula, the total event cost, and a link to the root cause analysis record where one was completed. The log rolls up to mean time between failures (MTBF), mean time to repair (MTTR), availability percentage and the annual cost of unreliability number that operations leadership uses to build the business case for reliability investment.

In most operations, the visible cost of a breakdown (labour plus parts) represents a small fraction of the true cost. The invisible cost dominates: lost production valued at contribution margin, the overtime catch-up needed to recover schedule, off-spec product and rework, customer credits and late-delivery penalties. A useful rule of thumb is the 1-to-10 rule: every $1 of repair cost typically masks $10 of total cost of unreliability when downstream impact is counted. The largest component, in nearly every case, is lost production, calculated as downtime hours multiplied by throughput rate multiplied by contribution margin per unit. Per-incident capture is the only credible way to surface this number. Backfilling from memory at month-end systematically under-counts because the people involved have moved on. The log forces the link, agreed with finance, in real time. The output is a sentence operations leadership can say in a budget meeting: "we lost $1.2 million to unplanned downtime last year" beats "we had 38 breakdowns" every time.

Learn more about maintenance and work orders in MapTrack.

Benefits of using this downtime cost tracking log

  • Visible business case for reliability investment: a dollar figure for the annual cost of unreliability gives operations a credible budget request the CFO can defend.
  • Root-cause prioritisation by dollar impact: ranking failure modes by total cost (not frequency) reveals that the top three failure modes typically drive 60 to 80 percent of the loss.
  • Finance alignment from day one: agreeing the lost production formula and contribution margin with finance means every downtime calculation uses the same baseline.
  • Contract and SLA negotiating power with suppliers: when a supplied component fails and the log shows the full event cost (not just parts), warranty claims have credible numbers attached.
  • Capex justification with payback math: a $300K bearing condition monitoring system is easy to justify when the log shows two similar failures last year cost $82K each in lost production alone.
  • Year-over-year benchmark and trend: a populated log lets operations track cost of unreliability per operating hour and per unit produced, measuring the impact of reliability initiatives.

Benefits of digitising forms in MapTrack

When you move your log/registers from paper to MapTrack, you get:

  • Field users can easily scan a QR code to complete a form on mobile. Unlimited users.
  • Automatically get alerts when faults are identified.
  • Link every form digitally as a PDF to the relevant asset, location or person.
  • Receive a digital PDF copy with every submission to your email.
  • Ability to share forms digitally.
  • Build conditional logic (show or hide questions based on answers).
  • Take pictures or attach photos. Not possible with a paper-based form.
  • Electronic signatures.
  • Edit forms later without reprinting.
  • Restrict permissions (who can view, complete or approve).
  • Build forms with AI (describe what you need and MapTrack suggests the form).
  • Trigger work orders automatically when a fault is logged during an inspection.
  • Track service intervals by hours, kilometres or calendar date in one place.
  • Attach supplier invoices and parts receipts to each maintenance record.

Book a demo to see how MapTrack handles log/registers.

Try MapTrack free for 30 days

Full access to every feature. No credit card required. Per-asset pricing so you scale as your fleet grows.

  • No credit card required
  • 30 days free trial
  • Cancel anytime

1-2 days/week saved

Bloody amazing! We used to spend 1-2 days a week tracking and managing our generators alone.
Saunders International

Steve McAllister

Asset Coordinator, Saunders International

What to include in a downtime cost tracking log

This downtime cost tracking log covers 8 key areas:

  • Incident identification: incident number, date and time the asset went down, date and time it returned to service, work order reference, who logged it and who reviewed it.
  • Asset and location: asset tag and description, line or area, asset class (critical, important, supporting), and the production rate the asset was running at when the failure occurred.
  • Downtime duration: scheduled start, actual stop, restart time, total downtime in hours, and a flag for whether the asset returned to full capacity or to reduced output.
  • Root cause: failure mode (bearing, seal, control, operator error), cause category (mechanical, electrical, instrumentation, operations, external), and a link to the formal root cause analysis record where total event cost exceeds the threshold (typically $20K).
  • Cost components: the six cost lines that together make up total event cost - lost production (hours x throughput x contribution margin), internal labour, parts and consumables, contractor and hire, safety and quality consequence, customer impact.
  • Recovery actions: short-term fix applied, long-term action raised (work request, engineering change, training, spares review), action owner and target completion date.
  • Total event cost: sum of the six cost components, reconciled against finance ledger entries at month-end. Variance between operations estimate and finance actual is flagged where greater than 10 percent.
  • MTBF and MTTR rollup: failures count, total downtime hours, operating hours in period, MTBF, MTTR, availability percentage, cost per downtime hour, and cost of unreliability for the period.

How to use this downtime cost tracking log

  1. Define the six cost-component formulas with finance and agree the contribution margin per unit for each production line or asset class before the first incident is logged.: The single biggest reason downtime cost logs fail is operations and finance disagree on the numbers. Sit down with the controller at the start of the year and agree six inputs: contribution margin per unit for each product or grade (unit sale price minus variable cost), the loaded labour rate for trades and operators, the parts uplift for emergency procurement, the contractor schedule of rates, the quality-consequence cost per tonne of off-spec material, and the customer-impact playbook. Document the formulas in the log header.
  2. Capture each downtime event in real time as the asset returns to service. Do not backfill from memory at month-end.: The shift supervisor logs the event within 24 hours of the asset returning to service, using the work order as the source for duration, labour hours and parts issues. Lost production is calculated immediately using the agreed formula. Contractor cost is added when the invoice arrives. Safety and quality consequence is added by the quality engineer after off-spec material is reconciled. Customer impact is added by sales when penalties are confirmed. The log is not closed until all six components have a number.
  3. Calculate the total event cost as the sum of the six components, then reconcile every line against finance ledger entries at month-end.: At the monthly close, the maintenance owner and the finance controller reconcile the log totals against the general ledger: maintenance labour against the maintenance cost centre, parts against storeroom issues, contractor against AP, quality consequence against scrap and rework accounts, and customer impact against credit-note accounts. Where operations estimated a number that finance cannot trace, the variance is investigated and the formula updated if needed. This monthly reconciliation gives the annual cost of unreliability number its credibility.
  4. Run a monthly trend review with maintenance, production and reliability engineering. Rank failure modes and assets by total cost (not frequency).: At the monthly review, sort the log by total event cost descending and look at the top five events. Sort by failure mode and identify any mode that appears more than twice. Sort by asset and identify any asset that absorbed more than 10 percent of period cost. For the top three failure modes by cost, confirm a root cause analysis is open and that corrective action is funded and assigned. Compare period MTBF and MTTR against the rolling 12-month baseline.
  5. Produce the annual cost-of-unreliability report for operations leadership and the board. Convert 12 months of data into a headline, a Pareto, and a funded action plan with payback math.: Once a year, roll the log up into a board-ready report. Lead with the headline: total cost of unreliability for the year, broken down by the six components, with a Pareto showing the top failure modes that drove 80 percent of the loss. Add the year-over-year trend. Then present the funded action plan: which failure modes get engineering effort next year, what condition monitoring or capex is requested, and what the expected reduction in cost of unreliability is.

In MapTrack, you can schedule and track maintenance digitally. Each submission is stored as a timestamped PDF against the asset record.

Get the free templateEnter your email above to download the full downtime cost tracking log as a PDF.Back to download form

How often should you complete this log/register?

Downtime cost capture is continuous, not periodic. Every event above the trigger threshold (typically 15 to 30 minutes for production lines, one hour for support equipment) is logged within 24 hours. The log is reviewed at three cadences. Monthly: the maintenance lead and finance controller reconcile the period totals against the ledger, the monthly trend review ranks failure modes and assets by total cost, and the top three events are confirmed to have open corrective action. Quarterly: a summary of the cost of unreliability, MTBF and MTTR trends, and the status of the top corrective actions is presented to operations leadership. Annually: the full cost-of-unreliability report is delivered to the executive team and the board. MapTrack work-order integration auto-pulls downtime durations, labour hours and parts issues from the work order into the log row.

Frequently asked questions

Lost production cost equals downtime hours multiplied by throughput rate multiplied by contribution margin per unit. Contribution margin is unit sale price minus variable cost per unit (energy, consumables, freight, variable labour), not gross margin and not net profit. Agree the contribution margin with finance once per year for each product so every downtime calculation uses the same baseline. Example: a 4-hour outage on a line producing 200 tonnes per hour at $40 per tonne contribution margin equals 4 x 200 x 40 = $32,000 in lost production. This is typically the largest single cost component in any downtime event, and the line finance can verify against the production schedule.

Mean time between failures (MTBF) equals total operating hours in the period divided by the number of failures recorded in that period. Mean time to repair (MTTR) equals total downtime hours in the period divided by the number of failures. Availability equals MTBF divided by (MTBF plus MTTR). Both formulas align with EN 13306:2017 maintenance terminology. The log captures duration on every row, so the calculation is automatic at month-end. Note that MTBF should be calculated against operating hours (time the asset was scheduled to run), not against calendar hours.

Use the cause category field to record the immediate failure mode (e.g. bearing, seal, motor, sensor) and link the row to a root cause analysis record where total event cost exceeds the threshold (typically $20K) or where the same failure mode has occurred more than twice in 12 months. The RCA distinguishes proximate cause from root cause and prevents the log from concluding "bearing failure" when the true cause is contaminated lubricant, an installation defect, or excessive vibration from a misaligned coupling. Without the link to RCA, downtime data is descriptive but not actionable.

Finance will not agree to a number that operations calculated alone. Invite the financial controller to a one-hour workshop at the start of the year and walk through six inputs: contribution margin per unit for each product (from the management accounts), the loaded labour rate, the standard parts uplift for emergency procurement, the contractor schedule of rates, the standard quality-consequence cost per tonne of off-spec material, and the customer-impact playbook. Document these in the log header. Reconcile monthly against the ledger. The number is now finance-owned, not operations-owned, which is what gives it credibility.

ISO 14224:2016 provides the international standard format for collecting reliability and maintenance data including downtime cost categories, originating in the petroleum industry but widely adopted. ISO 55001:2024 requires demonstrable financial planning for the asset portfolio, which downtime cost data informs. EN 13306:2017 defines the standard maintenance terminology including MTBF, MTTR and availability. IEC 60300-3-3 provides life cycle costing guidance. None mandates a specific template, but a documented per-incident log with monthly finance reconciliation is the de facto evidence used to satisfy ISO 55001 audit and reliability programme funding submissions.

Yes. Download and use this downtime cost tracking log at no cost. Open the file in your browser and use Print then Save as PDF. No MapTrack account is required. If you want digital downtime cost capture with auto-pulled durations from work orders, finance-reconciled monthly rollups, MTBF and MTTR trend dashboards, and Pareto analysis of failure modes by total cost, MapTrack can do that. Book a demo to see how it works.

Applicable regulatory standards

This template aligns with the following regulations and standards:

  • ISO 14224:2016 (Petroleum, petrochemical and natural gas industries - Collection and exchange of reliability and maintenance data)
  • ISO 55001:2024 (Asset management - Management systems - Requirements)
  • EN 13306:2017 (Maintenance terminology, including downtime, availability, MTBF and MTTR definitions)
  • IEC 60300-3-3 (Dependability management - Application guide - Life cycle costing)

Embed this free template on your website

Run an industry blog, trade association site, or training resource? Drop a preview of this free downtime cost tracking log straight into your page. The snippet is self-contained, needs no scripts, and links readers back to the full free template.

<div style="max-width:480px;font-family:system-ui,-apple-system,'Segoe UI',Roboto,sans-serif;border:1px solid #E5E7EB;border-radius:12px;padding:20px;background:#ffffff;">
  <p style="font-size:12px;font-weight:700;letter-spacing:0.05em;text-transform:uppercase;color:#0E7490;margin:0;">Free template</p>
  <p style="font-size:18px;font-weight:700;color:#071D49;margin:6px 0 0;">Downtime cost tracking log</p>
  <ul style="margin:12px 0 0;padding-left:18px;color:#374151;font-size:14px;line-height:1.6;">
    <li style="margin:4px 0;">Incident identification: incident number, date and time the asset went down, date and time it returned to service, work order reference, who logged it and who reviewed it.</li>
    <li style="margin:4px 0;">Asset and location: asset tag and description, line or area, asset class (critical, important, supporting), and the production rate the asset was running at when the failure occurred.</li>
    <li style="margin:4px 0;">Downtime duration: scheduled start, actual stop, restart time, total downtime in hours, and a flag for whether the asset returned to full capacity or to reduced output.</li>
    <li style="margin:4px 0;">Root cause: failure mode (bearing, seal, control, operator error), cause category (mechanical, electrical, instrumentation, operations, external), and a link to the formal root cause analysis record where total event cost exceeds the threshold (typically $20K).</li>
    <li style="margin:4px 0;">Cost components: the six cost lines that together make up total event cost - lost production (hours x throughput x contribution margin), internal labour, parts and consumables, contractor and hire, safety and quality consequence, customer impact.</li>
    <li style="margin:4px 0;">Recovery actions: short-term fix applied, long-term action raised (work request, engineering change, training, spares review), action owner and target completion date.</li>
  </ul>
  <p style="font-size:13px;color:#6B7280;margin:14px 0 0;padding-top:12px;border-top:1px solid #E5E7EB;">Free <a href="https://www.maptrack.com/templates/downtime-cost-tracking-log" style="color:#071D49;font-weight:600;text-decoration:none;">Downtime cost tracking log</a> by MapTrack</p>
</div>

Please keep the “by MapTrack” attribution link in the snippet.

Need to schedule and track maintenance digitally?

Register every asset in MapTrack, attach digital forms, and get a complete history of every inspection, service and compliance record.

Maintenance and work orders · All templates · Pricing · Book a demo