Tenant communication
How to communicate planned building maintenance to tenants
Use a practical checklist and message structure to communicate planned building maintenance clearly before, during, and after the work.
Planned maintenance gives a housing team something unexpected repairs do not: time to prepare residents. That advantage is easily lost when the notice is vague, sent too late, or split across several channels.
A useful maintenance message tells residents what will happen, how it affects them, what they need to do, and when they will hear from you again. It also gives staff one published source to update if the schedule changes.
Confirm the operational facts first
Before drafting the announcement, collect:
- the purpose and scope of the work;
- affected building, entrances, floors, or units;
- start date, working hours, and expected completion;
- interruption to water, power, heating, access, lifts, parking, or shared spaces;
- actions residents must take;
- access arrangements for private homes;
- contractor contact route for staff;
- internal owner for resident questions;
- contingency if the schedule changes.
Do not publish a precise promise when the contractor has only provided an estimate. Clearly label what is confirmed and what remains subject to change.
Write the title for recognition
Residents scan messages quickly. The title should identify the affected service or place and the date.
Prefer:
Water interruption on Tuesday, 8 September, 09:00-13:00
Avoid:
Important maintenance information
The first title lets someone understand the relevance from an email subject line or announcement list.
Use a predictable message structure
A planned-maintenance announcement can follow this order:
- What is happening: explain the work in plain language.
- When: give dates, working hours, and the expected interruption window.
- Where: name the affected buildings, entrances, floors, or units.
- Resident action: explain preparation, access, parking, or safety steps.
- What to expect: mention noise, contractor presence, or temporary routes.
- Next update: say when and where changes or completion will be published.
- Help route: tell residents how to ask a private or accessibility-related question.
Example planned-maintenance notice
Water interruption on Tuesday, 8 September, 09:00-13:00
A contractor will replace a valve in the central water installation at Riverside Tower. Water will be unavailable throughout the building from 09:00. We expect service to return by 13:00.
Please store the water you need before 09:00 and make sure all taps are closed during the interruption. The contractor will work in the ground-floor service room and does not need access to individual apartments.
We will update this announcement by 12:30 if the work is taking longer than expected. When service returns, brief discoloration may occur; let the cold tap run until the water is clear. Contact the housing team through a personal ticket if you need help preparing for the interruption.
Adapt the operational instructions to the actual work and local requirements. Do not reuse a generic safety instruction without confirming it with the responsible technical team.
Choose audiences deliberately
Send the announcement only to affected residents, but do not make the audience so narrow that relevant people miss it. Consider tenants, building staff, landlords, reception teams, and contractors separately.
Private access appointments belong in personal communication, not in a building-wide notice. General progress belongs in the shared announcement so staff do not have to answer the same question repeatedly.
This audience separation is a core capability to examine when choosing property manager communication software.
Coordinate channels around one source
Email, SMS, a lobby notice, or WhatsApp reminder may all be useful delivery methods. They should point to one maintained announcement rather than becoming separate versions of the truth.
If the schedule changes, update the source and redistribute the change. Include the updated time visibly. Our WhatsApp property management guide explains how chat can remain a signpost without becoming the maintenance record.
Communicate during the work
Publish an update when the work starts if the impact is substantial. If the team has promised a checkpoint, update residents at that time even when the expected completion has not changed.
When a delay occurs, state:
- what changed;
- the new estimate, if one is confirmed;
- what residents should do;
- when the next update will follow.
Avoid blaming contractors in a public notice. Residents need the current operational position and the next action.
Close the communication loop
When work finishes, confirm completion and mention any relevant next steps. If the maintenance revealed another problem, separate that follow-up from the completed work so residents can understand what is resolved and what remains open.
Store the final announcement with the maintenance record when your organization requires it. Review questions received during the work and turn stable answers into knowledge for the next project. This is one practical way to reduce repeated tenant questions.
Sicket supports building-scoped announcements, scheduled publishing, email previews, tickets, and shared incidents in one communication workflow. Explore the Sicket product or schedule a demo to see how planned updates connect to resident requests.
