How to keep tenants informed during repair delays

A repair can be delayed for a valid reason and still become a poor tenant experience. The problem is often not one missed completion date. It is the period in which the tenant cannot tell whether the request is moving, forgotten, or waiting for them.

Useful repair communication does not require constant messages. It requires an update whenever the meaning of the wait changes, plus a reliable checkpoint when nothing has changed.

Give every open repair a next-update date

An open status is not enough. Record the date by which the tenant should receive the next message. This date can be earlier than the expected repair date.

For example, a specialist inspection may take two weeks to arrange. The tenant should not wait two weeks for any contact. Confirm that the request was sent, who remains responsible, and when the housing team will check the appointment status.

Use the next-update date as an operational promise. It should remain visible to the case owner and queue owner until the update is sent.

Explain the current waiting state

“In progress” can describe almost anything. A more useful status explains who or what the case is waiting for:

• waiting for tenant information;
• waiting for access confirmation;
• appointment requested from contractor;
• appointment scheduled;
• inspection completed, diagnosis pending;
• parts ordered;
• follow-up repair required;
• building investigation underway;
• ready for closure confirmation.

Do not expose unnecessary internal detail. The purpose is to show the next dependency and prevent staff from confusing a waiting state with inactivity.

Use a four-part update

Most delay updates can follow the same structure:

1. What changed: State the event since the previous message.
2. Current position: Explain what the request is waiting for.
3. Ownership: Name who is responsible for the next step or tenant contact.
4. Next checkpoint: Give the date or time of the next update.

Example:

The plumber inspected the leak this morning and found that a replacement valve is needed. The contractor is checking availability for the part. Sam remains responsible for your request and will update you by Friday at 12:00, even if the delivery date is not confirmed yet.

This message separates confirmed facts from an uncertain forecast.

Write differently for common delay types

The contractor has not confirmed an appointment

Do not imply that the tenant must chase the contractor unless your process explicitly requires direct scheduling.

We sent the request and access details to the contractor on Tuesday. An appointment has not yet been confirmed. We will follow up tomorrow morning and update you by 15:00.

A part is unavailable

State whether a temporary measure is in place and whether the issue remains safe.

The required control unit is on back order. The supplier currently expects delivery next week, but that date is not guaranteed. The temporary heating setting remains active. We will check the order again on Monday and update this ticket.

More investigation is required

Explain why another visit is necessary without blaming the previous worker.

The first inspection confirmed moisture but did not identify its source. A building specialist will inspect the exterior wall next. We have requested an appointment and will contact you by Wednesday with the next step.

Access prevented the visit

Record the facts neutrally and make rescheduling easy.

The contractor could not enter the home during today’s appointment. Please choose one of the new time windows below or reply with another suitable time. The request remains open.

Send updates when triggers occur

A fixed weekly update is useful for long cases, but event-based updates should happen sooner. Common triggers include:

• priority changes;
• owner or contractor changes;
• appointment requested, confirmed, changed, or missed;
• inspection completed;
• new safety advice;
• part ordered or delayed;
• repair split into additional stages;
• expected date missed;
• work reported complete;
• request linked to a building-wide incident.

Templates can improve consistency, but each message should include the actual next step and date. A generic “we are working on it” message adds little certainty.

Keep one history across channels

If the tenant calls after receiving an email, the employee answering should see the same status, promises, and contractor notes. Otherwise, the tenant may receive a different answer or have to repeat the full story.

This is one reason a case-based conversation works better than disconnected mailbox threads or personal messaging accounts. The comparison of WhatsApp for property management explains where informal channels create operational gaps.

Separate personal details from building updates

A leak inside one home may become evidence of a shared pipe problem. Keep personal information in the private request, then create a building-level incident for shared facts such as affected services, investigation status, access instructions, and the next update.

Residents should not see who first reported the problem or details from another home. The guide to building-wide repair communication shows how to connect the two levels safely.

Do not use communication to excuse unsafe delay

Updates are not a substitute for appropriate repair action. Priority, legal obligations, safety measures, and escalation must be handled according to the facts and applicable rules.

In the Netherlands, the Huurcommissie explains that tenants should report maintenance problems clearly and describes routes that may be available for serious unresolved defects (maintenance and defects guidance). Housing teams should ensure their own procedures and advice are current; this article is operational guidance, not legal advice.

Close the loop after the visit

When work is reported complete:

1. Record what was done.
2. Check whether another visit or monitoring period is required.
3. Tell the tenant why the request is ready to close.
4. Give a simple way to report that the original problem remains.
5. Link any recurring symptom to the previous history.

The complete tenant repair request process covers intake through closure, while maintenance request tracking explains the fields needed to keep delayed work visible.

Property manager communication software can keep each update, owner, attachment, and deadline on the same request. Sicket provides that focused workflow alongside existing property administration. Review the product overview or schedule a demo to see it in context.