Ask any property manager how they handle a vendor problem and you'll hear some version of the same answer: "I'll email them." A missed visit, a quality complaint, a scheduling conflict — email is the default instrument for almost everything, because it's fast, it creates a paper trail, and nobody has to pick up the phone.
It's also how accountability quietly disappears across a portfolio, one unanswered thread at a time.
Email is a record. It is not a system.
An email proves you said something. It doesn't prove the vendor acted on it, and it definitely doesn't surface the pattern if the same vendor is quietly dropping the ball the same way at three different buildings. Each incident lives in its own thread, in its own inbox, usually belonging to whichever building manager happened to notice it that week. Nobody at the portfolio level is reading all of those threads together, because nobody could — there's no shared view, just a scattered archive of individually reasonable decisions that never add up to a pattern anyone can act on.
That's the actual cost. Not that email is slow or unprofessional — it's that email has no memory beyond the one conversation it's in.
What email can't do
It can't tell you a vendor's response time is getting worse across the portfolio. It can't flag that the same complaint has come up at two buildings in the same month. It can only tell you what happened in the one thread you're looking at, right now.
The vendor learns the real rules fast
Vendors figure out quickly whether "we'll email them" actually has teeth. If an email about a missed visit gets a brief apology and nothing else — no documented record a building owner would ever see, no effect on the relationship, nothing that follows the vendor to their next contract review — it stops functioning as accountability and starts functioning as a formality. The vendor isn't being malicious. They're responding rationally to the actual incentive structure, which is: handle the one person who emailed, and the problem goes away.
Across a single building, a hands-on manager can sometimes compensate for this through sheer persistence. Across a five- or ten-building portfolio, persistence doesn't scale. The manager at building three doesn't know the manager at building one already had this exact conversation with the same vendor six weeks ago.
What a real record actually requires
Fixing this isn't about writing sterner emails or cc'ing more people. It requires three things email structurally can't provide on its own:
- A record tied to the vendor, not the inbox. Every issue with a given vendor should be visible in one place, regardless of which building or which manager logged it.
- Visibility the vendor knows exists. A vendor who knows their track record is visible at the portfolio level — not just to whoever emailed them that day — behaves differently than one who knows each complaint dies in a single inbox.
- Something that survives staff turnover. When the building manager who "always handled" a particular vendor relationship leaves, the informal knowledge about that vendor's real reliability shouldn't leave with them.
This is what portfolio-wide accountability actually looks like.
Every vendor interaction, every building, in one record — not scattered across a hundred separate inboxes.
Email still has a place — just not this one
None of this means email is the wrong tool for everything. It's fine for routine coordination, for scheduling a walkthrough, for the hundred small logistics a building actually runs on. The failure mode is specifically using it as the system of record for vendor accountability — the thing you'd point to if a board member asked "how do we actually know our vendors are performing." If the honest answer is "we'd have to go search a few inboxes," that's not a record. That's hoping nobody asks.