Blog· October 14, 2026

Asset condition score in capital planning: a plain definition

Drone view of industrial building roofs with rust staining, set among surrounding trees.

If you run capital planning for a portfolio, you already know the problem the score is trying to solve: forty sites, one budget, and no way to visit all of them before the committee meeting. An asset condition score is the number that sorts the list. It's a rating assigned to a site, or to a specific asset at that site (the roof, the parking lot, the yard), that reflects how degraded it is and, by extension, how soon it's going to need capital.

The term comes out of the same tradition as the facility condition index (FCI) used in reserve studies: deferred maintenance cost divided by replacement cost, expressed as a ratio or a letter grade. Most REITs and FM teams don't run a full FCI on every roof and lot every year. What they run instead is a lighter, faster version of the same idea, applied annually instead of every five years, because five-year-old data doesn't help you build next year's budget.

How the score gets built

A condition score usually breaks into the sub-systems capital planners fund separately. For a typical commercial or retail site that's three buckets:

  • Roof surface: membrane wear, ponding, visible seam failure, debris accumulation.
  • Parking lot: alligator cracking, pothole density, faded or missing striping.
  • Yard and landscape: dead or overgrown vegetation, drainage pooling, general upkeep that signals a site isn't being maintained.

Each bucket gets a rating, and the three roll up into a single per-site number you can sort a portfolio by. Some teams weight the buckets (a roof failure costs more than a striping job, so it pulls the score down harder). Others keep it simple and flag anything below a threshold for a closer look. Either way, the output is the same thing a reserve study gives you, just refreshed on a cadence that's cheap enough to run every year.

The traditional way to get these ratings is a site visit: an engineer or inspector walks the roof, drives the lot, photographs the cracks, and writes it up. That works, and it's the standard for anything load-bearing or structural. It's also slow and expensive to repeat across a hundred-plus addresses every year, which is why most portfolios only get a real walk-through every three to five years and rely on manager reports in between.

Portfolio condition index, explained

Where the per-site score tells you about one address, a portfolio condition index lines every site's score up next to each other. It's not a separate metric so much as the same scoring method applied at scale: rank every roof, lot, and yard in the portfolio from worst to best, and you've got a prioritized capex queue instead of forty disconnected inspection reports.

That ranked view is the deliverable capital teams actually need. Nobody budgets off a condition score in isolation. They budget off the list: which ten sites need a roof replacement this cycle, which twenty need lot resurfacing, which can wait. A score only earns its keep once it's part of that comparison.

The gap most teams hit is cadence. A full engineering walk-through gives you the most defensible number, but doing it annually across a large portfolio means a truck roll to every site, every year, and that's rarely in the budget. A very-high-resolution aerial or satellite pass, read for the same three things (roof wear, lot cracking and striping, yard upkeep), gets you a score per site on an annual cycle without putting a person at every address. It won't replace a structural engineer's sign-off on a roof you're about to re-deck, but it will tell you, every year, which of your hundred-plus sites moved from "watch" to "fund now" since the last pass.

Asset Condition Review runs that annual pass and hands back a ranked list and a map layer built for exactly this: dropping condition scores straight into a capital plan instead of a stack of site-visit PDFs. If your next budget cycle starts with "which sites first," that's the question this is built to answer.

Start a pilot

← Back to the blog