A vendor quote for an HVAC repair goes out for approval on a Tuesday. Nobody follows up until the tenant calls again the following week, because the sign-off happened over email, outside the ticketing system, and there was no record showing anyone was waiting on a decision.
Facilities directors managing multi-site operations often have a system that logs tickets fine but breaks down somewhere between submission and resolution, an approval that stalls, a routing decision nobody documented, a status update that never reaches the person who asked for it. Facility work order management works best as a defined sequence, not a collection of habits.
Quick answer: This guide covers five stages: requests, routing, approvals, tracking, and resolution. Each stage depends on the one before it, poorly structured requests make routing unreliable, and routing without a defined approval stage pushes sign-off outside the system entirely. In practice, approvals are the stage that breaks down most often, since it's the one most likely to get handled informally even in an otherwise well-structured workflow. We cover the process side of stage one in more depth in How to Standardize Facility Service Request Tracking.
1. Structuring Service Requests at the Point of Submission
The quality of everything downstream depends on what gets captured at submission. A well-structured service request management process captures a consistent minimum every time: location, category, description, and urgency, gathered through the same method at every site, a mobile form, a QR code, a shared portal.
Vague or inconsistent requests create work later that a structured form prevents up front. A request that just says "AC not working" without a location or urgency level forces someone to chase down details that should have been captured the first time. Look for a batch tool that can push the same request template to every selected property at once, as one way to get that structure applied consistently across a whole portfolio rather than site by site. This step matters more than it might seem: facilities teams report spending roughly 60% of their working hours on coordination rather than hands-on repair work, according to data compiled by MPulse Software, and a lot of that time traces back to chasing down details that a structured intake form would have captured on the first submission.
2. Routing Requests to the Right Person Automatically
Once a request is structured consistently, it can route based on rules rather than manual judgment. Category and location should determine who gets assigned automatically, a plumbing issue goes to the plumbing team or an on-site vendor, an electrical issue goes to whoever handles that at that specific site. Manual routing, where a coordinator reads each ticket and decides who to call, doesn't scale past a handful of properties without becoming a bottleneck itself. Enforced Type and Class fields on every asset record keep the categorization behind that routing consistent, and preferred vendor routing that cascades automatically through a ranked list when the top choice doesn't respond extends the same logic to outside contractors.
3. Building Approvals Into the Workflow, Not Around It
Some requests need sign-off before work begins, anything above a cost threshold, anything affecting a leased space, anything requiring a vendor outside the standard list. The mistake many facilities teams make is handling approvals outside the maintenance requests system entirely, through a separate email or phone call that leaves no record tied to the ticket.
A defined approval stage inside the same workflow keeps that decision documented and visible, so nobody has to reconstruct after the fact who approved what, or why a request sat waiting for a signature nobody remembered was needed.
Cost-based approval specifically is worth checking for directly: a Not to Exceed amount set on a vendor quote, with the system blocking any invoice submitted above that ceiling, is one documented way this stage gets enforced automatically rather than relying on a phone call. Broader approval routing, for things like leased-space sign-off or vendor exceptions, is worth asking any vendor about directly rather than assuming it's covered, since it's a less universally built-out capability across this category of software.
4. Tracking Status Consistently Across Every Site
Tracking only works if status stages mean the same thing everywhere. Define a small, fixed set, submitted, approved (if applicable), assigned, in progress, resolved, and make sure every technician and site uses them the same way. Without that consistency, work order tracking across a portfolio becomes an approximation, since one site's "in progress" might mean something different from another's.
This stage also needs a built-in escalation trigger. A ticket that sits without a status change for longer than a set threshold should flag automatically, rather than waiting for someone to notice or a tenant to complain, and the cost of missing that window isn't small. MaintainX's 2024 State of Industrial Maintenance survey of more than 1,165 maintenance professionals found unplanned downtime costs an average of about $25,000 per hour, and a ticket that sits silently past its threshold is exactly the kind of gap escalation is built to catch. Threshold trigger alerts scoped by priority and location are what turn that rule into something the system enforces on its own.
5. Closing the Loop at Resolution
Resolution isn't just marking a ticket complete, it includes notifying the original requester and, where relevant, documenting what was done for future reference. A repair that's technically finished still feels unresolved to someone who never heard back, and a completed ticket with no notes attached loses value for anyone trying to spot a recurring issue at that location later.
Why These Stages Have to Work as a Sequence
Skipping or weakening any one stage undermines the ones after it. Poorly structured requests make routing unreliable. Routing without a defined approval stage pushes sign-off outside the system entirely. Inconsistent tracking makes resolution data unreliable for reporting.
UpKeep is one of the platforms facilities directors reference for streamlining this work, and it handles several of these stages reasonably well for single-site or smaller operations. Where the sequence tends to break down at scale is usually stage three, approvals, since that step gets handled informally more often than the others, even in otherwise well-structured systems. We walk through how these same stages connect end to end in The Complete Guide to Work Order Management in 2026.
Where LeanSite AI Fits
LeanSite AI, the platform this article's publisher builds, connects stages one through four as one workflow, according to its own published feature set, including Bulk Work Orders for standardizing intake across a portfolio and cost-based approval enforced through Not to Exceed amounts specifically, which is worth factoring in for teams where the approval stage tends to break down most. As with any vendor's description of its own product, this is worth confirming directly against a trial or demo.
See This Five-Stage Workflow in One System
The clearest way to judge whether a platform actually connects requests, routing, approvals, tracking, and resolution is to walk through a real request from submission to close. Book a LeanSite AI demo to see the full sequence applied to your own portfolio.
FAQ: Facility Service Request Management
Which stage causes the most delay in practice? Approvals, most often. When sign-off happens outside the ticketing system, a request can sit waiting for a decision nobody tracked, which is harder to catch than a delay visible inside the workflow itself.
Do all five stages need software to work? No. They can be defined as process first, but software makes it far easier to enforce consistent routing, approval documentation, and status tracking once request volume grows across multiple sites. We cover how to automate that enforcement in How to Automate Work Order Management in 2026.
How does resolution differ from simply closing a ticket? Closing a ticket marks it done; resolution includes notifying the requester and documenting what was done, which is what makes the record useful for spotting recurring issues later.
A facility service request process is only as strong as its weakest stage. For most multi-site teams, that weak point is the one nobody wrote down.
Written by Pelumi Akinwande, Operations Content Lead at LeanSite, who works directly with multi-site facilities and property operations teams evaluating work order software. Connect on LinkedIn.
© 2026 LeanSite · getleansite.com
