The management logic behind Facility Management
Facility Management is not a single process. It is an interdisciplinary domain that requires management logic to work as one system. This page describes that logic: the levels at which decisions are made, and the loop in which demand, strategy, service and improvement feed one another. It is a management system and a lifecycle — not the definition of FM itself.
Forcing FM into one linear process loses the domain. The logic below orders decisions; it does not replace the demand organisation, the services or the knowledge domains.
Strategic, tactical, operational
The three management levels are not invented here: they are derived from ISO 41002:2026, Facility management — Development of the facility management organization (published June 2026), which describes the development of the FM organisation across strategic, tactical and operational management levels.
- 01
Strategic
Horizon: 3–10 years
This level establishes what the organisation requires from its built environment and services: which outcomes, which level of risk, which portfolio, which policy and which market position. Decisions are few, heavy and hard to reverse — property choices, sourcing direction, policy frameworks, investment level. ISO 41002:2026 places here the link between core business objectives and the mandate of the FM organisation; ISO 41014:2020 and ISO 41018:2022 supply the matching strategy and policy development.
- 02
Tactical
Horizon: 1–3 years
Here strategy is converted into requirements, service design, contracts and performance frameworks. The tactical level translates: from policy statement to specification, from specification to sourcing choice, from sourcing choice to contract and indicators. It is also where capacity, budget and information provision are calibrated annually. Neglect at this level is the most common reason a well-written strategy never lands in operations.
- 03
Operational
Horizon: day to quarter
At operational level services are delivered, reported, repaired, measured and adjusted within existing frameworks. Decisions are numerous, small and fast: deployment, prioritisation, resolution, compliance, safety. This level produces the evidence — requests, measurements, costs, user experience — with which the tactical and strategic levels can test their own assumptions. Without that feedback the system goes blind.
From demand to recalibrated demand
Thirteen steps, one loop. The last step feeds the first: delivery changes what the organisation can reasonably ask for. Do not read it as a one-way line — several iterations run in parallel at all times, at different speeds and different levels.
- 01Strategic
Understand Demand
Establish what the core business, the people and the place actually require — before any solution appears.
- 02Strategic
Set Strategy
Choose direction: outcomes, portfolio, risk, sourcing direction and investment level (ISO 41014:2020).
- 03Strategic
Develop Policy
Fix strategy into frameworks against which decisions can be tested (ISO 41018:2022).
- 04Tactical
Specify Requirements
Convert policy into testable requirements: performance, quality, availability, compliance, information.
- 05Tactical
Design Services
Compose requirements into services with a comprehensible scope, responsibility and interface.
- 06Tactical
Source
Determine who delivers and in what composition: self-delivery, stand-alone, bundled or integrated (ISO 41012).
- 07Tactical
Contract
Fix performance, payment, information duties and exit — a variable separate from sourcing.
- 08Tactical
Mobilise
Transition into delivery: people, data, systems, access, working methods and knowledge handover.
- 09Operational
Deliver
Day-to-day delivery within the agreed frameworks, with the user as direct recipient.
- 10Operational
Monitor
Measure what was agreed and surface what deviates — factually, not anecdotally.
- 11Tactical
Evaluate
Judge whether delivered performance serves the intended outcome, not merely whether the target was met.
- 12Tactical
Improve
Intervene in design, contract, information or organisation — wherever the cause sits.
- 13Strategic
Recalibrate Demand
Return the evidence from delivery to demand itself. This step feeds the first; here the loop closes.
Step 13 feeds step 1. The loop never stops and has no end point.
Back to Understand Demand
Which standard belongs to which part of the loop
- ISO 41001Facility management management system — requirements
The whole loop, as auditable requirements
Sets the requirements the system as a whole must satisfy: policy, roles, objectives, control, evaluation and improvement.
- ISO 41002:2026Development of the facility management organization
The FM organisation that runs the whole loop
Gives guidance for building an FM organisation operating at strategic, tactical and operational levels. Source of the level structure on this page.
- ISO 41014:2020Development of a facility management strategy
Set Strategy
Connects core business objectives with strategic FM choices and their justification.
- ISO 41018:2022Development of a facility management policy
Develop Policy
Describes how policy is formed, adopted and made authoritative for later decisions.
- ISO 41012Strategic sourcing and development of agreements
Source & Contract
Guidance for sourcing choices and building agreements. A second edition is in development.
- EN 15221-8:2025Process architecture for facility management
Underlying process architecture & PDCA framing
Lays the process architecture beneath the loop and is aligned with the ISO 41000 series; supplies the PDCA framing used below.
Coming in Part 7
Is this a lifecycle, a management system, or a value chain?
All three readings appear in the literature and all three explain something. Read as a lifecycle, the emphasis falls on time: requirements age, contracts expire, buildings and use change. Read as a value chain, the emphasis falls on successive addition of value — the reading Porter made popular, and a poor fit for FM, because FM does not pass a product along but sustains an environment in which others create value.
This platform treats the whole as a management system with an embedded operating loop. That is a deliberate choice. A management system sets requirements for decision-making, responsibility and evidence without prescribing one order of action; the embedded loop shows that the steps feed one another repeatedly rather than once. A rigid process model would suggest FM ends at evaluation, and a value chain would suggest the demand organisation stands at the start and then disappears. Neither is true.
Relation to Plan-Do-Check-Act
Beneath the thirteen steps lies the PDCA rhythm that EN 15221-8:2025 explicitly adopts as process architecture for FM, aligned with the ISO 41000 series. Understand Demand, Set Strategy, Develop Policy, Specify Requirements, Design Services, Source and Contract together form Plan: the decision before delivery. Mobilise and Deliver are Do. Monitor and Evaluate are Check, monitoring being the measurement and evaluation the judgement of what that measurement means. Improve and Recalibrate Demand are Act — and this is exactly where FM departs from a simple quality circle: Act intervenes not only in delivery but in demand itself, so the next Plan starts from different premises. PDCA is therefore the rhythm, not the content; the thirteen steps are its FM-specific substance.
ISO 41001; ISO 41002:2026 (June 2026); ISO 41012 (second edition in development); ISO 41014:2020; ISO 41018:2022; EN 15221-8:2025. Paraphrased, not quoted verbatim.