Standardising Operations Across a Portfolio

Two buildings, same owner, same budget, same cleaning contract — and one lobby looks cared for while the other looks abandoned by Thursday. Nothing in the contract explains it. What differs is the standard each manager carries in their head.

Portfolio standardisation is the fix, and it is usually misunderstood as centralisation. It is not. It means the same minimum condition, the same inspection method and the same record in every building. It does not mean the same schedule, the same vendor or the same decisions.

Key takeaways

• Standardise the method, the vocabulary and the minimum condition. Leave schedules, vendors and local judgement to the site.
• Drift starts with ambiguity: if two managers describe "clean" differently, both are right and neither can be held to it.
• One page per area beats a 60-page manual, because a page gets used and a manual gets filed.
• Roll out in waves of two or three buildings, two weeks apart, so the second wave inherits the first wave's fixes.
• Keep a written exceptions register — the sites that genuinely differ are the reason portfolios stop trusting comparisons.

What does portfolio standardisation actually mean?

It means three things: one minimum condition, one method of measuring it, and one format for recording it. Everything else in a portfolio can vary by building without harming consistency.

The minimum condition is the floor, not the target. A downtown tower may aim higher than a suburban office park, but neither should fall below the floor. Written as a photograph and a scored level, the floor is enforceable; written as an adjective, it is a mood.

The method is how you measure — which areas, which items inside each area, which scale, how many photos, who inspects. The record is what the method leaves behind: one report format, one naming convention, one place to file it. Holding a portfolio to one standard does not require holding it to one way of operating.

Why do portfolios drift apart in the first place?

Because standards are transmitted by people, and people leave. A standard that exists only in a manager's habits dies with their transfer, and its replacement is whatever the next manager learned somewhere else.

Four mechanisms account for most of the drift:

• Vacancies. A building without a manager for six weeks is inspected by whoever has time, using whatever format they prefer.
• Procurement. A new cleaning contract arrives with its own inspection form, so the portfolio now has two formats for one question.
• Local fixes. A site writes its own checklist for a real problem — a food court, a parking garage — and the portfolio now has two definitions of a washroom.
• Reporting pressure. A manager who knows a low score invites questions learns to score generously, and the numbers stop comparing.

What should be standardised and what should not?

Standardise the parts that make sites comparable; leave local the parts that make them work. The test for any element: if two buildings produce different values for it, does that stop the owner comparing them?

How do you write a standard people will follow?

One page per area, five parts, written by the people who inspect. A standard that takes an hour to read is a document nobody opens at 7am on a Tuesday.

1. Scope — one sentence naming the area and what is inside it, e.g. "washrooms: all fixtures, floors, partitions, dispensers and waste".
2. The item list — eight to fifteen items, each a thing you can point at, not a quality.
3. The levels — what a 1, a 3 and a 5 look like, each with a reference photograph.
4. The critical items — the ones that fail the area regardless of score, such as a blocked fire exit.
5. The evidence — where photos go, how many, and what "done" means for that area.

Draft page one yourself, then have two managers inspect the same area against it before you write page two. The first inspection always reveals a word that meant different things to different readers. The same discipline sits behind writing SOPs for building operations, and the two documents should reference each other rather than compete.

How much central control is too much?

Too much control is when sites start working around the standard instead of to it. The signal is not resistance; it is a parallel spreadsheet. If a building keeps its own tracker, the central system has failed a usability test, not a compliance test.

Three levers are enough to hold a portfolio together:

• The template. One inspection form per building type, maintained centrally, versioned and dated. Sites may propose additions; they do not fork the form.
• The vocabulary. One name for each area and item. A "washroom" in one building and a "restroom" in another breaks comparison before anyone inspects anything.
• The thresholds. The scores that trigger action, agreed once: for example, level 3 or below on any critical item opens a deficiency within 24 hours.

Everything else belongs to the building. Central teams that dictate the calendar get compliance on paper and nothing else.

How do you roll it out without a big-bang change?

