Scheduling preventative maintenance by property age and vintage

Most portfolios run one preventative maintenance calendar. Quarterly filters, annual HVAC service, done.

That calendar is simultaneously too light for a 1966 Class C building and too heavy for a 2025 lease-up, and applying it to both is a decision most operators make by default rather than deliberately.

Age changes failure rates, so it should change intervals

The reason to vary by vintage is not sentiment about old buildings. It is that component failure rates are not flat over time.

A 1966 property has original or near-original cast iron drain lines, galvanized supply, and mechanical systems that have been replaced piecemeal by different contractors over sixty years. Its failure modes are water and drainage.

A 2025 lease-up has warranty coverage, documented systems, and a punch list. Its failure modes are installation defects surfacing in the first eighteen months.

Those two need different schedules, and a quarterly filter change is not the interesting difference between them.

Target the schedule on four property attributes

Year built. The strongest single predictor of what will fail.

Vintage or renovation date. A 1966 building fully repiped in 2019 behaves like neither a 1966 nor a 2019 property, and the year built alone will mislead you.

Market. Climate drives HVAC load, moisture risk, and filter intervals. A Tampa property and a Denver property with identical construction do not need the same schedule.

Asset class. Class A residents report issues faster, which changes how much you need preventative inspection versus reactive response.

GetDone's PM schedule templates target by property age, vintage, and market, with a nightly fan-out into recurring entries and an eligible-properties preview before you commit. The preview matters more than it sounds: a template targeting the wrong 30 properties creates 30 properties' worth of work nobody planned.

Start from what actually failed last year

The best input to a PM schedule is your own reactive work order history, and almost nobody uses it.

Pull last year's work orders by category and by property. Sort by volume. The top three categories at your oldest properties are your PM candidates, because those are the failures already happening on a schedule you did not choose.

If water intrusion is in that top three anywhere, that property needs a moisture inspection interval rather than a filter interval, and it is also the one where documentation matters most.

The compliance items are not optional and should not be on the same list

Worth separating deliberately.

Pool inspections, life-safety and light inspections, and anything with a statutory interval are compliance obligations with an exportable evidence requirement. They belong in a gated workflow that produces a log, not on a general PM calendar where a miss looks like a missed filter change.

GetDone handles those as high-risk workflows with a pool log PDF and multi-page light inspection reports, separate from recurring PM entries. The reason is that a missed compliance inspection has a different consequence than a missed convenience task, and a single list flattens that.

An HUD inspection checklist for affordable properties is planned rather than shipped, and worth saying rather than implying.

What PM buys, and what it does not

The honest case for preventative maintenance is that it converts unpredictable expensive failures into predictable cheap ones. It does not reduce total work orders in year one, and anyone selling it that way is overselling.

What it does reduce is emergency after-hours work, which is the most expensive labor you buy, and water damage, which is the failure that compounds.

Being straight about our own state here: predictive maintenance, meaning a system that tells you when a component is likely to fail based on its history, is not something we do. Nor does anyone else in this category convincingly. Warranty and asset aging tracking is requested rather than built. The current honest position is scheduled preventative maintenance targeted by property attributes, which is a real improvement on one calendar for everything and is not prediction.

Attribute targeting is what survives staff turnover

At 86 properties, maintaining per-property schedules by hand does not survive staff turnover. The schedule drifts, then nobody trusts it, then it gets ignored.

Property attributes sync daily from the property list, mapping code, class, year built, market, and the assigned PM, regional, and maintenance supervisor. Templates target on those attributes rather than on a list somebody maintains, which is the mechanism that keeps the schedule correct when a property changes hands or gets renovated.

Pull last year's work orders by category

Last year's work orders, grouped by category, filtered to your three oldest properties.

Whatever is at the top of that list is what your PM schedule should be built around, and it is probably not what it is built around today.

What is your oldest property's top failure category?