Resources · Guide · 4 min read

Managing 20 buildings without losing control

Six principles for growing: single entry, same process, shared vendors, tiered delegation, simple indicators and reports that build themselves.

You do it by standardizing, not by working harder: one place of entry, the same process in every building, shared vendors, tiered delegation and simple indicators.

Managing twenty buildings with the same team that once managed five isn't achieved by working harder, but by standardizing. Growth breaks property management companies for the same reason: every building has its customs, every request arrives through a different channel and the information lives in the head of whoever handles each account. This guide proposes six principles for growing without losing control, with practical examples you can apply without changing your team.

1. A single place of entry

If requests arrive by calls, personal messages and emails, your team spends the day sorting instead of solving. Define a single channel per building and tell every tenant. Each request is born with a date, building, unit, description and, if possible, a photo. What doesn't come in through there is kindly redirected.

2. The same process in every building

The same flow — receive, sort, assign, quote if needed, schedule, close with confirmation — should apply in all twenty. Real differences (one building with a doorman, another with no elevator) fit inside the same process as data, not as different procedures. When every building works the same way, anyone on the team can cover for anyone else.

3. A shared vendor directory

Gather the vendors of all your buildings into one directory, with two options per trade, areas covered, agreed rates and a performance record. Vendors serving several buildings give you better terms and the slowest ones become obvious. Set approval thresholds by amount so not everything has to pass through you.

4. Delegate in tiers

Move from "everything goes through me" to three tiers: what each manager decides without asking, what needs your sign-off and what goes to the board. Write it down. With clear limits, your team resolves things faster and you focus on exceptions.

5. Simple indicators, reviewed every week

You don't need a complex dashboard. Four numbers are enough: open requests per building, first-response time, requests older than ten days and spending against budget. Reviewing them every week in fifteen minutes shows you which building is slipping out of control before the board complains.

6. Reports that nearly build themselves

Every building has a board waiting for its monthly report. If data is recorded during the month, the report is a compilation; if it's gathered on the last day, it's hours lost multiplied by twenty. Define a fixed report structure and feed the data from day one.

Signs you're at the limit

  • Your team lives putting out fires and there's no time to prevent them.
  • Boards learn about problems before you do.
  • Answers depend on who handled it.
  • When someone is out, an account stops.

If you recognize two or more, you don't need to hire right away: you need process and a single place where the information lives.

Protect quality as you grow

Growing shouldn't mean service turns impersonal. A clear notice at each stage, a close with confirmation and respectful treatment make tenants feel they matter. What should become automatic is the repetitive work; attention to delicate matters remains with people.

A ninety-day plan

In the first month, define the single channel and the standard process, and migrate two or three pilot buildings first. In the second, gather vendors into a directory, set approval thresholds and begin measuring the four indicators. In the third, extend the process to the rest, refine it with what you learned and build the fixed structure of the monthly report. At the end of ninety days, you'll have a baseline to decide whether you need more people or just a better process.

A frequent mistake: copying the way of working of the hardest building

When a building gives trouble, it's tempting to design the process around it and apply it to all, which drowns the others in paperwork. Design for the common case and treat exceptions as exceptions, with their own route. Review the standard process once a quarter with the whole team: the people closest to the work spot what needs to change before it becomes a problem.

How TriDot does it

In the property managers edition, each building has its portal and all share one flow: the tenant reports to Dot on WhatsApp with a message or a photo, Dot records and follows up, vendors respond from their portal, quotes are compared in one place and the monthly report is built from the period's figures. You see all twenty buildings and decide what needs your judgment: Dot does the repetitive work, you decide.

Meet the property managers edition or book a 30-minute call and we'll go over how your buildings would scale.

Frequently asked questions

Quick answers

Do I need to hire more people?

First you need process and a single place where the information lives; then evaluate.

Which indicators should I follow?

Open requests per building, first response, requests older than ten days and spending against budget.

How do I avoid losing the personal touch?

Automate the repetitive and leave the delicate to people, with clear notices at each stage.

Want to see it together?

Book 30 minutes by video call and we'll show you TriDot, and Dot at work, with cases like yours. You pick the day and time.