The Data Custody Gap: Who Can Use Building Technology Data?

The Data Custody Gap Is an Operations Problem

Modern buildings generate a steady stream of readings, alarms, access events, tickets, network status, energy information, and maintenance records. Yet a building can have plenty of data and still struggle to make a basic operating decision. The problem is often not missing information. It is missing shared meaning, clear responsibility, and dependable access to the context needed when something goes wrong.

This episode examines the data custody gap: the operational gap that appears when nobody has clearly defined who validates building information, what a record means, who may use it, and who keeps it current as equipment, people, vendors, and systems change.

When Different Names Point to the Same Equipment

The episode opens with a realistic cooling issue. Three tenant suites begin getting warm, but the control screen, service ticket, and work-order record each use a different name for what may be the same asset. One system calls it AHU4. Another calls it Northwing Supply. A third identifies it as asset 117. The person with the only useful trend history is unavailable.

Forty minutes later, the team still cannot answer whether the issue is local to one piece of equipment or affecting a larger area. The technical problem may be manageable, but the response has stalled because people cannot confidently connect their records to the same physical asset.

• Tenants need to know what is happening and whether their work should change.
• Operations teams need to know the affected area, the likely cause, and the next action.
• Service providers need enough context to diagnose the problem without spending the first part of the call reconciling names.
• Leadership needs a credible update based on what is known, what is being checked, and when the next update will come.

In this situation, the building has not run out of data. It has run out of shared meaning.

Start With the Decision, Not the Dashboard

A colorful dashboard is not automatically useful. Information becomes useful when it supports a real operating decision. The episode recommends starting with the workflow and asking practical questions:

• Is the equipment operating within its expected range?
• Did something change from yesterday?
• Can the responder identify the asset and its location?
• Can they see recent history and determine the next action?
• What breaks if this system or process goes down?

The answers determine what information deserves attention. During routine maintenance, an asset record and service history may be enough. During a cooling issue, alarm timing, recent sensor work, affected areas, escalation authority, and trend history may become critical evidence.

The same applies beyond HVAC equipment. Access events, network status, service tickets, and energy information matter when they connect directly to an operating decision. The mistake is treating every available data point as equally important rather than identifying the minimum information needed to protect continuity.

What Data Custody Actually Means

Data custody is not limited to legal ownership. In this discussion, it means operational care for information. A system may collect a value, but someone must be accountable for confirming that it is accurate, defining what it means, determining who can use it, and keeping it current.

For example, someone needs to recognize that AHU4 and Northwing Supply identify the same asset, correct the relevant records, and ensure the next technician can understand the connection without relying on the memory of the person who installed the equipment.

That responsibility becomes harder when multiple teams contribute to the same workflow:

• Facilities understands the equipment and the building outcome it must support.
• IT manages connectivity, identity, and system boundaries.
• Security may control sensitive event information.
• A service provider may operate part of the platform or hold useful diagnostic history.

No single department must own everything. But every critical workflow needs an accountable role. If a record is wrong, someone must be responsible for ensuring it gets corrected.

Ownership Requires an Operating Mechanism

Assigning an owner on paper is not enough. A maintenance supervisor may be accountable for an asset record, but that person cannot maintain reliable information if every project uses a different naming convention, handoffs are incomplete, and nobody has time or authority to validate the information.

Effective custody requires more than a name on a responsibility list. It requires:

• An accountable role with time and authority to act.
• A required validation checkpoint.
• A visible handoff process.
• Clear authority to correct inaccurate records.
• Consistent naming across controls, work orders, preventive maintenance schedules, and service records.

A renovation provides a useful example. New air handling units are installed, the project closes, and the operating team receives a spreadsheet. The spreadsheet uses one equipment name while the control screen uses another. The preventive-maintenance schedule misses an asset, and the last verified sensor replacement date is unavailable. The equipment transferred, but its operational context did not.

During normal work, people can compensate with memory. During an urgent call, they lose time matching names instead of diagnosing the condition. Reliable maintenance includes reliable information around the asset.

