When rent growth slows and operating expenses rise, it can become harder to carry out the business plan behind your property purchase. Revising that plan requires knowing which assumptions have changed, what the property can afford, and why it is performing as it is. In our conversation with Taylor Kolle, Senior Asset Manager at RREAF Holdings, we explored how asset managers make those decisions while working with software exports, spreadsheets, and operating information spread across different systems. You can listen to the full episode for the discussion.
Re-underwriting starts with the property's current options
Taylor described a pro forma as a forecast made at a particular point in time. Updating that forecast means checking its assumptions against how the property is performing, how the deal is financed, and the market outlook. The asset manager needs to understand both how the property operates and what its finances allow. A property that needs to conserve cash may have limited room for concessions or capital improvements. Another property with similar operations but a different capital basis may have more flexibility. What the team can do depends on how the investment is structured as well as what is happening at the building.
Concessions, or leasing incentives, make that review harder because asking rents may not show how much rent the property actually receives. Taylor explained that some properties avoid concessions to preserve effective rents, the rent received after incentives are accounted for. Others use concessions more frequently while maintaining higher asking rents. Looking only at asking rent can therefore give a misleading picture of current and expected revenue. Before using past leasing results in a revised forecast, the asset manager needs to understand how the property achieved them and whether the same approach can continue.
Technology has to justify its place in the revised plan
We asked Taylor how he evaluates technology when capital is competing for attention across a portfolio. He applies the same discipline he would bring to another capital project, while considering differences in pricing, implementation, and what the property staff will need to operate. His comparison with a roof replacement helps explain the work involved: each investment has a purpose, a cost, and an expected result, but evaluating those results requires different information. Technology also often needs to be reviewed across the portfolio because the same initiative may perform differently at different properties.
So technology, like any other capital project, needs to be evaluated with the same discipline.
Taylor Kolle
Taylor's concern was whether promised improvements become measurable operating results. A polished dashboard can display information without helping staff carry out the property's business plan. He also described reviewing rising software costs against the performance each platform provides and against available alternatives. That review can lead to a platform change when higher prices are no longer justified. We share his emphasis on measuring the return. Before continuing to pay for technology, expanding its use, or replacing it, an owner needs evidence of what it contributes.
Keeping historical data makes those decisions easier
Comparing performance over time becomes difficult when the records needed for that comparison remain tied to a particular software platform. Taylor discussed KPI scorecards in Excel fed by exports from property management software. He emphasized the need for a dedicated commitment to historical data: storing it somewhere the team can access and managing it consistently. Those records let the team review past trends when forecasting future performance. During a software change, the team also needs to move information from the prior system into the next one.
And if you don't manage and own the data that you have historically, or you know, if it is a different property management software.
Taylor Kolle
For us, this is why data ownership matters when evaluating a technology investment. If changing a platform makes prior records difficult to retrieve, the asset manager has another cost to weigh alongside licensing and implementation. Keeping that history accessible lets the team compare results before and after the change. When a scorecard changes, the team can use those records to investigate which operating conditions produced the number and what would need to change to improve it.
Vendor comparisons need a consistent scope of work
Taylor described sharp increases in repairs, maintenance, and unit-turn costs that required a closer look at what vendors were charging for. His painting example showed why an invoice total alone can be difficult to judge: unit sizes differ, and the service included in one job may differ from another. He described analyzing expense trends to determine whether the team needed to realign its vendor relationships or standardize the scope across services. The response depends on whether the concern is the vendor relationship or differences in the work included. Comparing charges for a clearly defined service helps the team discuss price, choose a provider, and estimate future turn expenses. Without that definition, a budget can carry forward costs that nobody has checked against the work being purchased.
Insurance requirements also matter when comparing vendors. Taylor explained that lender agreements and investment partnerships can impose different requirements at different properties. His team also considers the risk associated with the service: painting and major mechanical or plumbing work can call for different coverage requirements. Define the work and identify the applicable requirements before comparing proposals, so the vendor you choose can meet both. Taylor described seeking more strategic partnerships with providers as expenses rose, which requires understanding their services well enough to discuss the terms. Understanding what each invoice covers helps the asset manager plan future expenses. It also helps explain why apparently similar jobs may need different treatment across the portfolio.
Accurate maintenance records depend on how work gets recorded
When we asked what building-level information would help him, Taylor pointed to maintenance turn times and outstanding work orders. He also described a basic capture problem: a technician may replace a light bulb without entering a work order, even though the task took time. The work happened, but the record leaves it out. That omission matters when an asset manager uses recorded activity to assess workload or understand how the property uses staff time. Taylor emphasized centralizing the information and making it easy for teams to enter, review, and evaluate. The person doing the work needs a practical way to record it as part of the job. Otherwise, the asset manager may be assessing the team's work from incomplete records.
And so Centralizing a lot of that data, making it easy to review and evaluate and input by our teams is crucial.
Taylor Kolle
Taylor's advice to other asset managers followed from that example: develop enough range to understand the operational issues behind an investment decision. He described a role that increasingly requires skill across financial analysis, operations, and the assessment of information available through AI. We discuss how people use records to make decisions throughout the Peak Property Performance® book and the Peak Property Performance® Podcast. The maintenance example shows why an asset manager assessing staffing or maintenance performance needs to understand how the work was recorded. Making that recording manageable for the property team helps owners understand the work they are paying for and decide what needs attention.
About OpticWise: OpticWise provides owner-controlled data & digital infrastructure for commercial real estate, from a single property to portfolio-wide intelligence. See how we help or read customer outcomes.
Own your data & digital infrastructure. Operate with strategic foresight. Build for the long game.