How to Record That Maintenance Work Was Completed

In a commercial building, proof that work happened arrives by itself. Someone sends an invoice,
and the invoice is the record.

In a place of worship, a great deal of work is donated, done at cost, or done by a member of
the congregation on a Saturday morning. There is no invoice, so there is no record, and a year
later nobody can say when the roof was last looked at or who did it.

This matters in three ordinary situations: when a committee changes over, when something fails
and you want to know what was done to it last, and when someone asks — reasonably — what the
building's money and effort have gone on.

The smallest useful record

One line and one photo. That is the whole system.

• Date.
• What was done, in plain words. "Replaced the washer in the ablution area tap."
• Who did it. A name, even if unpaid.
• One photo of the finished work.

If you record nothing else for the rest of the year, record that. It takes under a minute and
it answers almost every question that will be asked later.

Photograph the finished state, not the process

People photograph the broken thing because that is when they think to take a picture. The
useful photograph is the one taken afterwards.

A picture of a repaired hinge, a cleared gutter, a new light fitting in place — that is the
one that answers "was this actually done". Take it from far enough back that the location is
recognisable. A close-up of a pipe could be any pipe in the building.

Where the work will be hidden afterwards, photograph it before it is covered. Nobody can
verify a pipe once it is behind a wall.

Attach the record to the place, not the person

The most common failure is that all this evidence lives in one volunteer's phone. When they
step back from the committee, the building's entire maintenance history leaves with them.

Wherever you keep the log — a folder, a shared drive, a chat group with a searchable name —
the test is: could a new committee member find last year's work without asking anyone? If the
answer is no, it is stored in the wrong place.

A shared folder with one file per year, named by year, is not sophisticated but it passes that
test.

Describe it so a stranger understands

Write the line for someone who was not there. "Fixed the thing in the back room" is a note to
yourself, and it will be useless to you within a month.

Two details make a description durable: the location and the component. "Replaced the flush
valve in the second washroom cubicle, left side" will still mean something in five years. So
will "cleared the gutter along the north wall".

When money changed hands, keep the number

Donated work still often involves bought parts. Record what was spent, even roughly, and keep
the receipt with the log rather than in a separate box of receipts.

This is not about accounting rigour. It is that the question "what does this building cost to
keep running?" is unanswerable unless the small amounts are captured, and the small amounts are
most of them.

Review it once a year, out loud

Sit down with the log once a year before you set a budget. Read through what happened. Two
things fall out of that reading almost every time: a pattern of small repairs on one item that
is telling you something is failing, and a realisation of how much unpaid effort the building
is absorbing.

Both are findings worth having, and neither is visible from inside any single month.

When a shared folder stops being enough

The folder starts to strain when several people need to add to it from their own phones, when
you want to find everything done to one item rather than everything done in one year, or when
the volunteer who files things stops doing it.

That is the point at which structuring the record automatically — capturing the photo, the
date and the location as the message is sent, which is how systems like Laksana approach it —
saves more effort than it costs. Before that point, a folder and a habit will serve you
perfectly well.