In waves of two or three buildings, two weeks apart, starting with the site most likely to succeed. A portfolio-wide launch on the first of the month produces goodwill on day one and silence by week six.

Do not launch during a contract transition, a budget cycle or a peak season. A standard introduced mid-mobilisation inherits the mobilisation's chaos.

How do you keep sites from drifting back?

Re-check a sample every quarter, and make the sample public before it happens. Drift is a maintenance problem, and the cheapest control is the expectation of a check.

• Quarterly cross-inspection. A manager inspects four areas in a building that is not theirs, blind, before comparing notes with the building manager. Same logic as calibrating building inspectors, run on a schedule.
• A tolerance rule. Scores within one level are agreement. A two-level gap on the same area is a definitions problem and goes back into the standard, not into a performance file.
• A visible variance measure. Report the spread between buildings of the same type and age, not just the average. A portfolio averaging 4 with buildings ranging from 2 to 5 is less healthy than one averaging 3.8 with everything between 3 and 4.

Benchmarking only works once the standard is stable; the sequencing is covered in benchmarking sites fairly across a portfolio.

What does standardisation look like on the record?

It looks boring, which is the point: every building produces the same report, in the same order, with photos taken at the same points. A reader can open two buildings side by side and see the difference in condition rather than the difference in author.

Keep the fixed photo points short — entrance, reception, one standard washroom, a stairwell, the loading dock — and file by area and date, never by whoever produced the file. A folder of documents named after their authors is a record in name only.

What about sites that genuinely are different?

Give them an exception, in writing, with a review date. A portfolio of offices, one lab and two retail concourses needs a lab standard and a retail standard, not a compromise document that fits nothing.

Run it as a register with four columns: building, area, why the shared standard does not fit, and when the exception is reviewed. The register protects genuine differences and stops the standard being quietly abandoned at the sites with the most confident managers.

Where an exception is really a coverage gap, add the area to the shared standard. Nine times out of ten, a site that wants its own form wants one extra area, not one different standard.

Frequently asked questions

Does standardising a portfolio mean centralising decisions?

No. It means fixing the minimum condition, the measurement method and the record format, and leaving schedules, vendors and daily judgement with the building. The more decisions you pull up, the more slowly the portfolio responds.

How long does it take to standardise a 20-building portfolio?

Roughly four months at a sensible pace: two weeks writing lists, two weeks piloting, then waves of two or three buildings every two weeks. Portfolios that attempt it in a fortnight get documents; portfolios that give it a season get behaviour.

What if managers refuse to use the shared template?

Usually they are protecting something real — a site-specific area, a report their owner prefers. Ask which item is missing rather than whether they will comply, add the gap where it belongs, and keep the single template.

Should tenants see the standard?

Yes, at least the minimum condition and the response times attached to it. A tenant who knows what level 3 looks like stops arguing about taste and starts reporting specifics, which is easier to act on and easier to defend.

Can we standardise without buying software?

Yes. A shared template, a naming convention and a filed PDF set will carry twenty buildings. Software becomes worth paying for when the volume of inspections makes filing, finding and comparing reports the bottleneck.

The standard you can defend

A portfolio running on one standard can answer the owner's hardest question — why does this building score what it scores? — without a meeting. The area list is the same, the photographs are at the same points, and the scale means the same thing in every lobby.

It also makes property management operations inheritable: a new manager joins, reads one page per area, inspects with a colleague, and is calibrated within a month rather than a year. External frameworks help with vocabulary, not the work. BOMA Canada's BOMA BEST programme is a reasonable reference when an owner asks how the portfolio compares to a recognised Canadian benchmark, and CCOHS treats documented, reviewed procedures as a core element of an occupational health and safety programme.

NeatScore carries the inspection end: area-specific checklists on APPA 1–5 scoring, critical items flagged, a photo per item, offline inspections that sync, deficiency tracking and a dated branded report that looks the same in every building. Try it free for 14 days, or see pricing.