Access Should Match the Job

Better custody does not mean unrestricted access for every person. The episode recommends separating four questions:

• Who needs to know an issue exists?
• Who needs detail to diagnose it?
• Who can change the system?
• Who communicates the impact?

These may be different roles. Access should match the job and the organization’s risk model while still making necessary information available to the people who need it. Facilities and IT should coordinate before an outage, not make assumptions about who owns information while people are waiting for an update.

Review Information at Custody Events

The best time to discover a data custody problem is not during an incident. Review workflows at moments when information is likely to change:

• Project completion.
• A service-provider transition.
• A staff change.
• A system upgrade.
• A change in how the building is used.

The review does not need to become a large program. Test one workflow with a real operating question. Do not simply confirm that a dashboard loads. Ask which equipment serves an area, what changed recently, who receives the alert, and who acts next.

A 10-Minute Data Custody Review

Listeners can begin this week by selecting one workflow that matters when something goes wrong. Define the operational question it must answer, such as which area is affected or who needs to respond. List the minimum records required. Name the accountable role. Consider what happens if that person changes or the system is replaced.

Then test the workflow with someone outside the project team. Ask them to find the asset, interpret the record, and identify the next action. If they get stuck, treat that as process feedback, not user failure.

The goal is not perfect information. The goal is trustworthy information at the moment a decision has to be made. Keep records understandable, validate them when the building changes, and preserve context when people or service relationships change.

The Data Custody Gap: Why Building Data Fails When Operations Need It Most

Buildings produce more information than ever. Automation systems generate readings and alarms. Equipment records track maintenance. Access systems log events. Networks report status. Service platforms store tickets, work orders, and diagnostic history. Energy information can reveal changes in operating conditions.

Despite this volume, building teams can still lose valuable time during an incident because they cannot answer a basic question: what does this information mean, and who can act on it?

That is the data custody gap. It appears when building information exists but is not dependable in the context where someone must make a decision. The issue is not merely technical. It affects tenant communication, maintenance response, security coordination, business continuity, and confidence in the organization’s ability to operate the property.

More Data Does Not Automatically Create Better Decisions

Consider a cooling complaint involving several tenant suites. A control screen identifies the relevant equipment as AHU4. A service ticket refers to Northwing Supply. A work order calls it asset 117. Trend history exists, but the person who knows where to find or interpret it is unavailable.

The team may be looking at real records in each system. But if nobody can verify that all three names identify the same asset, the response slows down. Instead of determining whether the problem is isolated or spreading, the team spends time reconciling vocabulary.

That delay matters. Tenants do not experience the incident as a data-management issue. They experience warm spaces, uncertain communication, and a lack of clarity about what happens next. A technical issue can still take time to resolve, but a coordinated response should begin immediately.

The practical lesson is simple: begin with the decision, not the dashboard. Ask what a person needs to know in order to take the next dependable action.

• Is equipment operating within its expected range?
• What changed from the previous day?
• Which asset serves the affected area?
• What work was performed recently?
• Who is authorized to request deeper review or escalation?
• Who is responsible for communicating the impact?

When information answers these questions, it supports operations. When it does not, it may be technically available but operationally incomplete.

Data Custody Is Operational Care

Data custody should not be understood only as a legal ownership question. In a building environment, custody is operational care for information. It includes deciding who validates a record, who defines what a name means, who can use the data, and who keeps the information current through changes.

For an asset record, this can be as straightforward as ensuring that the name in the control system, the work-order system, the preventive-maintenance schedule, and the service-provider platform all point to the same equipment. It also means preserving information that may matter later, including recent sensor work, service history, alarm timing, affected areas, and escalation paths.

Without that care, teams depend on individual memory. Someone may know that AHU4 and Northwing Supply are the same unit. Someone may remember which areas the equipment serves. Someone may know which provider can access the useful trend history. But a process dependent on one person’s memory is not dependable. It is fragile by design.

Accountability Needs More Than an Owner Field

Many organizations respond to unclear information by assigning an owner. That is necessary, but it is not sufficient.

