When the Tenant Is Not Your Customer but Is Your Problem

Why this matters

On a managed property the person standing in front of your tech is not the person who hired you, is not the person who pays you, and cannot approve a single thing you are about to do. Your tech's instinct, built over years of residential work, is to treat whoever opens the door as the customer: explain the problem, quote the fix, take the go-ahead. Every one of those reflexes is wrong here, and the cost of getting it wrong is not a bad review. It is a manager who now has to walk back a price the tenant heard, an owner who was told something the manager never said, and a shop that has volunteered itself as a witness in somebody else's dispute.

This card is mostly about what you deliberately leave out of the tenant conversation. The list of things you do not say is shorter to teach, easier to enforce, and does more good than any script of things you should say.

The three-party split, stated precisely

• The owner carries the asset and the money. They approve spend, and they usually never meet you.
• The manager carries the relationship, the schedule and the authority to spend up to a limit somebody else set. They hired you and they are the one you report to.
• The tenant carries the consequence. They live with the fault, the noise, the wet carpet and your arrival time, and they have essentially no authority over any of it.

Every awkward moment on a managed property traces to one of those three trying to act in another's lane, and most often it is the tenant, because the tenant is the only one physically present.

What the tenant genuinely controls

Short list, and worth teaching because techs habitually give the tenant either too much authority or none at all.

• Physical access. Their door, their time window, their pets contained, their belongings moved. This is real authority and it is total.
• The symptom history. They are the only source for when it started, what it does at night, what makes it worse. Treat this as evidence, not opinion.
• Their own property. You do not move, unplug, disconnect or relocate a tenant's belongings without asking them, even when the manager told you to.
• Whether they are comfortable with you in the unit alone. If they want to stay in the room, they stay in the room.

That is the whole list. Nothing on it involves scope, price, timing across visits, or whether a repair happens.

The exclusions, and why each one earns its place

This is the load-bearing section. Each item is something a competent, well-meaning tech will say by default, and each one has to be trained out.

Price, in any form. Not the number, not a range, not "this is usually a couple hours of labor," not "that part is not cheap." The tenant is not paying, so any figure they hear is pure liability: it travels to the manager as a quote, to the owner as a commitment, and back to you as a ceiling you never agreed to. The one legitimate answer is that pricing goes to the office and the manager will have it.

Whether the work will be approved. "They will definitely fix that" and "honestly they should have replaced this years ago" both put you on record predicting somebody else's decision. When the owner declines, the tenant now believes the contractor said it was necessary and the landlord refused, and the manager gets to referee a fight you started.

Blame and fault attribution. Whether this is the last contractor's error, the owner's deferred maintenance, or the tenant's own use. Fault determination on a managed property has money and sometimes a security deposit attached, and it belongs in your written report to the manager, phrased factually, not in a hallway conversation. Your findings do not change. Your audience does.

Lease interpretation. Who is responsible for the filter, the bulb, the drain, the yard. You have not read the lease, leases differ on exactly these items, and being confidently wrong about it is the fastest way to be quoted in a deposit dispute.

Scheduling commitments beyond today. "I will be back Thursday" is a promise the manager did not authorize and may not be able to fund. The correct form is that you will report today's findings and the office schedules from there.

Comparative commentary on the property or the manager. "This building is a mess," "your management company never approves anything." Techs say this to build rapport. It reads as agreement with a grievance, and it gets repeated verbatim.

Anything about another unit. What you found next door, who else is complaining, whether the neighbor's problem is the same. Beyond the plain awkwardness, on a shared system you may be handing one tenant a theory about another tenant's behavior.

Notice what is not on the exclusion list: the technical facts of what you found in that unit. You can and should tell the tenant what you did today, what you found, what you turned off and why, and what they should do or avoid until somebody comes back. Withholding that turns a reasonable boundary into stonewalling, and it is the single most common overcorrection after a shop first teaches this list.

The duties you owe the tenant anyway

None of these come from a customer relationship. They exist because a person lives there.

