How a Facilities Management Company Unified Work Orders Across 200 Sites

Meridian Facility Services, a Denver-based facilities management provider responsible for 214 office buildings and retail centers across 14 U.S. states, ran maintenance for years on disconnected spreadsheets, personal inboxes, and phone calls to whichever local contractor each site manager happened to trust. In 2025, the company replaced that patchwork with a unified facilities management work order automation platform, built in just 10 weeks on Informat, the AI-powered low-code development platform.

The results arrived within six months of full rollout. Mean time to repair fell 40%, from 5.2 days to 3.1 days. The reactive-to-preventive maintenance ratio shifted from 80/20 to 45/55. Consolidated contractor spend dropped 12%, and client renewal rates climbed from 78% to 94%. Just as important, quarterly client reporting went from a nine-day scramble to a live dashboard that clients now check daily.

This case study explains how the transformation happened: the operational pain that forced change, the build-versus-buy decision, the 10-week delivery, the 200-site rollout, and the numbers that followed. The details are drawn from a composite of mid-market facilities management operators, but every pattern described here is one that multi-site teams will recognize immediately.

The Breaking Point: 200 Sites, 200 Versions of Work Order Management

By January 2025, Meridian Facility Services managed roughly 26 million square feet on behalf of 37 property-owner clients. The company had grown through regional acquisitions, and every acquisition brought its own habits, templates, and vendor relationships. Nobody had ever forced the 214 sites onto one operating model, so each site manager ran maintenance the way they always had.

A Patchwork of Spreadsheets, Inboxes, and Phone Calls

A tenant report of a failed HVAC unit might live in an Excel workbook, a voicemail, a text message, or nowhere at all. Work orders had no shared definition of priority, no consistent trade categories, and no common lifecycle. As a result, headquarters had no reliable answer to basic questions such as how many work orders were open across the portfolio or how long repairs actually took.

The fragmentation showed up in five recurring symptoms:

• No standardization: the 214 sites used more than 190 different spreadsheet formats and naming conventions for the same maintenance tasks.
• Reactive-only maintenance: 80% of all work recorded in the first half of 2025 was unplanned breakdown response, with only 20% planned preventive work.
• Unknown contractors: invoices arrived from more than 1,100 vendors, many of whom had never been vetted for insurance coverage, safety compliance, or negotiated rates.
• No SLA tracking: response and resolution times were not measured, so the service level agreements written into client contracts were effectively unenforceable promises.
• Quarterly reporting scrambles: assembling a single client business review took an average of nine business days of manual data collection.

The Client Loss That Forced Change

In March 2025, a property-owner client audited Meridian's performance across its 12-building portfolio and asked for average response times on critical work orders. Meridian needed three weeks to assemble an answer from site-level spreadsheets, and the data it produced was incomplete. The client moved its portfolio to a competitor in April 2025, and the board issued a mandate that same month: one system, every site, before year end.

"We had 214 sites and, honestly, 214 different operating models. When a major client asked for a simple number, the average response time on critical work orders, it took us three weeks to produce an answer, and the answer was embarrassing. That was the moment we stopped debating and started building."

— Elena Vasquez, Operations Director, Meridian Facility Services

Why Fragmented Work Order Management Costs More Than Leaders Think

Facilities management work order automation is the use of software to capture maintenance requests, convert them into structured work orders, route them to the right technician or contractor, track them against service level agreements, and close them with verifiable documentation. It replaces manual dispatching and spreadsheet tracking with rule-driven workflows. For multi-site operators, it is the difference between managing a portfolio and merely reacting to it.

The stakes are large because the industry is large. According to Fortune Business Insights research published in 2024, the global facility management market was valued at USD 1.29 trillion in 2023 and is projected to reach USD 2.03 trillion by 2032. In the United States alone, the Energy Information Administration's 2018 Commercial Buildings Energy Consumption Survey, released in 2021, counted 5.9 million commercial buildings comprising 97 billion square feet, and every one of them requires maintenance.

Fragmentation carries a documented penalty. Deloitte's 2017 analysis of predictive maintenance found that poor maintenance strategies can reduce productive capacity by 5% to 20%, while unplanned downtime costs industrial operators an estimated $50 billion annually. Conversely, the McKinsey Global Institute's June 2015 Internet of Things analysis estimated that condition-based and predictive approaches can cut maintenance costs by 10% to 40% and reduce downtime by up to 50%. Industry bodies such as the International Facility Management Association (IFMA) have urged operators for years to benchmark maintenance performance, yet benchmarking is impossible when every site keeps its own books.

For Meridian, the hidden costs of fragmentation were concrete:

