How a service request becomes project work in facilities management

Learn how to tell when a service request signals project work in facilities management. The key cue is a change in the facility’s function, which triggers planning, approvals, and a defined timeline. Other factors like suppliers, equipment, or budgets alone don’t define a project.

What makes something project work in facilities management? It’s a question that comes up more often than you might think, especially when you’re juggling routine maintenance with bigger moves that shift how a building functions. The answer is both simple and surprisingly nuanced: a project usually begins when the requested work changes the function of the facility—how it’s used, what it can do, or who uses it. Everything else can feel like “just another task,” but once the operation or purpose shifts, you’ve stepped into project territory.

Let’s unpack what this really means in the real world of FM, beyond policy manuals and buzzwords.

Why “changing the function” is the gold standard

Imagine walking through a building and spotting a simple electrical upgrade: wiring for new lighting in a hallway. That’s a common repair or upgrade—no dramatic shift in how the building operates. The function remains the same: people still move, work, and gather in the same spaces, just under better lighting.

Now switch the lens: what if that same space is being converted from a general office to a specialized lab with chemical storage, fume hoods, and precise ventilation? Or consider repurposing a conference room into a data center with raised floors, climate control tuned to equipment heat loads, and tight power management. Suddenly, you’re not just replacing parts; you are reconfiguring capabilities, workflows, and safety requirements. The building’s function is changing, and with it, the project becomes: a defined initiative with planning, design changes, approvals, and a start-to-finish timeline.

That “change of function” criterion is what separates ongoing maintenance from a true project. It signals that the work isn’t just about keeping things running at today’s standards—it’s about repositioning the building to support new needs, new uses, or new levels of performance.

Keeping the line clear between routine tasks and project work

There are several signals that help FM leaders decide whether a request is project work or something more routine. The most reliable signal, as we’ve just discussed, is functional change. But there are other considerations that often accompany a shift in function and help keep the decision-making process transparent:

• Scope and complexity: If the work requires design changes, permits, or reconfiguring utilities and spaces, it’s more likely to be a project. Routine tasks tend to fit within existing layouts and don’t demand significant redesign or risk assessment.

• Stakeholder impact: Projects typically involve multiple departments, users, or occupants—think lab managers, safety officers, or building engineers. If a request touches several groups, you’re probably in project territory.

• Timeline and milestones: Projects have a defined start, major milestones, and a finish. Routine tasks have a steady cadence and no formal stop/start points.

• Risk and compliance: If the change triggers safety, regulatory, or code implications, you’re stepping into project management territory. Compliance planning, approvals, and testing become essential.

• Budget governance: While budget thresholds aren’t the defining feature of a project, they’re a governance signal. If a change requires formal approvals, it often sits within a project framework, even if the expenditure itself isn’t extraordinary.

The human side: stakeholders, conversations, and the why

Projects aren’t just about numbers and schedules. They’re about people—the people who will use the space, the people who must keep it safe, and the people who must adapt to new workflows. When a space is reimagined, the questions aren’t only technical; they’re practical, almost intimate. How will occupants move through the space? How will the new layout affect collaboration, privacy, or acoustics? What’s the plan for training users on new systems? These questions underscore why a function-changing project needs a formal approach: to ensure people can still do their jobs smoothly, safely, and efficiently after the change.

Let me explain with a quick vignette. Picture a corporate campus deciding to shift a wing from general offices to a collaborative, activity-based work environment with hot-desking, shared huddle rooms, and flexible furniture. It’s a “smarter” use of space, but it also means new IT infrastructure, different HVAC zoning, acoustic treatments, and updated wayfinding. It’s not something you fix with a simple reorder of desks. It’s a project because it redefines how the building functions for its occupants, touching every corner from electrical loads to user experience.

Planning for project work: the lifecycle in FM

Once you’ve identified a change in function as the driver, you’re naturally stepping into the project lifecycle. Here are the typical stages you’ll see in FM practice:

• Initiation: Define the need, articulate the intended function change, identify key stakeholders, and establish high-level objectives. This is where you decide whether to proceed with formal project governance.

• Feasibility and design: Assess feasibility, explore design options, and begin early coordination with architects, engineers, and safety specialists. This stage answers: how will the function change, and what will it require to get there?

• Approvals and governance: Secure the necessary approvals from building owners, tenants, and regulatory bodies. This is the “red tape” part, but essential for ensuring compliance and accountability.

• Detailed planning: Develop a detailed scope, schedule, budget, and risk plan. Define milestones, procurement needs, and change-control processes.