A named owner cannot repair a broken process alone. If projects use inconsistent naming conventions, if the handoff to operations is incomplete, if records cannot be updated easily, or if the accountable role has no time to validate the information, ownership remains theoretical.

Reliable custody combines accountability with an operating mechanism. Every critical workflow should have an accountable role, but it should also include a visible handoff, a required validation step, and authority to correct records when they are wrong.

Renovation closeout is a common pressure point. New equipment may be installed and activated successfully, while the information around that equipment arrives as a spreadsheet with incomplete context. The control system may use one label, the maintenance program another, and the service history may omit recent work. In normal conditions, staff can often compensate. In an urgent call, the first part of the response becomes a search for basic context.

The equipment has transferred, but the context has not. That gap reduces reliability even if the physical installation is sound.

Facilities, IT, Security, and Providers Need Defined Roles

Building data crosses operational boundaries. Facilities understands what equipment must do for the building. IT understands connectivity, identity, and system boundaries. Security may manage sensitive event information. A service provider may operate a platform or hold diagnostics needed for troubleshooting.

The goal is not to force every record into one department. It is to clarify responsibility before an incident creates pressure. Teams can begin by separating the roles involved in each workflow:

• Who needs to know that an issue exists?
• Who needs detailed information to diagnose it?
• Who can change the system?
• Who provides technical support for the connection or platform?
• Who communicates operational impact to occupants or stakeholders?

These roles may overlap in a small organization or remain distinct in a larger property portfolio. What matters is that they are understood and tested. No one should be guessing during an outage whether facilities, IT, security, or a service provider has the next responsibility.

Access also requires care. Effective custody is not unrestricted access to every system and record. Instead, access should match the job and the organization’s risk model. The necessary information must be available to the people who need it, while sensitive information and system-change authority remain appropriately controlled.

Test Information With Maintenance Questions

A dashboard loading successfully does not prove that a workflow works. A better test uses the questions someone would ask during routine maintenance or an incident:

• Can a technician find the asset?
• Can they identify the affected area?
• Can they see the last relevant work?
• Can they tell what changed?
• Can they identify the next action and the responsible role?

These questions reveal whether information is actually usable. They also expose the difference between a system that stores data and a process that supports operations.

The most valuable test involves someone who did not build the process. Ask that person to locate an asset, interpret the record, and identify what happens next. If they cannot do it, the answer is not to blame the user. The result is feedback that the process needs clearer naming, better handoff, more complete records, or a more visible escalation path.

Review Custody When Change Happens

Waiting for an incident to find gaps is costly. Review critical information at custody events: project completion, service transitions, staff changes, system upgrades, and changes in how a building is used.

These are the moments when names, responsibilities, access requirements, equipment context, and communication paths are most likely to shift. A focused review does not need to become an enterprise-wide data program. It can begin with a single critical workflow.

Write down the operational question that workflow must answer. For example: Which area is affected? Which equipment serves it? What changed recently? Who responds next? Then list the minimum records required to answer those questions. Name the accountable role, define the relevant users, and test whether the information survives a personnel change or system replacement.

Trustworthy Information Creates Operational Credibility

The goal is not perfect information. Buildings change, systems evolve, people move between roles, and vendor relationships shift. The goal is trustworthy information at the point where a decision must be made.

When custody is clear, an occupant request maps to an asset. The asset maps to the affected area. Recent work is visible. The accountable operations role is known. The technology support path is understood. Communication responsibility does not need to be invented in the moment.

The technical problem may still require time to resolve. But the team can begin coordinating immediately and explain what is known, what is being checked, and when the next update will come. That credibility improves the operating experience for tenants, staff, service teams, and leadership.

For organizations responsible for commercial properties and technology environments, the next step is practical: choose one workflow that matters when something goes wrong. Identify the question it must answer, the minimum information it requires, the role accountable for its accuracy, and the people who need access. Then test it with someone outside the project team.

To hear the full conversation on making building information usable through change, listen to this episode of Built, Wired & Secured.