• Premium pricing: unvetted local contractors charged emergency rates for work that consolidated vendors would perform under negotiated rate cards.
• Repeat failures: skipped preventive maintenance turned $300 belt replacements into $18,000 compressor failures.
• Administrative drag: site managers spent an estimated 11 hours per week on manual work order tracking and invoice reconciliation.
• Client churn risk: without SLA evidence, every contract renewal became a negotiation based on anecdotes rather than performance data.

Why Meridian Chose a Low-Code Platform Over a Traditional CMMS

From May to July 2025, Meridian evaluated three enterprise computerized maintenance management system (CMMS) suites alongside a low-code build. A CMMS is packaged software for tracking maintenance activity, and the incumbent products were mature. However, vendor quotes ranged from $380,000 to $600,000 for implementation, timelines ran 9 to 14 months, and each product forced Meridian to adapt its processes to the software rather than the reverse.

Two structural problems stood out. First, per-seat licensing made it prohibitively expensive to give portal access to hundreds of external contractors and dozens of client stakeholders. Second, Meridian's commercial differentiator, client-specific service models, required a degree of workflow flexibility that the packaged tools could not offer without costly customization projects.

The Build-Versus-Buy Evaluation

The selection committee scored every option against six criteria:

• Time to first production value under 90 days.
• Site-level configurability under centralized governance.
• A mobile-first experience for 480 field technicians.
• Contractor and client portals without punitive per-seat costs.
• Native integration with NetSuite accounting and building management system alerts.
• The ability for business analysts, not professional developers, to maintain workflows over time.

The low-code route won on every criterion. That outcome matches the broader market trajectory: Gartner's December 13, 2022 forecast projected that the worldwide low-code development technologies market would reach $26.9 billion in 2023, growing 20% year over year, and predicted that by 2026 developers outside formal IT departments would account for at least 80% of low-code tool users.

Meridian selected Informat's AI-powered low-code platform and staffed the build with two business analysts and one IT systems lead — no external development agency and no new hires. The economics of that decision, including payback measured in months rather than years, mirror the patterns documented in our analysis of low-code ROI and the economics of enterprise value.

Inside the 10-Week Build on Informat's Low-Code Platform

The project kicked off on September 8, 2025, with a hard deadline: a functioning pilot before the winter maintenance season. The team worked in weekly increments, demonstrating working software to a council of eight site managers every Friday. Because the platform generates working applications from visual models rather than hand-written code, feedback gathered on Friday was usually live in the build by the following Tuesday.

The 10-Week Delivery Timeline

1. Weeks 1–2 — Standardize the process: map how all 214 sites actually handled requests, then define a single work order taxonomy covering 11 trades and 4 priority tiers, each with a target response time.
2. Weeks 3–4 — Build the core work order model: configure the work order object, its lifecycle states, role-based permissions, and assignment rules in the visual designer.
3. Weeks 5–6 — Deliver mobile and contractor experiences: configure the technician mobile app with offline support and photo capture, plus the contractor portal for job acceptance and documentation.
4. Weeks 7–8 — Activate preventive maintenance and SLA automation: load the asset register, create recurring maintenance templates, and switch on SLA timers with automatic escalation chains.
5. Weeks 9–10 — Connect dashboards, integrations, and data: deliver client-facing dashboards, connect NetSuite for invoice matching, migrate 18 months of history from more than 190 spreadsheets, and train the pilot region.

AI assistance compressed the schedule further. The team described forms, views, and automation rules in plain language, and the platform's AI assistant produced first drafts that the analysts then refined. By the team's own tracking, this approach cut configuration effort by roughly a third compared with their initial estimates.

The pilot went live on schedule on November 14, 2025, across 12 sites in the Mountain West region. Total build effort came to approximately 1,900 person-hours, a fraction of the 9-to-14-month implementations quoted for the packaged alternatives. Crucially, nothing was frozen at go-live: the same analysts who built the system continued shipping weekly improvements throughout the rollout, which kept site managers engaged because their feedback visibly changed the product within days.

Five Modules That Deliver Facilities Management Work Order Automation

The finished platform is organized into five connected modules. Each one replaced a manual process that previously varied site by site, and together they form the operating system for Meridian's entire service business.

Centralized Work Order Hub

Every request now becomes a structured work order regardless of how it arrives. Intake channels include:

• A tenant request page reached through QR codes posted in lobbies and service areas.
• Email parsing that converts inbound messages into categorized work orders automatically.
• Direct entry by site managers from desktop or phone.
• Building management system alerts that open work orders the moment equipment faults are detected.

Each work order carries a trade, a priority tier, an SLA clock, and a full audit trail. Duplicate detection flags repeat reports of the same issue, which previously generated multiple contractor visits, and multiple invoices, for a single fault.

Mobile Technician App

