Multi-Site Standardization Guide

What to standardize and what not to

The most common mistake in portfolio standardization is forcing identical scopes onto genuinely different properties. A medical campus and a warehouse do not need the same work, and pretending otherwise produces a scope that overserves one and underserves the other.

What standardization actually gives you

The benefits are mostly about information rather than cost, though cost benefits do follow.

• Properties become comparable, so outliers are identifiable
• One point of contact rather than a separate relationship per site
• Consolidated reporting that rolls up for ownership
• Route density savings where properties are geographically clustered
• Consistent standards, so a tenant moving between your properties sees the same quality
• Capital planning across the portfolio rather than property by property surprises

How to implement it

Standardizing across an entire portfolio at once is rarely the right approach. Phasing lets you validate the structure before committing every property to it.

1. Group properties by type, since each type needs its own base specification
2. Build a base scope structure with standard categories that applies to all
3. Adjust the specification within that structure per property type
4. Define one documentation and reporting format for every site
5. Start with a subset of properties to validate the structure works
6. Roll out to remaining properties as contracts come up for renewal
7. Review portfolio wide quarterly, comparing sites against each other

One standard, sites that are nothing alike

The tension in every portfolio is the same. You want one standard so the sites are comparable, and you know a warehouse and a medical campus cannot run the same program.

Both instincts are right. The resolution is to standardise the structure rather than the specification.

Structure means the things that make sites comparable: report format, reporting rhythm, escalation path, how scopes are written, what a standard looks like. Specification means the actual work, which should differ, because the properties differ.

Get that split right and a regional manager can read two reports side by side and understand both, even though the work behind them is completely different.

Rolling it out without doing everything at once

Standardising a portfolio in one move is how these projects fail. Contracts end at different times, sites have different contractors, and doing all of it at once means doing none of it well.

The practical approach is to write the standard once, then apply it as each contract comes up for renewal. Within two years most of the portfolio has converted with no disruption and no early termination cost.

Start with the site that is causing the most trouble, not the easiest one. It proves the standard against a hard case, and it produces the visible improvement that funds the rest of the programme.

1. Write the standard scope structure once, with the tasks left as blanks
2. Pick the most troublesome site and apply it there first
3. Measure the result against the condition baseline you took at the start
4. Apply it at each renewal rather than terminating contracts early
5. Review the standard once a year against what the sites taught you

Comparing sites fairly

Once reporting is consistent, the temptation is to compare cost per square foot across the portfolio and act on the outliers. That number is usually misleading.

A dense retail site with forty planters costs more per square foot than an industrial site that is mostly turf, and it should. The comparison that means something is cost against the standard the site is held to, and against its own history.

The genuinely useful comparison is trend. A site whose cost is rising faster than the others, or whose complaint volume is climbing, is worth a visit. A site that is simply more expensive than another is probably just a different property.

One contractor or several

Portfolios spread across a wide geography face a real choice, and neither answer is always right.

One contractor gives you a single relationship, one report format, one escalation path, and real leverage. It works when the sites are within a sensible operating radius of that contractor.

Several contractors give you local route density, which is what actually produces consistent scheduling. A contractor servicing one site ninety minutes outside their normal area will service it last, in whatever time is left.

The workable middle is to standardise the documents and the standard, and let geography decide how many contractors deliver against them. What you are buying is a consistent specification, not necessarily a single company.