• Tell them what you shut off and what that means for them tonight. If the water heater is isolated or a circuit is off, they need to hear it in plain words, from you, before you leave.
• Tell them what is unsafe to use and what to do instead. Specific and immediate: do not use that outlet, keep the door to that room closed, do not run that appliance until somebody comes back.
• Leave the unit no worse. Drop cloths, boots, tools accounted for, doors and windows as you found them, nothing hot or sharp left within a child's reach.
• Be straight about timing. "I do not know when they will approve it" is honest. "Soon" is not.
• Never discuss them by name in a shared space. Hallways, laundry rooms and elevators carry.

The one exclusion that reverses

Every rule above bends completely around an immediate hazard, and the reversal is total: on a hazard you speak to the tenant first, directly, before any call to the manager.

If you smell gas, everyone leaves the building immediately, nothing is switched on or off, no lights, no phone used inside, and the call to the gas utility emergency line is made from outside and upwind. If there is water reaching energized equipment, wiring or a panel, nobody touches the equipment or stands in the water, power is cut at the point of supply if it can be reached from a dry position outside the affected area, and the tenant is moved out of that area now. If a carbon monoxide alarm is sounding, everyone leaves for fresh air and the fire department is called from outside, before anyone tries to determine whether it is a false alarm.

You do not wait for the manager to authorize telling a tenant that their unit is not safe to be in. The manager call comes second, and it comes from outside the building.

Worked example: a portfolio's complaint rate, before and after the list

A shop working nine managed properties tracked tenant-facing visits and manager complaints for one quarter. 64 visits produced 7 complaints, which is about 11% of visits.

Reviewing all seven with the techs who ran them, five traced directly to a sentence that falls in the exclusion list: two price statements ("that compressor is not going to be cheap"), two fault statements ("whoever installed this did it wrong"), and one lease interpretation ("filters are on you, not them"). The remaining two were scheduling: a tech who said he would return the next day and did not.

The shop printed the exclusion list on the back of the work-order card, walked it through one huddle, and ran it as the only change. The following quarter: 71 visits, 2 complaints, about 3%. Complaints fell from roughly 11% of visits to roughly 3%.

The honest part of that result is in the two that remained. One was a scheduling promise again, and one was a price statement - the same category the list was written to eliminate, from a tech who had been in the huddle. The list moved the rate down by a large margin, it did not close the category, and a shop that reports this as "we solved it" will stop reinforcing the one control that produced the improvement. The five-to-two split also says something useful about where to spend coaching time: price and fault were the two heaviest categories going in, and price survived.

Where the exclusions leak

They leak in three predictable places, and none of them is the front door.

On the way out, at the truck. The formal part of the visit is over, the tech relaxes, and the tenant follows him out to ask the real question. This is where price and approval predictions get made.

In a text thread the tenant started. A tenant who has the tech's cell number is a standing exception to every rule above, because text feels informal and is permanently quotable. Tenant contact belongs on office channels.

Through a second tech. The tech who ran the exclusion list correctly on visit one gets replaced on visit two by somebody who never saw the file. Access and communication history has to live on the property record, not in one person's head.

How to verify you got this right

Pick your three most recent managed-property complaints and ask one question of each: was there a sentence from your side that fell in the excluded list. If the answer is yes on two of three, the problem is training, not personalities, and it is fixable in one huddle.

Then read your own written report to the manager on a job where fault was in question. It should contain the fault finding, clearly and factually, because your manager needs it. If your report is as vague as your hallway conversation was, you have not applied the exclusion list, you have just gone quiet, and you have made yourself less useful to the person who actually hired you.

References

• See related: Property Manager vs Tenant: Who Decides Decision Tree
• See related: How to Handle a Tenant Who Refuses Access
• See related: The Shared System: Multiple Tenants, One Cause
• NFPA 72, National Fire Alarm and Signaling Code, which carries the carbon monoxide detection requirements formerly published as NFPA 720
• Gas utility emergency response guidance, evacuate-first procedure for suspected leaks