From repair report to resolution.

The repair itself is only part of the job. Someone reports it, someone contacts a contractor, and someone else asks whether anything has happened. Without a shared record, the same question starts again each time.

Start with a useful report

A useful report gives the next person enough information to act. Record the exact location, describe what has changed and add a photo if it is safe to do so. Check whether the issue already has a record before opening another one.

Keep the original report and later updates together. It makes repeat problems easier to recognise.

Give it a clear owner

An owner is the person responsible for moving the repair forward. They might contact a contractor, gather information or confirm the next appointment. Make that responsibility visible.

Separate "who is following this up?" from "who is doing the work?" A resident can coordinate a repair without carrying it out.

Peace of mind starts with knowing what happens next.

A clear owner. A clear next action. A clear next update.

Make updates predictable

"In progress" is a start, but it leaves people guessing. Pair the status with the next action and a date for the next update. If there is no change, say so — and explain what you are waiting for.

A short, consistent update is easier to understand than a long thread. Use the same three fields each time:

• Status — e.g. Contractor booked
• Next action — e.g. Alex meets them on Tuesday
• Next update — e.g. Tuesday, by 5pm

Close the loop

When the work is finished, record what was done and whether the reported issue has been resolved. Attach relevant photos, invoices or contractor notes to the same record.

That history is useful the next time something goes wrong, when you plan maintenance, or when someone new takes over the building admin. See also a building handover without the gaps.

Try this with one open repair

Can you find its owner, next action and next update without asking someone? If one is missing, that is a useful place to start.