What Happens When Maintenance Lives in People Instead of Systems
The Difference Between Activity and Control
In many residential communities, maintenance is not governed by a system. It is governed by availability.
Requests come in through the front desk, through calls, through direct outreach to technicians. Staff relay information as quickly as possible, and the team responds based on who is reachable and what else is already in motion. Work gets completed, issues are resolved, and from a resident perspective, service appears to function.
From a management perspective, however, something very different is happening.
There is no consistent structure controlling how work enters the system, how it is assigned, how it progresses, or how it is completed. Instead, the operation relies on individuals to carry context, remember status, and follow through on tasks that are often interrupted by competing priorities.
At that point, maintenance is no longer a system. It is a collection of actions.
🔵The Difference Between Activity and Control
For General Managers, the distinction between activity and control is where operational risk begins to surface.
A building can be extremely active. Calls are being answered, technicians are moving throughout the property, and issues are being addressed as they arise. On the surface, this can feel like responsiveness.
But responsiveness without structure is not control.
Control requires the ability to answer very specific questions at any given moment:
Where does each request currently sit? Who is responsible for it right now? What is preventing it from being completed? How long has it been in that state?
In an unstructured environment, those answers are rarely available without manually reconstructing the situation. They exist across conversations, partial notes, and individual memory, but not within a system that can be relied upon in real time.
That gap is where inconsistency — and eventually risk — begins to develop.
🔵When Work Has No Defined Path
In the absence of a structured workflow, maintenance requests do not move through a lifecycle. They move through people.
A request may begin with a phone call, transition to a technician, pause when a part is required, and resume only when someone remembers to follow up. Responsibility shifts informally, and progress depends on individual awareness rather than a defined process.
From a distance, work continues to move. Internally, however, there is no clear line of ownership or visibility into where any given task stands at a specific point in time.
This becomes particularly challenging when multiple departments intersect. Procurement, vendor coordination, and internal maintenance all contribute to the same outcome, but without a shared system, there is no unified view of how those pieces are progressing together.
For leadership, this creates a blind spot. The building appears operational, but the underlying process is not measurable or controlled.
🔵The Risk That Develops Quietly
Workarounds are often viewed as harmless. They are practical solutions created by experienced teams who understand how to keep operations moving.
However, when examined more closely, they introduce a level of fragmentation that is difficult to detect and even harder to manage.
Information becomes distributed across multiple locations. Visibility is reduced to what an individual happens to know or can access quickly. Accountability becomes tied to people rather than to processes.
In situations that require speed and clarity — whether maintenance-related, operational, or safety-driven — staff are forced to make decisions based on incomplete context. They are choosing between following a process that is too slow to support the situation or acting on what they can access immediately.
In most cases, they choose speed.
That choice is understandable, but it has consequences. It means the system designed to support the building is no longer the system being used to operate it. The building is effectively running on a combination of formal tools and informal workarounds, with no single source of truth governing both.
🔵A Small Question That Revealed a Larger Issue
During a working session with a maintenance team, the conversation moved into the unit data view — the central record for each unit, where resident information, history, and documentation are stored.
While reviewing that unit card, one of the technicians asked whether images could be attached directly to it.
The question itself was straightforward. The implication behind it was not.
The technician explained that having immediate access to the location of cutoff valves within the unit would change how they respond to emergency leaks. Under the current process, identifying those valves required leaving the unit, locating physical plans, interpreting them, and then returning to shut off the water.
By the time that sequence was completed, the situation had often escalated.
What the technician was asking for was not additional documentation. It was the ability to act immediately, with the right information, at the point of need.
From a General Manager’s perspective, this is where the issue becomes clear.
Critical operational knowledge existed. It was simply not accessible in a way that supported real-time response.
🔵When Structure Changes Behavior
Once maintenance workflows are brought into a structured system, the shift is not primarily about efficiency. It is about consistency.
Requests enter through a defined intake. Responsibility is assigned explicitly. Status is visible without requiring follow-up conversations. Dependencies, such as procurement, are tracked as part of the same process rather than as separate efforts.
Instead of relying on individuals to remember what needs to happen next, the system carries the work forward.
The concept often described as “ball in court” becomes visible rather than implied. At any given moment, leadership can see exactly where responsibility sits and what is required to move a task forward.
This changes how decisions are made.
It also changes how risk is managed.
🔵What This Means for Operational Leadership
When maintenance lives in people instead of systems, performance becomes uneven by definition.
Strong team members compensate for gaps. Experienced staff carry context others do not have. Processes work well — until they don’t.
From a leadership standpoint, this creates a fragile operation. It depends on continuity of staff, informal communication, and individual follow-through to maintain consistency.
That model does not scale, and it does not hold under pressure.
When maintenance is structured within a system, the operation becomes independent of any single individual. Work is defined, tracked, and completed within a controlled environment where visibility exists at every stage.
For General Managers, that distinction is critical.
It is the difference between managing activity and managing the operation itself.
🔵A Different Standard for Maintenance
The standard for maintenance is not how quickly a technician can respond to a call.
It is whether the operation provides full visibility, clear ownership, and immediate access to the information required to act.
When those conditions are in place, response becomes faster not because individuals are working harder, but because the system removes the friction that slows them down.
That is what creates consistency across the building.
🔵CE OneSource
Maintenance should not depend on who is available, who remembers, or who happens to be involved at the moment.
It should depend on a system that carries the work — clearly, consistently, and completely — from start to finish.
Concepts Definition
The structured progression of a maintenance request from intake through assignment, execution, and completion.
The ability to see the real-time status, ownership, and progress of all active work within the building.
Processes carried out through calls, texts, or verbal coordination rather than within a structured system.
The ability to clearly identify who is accountable for a task at any point in time.
Dr. Robert Bess is the founder and CEO of CE OneSource and Global Building Technologies, with more than 35 years of experience across construction, closeout, warranty, and building operations. As the architect behind CE OneSource, his work focuses on eliminating operational fragmentation and establishing structured, lifecycle-based systems that carry buildings from construction through long-term operations without loss of continuity. Dr. Bess has led operational readiness efforts across large-scale hospitality developments, integrated resorts, and luxury high-rise residential communities, and writes on building lifecycle intelligence, operational continuity, and the systems that allow buildings to remember — and learn.
AI Summary
“Many buildings manage maintenance through informal workflows such as phone calls, text messages, and verbal coordination rather than structured systems. This creates limited visibility, inconsistent response times, and difficulty tracking responsibility. When maintenance lives in people rather than systems, the operation becomes dependent on individual staff performance — a model that does not scale and does not hold under pressure. CE OneSource structures the full maintenance lifecycle within a single environment, creating visibility, accountability, and consistency across the building. “
