Atom AI

AI built inside your CMMS to make your FM operations smarter and easier

Explore Atom Assistants
Work Orders

Maintenance Report Template

A maintenance report template for a shift or a day on one site: what the team did, what is still open and why, and what the next shift is walking into. It is a period report rather than a record of one job, and the section that earns it is the handover, because an isolation put in at eleven at night and never written down is found three days later by somebody who has no idea why it is there.

  • One period, stated: shift, day or week
  • Every open job carries a reason, not just a status
  • Temporary measures left in place, listed explicitly
  • A handover section written for somebody who was not here
maintenance-report.xlsx

Maintenance Report

The period, and the handover

Per job
Closed, Open or Escalated
Per open job
Why, not just what
Per period
Closure rate and reactive share
Watched weekly
Temporary measures standing
#FOR THE NEXT SHIFTLOCATIONWHENWHO
1AHU-2 on a temporary belt, order the correct size
2Roof access rebooked when dry
3Isolation still in place on the riser
plus work completed with a status against each job, the jobs still open with a reason attached to every one, plant out of service and the alarms received, temporary measures left in place, safety and incidents, the period in figures including closure rate and reactive share, and a handover carrying two signatures and a time.

The document you will get. Download for the full, editable file.

Who this maintenance report is for

One period on one site, and four people who read it at four different moments.

  • The shift that is handing over

    A structure that makes a two-minute handover possible, so the things that matter get said rather than remembered halfway home.

  • The shift coming on

    Section seven, first. What is on a temporary fix, what is isolated, what is booked and what will go wrong tonight if nobody touches it.

  • The site or facilities manager

    Closure rate and reactive share across the week. One report is an anecdote; twenty of them describe how the site is actually being run.

  • Whoever answers for safety

    Permits issued and closed, contractors on site, near misses, and anything still isolated at the end of the period.

Where shift reporting carries the site

The structure suits any site with a maintenance presence and more than one shift. What changes is what breaks and who notices. If you run one of these, the sector page goes further than the template does.

What a shift maintenance report should contain

A maintenance report is a period record for a site rather than a record of one job. It covers a stated shift, day or week: the work completed, the jobs still open with a reason against each, plant out of service, temporary measures, safety and incidents, the period in figures, and a handover to the shift coming on.

A. The period, the exceptions, and the handover

FieldWhat goes in itWhy it earns its place
Report detailsSite, the period stated explicitly, the times covered and who was onShift, day or week, picked once and kept. A report that changes period cannot be trended, and the trend is the only reason to write these up rather than talk.
Work completedJob number, time, location, what was done, by whom, hours and statusStatus is Closed, Open or Escalated, spelled exactly that way, because the summary counts it and three words beat a sentence.
Still open at the endJob number, location, what is outstanding, why, priority and the next actionThe why column is what makes this a handover rather than a list. Waiting for a part, waiting for weather, waiting for access and waiting for a decision are four different jobs.
Plant out of serviceAnd the effect it is havingOut of service with no effect recorded is a line nobody can prioritize. The effect is what tells the next shift whether to chase it tonight.
Alarms receivedAnd how each was dealt withIncluding the ones that turned out to be nothing, because an alarm that repeats every night is a pattern only visible across reports.
Temporary measures left in placeOverrides, props, isolations and hired equipmentThe single most important line in the document. These are the things that are holding the building together and are invisible to anybody who was not there when they were put in.
Areas closed or restrictedWith what is affectedSomebody will walk into it in the morning, and the report is the only thing standing between that person and a surprise.
Safety and incidentsAccidents, near misses, permits issued and closed, contractors on sitePermits issued and closed on the same line, because an open permit at the end of a shift is a handover item whether or not anybody thought of it that way.
For the next shiftItem, location, what to do, when, who and priorityWritten for somebody who was not here and does not know the building as well as you do. It is the section they will read first and often the only one.
The period in figuresJobs handled, closed, open, escalated, closure rate, hours and reactive shareReactive share is the number that describes the site rather than the shift. A week at seventy percent reactive is not a staffing problem being solved by a better report.
Temporary measures still in placeCounted, as a figure in its own rightRead across a week rather than a day. One is normal; five standing on Friday that were there on Monday means nothing is being closed out.
HandoverTwo signatures and a time, plus whether a verbal handover was givenThe time matters. A report signed at the end of a shift and a report signed an hour later describe different handovers, and only one of them happened in person.

