The single-building vs multi-property divide
A single 500,000 sq ft commercial building has approximately 1,000 maintainable equipment items, 25-50 active AMCs, 8-15 in-house maintenance staff, and 40-100 maintenance work orders per day. It is a complex operation but it sits in one place and one team understands all of it.
A property firm operating 40 buildings — typically a mix of small (50,000 sq ft) and large (500,000 sq ft+) — multiplies all of this by a factor of 20-30. The total maintainable equipment base is 25,000-40,000 items. The AMC portfolio has 500-1,500 contracts. The maintenance headcount is 200-400 people across multiple cities. Daily work order volume reaches 1,000-2,500.
At this scale, single-building thinking breaks down. The firm needs different mental models, different software architecture, and different management cadence. Most multi-property firms make the leap badly and end up with bloated headcount and inconsistent quality.
The four mental shifts required
1. Standards over heroics
A single-building facility manager succeeds by being a hero — knowing every piece of equipment, every tenant pain point, every vendor weakness. This works at scale 1; it does not scale to 40.
A multi-property operation succeeds through standards: standard equipment lists, standard PM schedules per equipment class, standard checklists, standard vendor SLAs, standard escalation matrices. Heroes still matter but they execute against the standard rather than improvise.
2. Central + distributed model
Some functions centralise (vendor relationships, equipment standards, procurement, training, IT). Others remain distributed (daily operations, tenant interaction, breakdown response, security shifts).
Getting this split right is the central organisational design question of multi-property maintenance.
3. Data over anecdotes
A single-building facility manager runs on relationships and observation. A multi-property head of maintenance runs on data — PM compliance by building, tenant satisfaction by trade, vendor performance by category, energy intensity by sq ft. Without this data, the head of maintenance cannot allocate attention to the buildings and issues that need it.
4. Programme over project
Single-building maintenance has projects: replace the lift, refurbish the cooling tower, redo the lobby. Multi-property maintenance has programmes: lift modernisation across the portfolio, energy efficiency upgrade across the portfolio, fire safety compliance across the portfolio.
Programme thinking dramatically improves capital efficiency because the firm leverages negotiating power, standardisation, and learning across buildings.
What multi-property CMMS architecture has to do
A CMMS designed for single buildings rarely scales to multi-property. The architectural requirements differ:
Multi-tenant data model
The platform must handle multiple buildings, each with its own equipment list, PM schedules, vendor list, and tenant base. Roll-up reporting consolidates across buildings while drill-down focuses on a specific site.
Standard libraries
Equipment classes (AHU, chiller, lift, pump, generator) have standard PM templates. When a new building is added, the system applies the templates rather than requiring a from-scratch schedule build. This is critical for fast onboarding of new properties.
Centralised procurement
Spare parts purchased centrally (because volume drives discounts) and distributed to buildings as needed. The CMMS tracks central inventory plus building-level inventory plus consumption by building, with auto-replenishment triggers.
Vendor management at portfolio level
A single fire safety vendor may serve 25 buildings across the portfolio. The CMMS shows that vendor's aggregate performance (SLA compliance across all 25 buildings), making renewal and renegotiation decisions data-informed.
Tenant request unification
A tenant in one building uses the same app, sees the same SLA promises, gets the same quality of service as a tenant in another building. The CMMS makes this consistency possible.
Multi-city operations
Buildings in different cities have different vendor lists, different statutory requirements, different operating costs. The CMMS handles city-specific configurations while maintaining portfolio-level standards.
Mobile-first for distributed teams
Maintenance staff in 40 buildings cannot share a single desktop interface. Every workflow must work on mobile, with offline support for areas with poor connectivity.
The maintenance ops centre
Multi-property firms typically run a central Maintenance Operations Centre (MOC) — a team of 8-20 staff who:
- Monitor the portfolio dashboard for emerging issues
- Triage high-impact incidents and coordinate response across buildings
- Track SLA compliance and intervene with under-performing sites
- Coordinate vendor visits across multiple buildings (especially for vendors that serve the whole portfolio)
- Produce daily, weekly, and monthly performance reports
- Coordinate the spare parts pipeline across the portfolio
- Manage programme-level initiatives (e.g. portfolio-wide energy audits)
The MOC requires the CMMS to surface the right information at the right time. Without it, the MOC drowns in alerts and adds little value.
The metrics that matter at multi-property scale
A multi-property head of maintenance lives on these eight metrics:
- 1Portfolio-wide PM compliance % — should be 88%+ for a well-run operation
- 2Median breakdown response time — should be under 45 minutes for high-priority calls
- 3Tenant satisfaction score for maintenance — should be 8.5/10+
- 4MTBF for critical equipment classes (lifts, chillers, fire systems) — should be improving year-over-year
- 5Maintenance spend per sq ft — should be flat or declining in real terms with quality improving
- 6AMC compliance % (visits confirmed delivered) — should be 96%+
- 7Spare parts inventory turn — should be 4-6x annually
- 8PM-to-corrective ratio — should be 70:30 or better
A monthly review of these eight metrics across the portfolio, with red-flag identification on specific buildings, is the operating rhythm. Buildings that are consistently below standards get focused intervention.
What goes wrong without proper multi-property CMMS
Multi-property firms running on single-building software or on spreadsheets typically experience:
- Inconsistent quality. Building A is well-maintained; Building B is a mess. Tenants of Building B notice and switch.
- Vendor leverage compression. Vendors who realise the firm cannot see across buildings exploit information asymmetry on pricing.
- Spare parts chaos. Each building buys its own parts; some buildings stock-out while others overstock. Working capital tied up in slow-moving inventory.
- Tenant complaints that fall through cracks. A tenant complaint at Building B about lift speed escalates because the central team did not see it before the tenant did.
- Owner reporting gaps. Owners want portfolio-level reporting; the firm cobbles together monthly slides from 40 building-level reports.
These pain points compound until either the firm adopts proper multi-property CMMS or stops growing.
The investment
For a 40-building portfolio with 200-400 maintenance staff and ₹40-80 crore annual maintenance spend, multi-property CMMS investment is typically:
- Year 1: ₹40-80 lakh (licences, implementation, training, integrations)
- Years 2+: ₹15-30 lakh annually
Against typical savings of 8-12% of maintenance spend (₹3-10 crore annually) plus consistency and growth-enabling benefits, the payback is 6-12 months and the lifetime ROI is in the high single-digit multiples.
The bottom line
Multi-property maintenance is a different operational discipline from single-building maintenance. The firms that recognise this and invest in proper architecture (technology, standards, ops centre, metrics) scale profitably. The ones that try to scale single-building thinking get stuck around 15-25 buildings and start losing ground to better-organised competitors.
For property firms past 10 buildings, the multi-property maintenance investment is not a debate. It is the operating-system upgrade that determines whether the firm continues to scale or stagnates.
