How to Collect Maintenance Requests From Congregation Members

A tap drips. A fan rattles. A light above the stairs has been out for a fortnight. In almost
every place of worship, the way you find out is the same: somebody mentions it to somebody
else, after prayers, on the way out, and it either sticks in that person's memory or it does
not.

This is not a discipline problem. It is a design problem. Nobody is going to stop on their way
out of a service to open an app.

So the goal here is narrower than it first appears. You are not trying to change how people
report things. You are trying to make sure that what they already say lands somewhere it will
not evaporate.

Pick one place things land

The single most useful decision is choosing one destination for requests, and being boring
about it. It does not matter much what it is. A notebook kept in the office. A shared phone
number. A group chat. One column in a spreadsheet.

What matters is that there is exactly one, and that everyone who might receive a report knows
which one it is. Two places to look is the same as no place to look, because the thing you are
hunting for is always in the other one.

If your committee already runs a group chat, use it. The tool people are already in beats the
better tool they are not.

Give the message a shape

A verbal report is usually missing the two things you will need later: where, and who said it.
"The light is out" is not actionable in a building with forty lights.

Ask for three things, and no more:

1. Where — a room, a door, a floor. Specific enough for someone else to find it.
2. What — in the reporter's own words. Do not translate it into technical language.
3. Who — the name of the person reporting, so you can tell them when it is fixed.

Three fields is about the limit of what anyone will give you in a corridor. Asking for a fourth
gets you nothing extra, and often loses you the first three.

Write it down in front of them

This sounds trivial. It is the whole trick.

When somebody tells you about a problem, take out the notebook or open the chat and write it
while they are standing there. Two things happen. The report actually gets recorded, rather
than depending on you remembering it through the next four conversations. And the person can
see it being recorded, which is what stops them repeating it to three other committee members
over the following week.

Most duplicate reports are not people being difficult. They are people who have no evidence
that the first report went anywhere.

Close the loop out loud

A place of worship runs on goodwill, and goodwill is spent by silence. When something gets
fixed, tell the person who reported it. A sentence is enough.

This is the cheapest thing on this list and the one most often skipped. It converts a
congregation that feels ignored into one that keeps telling you useful things, which is the
only way you will ever hear about the small problems while they are still small.

A worked minimum

If you want the smallest thing that works, it is a notebook with five columns: date, where,
what, who reported it, and done. One line per problem. A page lasts a month in most buildings.

That notebook will outperform an elaborate system nobody updates, and it survives a change of
committee, which matters more than most people expect.

When the notebook starts to hurt

The notebook stops being enough at a fairly predictable point: when more than one person needs
to see it at the same time, when you start being asked what is still outstanding rather than
what happened, or when the building is large enough that "the light on the stairs" is
ambiguous.

At that point the honest options are a shared spreadsheet, or software that keeps the same
five columns while letting several people read them at once. Tools like Laksana work by
structuring what people already send in chat rather than asking them to file a ticket, which
is the constraint that matters in a building run by volunteers and visited by everyone.

Either way, the method does not change. Only the cost of keeping it up to date does.