The reason this document exists is that the most dangerous information on a maintenance shift is the information that lives in one person's head and leaves the site with them. Almost everything else is recoverable: a job that was not written up is still in the system, a reading that was missed can be taken again tomorrow, and a part that was not ordered will be ordered when somebody notices. Temporary measures are not like that. A valve chained shut, a breaker left off, a prop under a failing ceiling tile, a door wedged because its closer has gone, a hired pump sitting on the floor of a plant room: each of them was a sensible decision at the time and each of them is actively invisible afterwards. Nothing alarms, nothing is obviously wrong, and the building works. Three days later somebody finds a valve that is shut and no record of why, and the choices are to open it and find out, or to leave it and not know what it was protecting. Both are bad, and both are the direct result of a line that took fifteen seconds to write and was not written. The same logic applies, less dramatically, to the why column against every open job. A list of open jobs tells the next shift what is outstanding and nothing about what to do, so the first thing they do is rediscover why each one stopped, which is the single most wasteful thing a handover can cause. Waiting for a part that lands Thursday, waiting for a tenant to clear a room, waiting for dry weather and waiting for somebody to approve the spend look identical in a status column and require four completely different responses.

B. What it looks like filled in

One day shift on one site. The figures are ordinary and the two numbers that matter are not percentages.

LineValue
Jobs handled14: 11 closed, 2 open, 1 escalated
Closure rate79 percent
Labor hours8.5
Reactive jobs6 of 14, so 43 percent reactive
Plant out of service1
Temporary measures still in place2, handed over with 3 items

Seventy nine percent closure and forty three percent reactive is a perfectly normal day, and neither number is the reason to write the report. The two that matter are at the bottom: one item of plant out of service and two temporary measures still standing at the end of the shift. Those are the lines that cannot be reconstructed tomorrow from the job system, because the job system holds what was raised and closed, not what was improvised to keep the building running until it can be. Read on its own this is a good day. Read across a week it starts to say something else: if those two temporary measures are still on Tuesday's report, and Wednesday's, and they are the same two, then the site is not closing things out, and the closure rate of seventy nine percent is being achieved on the easy jobs while the awkward ones sit behind a temporary fix. That is the trend the template is built to expose, and it is why the period has to be picked once and kept. For the detail of any single job on this report, use the work order completion report, and for the register the jobs are drawn from, work order tracking.

Download the maintenance report template

Word for the version a shift lead fills in at the end of a period, Excel for the one that counts jobs by status and calculates closure rate and reactive share, with a Period Log that carries those figures across a month, and PDF for the copy that gets signed at handover. Free, and yours to rebrand.

Get the template

How do you write a maintenance shift report?

Write the handover section as though you will not be there to explain it. Six steps.

  1. State the period and keep it

    Shift, day or week, with the times covered and who was on. Changing period between reports destroys the only thing a run of them is good for.

  2. List the work with a status against each job

    Closed, Open or Escalated, spelled exactly that way. Hours against each, because the total is what makes the reactive share meaningful later.

  3. Give every open job a reason

    Waiting for a part, access, weather or a decision. Those are four different jobs and they look identical in a status column.

  4. Write down every temporary measure

    Overrides, props, isolations and hired equipment, with where they are. This is the line that cannot be recovered after the shift leaves.

  5. Record plant out of service and its effect

    And every alarm with what was done about it, including the ones that came to nothing, because a nightly repeat is a pattern.

  6. Write the next-shift section for a stranger

    Item, location, what to do, when and who. Then sign it, note the time, and say whether a verbal handover actually happened.

The isolation nobody wrote down is still in place. See how Atom AI assistants carry open jobs, overrides and handover items between shifts.
See Atom AI assistants

A shift report versus a monthly service report

Two documents that both summarize maintenance over a period, written for different readers, on different clocks, with different consequences for being wrong.

AspectThe shift reportThe monthly service report
Who reads itThe next shift, tonightThe client, at a review
What it is forContinuityAccount and evidence
Its most valuable lineTemporary measures standingPerformance against the agreement
How long it stays usefulAbout twelve hoursFor the life of the contract
What it costs to omitSomebody rediscovers itA disputed invoice
Written byWhoever was onWhoever runs the account

The confusion between these two is worth being explicit about, because they share a name and almost nothing else. A shift report is an operational document with a short half-life, written at the end of a period by the people who were on it, for the people coming on next. Its value is almost entirely in the exceptions: what is broken, what is improvised, what is isolated and what will become a problem in the next few hours. Twelve hours later most of it is of no further interest, and that is fine, because it has already done its job. A monthly service report is an account rendered to a client: planned work completed against what was contracted, response times against the agreement, spend, and the evidence behind all of it. It is read at a review by somebody deciding whether the contract is being honored, it is referred back to months afterwards, and its most valuable line is performance against what was promised rather than what is currently propped up. Keeping them separate matters practically as well as editorially. A shift report that starts reaching for monthly framing stops being read by the next shift, and a monthly pack assembled out of shift reports is full of operational detail no client wants and missing the contractual measures they do. Use the monthly service report for the second, and the work order completion report when the thing being closed out is one job rather than a period.

