The starting point

A communication plan your property team can use

Build a practical landlord–tenant communication process with clear contacts, useful updates, accessible channels, and a reliable handoff.

Good property communication answers the next question before someone has to ask it. What is happening? Does it affect me? What should I do? When will I hear more? A simple process makes those answers consistent even when different people are handling the issue.

Give each kind of request a clear route

Separate routine maintenance, urgent problems, leasing questions, and account questions. Publish the right contact for each, the hours it is monitored, and what to do outside those hours. Do not make a general inbox look like an emergency response service.

Keep the same contact information on the property website, welcome material, posted information, and staff instructions. Assign one person to update those places when a phone number, provider, or responsibility changes.

Keep the issue in one record

Record when it came in, the location, the issue, who owns the next action, and when an update is due. A text can alert someone to a change, while the service record holds the full history. If a conversation moves to a phone call, add the outcome to the record.

Promise the next update you can deliver

Use specific update times rather than promises you cannot support. “We will update you by 3 p.m.” can be more useful than an unconfirmed repair estimate. If the work is still waiting on a contractor, say so and give the next check-in.

Plan for the people receiving the message

Ask about preferred contact methods and language needs. Use readable text alongside diagrams or posted notices, and provide another way to reach the team. The Department of Justice’s effective communication guidance is a reference for considering communication disabilities and appropriate aids or services.

Close the loop

Before closing a request, record what was done, whether follow-up remains, and how the tenant should report a continuing problem. At a shift change, hand over open issues with the next action and the promised update time.

Build a communication checklist