A maintenance update should answer the resident’s next question.

Acknowledge the report without inventing a diagnosis

A resident reports a problem and receives a message saying it is being handled. That may confirm receipt, but it leaves several questions unanswered: was the issue understood, who is responsible and when will there be an update? Begin with the report reference, a concise description and the next action. Do not state that a component has failed before a competent person has assessed it. Urgent or potentially unsafe situations should follow the building’s established escalation procedure immediately; a communication template must never become a reason to postpone the appropriate emergency response.

Use statuses that describe real work

Use a small set of statuses with operational definitions. Received means the report exists. Assessed means an appropriate person has reviewed it. Scheduled means access and attendance have been arranged. Awaiting a part means a specific dependency remains. Work completed means the task has been performed; verified means the agreed check has also occurred. Adapt these terms to the actual operation rather than creating a dashboard the team cannot maintain. The resident-facing wording should remain plain. A status that sounds reassuring but has no evidence behind it cannot help someone plan their day.

Promise an update you can control

Distinguish the next update from the repair completion date. A manager may be able to commit to an update tomorrow while a supplier has not confirmed delivery of a required part. State that difference clearly. Record the update owner and trigger a follow-up when that promise is approaching. Do not keep moving an estimated completion date without explaining what changed. An honest message can say that diagnosis is complete, the part is being sourced and the next update will follow at an agreed time. It should not suggest progress that no one has verified.

Explain disruption and access

Before attendance, explain the expected access arrangement and any known effect on the resident’s use of the space. Confirm who will attend through the building’s approved process, what permission is needed and how the appointment can be changed. Avoid circulating keys, access codes or unnecessary personal details in an open team chat. For planned building work, use the relevant professional assessment and operating procedure. RICS guidance on planned maintenance emphasises organised inspection and reporting for built assets; it does not make this communication checklist a technical diagnosis or a maintenance specification.

Verify completion with evidence

Closing a ticket should reflect the agreed completion test, not only the contractor’s departure. Record the work carried out and the result of the appropriate check, with photographs or other evidence where suitable and permitted. Explain any operating instructions through the competent person responsible. Invite the resident to report a continuing issue through the same reference so the history remains connected. Do not ask someone to certify technical work they are not qualified to assess. Where a follow-up check is required, give it a named owner instead of hiding it inside a completed status.

Learn from the communication gaps

Review the gaps between actions and messages. Count missed promised updates, repeated requests for status and tickets reopened after closure, using consistent definitions and periods. These are operating signals, not proof that communication alone caused a change in resident satisfaction or repair speed. Look at a few cases from end to end and ask which information was unavailable at the moment it mattered. Adjust the workflow or ownership before adding another automated message. The goal is a record that helps the resident understand the situation and helps the team take the next responsible action.