A One-Page Format to Report Building Maintenance to a Mosque Committee

Committees meet occasionally, sit for an hour, and have a great deal to get through. A
maintenance report that runs to five pages will not be read, and a verbal summary from memory
will be argued with.

What works is one page, the same shape every time, filled in from whatever records you already
keep. The sameness is doing real work here: once people recognise the format, they stop reading
it from scratch and start comparing it to last time, which is where the useful questions come
from.

The five blocks

1. What was completed since we last met. A list. Date, what, who. Five to ten lines is
normal. This block exists to make effort visible, and in a building run on goodwill that is not
a vanity exercise.

2. What is still open. The same list, for things not finished, with one extra column: how
long it has been open. That column is the single most useful number on the page, and it is the
one most reports leave out.

3. What it cost. Total spend since the last meeting, then the three or four largest items
individually. Not a full ledger — that belongs with the treasurer. Enough that nobody is
surprised.

4. What is coming. Anything known to be needed in the next few months, with a rough figure
where you have one. This is where a committee gets the chance to decide rather than react.

5. One thing we should decide today. A single question, phrased so it can be answered in
the meeting. "Do we pay someone to clear the gutters, or keep asking for volunteers?"

That last block is what turns a report into a decision. Without it, maintenance is a standing
item that gets noted and never resolved.

Show ageing, not volume

The instinct is to report how many requests came in. It feels like the measure of activity.

It is the wrong number. A committee cannot act on "we received eleven requests". They can act
on "three things have been waiting more than two months, and here they are".

Sort the open list oldest first. The top of that list is the agenda, every time, and it takes
no analysis to produce.

Keep the same page

Resist the urge to improve the format each time. A report that changes shape forces everyone to
re-learn it, and quietly hides trends — you cannot see that spending has doubled if the
spending block moved and changed units.

If the format genuinely needs changing, change it once and say so at the top.

Write it from the log, not from memory

If you keep the kind of running log described elsewhere in this pathway, this report is an
extraction rather than an essay. Open the log, copy the completed lines into block one, the
unfinished ones into block two, add the money, and you are done in under twenty minutes.

If writing the report takes longer than that, the problem is usually not the report. It is that
the underlying record does not exist and you are reconstructing it each time, which is both
slow and unreliable.

Send it before, not during

Circulate the page a few days ahead. A committee that has read it arrives with questions; a
committee handed it at the table spends the item reading in silence and then approves whatever
is in front of them.

You will also get corrections in advance, which is much less uncomfortable than getting them in
the room.

Keep every one

File the reports in order. Four of them side by side will tell you things no single one can:
which items keep reappearing, whether the open list is growing, whether spend is drifting up.

That series is also the handover document for the next committee. It is far more useful than a
briefing, because it shows the building's actual pattern rather than one person's summary of
it.

When assembling the page from the log starts to eat an evening, that is the signal to let a
system produce it — a report built automatically from work already recorded removes the step
where a tired volunteer transcribes a month of activity by hand.