Managing Difficult Tenants Within the Rules
Difficult tenants are managed with a process and a file, not with confrontation. Here is how to define the behaviour, record it, and escalate correctly.
Difficult tenants are managed with a process and a file, not with confrontation. The moment a manager starts describing a resident as a problem person rather than a pattern of dated behaviours, the situation becomes personal and the record stops being useful. Every step that follows depends on one discipline: turning complaints about a person into documented observations about conduct, impact and response.
That discipline is also self-protective. When a case reaches the owner, the insurer or a tenancy board, the manager who has dates, verbatim quotes and a consistent process is in a completely different position from one who has a folder of frustrated emails.
Key takeaways
- Define the behaviour, not the person: what happened, when, who saw it and what it prevented.
- Apply the same process to every household; inconsistency is the fastest way to lose a case and a reputation.
- Keep two files — the conduct record and the building record — and never mix opinions into either.
- Anything involving threats, weapons or immediate risk goes to police first and the paperwork second — critical
- The manager documents and escalates. Grounds for ending a tenancy are identified by the owner's lawyer or the tenancy board, never invented on site.
Why difficult tenants need behaviour, not labels
A difficult tenancy is one where a pattern of conduct creates cost, risk or distress that ordinary management cannot resolve. The conduct may be noise, aggression toward staff, repeated rule breaches, damage, an unsafe unit, or a refusal of access that blocks required work. What all of these share is that they are described in behaviours you can observe rather than traits you have inferred.
The distinction is not semantic. "Intimidating" is a conclusion. "On 14 March at 09:40, raised voice, stood over the desk, swore twice, refused to leave when asked" is an observation that can be acted on, shared with an owner and tested. Managers who record observations can hold a firm line; managers who record conclusions are exposed the first time someone asks how they know.
Most difficult cases have one root behaviour, not five. A noise complaint recurring every second weekend is a different problem from a chronic one, and the fix, the record and the escalation route differ. If the pattern is unclear, the complaint categorisation process surfaces it faster than another conversation. Difficult cases are the edge of a wider system — the routine side is covered in tenant relations in property management.
The four behaviours that need a process, not a reaction
Almost every case sits in one of four categories, each needing a first step, a record format and an escalation point agreed in advance.
| Behaviour | First step | What you record | Escalation route |
|---|---|---|---|
| Repeated noise or nuisance | Timed log of dates, duration and source | Entry per event with time, description and who reported it | Owner, for a formal notice process |
| Aggression toward staff or contractors | End the interaction, secure the area | Incident report with verbatim wording and witnesses | Manager, then police where a threat is made — critical |
| Damage or unsafe unit condition | Inspect with proper notice | Photos, area scores, dated inspection | Owner, plus fire or health authority where applicable |
| Repeated rule breaches (smoking, pets, occupancy, short-term letting) | Written reminder citing the rule | Case log showing the same steps as comparable cases | Owner, for a formal process |
Two things make this table work. The escalation route is decided in advance, so no one improvises at 11 p.m. And the recording format is fixed, so entries from different staff are comparable. If one manager writes "noise issue again" and another writes three timed entries, you do not have a case.
Why informal fixes make a difficult situation worse
The instinct with a difficult tenancy is to smooth it over: a quiet word in the hallway, an unrecorded promise, a favour granted to keep the peace. Three problems follow. The favour becomes a precedent other residents cite. The quiet word leaves no trail, so the next incident starts from zero. And the file now shows informal accommodation that contradicts the rules being enforced.
None of that means being rigid for its own sake. Managers should stay warm and flexible about solutions. The line is between flexibility on how a problem is solved and flexibility on whether it is recorded.
What a conduct file should contain
A conduct file is a factual log kept separately from the maintenance record. Six elements make it defensible.
- Date and time of each event, in local time, recorded the same day.
- What was observed or reported, in plain description, without adjectives about the person.
- Verbatim wording where language matters, in quotation marks.
- Who else was present, by role, so corroboration is possible.
- Impact, stated concretely: a resident who could not sleep, a contractor who declined to return, a work order that could not proceed.
- The building's response and the date it was communicated.
What the file should never contain: diagnoses, speculation about personal circumstances, notes about a resident's appearance, or summaries written weeks later from memory. The file is evidence for a future conversation you may not be in the room for.
How to hold the conversation without escalating it
Most difficult-conversation failures happen in the first thirty seconds, when the manager opens with a judgement or an accusation. Open with the record instead. "I want to talk about three noise reports on 2, 9 and 16 February" is factual and hard to argue with. "You've been disturbing the whole floor" invites a defence of character.
Four habits keep the meeting controlled. Sit at a table rather than across a desk where possible. State what happens next before the resident responds, so the shape of the conversation is set. Write down what they say while they say it. And end with a specific next step and a date. If the conversation becomes abusive, end it calmly and record that it was ended, with the reason — critical.
Where a resident arrives with a support person, an interpreter or a family member, accommodate that. It is normal practice and it usually improves the outcome; the access and entry protocols cover the same principle for entry to the unit, where advance notice and a clear reason reduce conflict more than any script.
When does a difficult tenant become a tenancy matter?
A situation becomes a tenancy matter when the conduct engages the lease or the province's residential tenancy legislation: a rule breach that persists, unpaid rent, damage, an illegal act, or interference with other residents' reasonable enjoyment. The manager's job at that point is to assemble the file and route it — not to decide whether grounds exist.
That routing matters because the test is legal, not managerial. Provincial legislation defines what counts, the notice periods and the evidence required; Ontario routes through the Landlord and Tenant Board and British Columbia through its Residential Tenancy Branch. The owner's lawyer or the tenancy body decides the ground and the process. "Four documented noise events, notices issued on these dates, no change" is a case; "being difficult" is not.
Escalate early enough that the file can still be improved. Handing a thin file to counsel a week before a hearing deadline is the most common way a legitimate complaint fails. The sequence from first report to formal step is set out in escalation and dispute resolution in buildings, and the routine that prevents most of these cases is in handling tenant complaints so they do not escalate.
Safety comes before process
No documentation objective justifies putting staff or contractors in harm's way. Three situations override the normal sequence — critical.
- A threat of violence. Leave, secure the area, call police, then write the incident report. Do not continue the conversation to "keep the peace".
- Weapons or an immediate danger. Police only. The tenancy process resumes afterwards.
- A contractor refusing to enter a unit. Accept the refusal, document it, and do not send staff in until the risk is assessed by someone qualified. CCOHS publishes guidance on preventing violence and harassment for workers who deal with the public, which is the frame to use when briefing staff.
Injuries and near misses also go through the occupational health and safety incident report; the conduct file supplements it.
Supporting the residents on the other side of the case
Most difficult-tenancy work involves a second household that is being affected. Those residents need three things: acknowledgement within a defined time, a statement of what the building can and cannot do, and notice when something changes. What they usually get is silence, because the manager cannot discuss another resident's case.
You can say what is being done without naming anyone: "We have received your reports, we have raised the matter through the building's process, and we will update you by 30 March." That is honest, protects privacy, and buys the time the process needs. Where the pattern affects shared areas — noise through a corridor, smoke in a stairwell, damage to a lobby — the building record should show it too.
Frequently asked questions
What counts as a difficult tenant?
A documented pattern of conduct that ordinary management cannot resolve: repeated noise, aggression toward staff, persistent rule breaches, damage or an unsafe unit. The label should describe behaviours you can date and describe, not a personality.
Can a manager evict a tenant directly?
No. A manager documents and escalates; the owner's lawyer or the provincial tenancy body determines whether grounds exist and what process applies. Changes to locks, service cut-offs or removing belongings are not manager tools and create liability. The only immediate override is a safety emergency, and that goes to police.
How many incidents justify escalation?
It depends on the conduct, not a fixed count. Noise usually needs a pattern with dates; a single credible threat needs immediate escalation. The useful test is whether the file shows the same behaviour recurring after a clear expectation was communicated.
Should we tell other residents what is happening?
Tell them what the building has done and when they will hear next, without identifying anyone or disclosing another tenancy's details. A short, dated update to affected residents is a standard part of the process and prevents the same complaint arriving twice a week.
What if the behaviour is caused by a disability or illness?
Do not assess it, and do not treat it as a reason to drop the process. Record only what you observed and route any accommodation request to whoever decides in your organisation with the owner's counsel.
Make the file the process
Pick the building with the most open conduct issues and rebuild one case from the dates up: events, records, communications, responses. Most cases improve the moment the timeline is visible, because the gap is usually in the middle — a notice sent, no follow-up recorded. NeatScore handles the building side: area-level inspections with APPA 1–5 scoring, photos per item, deficiency tracking with age, offline inspections that sync and branded PDF reports. Try it free for 14 days, or see pricing.
Not legal advice. What constitutes a breach, the notice required and the evidence a board will accept are set by provincial tenancy law. This article describes a manager's documentation and communication process only. Have the owner's lawyer or your provincial tenancy authority confirm any step that could affect a tenancy.
