A multi-site maintenance program applies one scope, one reporting format and one escalation path across every location, backed by a shared asset registry and a single point of contact. Routing groups nearby sites into efficient service runs, and consolidated reports let you compare locations. Onboarding each new site follows the same steps: survey, tag, baseline, schedule and review.
- Standardize the scope, the checklists and the report format first. Sites will differ in equipment, but the way you describe and measure them should not.
- An asset registry is the foundation. Without a complete, tagged list of equipment, you cannot schedule, budget or compare.
- One named point of contact at the contractor, and one for your team, prevents the classic multi-site problem of nobody owning the issue.
- Routing and service territory matter. Sites clustered along the same freeway corridors can be served together, while distant sites need their own planning.
- Consolidated reporting is useful only if the underlying records are consistent. Comparing sites needs comparable data.
Why portfolios need a different kind of program
Running maintenance for one building is a matter of attention. Running it across twelve, or forty, is a matter of structure. The temptation is to let each site manager hire a local vendor and handle their own problems, which feels flexible until you try to answer a simple question: which of our sites has the most refrigeration emergencies?
Without a common structure, the answer is spread across inboxes, invoices in different formats and the memories of individual managers. With one, it is a report. The purpose of a portfolio program is to make the whole group legible, so decisions about repair, replacement and budget are based on comparable information.
The same logic applies whether the portfolio is a set of retail stores, a group of medical offices, a chain of restaurants or a mix of managed properties. The details differ, as in restaurant multi-unit service or office and property manager contracts, but the underlying structure is the same.
What to standardize and what to leave local
Standardization does not mean pretending every site is alike. A coastal store and an inland warehouse have different needs. It means agreeing on the framework while allowing the content to vary.
| Standardize across all sites | Allow to vary by site |
|---|---|
| Scope structure by asset class | Which asset classes are present |
| Checklist format for each class | Frequency, based on duty cycle and environment |
| Report layout and finding categories | Access rules, hours and security procedures |
| Approval thresholds and how repairs are quoted | Local code or permit differences |
| Escalation path for urgent calls | Local contact on site |
| Asset naming and tagging convention | Equipment brands and ages |
| Review meeting format and cadence | Seasonal timing influenced by local climate |
A good starting point is the contract basics in commercial HVAC maintenance contract scope of work and the terms in maintenance contract terms, response times and exclusions. Write them once at the portfolio level and attach site schedules to them.
Single point of contact and escalation
Multi-site programs fail quietly when responsibility is blurry. A store manager sees a warm cooler, calls the number on a sticker, and the call enters a queue no one owns. A clear escalation path fixes that.
- One account contact at the contractor who knows the portfolio, the contract and the history, and who can answer questions about any site.
- One program owner on your side who approves scope changes and resolves disputes.
- Site contacts who can give access and describe symptoms, but are not expected to make technical or financial decisions.
- A written escalation ladder for urgent calls, with phone numbers and what information to have ready.
- A rule for approvals, such as which repairs a site manager can approve on the spot and which need the program owner.
Because Davinci's mechanical, refrigeration and controls work is performed by its own UA Local 250 crew with no subcontractors, the account contact is coordinating one team rather than a chain of vendors. That makes it simpler to know who was on site and who is responsible for the follow-up.
Routing, territory and honest limits
Southern California portfolios are shaped by its freeways. Sites along the 5, the 55 or the 91 can often be grouped into a logical service run. Sites on opposite sides of the region cannot. Good program design starts with a map and a candid conversation about where service is practical.
- Cluster by corridor. Group sites that sit near each other so scheduled visits are efficient.
- Plan around traffic and access. Some sites have loading dock windows, security check-ins or mall rules that affect when a visit can occur.
- Separate scheduled from urgent. Scheduled routes can be planned. Urgent calls cannot, and the agreement should say how they are handled.
- Be clear about geography. Davinci's home base is Orange County. Larger commercial, public and bid work extends into Los Angeles County, the Inland Empire, San Diego County and Ventura County, but Davinci does not have offices or yards outside Orange County. Talk through how sites far from Orange County would be handled before you commit.
Portfolios that spread beyond a service area sometimes use more than one contractor. In that case the standardization work becomes even more important, because the reports from different contractors need to be comparable. Insist on the same finding categories and the same asset naming across vendors.
The asset registry
Everything else depends on knowing what you own. The registry is the list of every piece of covered equipment at every site: type, make, model, serial number, location, install year if known, capacity, refrigerant type where relevant, and what it serves.
In the DaVinci Portal, each asset in the registry receives a QR-coded label and its own record. Service history, readings and photos accumulate under that record. Sites roll up into a portfolio view without anyone having to merge spreadsheets. A registry built carefully at the beginning pays off every time a question comes up later.
The registry also answers practical questions. How many units of this make are at end of life? Which sites have R-22 equipment still in service? Which cold-storage condensing units are outdoors and exposed to coastal air? When replacement budgets are being discussed, the registry is the starting point, and it connects to the restaurant refrigeration inventory and risk ranking method for operators with food service sites.
Consolidated reporting that supports decisions
A portfolio report is only as good as the site reports underneath it. When each visit is recorded the same way, the roll-up can show things a single-site manager cannot see.
- Open findings by site and by age, so nothing sits unapproved for months.
- Repeat repairs by asset and by site, which point to root causes, installation issues or end of life.
- Emergency calls compared across similar sites, which can show where equipment or maintenance practice differs.
- Replacement candidates ranked across the portfolio, so capital goes where risk is highest.
- Program completion, showing whether scheduled visits actually happened.
The companion page on maintenance reporting and documentation explains the site-level report that feeds all of this. Review the consolidated picture regularly with your account contact, and record the decisions made.
Onboarding a new site, step by step
A repeatable onboarding process is what lets a portfolio grow without losing control. The steps below are qualitative. How long each takes depends on the size of the site and the number of assets, and the process should not be rushed to meet an arbitrary date.
- Confirm scope and ownership. Decide which asset classes are in the program, who is the site contact and who approves repairs.
- Collect access information. Gather keys, roof access, security procedures, alarm codes and hours restrictions, and store them securely.
- Survey the site. Walk the building and list every covered asset, including those that are hard to find, such as units on upper roofs or equipment in locked rooms.
- Tag and register. Apply QR labels, record data plate details and add each asset to the registry.
- Baseline. Take initial readings and photos for each asset so later visits have something to compare with.
- Report the initial condition. Classify findings as completed, needs approval or watch, and flag any immediate safety or compliance concerns.
- Set the schedule. Assign frequencies by asset class and exposure, and place the site on a route.
- Hold a first review. Walk through the baseline report with the site contact and program owner, and agree on priorities.
For sites with complex needs, such as medical offices or commercial kitchens, add a step to identify critical spaces and the limits on shutting equipment down. See the commercial maintenance plans page for how Davinci's quarterly, bi-annual and annual tiers can be matched to different site types.
Keeping a portfolio program healthy over time
Programs tend to drift. Sites open and close, equipment gets replaced, managers change, and the original scope slowly stops matching reality. A regular review keeps the program honest.
- Update the asset registry whenever equipment is added, replaced or removed.
- Review frequencies annually against actual findings, and adjust where sites differ from the plan.
- Revisit the escalation ladder when contacts change.
- Compare contractor performance by the records, such as completed visits, closed findings and repeat calls.
- Plan capital using the registry rather than reacting to failures.
The broader program design principles are in the commercial HVAC preventive maintenance program guide, and the property management industry page describes the managed-property side. To talk through a portfolio, see the maintenance plans service page.