Meridian's 480 in-house technicians receive assignments, navigate to sites, and document work entirely from their phones, including in basements and mechanical rooms with no connectivity, thanks to offline mode. Before-and-after photos, parts usage, and time logs are mandatory at closeout. Consequently, disputes about whether work was completed correctly dropped sharply, and the closeout documentation became the backbone of client reporting.

Preventive Maintenance Scheduling

The team loaded an asset register of roughly 41,000 assets — HVAC units, elevators, roofs, fire systems, and parking equipment — each tagged with a maintenance template. The scheduler generates preventive work orders automatically from calendar intervals, seasonal triggers, and runtime thresholds. This module is what moved the portfolio's reactive-to-preventive ratio from 80/20 toward 45/55 within six months of full rollout.

Contractor Management Portal

Approved contractors log in to accept jobs, upload insurance certificates, submit completion documentation, and invoice against closed work orders. Certificate expiry automatically suspends new assignments until documents are renewed. Rate cards are enforced at invoice matching, so out-of-contract pricing gets flagged before payment rather than discovered in an audit months later.

Client Dashboard and SLA Automation

Every client sees a live dashboard of open work orders, SLA performance, preventive maintenance completion, and spend across their portfolio. Behind the scenes, SLA timers trigger a three-step escalation chain — technician reminder, site manager alert, regional director notification — before a breach ever occurs. This layered design is a textbook example of the patterns described in our guide to hyperautomation and AI workflow automation in the enterprise: individual automations are useful, but chained automations change outcomes.

Rolling Out Preventive Maintenance and Mobile Workflows Across 200 Sites

A build is only half of a transformation; the other half is adoption. Meridian phased the rollout across four waves so that lessons from each wave improved the next one.

1. Pilot — 12 sites (November 14 to December 5, 2025): the Mountain West region, chosen deliberately for its mix of office towers and open-air retail centers.
2. Wave 2 — 60 sites (December 2025): the two largest regions, supported by champions recruited from the pilot.
3. Wave 3 — 80 sites (January 2026): the remaining office portfolios, plus activation of client dashboards for the top 10 accounts.
4. Wave 4 — 62 sites (completed February 27, 2026): the final retail sites and the formal retirement of every legacy spreadsheet.

Change Management for 200 Site Managers

Training was deliberately light: one 90-minute virtual session per role, backed by two-minute task videos embedded directly in the app. Each wave ran a two-week parallel period during which the old spreadsheets remained visible but read-only, which removed the safety-net excuse without triggering panic. A weekly data-quality leaderboard, reviewed in regional calls, turned adoption into friendly competition.

Resistance was real, particularly among long-tenured site managers with deep local contractor relationships. Meridian addressed it by letting managers nominate their trusted vendors into the approved contractor pool, provided those vendors met insurance and rate-card requirements. As a result, consolidation felt like curation rather than confiscation, and the loudest skeptics became the program's most persuasive advocates.

"I ran my buildings from a spreadsheet for nine years, so I was the biggest skeptic in the pilot. Two months in, I could see every open ticket, every contractor's ETA, and every SLA clock from my phone. I would not go back for anything."

— Priya Nair, Regional Facilities Manager, Meridian Facility Services

The Results: Faster Repairs, 96% SLA Compliance, and 12% Contractor Savings

Meridian's internal operations review, completed on June 30, 2026, compared the first half of 2026 against the first-half-2025 baseline. The platform now processes roughly 9,000 work orders per month across the portfolio, and every metric the board tracks moved in the right direction.

Before and After: The Numbers

Metric	Before (H1 2025)	After (H1 2026)	Change
Reactive-to-preventive work order mix	80/20	45/55	Preventive share up 35 points
Mean time to repair (priority 1-2)	5.2 days	3.1 days	-40%
SLA compliance rate	61%	96%	+35 points
First-time fix rate	64%	81%	+17 points
Active contractors	1,100+	290 approved	-74% vendor count
Annualized contractor spend	$48.2 million	$42.4 million	-12%
After-hours emergency callouts	310 per month	192 per month	-38%
Client report preparation	9 business days	Real-time dashboard	Same-day
Client renewal rate	78%	94%	+16 points

The headline takeaway from the table: preventive maintenance and SLA automation together cut mean time to repair by 40% while reducing total contractor spend by 12%. Faster service and lower cost are not opposing goals when work is orchestrated centrally.

Beyond the core table, several second-order effects surfaced during the review:

• Invoice disputes fell roughly 70% because every invoice now matches a documented, photo-verified work order.
• Technician utilization improved 14% as smarter routing reduced windshield time between sites.
• Two new portfolio clients signed in May and June 2026, and both cited the live client dashboard as a deciding factor during the sales process.
• Insurance exposure shrank, since expired contractor certificates can no longer slip through unnoticed.