When the template starts to feel limiting

The file handles one period well. Four things get difficult as soon as there are twenty of them.

  • Temporary measures live in one report

    The list that matters is the one standing across a week, and on paper that means opening five files and comparing them by hand.

  • Open jobs are retyped every period

    A job open for four days appears in four reports, written out four times, with the reason drifting a little each time.

  • Closure rate and reactive share need totaling

    One report is an anecdote. The figure that describes the site is the month, and nothing adds it up unless somebody sits down to.

  • The handover depends on the report being read

    It is signed, filed, and nothing confirms the item about the isolated riser reached the person who needed it.

What running this in Facilio looks like

The handover does not change. What changes is that nothing has to be carried forward by hand.

  • Work Order Intelligence

    Open jobs carry themselves forward

    A job still open at the end of a shift is still open at the start of the next one, with its reason attached, rather than retyped into a second report.

  • Ops Performance Intelligence

    Temporary measures stay visible

    An override or an isolation is held against the asset until it is removed, so the ones standing all week surface on their own.

  • Audit Report Intelligence

    The period adds itself up

    Closure rate and reactive share across a month, which is the figure that describes the site rather than the shift.

  • Asset Intelligence

    Alarms accumulate against the plant

    The alarm that came to nothing three nights running is a pattern on the asset rather than three separate lines in three separate reports.

Hallucination-free by design. Atom AI answers from the records in your tenant rather than generating plausible text, so an empty field reads as empty rather than filled in for you.

Frequently asked questions

What is a maintenance report?

It is a period record for a site rather than a record of one job. This one covers a stated shift, day or week: work completed with a status, jobs still open with a reason, plant out of service, temporary measures, safety and a handover.

The closing paperwork for a single job is a different document, and so is the monthly pack a provider sends a client.

What should a maintenance shift report include?

The period stated explicitly and who was on, every job with a status of Closed, Open or Escalated, the open ones with a reason attached, plant out of service and its effect, and the alarms received.

Then temporary measures left in place, areas closed, safety and permits, the period in figures, and a next-shift section with an item, a location, an action and an owner.

Why do temporary measures matter so much?

Because they are the only information on the shift that cannot be recovered later. A job that was not written up is still in the system; an isolation that was not written down is invisible.

Three days later somebody finds a valve shut with no record of why, and the options are to open it and find out, or leave it and not know what it was protecting.

Why record a reason against every open job?

Because waiting for a part, waiting for access, waiting for weather and waiting for a decision look identical in a status column and need four completely different responses.

An open job with a reason attached is a handover. An open job without one is the next shift starting the diagnosis from the beginning.

Should this be daily, weekly or per shift?

Any of them, but only one of them. The template asks for the period to be stated and the point is to keep it, because a report that is daily on weekdays and weekly at weekends cannot be compared with itself.

The trend across reports is the only reason to write them up rather than talk, and a changing period destroys it.

What does the reactive share tell you?

How the site is actually being run, rather than how the shift went. A single day at forty three percent reactive is unremarkable; a month at that level is a planned maintenance problem.

It is the figure to take to whoever sets the budget, because it is the one that does not change because the team worked harder.

Is this the same as a monthly service report?

No. A shift report is operational, written for the next shift, and most of it is of no interest twelve hours later. That is not a flaw; it has already done its job by then.

A monthly service report is an account rendered to a client: planned work against contract, response times against the agreement, and the evidence behind both. Different reader, different clock, different consequences.

How many temporary measures is too many?

The number matters far less than how long the same ones have been standing. One on any given day is normal and often sensible.

Five on Friday that were also on Monday, and are the same five, means the site is not closing things out and the closure rate is being earned on the easy jobs.

In one paragraph

A maintenance report works when it covers one stated period and is written for the person coming on next. Give every job a status and every open job a reason, because waiting for a part and waiting for a decision look identical otherwise. Write down every temporary measure left in place, since that is the only thing on the shift nobody can reconstruct afterwards, and read the count of them across a week rather than a day.

Write it for the person who was not there

State the period, attach a reason to every open job, list every isolation and override, and write the handover for a stranger. Once open jobs are retyped each period, or the temporary measures standing all week only exist in five separate files, the paper version has reached its limit.

Maintenance Report Template Word · Excel · PDF