Resources

What keeps retail Facilities teams in fire-drill mode

Written by Immersion Data Solutions | 11. 17.2026

Five takeaways from our recent webinar, “Building a Preventive Maintenance Program when You’re Drowning in Tickets”

Most retail Facilities teams already have a preventive maintenance program. The calendar is set. Inspections are on the schedule. The work order system is running. Then a roof leaks, an HVAC unit fails or a store manager calls in an urgent request, and the plan goes out the window again.

That cycle was the focus of a recent Immersion Data Solutions webinar for Facilities leaders. Tia Kachman, COO of Immersion Data Solutions, hosted the session with senior Project Manager Betsy Hewgley and Solution Architect Jack Loukusa. All three work closely with multi-site retail teams.

Their central argument: Even a well-designed maintenance program can struggle when the site information supporting it is incomplete or outdated.

Want to hear the full conversation? Watch the webinar recap to hear Tia, Betsy, and Jack discuss why preventive maintenance programs fall into reactive cycles and how better property information can help. Watch now

Takeaway 1: The first visit turns into a fact-finding trip

A work order may describe the problem without giving a vendor everything needed to resolve it. Equipment specifications, access requirements, and the conditions surrounding the repair can all affect whether the right technician arrives prepared to do the work.

“Somebody needs a photo, somebody has to call the store, a vendor gets there and realizes they don't have the right equipment or access to the space,” Hewgley said. “None of those seem huge at the time. But when you're doing it across hundreds and thousands of locations, it adds up really quickly.”

All that rework leads to disruption – and more firefighting. Preventive work slides further down the list.

Takeaway 2: Firefighting crowds out the work that would end it

When tickets pile up, adding checklists, increasing inspections, or pressing vendors for faster responses can seem like the obvious fix. Those steps tighten the process, but they don't fill the information gap that keeps causing the tickets.

“Every hour spent researching and reacting to a ticket is an hour not spent collecting and validating the condition information that would actually prevent the next ticket,” Kachman said. “Reactive work does not compete with prevention. It prevents prevention.”

Takeaway 3: Scattered information makes it difficult to know what's current

Facilities teams often have much of the information they need, but it's scattered across project folders, vendor emails, work orders, and individual employees' records. Finding the right information is difficult enough; knowing whether it's still accurate is another problem. When a team can't confirm equipment details or current site conditions, it may have to contact the store or send someone out to verify them.

Loukusa said this is why so many programs stay on a fixed calendar “by necessity, not by design.” A quarterly schedule tells a team when to inspect an asset. It doesn't account for equipment replaced last month, a recurring access problem, or condition differences that warrant closer inspection.

Kachman pointed to the weather as an example. Rooftop equipment in a Minnesota winter wears down differently than the same unit in Texas, but a calendar treats them the same. Once a team can see how an asset changes over the years, they can identify where more frequent inspections may be warranted, alongside equipment age, maintenance records, and local operating conditions.

Takeaway 4: One validated record can answer the next question

The panel described the Phygital twin as a validated digital record of each store that can be updated as conditions change. That record is only useful if it reflects changes at the property. Equipment replacements, renovations, and other significant updates need to be incorporated so teams aren't making decisions from outdated documentation.

Techs can walk through the store on-screen before they arrive. They can see what they need to fix, what sits around it, and what might slow them down.

Hewgley shared one case where someone at a corporate office had the Phygital twin open and guided a tech through the store, step by step, to the right spot.

Loukusa described a Facilities team that didn't know the make, model, and serial number of the equipment across its stores. Phygii recorded those details during the original store capture and organized them into reports. The team skipped a separate inventory trip and went straight to budgeting.

The same record also serves other teams. Construction uses it to plan remodels. Brand checks signage standards. Real Estate uses it for due diligence and lease talks. Clients report savings in preconstruction planning costs.

One client asked Phygii to start counting wood and blue cash wrap finishes in its next round of captures. Hewgley said she didn’t need to wait for the next round of captures; she could get them an answer that same day.

Takeaway 5: Start with one problem and a few numbers

You don't need to overhaul the whole portfolio. The panel recommended a focused pilot. Pick a group of similar stores with a clear, costly problem, such as repeat HVAC calls, an upcoming maintenance cycle, or a planned capital project.

Before launching the pilot, establish a baseline so you can measure whether better site information makes a difference. Depending on the problem you're trying to solve, that might include:

  • Number of work orders in the targeted category
  • Percentage of issues resolved on the first dispatch
  • Time spent tracking down or verifying site information
  • Cost of repeat visits or redundant site surveys

Choose three or four measures that matter most to your team, and establish who will be responsible for keeping the property information current. The results should help determine whether the approach is worth extending to more stores, based on measurable reductions in repeat work, unnecessary visits, or time spent retrieving information.

“Facilities leaders usually know which stores are in trouble. What they don't have is proof they can take to leadership,” said Loukusa. “A focused pilot gives them that proof in their own numbers.”

That proof also answers a question from the Q&A: “How do you get budget for prevention when the fires are so visible?” Loukusa’s advice was to start with costs the company already pays, such as repeat dispatches and trips to recollect store data.

Watch the full recap for more insights from the panel, including how to build a stronger case for preventive maintenance and measure the impact across your portfolio.

From reactive maintenance to better Facilities decisions

Facilities teams will always have emergencies to manage. But they shouldn't have to spend so much time tracking down basic information about their stores before they can respond.

Better property information helps teams prepare vendors, avoid unnecessary site visits, make more informed maintenance decisions, and build a stronger case for capital investment. And when that information is maintained and reused across the portfolio, the benefits extend well beyond the original maintenance problem.

See how Phygii helps Facilities teams work with better information

Explore how Immersion Data Solutions helps multi-site retailers document property conditions, support preventive maintenance, and make more informed capital planning decisions.

Explore Phygii for Facilities