"For the first time in a decade of outsourcing facilities work, I can open a dashboard and see the live status of every work order across our 31 retail centers. Meridian went from being our hardest vendor to audit to being the benchmark we hold every other vendor to."

— Daniel Okafor, Vice President of Asset Management, Northgate Retail Partners

Lessons Learned for Multi-Site Facilities Management Teams

Meridian's leadership is candid that the technology was the easier half of the project. The durable lessons are organizational, and they generalize to any multi-site operation considering work order automation.

• Standardize the taxonomy before touching software. The two weeks spent defining 11 trades and 4 priority tiers prevented months of rework. A tool cannot unify what the business has not defined.
• Pilot with skeptics, not enthusiasts. Winning over the most spreadsheet-loyal region produced credible internal champions and surfaced the hardest edge cases early.
• Bring contractors inside the system. Treating 290 vendors as portal users rather than email recipients is what made SLA tracking and invoice matching enforceable.
• Frame SLA automation as client experience, not surveillance. Escalations were positioned as protecting site managers from breaches, which defused the perception of monitoring.
• Keep shipping after go-live. More than 60 change requests were delivered in weekly releases between November 2025 and June 2026, continuously converting user feedback into trust.

The final lesson concerns sequencing. Meridian did not attempt a big-bang overhaul; it fixed one painful, measurable process end to end, then expanded. Moreover, the work order platform has since become the foundation for adjacent use cases — capital project tracking, energy monitoring, and vendor scorecards — following the incremental playbook outlined in our examination of AI-driven digital transformation strategy for the enterprise.

In other words, the platform decision mattered less because of any single feature and more because it let a three-person business team keep evolving the system at the speed of operational feedback. That is the defining advantage low-code development holds over both spreadsheets and rigid packaged software.

Frequently Asked Questions About Facilities Management Work Order Automation

Multi-site operators evaluating a similar move tend to ask the same three questions. The answers below reflect Meridian's experience alongside current industry benchmarks.

How long does it take to implement facilities management work order automation?

On a low-code platform, a multi-site core system typically takes 8 to 12 weeks to build, followed by a phased rollout of two to four months depending on site count. Meridian built its platform in 10 weeks, between September 8 and November 14, 2025, and completed the 214-site rollout 15 weeks later. In contrast, the traditional CMMS implementations quoted to Meridian ranged from 9 to 14 months before the first site would have gone live.

What does work order automation cost for a multi-site operation?

Costs fall into four buckets, and the mix differs sharply between packaged and low-code approaches:

• Platform licensing, which low-code models typically price without per-seat penalties for external contractors and client viewers.
• Configuration and integration effort, which Meridian covered with three internal staff instead of a systems integrator.
• Training and change management, deliberately kept light through embedded task videos and champion networks.
• Data migration from legacy spreadsheets, shared drives, and email archives.

Meridian recovered its total first-year cost before that year ended: the 12% reduction in contractor spend alone returned roughly $5.8 million annualized, which dwarfed the platform investment many times over.

Can a low-code work order platform integrate with accounting and building systems?

Yes, and integration is usually the deciding factor for finance teams. Meridian connected Informat to NetSuite so that approved, work-order-matched invoices flow directly into accounts payable, and it wired building management system alarms into work order intake so equipment faults create tickets without human dispatch. Modern low-code platforms expose REST APIs and webhooks precisely so operational workflows can exchange data with finance, HR, and IoT systems in real time.

Conclusion: Facilities Management Work Order Automation as a Growth Engine

Meridian's story began as damage control after a lost client and ended as a commercial advantage. Facilities management work order automation did more than tidy up operations: it converted maintenance data into the company's strongest sales asset, because prospects can now see, rather than merely be told, how the portfolio performs. In a services industry where contracts renew on trust, verifiable performance data lifted client renewal from 78% to 94% in a single year.

The pattern is repeatable for any multi-site operator:

• Standardize the work order taxonomy first, because software amplifies whatever definitions it is given.
• Choose a platform that welcomes external users — contractors and clients — without punitive licensing.
• Automate preventive maintenance scheduling and SLA escalation before chasing advanced analytics.
• Roll out in waves, keep shipping weekly improvements, and let skeptics become champions.

Ten weeks of building on a low-code foundation achieved what a decade of spreadsheet discipline never could: one operating model across 200-plus sites, visible to every stakeholder in real time. For facilities leaders weighing the same move, the arithmetic is straightforward, since a 40% faster repair cycle and 12% lower contractor spend paid for the platform within the first year. To explore how a similar system could be assembled for your own portfolio, visit Informat, the AI-powered low-code platform, and start with the single process that hurts the most.