Multi-Property Exterior Standards

Portfolio exterior management has one structural question underneath everything else: which decisions belong at the center and which belong at the property. Answer it well and the portfolio gets consistency where consistency matters and adaptation where conditions differ. Answer it badly — which is common — and it gets uniformity where properties differ and inconsistency where they should match.

The Split

The pattern: standardize the definition of what good means and the mechanics that make properties comparable. Localise anything determined by conditions on the ground.

Tiering Rather Than Uniformity

Portfolios rarely contain one class of asset. A single standard applied across a flagship property and a suburban secondary asset either overspends on one or underserves the other.

A tier structure resolves this without abandoning consistency. Two or three tiers, each with its own appearance standard, inspection cadence, and response expectations, and each property assigned a tier. What stays constant across tiers is the specification format, the compliance requirements, and the meaning of acceptable — what varies is the threshold.

Assigning tiers is a portfolio decision and should be explicit, because implicit tiering is what actually happens otherwise, based on which properties get attention.

What Makes Properties Comparable

The analytical benefit of standardization is comparison, and comparison needs a small number of consistent inputs.

• Cost per unit area on a common specification. Meaningless across different scopes; informative on the same one.
• Reactive spend as a share of total. The clearest single indicator of an under-programmed property.
• Maturity stage, assessed against a common model.
• Open deferral items, and how many are progressive.
• Frequency by zone type, which reveals whether local calibration is happening or defaulting.

A portfolio review built on these five identifies under-served assets faster than reviewing invoices, because invoices show spend rather than whether spend is working.

Rolling Out Without Disruption

Portfolios rarely start clean. Each property has an incumbent vendor, an inherited schedule, and an undocumented understanding of what is included. Imposing a new standard everywhere at once creates more disruption than it resolves.

1. Inventory first. Vendor, frequency, scope, annual spend, and whether documentation exists, per property. The inventory alone usually surfaces the outliers.
2. Apply at natural transition points — renewals, vendor changes, acquisitions — rather than forcing them.
3. Start with the properties furthest from standard, which are usually the ones whose arrangements are least formal and therefore easiest to change.
4. Accept partial adoption. A property using the central specification and compliance requirements while retaining its own vendor is most of the benefit.

Within a normal contract cycle most of a portfolio converts without a single disruptive transition.

Standards That Survive Local Adaptation

A standard that cannot be adapted gets ignored; one that can be adapted without limit stops being a standard. The workable distinction is between the requirement and the implementation.

State requirements as outcomes and constraints — what acceptable means, what must be documented, what compliance is required, what methods are prohibited on which substrates. Leave implementation local — which vendor, which schedule, which window, which sequence. A property meeting the requirement by a different route is complying, not deviating.

The Central Function's Real Job

In practice the highest-value central activity is not writing the standard but maintaining the comparison. Properties calibrate locally and correctly; what nobody at property level can see is that their reactive share is twice the portfolio norm, or that they are two maturity stages behind comparable assets.

That visibility is the thing only the center can provide, and it is worth prioritizing over further standardization once the basics are in place. See the appearance maturity model and multi-site and portfolio programs.