• Execution: Implement the design and construction work. Coordinate trades, test systems, and manage on-site safety and quality.

• Commissioning and handover: Verify that the new function performs as intended, train users, and transfer operation and maintenance responsibilities to the facilities team.

• Post-implementation review: Assess whether the change met the intended objectives, capture lessons learned, and adjust operations as needed.

In practice, you’ll often see the line between maintenance tasks and projects blurring at the planning stage. A preventative maintenance upgrade might evolve into a project if it’s paired with a space reconfiguration or a new occupancy pattern. That’s not a failure of process—it’s a natural consequence of designing buildings that flex with users’ needs.

Budget, risk, and governance: the cadence of a project

Budget thresholds matter, but they’re governance levers, not the sole determinant of whether something is a project. The larger point is about risk and accountability. Projects typically require formal risk assessments, scheduling rigor, and stakeholder sign-offs. Routine work tends to ride on established contracts, valid for day-to-day operations, with fewer moving parts and fewer layers of approval.

This is where many FM teams find themselves juggling the balance between agility and control. You want to avoid bureaucratic drag, but you also want to protect occupants, ensure safety, and keep performance goals in sight. The sweet spot often involves a tiered approach: routine improvements under a certain cost and scope get delegated to operations, while larger, function-changing initiatives go through a light but structured project governance process. The key is to have clearly defined criteria—functional change being the compass that guides decisions.

Real-world examples: when a change is a project, when it isn’t

• A building shifts from mixed-use to a high-density residential cluster with common lounges and shared kitchens. The function changes: the building isn’t just housing; it’s creating community spaces, requiring different life-safety planning, ventilation considerations, and waste systems. Project territory, for sure.

• An electrical panel upgrade to support more robust data center operations in a former storage area. If this upgrade enables new capabilities and space usage that weren’t part of the original design, it’s a project because it alters how the space is used and what it can support.

• Upgrading lighting in hallways to LED for energy efficiency, without changing how spaces are used. Here, the function remains the same. It’s likely routine work, as it improves conditions without altering occupancy patterns or space configurations.

• Reconfiguring a conference suite into a multi-purpose collaboration hub with movable walls and integrated AV. The function changes—spaces are used differently, with new workflows and user experiences—so project management comes into play.

A more intuitive lens: the “why” behind the change

Beyond technical criteria, the underlying motive often reveals the nature of the work. If the change is intended to unlock new capabilities, support evolving operations, or accommodate different user groups, you’re more likely dealing with project work. If the goal is to maintain status quo, fix something broken, or restore a previous condition, you’re probably looking at routine tasks.

This pivot isn’t just academic. It affects how teams communicate, how timelines are set, and how success is measured. Projects typically define success in terms of outcomes—space usability, occupancy comfort, safety compliance, and operational resilience—rather than merely completing a task on schedule. That outcome-oriented mindset helps FM professionals align with broader organizational goals, from sustainability targets to occupant well-being.

A practical mindset for FM teams

If you’re navigating a busy FM portfolio, here are a few pragmatic tips to keep this distinction clear without slowing things down:

• Create a simple decision rubric: a checklist that asks, “Does this change how the space is used?” and “Does it require new approvals, design changes, or safety considerations?” If yes to any, lean into project governance.

• Document the rationale: even for what seems like a minor change, write down why the function needs to change. It helps keep stakeholders aligned and creates a trail for future reference.

• Build cross-functional awareness: involve facilities, safety, IT, and operations early. When multiple groups are affected, project collaboration is more efficient.

• Track outcomes, not just tasks: after a function-changing initiative, measure impact in occupancy satisfaction, efficiency gains, or safety improvements. It reinforces the value of the project approach.

• Maintain flexible workflows: have a nimble process for altering scope if needs shift. Buildings aren’t static, and neither should your project plans be.

A closing thought: the beauty of intentional change

There’s something satisfying about recognizing when a request truly marks a shift in a building’s life. It signals forward momentum—the architecture responding to evolving needs. It also invites a kind of disciplined creativity: you’re not just patching things up; you’re reimagining how space serves people.

In the end, the criterion that really stands out is simple but powerful: a project is born when the requested work changes the function of the facility. That single idea—function as the defining line—helps FM teams navigate the maze of maintenance, upgrades, and transformations with clarity and confidence. And as buildings continue to adapt to new technologies, new workflows, and new ways of working, that clarity remains a steady compass, guiding everything from budgeting conversations to safety planning. If you start from that principle, you’ll find yourself thinking not just about what needs to be done, but about how the space will live and breathe once the work is complete. That’s the heart of effective facilities management.