•

Equipment Downtime Log Template for Operations

A horizontal hourglass and metallic beads intersect selected time-window frames above a painted quarry.
What’s in this article?

    Measure equipment unavailability against the hours it was actually needed. This copy-ready register separates stop events, scheduled use and reviewed totals so overlapping reports do not inflate lost time.

    A printer can be unavailable overnight without delaying a single scheduled job. Two reports about the same stopped scanner can also describe one interruption, not two. An equipment downtime log needs more than a start time and a repair note if the totals will guide operational decisions.

    This resource is for coordinators tracking ordinary shared service equipment. Copy the blocks below into a document or spreadsheet; the complete resource is inline. It records time and review decisions, not repair instructions or permission to use equipment.

    Choose the measurement boundary before logging stops

    Keep two measures separate: elapsed unavailability is the full time an item could not provide its agreed service; scheduled downtime is the portion of that interval inside the item’s scheduled-use windows and reporting period. This template reports the second measure for operational comparison and retains the first for context.

    Do not describe every stop as a breakdown. A wait for materials, an approved service window and a fault can interrupt planned work for different reasons. Keep planned/unplanned classification separate from the reason code. Never reclassify an unexpected stop as planned merely because someone later approved the repair.

    A maintenance log records service history. This register accounts for unavailable time, including interruptions with no repair. Link the records rather than reconstructing one from the other.

    Copy the setup and schedule blocks

    The coordinator owns the register; an operations reviewer approves period totals. Name a backup for each. The timing rules here are recommended company choices, not industry standards.

    REGISTER SETUP
    Register ID: [unique reference]
    Site/team: [name]
    Coordinator / backup: [people]
    Period reviewer / backup: [people]
    Reporting period: [start inclusive / end exclusive, date-time + zone]
    Register time zone: [named zone; retain offset for each timestamp]
    Service definition: [what counts as available for this equipment]
    Capture rule: [all known complete stops; record estimates as estimates]
    Partial/reduced operation: [record separately; excluded from full-stop total]
    Schedule version / approved by / approved at: [reference / person / time]
    Review cadence: [each staffed shift, or another explicit choice]
    Escalation contact: [person + work contact]
    
    SCHEDULE — repeat one row per asset per needed-use window
    Window ID | Asset ID | Start date-time + offset | End date-time + offset
    [W-01] | [asset] | [start inclusive] | [end exclusive]
    Schedule source / revision / approver: [references]
    Exclusion or amendment reason: [details / none]

    Use actual date-times, not a time-of-day alone. End must be later than start. Merge overlapping schedule windows for the same asset before calculating the denominator. Preserve the approved schedule version: changing it after an interruption requires a dated reason and reviewer decision, not a silent denominator adjustment.

    For this register, an approved maintenance stop inside a needed-use window remains scheduled downtime, classified as planned. A period when the item was never scheduled to be needed contributes neither scheduled minutes nor scheduled downtime. State that convention beside every summary so readers do not confuse it with a different availability metric.

    Copy the downtime event record

    Create one event for one continuous full-service interruption on one asset. A second witness or repair ticket is another source for that event, not another duration to add.

    DOWNTIME EVENT — repeat for each interruption
    Event ID: [unique]
    Asset ID / location: [identifier / place]
    Service affected: [agreed function that is unavailable]
    Unavailable from: [date-time + offset]
    Start precision: [observed / estimated + basis]
    Available again at: [date-time + offset / blank while open]
    End precision: [observed / estimated + basis / not yet known]
    Reported by / reported at: [person / timestamp]
    Planned classification: [planned / unplanned / unresolved]
    Plan reference agreed before stop: [reference / none / awaiting evidence]
    Observed reason: [fault / service / supply wait / setup / other / unknown]
    Observation and evidence: [facts / record references]
    Fault report / work order / service record: [IDs / none]
    Event owner / backup: [people]
    Current status: [open / restoration recorded / reviewed / void duplicate]
    Next action / owner / review due: [action / person / timestamp]
    Restoration evidence and authority reference: [reference / pending]
    Duplicate-of event ID: [ID / not a duplicate]
    Reviewer / reviewed at: [person / timestamp]
    Correction history: [old value / new value / actor / time / reason]

    Require asset identity, start, reporter and owner to accept an event. An estimated start is allowed only with its basis visible. Do not invent a precise timestamp from “sometime this morning.” Require a restoration time and supporting reference before marking restoration recorded; require a reviewer before marking reviewed.

    The log does not establish safe operating condition. When a fault needs an authorized release decision, link the equipment fault report. A completed repair message alone is not the restoration evidence required by your applicable release process.

    Calculate lost minutes without double-counting

    Clip each interval to the correct window

    For a closed event and one schedule window, first restrict both to the reporting period. Then calculate their intersection in minutes:

    Effective start = latest(event start, window start, period start)
    Effective end = earliest(event end, window end, period end)
    Lost minutes = MAX(0, (Effective end - Effective start) in minutes)

    For spreadsheet date-time values already expressed on a consistent timeline, the corresponding closed-event formula is =MAX(0,(MIN(C2,F2,H2)-MAX(B2,E2,G2))*1440), where B/C are event start/end, E/F schedule start/end, and G/H period start/end. The output is minutes. This formula assumes valid nonblank date-times and a common time basis; validate those inputs first.

    For an open event, substitute an explicitly recorded as-of timestamp for its missing end. Do not treat that as a confirmed restoration. Label the resulting period total provisional. Convert offset-bearing timestamps to a common timeline before subtraction; local spreadsheet date-times alone cannot resolve a daylight-saving clock change.

    Union intervals before totaling

    For each asset, sort clipped intervals by start. Merge intervals that overlap or touch, carrying forward the latest end. Add the lengths of the merged intervals, not the lengths of all source rows. Keep the original event references on the merged result.

    If two reports cover 09:10–09:40 and 09:25–09:50 for the same unavailable item, the union is 09:10–09:50: 40 minutes, not 55. Resolve duplicate reports without deleting the evidence. If genuinely separate reasons overlap, retain both reason references but count the asset’s unavailable minute only once.

    PERIOD SUMMARY — repeat per asset
    Asset ID / period / schedule version: [references]
    Scheduled minutes: [union of needed-use windows inside period]
    Confirmed lost minutes: [union from reviewed, closed intervals]
    Provisional total lost minutes: [union including open/unreviewed intervals]
    As-of timestamp: [fixed timestamp used for open intervals]
    Open or unresolved events: [IDs / none]
    Scheduled downtime %: [lost minutes / scheduled minutes × 100]
    Total basis: [confirmed only / provisional including listed events]
    Reviewer / review time: [person / timestamp]
    Decision / follow-up / owner / due: [details]

    When scheduled minutes are zero, show “not applicable—no scheduled use,” not 0% availability or a division error. For a complete reviewed period, scheduled availability percentage is 100 × (scheduled minutes − lost minutes) / scheduled minutes. Do not label it OEE, MTBF or repair time. Those measures require different inputs and definitions.

    At fleet level, summing minutes across different assets produces asset-minutes, not elapsed site outage time. A spare that keeps the job moving does not erase the original asset’s unavailability; record the workaround separately. Do not infer lost revenue or idle labor from this register.

    Worked example: one overnight stop, two needed-use windows

    Fictional example: label printer LP-04 is unavailable from November 16, 2026 at 16:30 UTC−06:00 until November 17 at 09:20 UTC−06:00. Its approved needed-use windows are 08:00–17:00 on each day. The reporting period includes both full days.

    ItemCalculationResult
    Scheduled use9 hours on each of two days1,080 minutes
    First day’s intersection16:30 to 17:0030 minutes
    Second day’s intersection08:00 to 09:2080 minutes
    Scheduled downtime30 + 80110 minutes
    Elapsed unavailability16:30 to next day 09:201,010 minutes
    Scheduled downtime percentage110 / 1,080 × 10010.19%

    A second report says the same printer was down from 08:45 to 09:10 on November 17. Link it to the original event; those 25 minutes are already included. Adding them would incorrectly raise the total to 135 minutes.

    If the review occurs at 09:00 while restoration is still pending, the provisional scheduled loss is 30 + 60 = 90 minutes. Retain that as-of snapshot. Later replace the provisional calculation with the reviewed 110-minute result, preserving the earlier report and correction history.

    Review the queue and handle uncertain records

    • Each staffed shift: the coordinator checks open events, confirms the next action and sets a specific review-due timestamp. An event is overdue when now is later than that timestamp and it is not reviewed or void duplicate. Escalate to the named backup; do not invent a restoration deadline.
    • Unknown start: preserve the estimate or a documented bound. Flag the summary as uncertain rather than presenting an exact percentage without qualification.
    • Overlapping causes: choose a documented allocation rule before reporting minutes by cause. Otherwise report a combined/unallocated category; cause subtotals must not exceed the union total.
    • New stop after restoration: create a new linked event. Do not extend the old interruption across a period when service was genuinely available.
    • Invalid chronology or missing identity: block final review until corrected. Do not clamp negative input durations to zero and call the record valid.
    • Period end with an open event: clip to period end for that period, keep the original event open, and carry its reference forward. Do not create a second full-duration copy.

    Before signing off, the reviewer reconciles event references, schedule version, overlap decisions, open items and totals. A final percentage requires complete reviewed inputs. If that standard is not met, publish an explicitly provisional internal summary instead of concealing the gap.

    Where Workhint fits

    A controlled spreadsheet is enough to begin if one coordinator owns it. For multi-role handoffs, Workhint’s Workflow Engine describes routing approvals to defined roles and requiring details, files or notes before work advances. Those capabilities are relevant to requiring restoration evidence before a record reaches review.

    The Workflow Automation Software solution describes structured forms and tracking stages, owners and next actions. The register can serve as configuration requirements for that kind of workflow. It is not evidence of a prebuilt downtime module, automatic equipment telemetry or native interval-union calculations; establish and test the calculation implementation separately.

    Frequently asked questions

    Should planned maintenance count as downtime?

    In this template, yes when it overlaps an approved needed-use window, but report it separately as planned. Time outside those windows is excluded from scheduled downtime. State the convention whenever you share the total.

    Can I just add the durations on every report?

    Only after duplicate and overlap checks. Multiple reports can describe the same unavailable minutes. Merge overlapping intervals for the same asset before totaling.

    Does a closed work order end the downtime clock?

    Not automatically. Use the evidence-backed time the agreed service became available again under your applicable release process. Keep work-order completion and service restoration as separate facts.

    Is there a downloadable spreadsheet?

    No file is required or promised. The setup, schedule, event and summary blocks are complete inline resources to copy into your own document or spreadsheet. Test its date handling and overlap logic before relying on calculated totals.

    Start with one asset and reconcile one period

    Agree the service definition, schedule and reviewer first. Enter one closed event, one overlapping report and one open event, then reconcile the expected minutes by hand. Once those cases agree, use the register for regular review without confusing evidence collection, technical release and time measurement.

    Comments

    Leave a Reply

    Your email address will not be published. Required fields are marked *


    The reCAPTCHA verification period has expired. Please reload the page.