You Just Inherited an Undocumented Building. Now What?

At some point you will be handed a building nobody has documented. The as-builts describe a different mechanical layout. The point list is a spreadsheet from 2014 with a tab called final_v3_REVISED. Nobody knows the supervisor password, and the contractor who built it has been out of business for six years.

This is normal. It is also the situation where your first week determines the next three years, because everything you fail to write down now becomes something you rediscover repeatedly later.

The mindset that helps. You are not trying to fix this building in week one. You are trying to build an accurate map of it. Every hour spent on the map pays back the first time something breaks at 4pm on a Friday.

Day one: get access before you need it

Access problems are the thing that turns a two-hour job into a two-week job, and they are always discovered at the worst possible moment.

Supervisor and workstation credentials — and confirm they actually work, on site, before you leave.
Controller-level access for each platform present. A supervisor password is not the same as a controller password.
Gateway configuration logins. These are the most commonly lost credentials in any building, and a factory reset to recover one wipes the point mapping with it.
Network details from IT — IP scheme, VLAN, what's allowed through the firewall, and who to call when it changes.
Remote access, if it exists, and how it is secured.

Test every credential the day you receive it. A password that was written down wrong, or that belongs to an account that has since been disabled, is functionally the same as no password at all — but you won't discover which until you're standing in front of a panel needing it.

Week one: build the inventory

You cannot maintain what you cannot enumerate. Build the list before you build opinions.

Layer	What to capture
Supervisory	Platform and version, station names, where it physically lives, backup status
Network	IP addresses, subnets, VLAN, BACnet network numbers, router and BBMD configuration
Field trunks	Protocol, baud rate, device addresses, physical routing, termination
Devices	Make, model, firmware, address, what equipment it serves
Gateways	Make, model, both-side protocols, point mapping export
Legacy	Anything proprietary or out of production — flag it now, source documentation while you can

Discovery tools do a lot of this for you. A BACnet browser will enumerate devices and objects. A Modbus master will confirm what answers on a trunk. Where documentation is missing, the live system is the most accurate record available — capture it while you have access.

Back everything up before you change anything

Before the first configuration change, take a full backup: station, controller programs, gateway point mappings, graphics. On a building with no documentation, the current running configuration is the only description of the system that exists. Losing it is unrecoverable.

Store it somewhere that is not the building.

The three faults to check before anyone asks

In a building nobody has been maintaining, these three are common enough to be worth checking proactively — and all three are invisible from the front end.

Simultaneous heating and cooling

Trend heating valve, cooling valve and discharge air on a sample of zones at five-minute intervals for three days. In an undocumented building with copied templates, if one box has an inverted valve, many probably do.

Sensor drift on the high-leverage sensors

Outdoor air first, then discharge air. A drifted outdoor sensor silently disables economizers across every unit that references it.

Economizers that never run

Trend outdoor air temperature, damper position and mechanical cooling together across a few days of suitable weather. Mechanical cooling running through free-cooling weather is common and expensive.

Finding any of these in your first month is also, frankly, good politics. It converts “the new tech is still getting up to speed” into “the new tech found something everyone else missed.”

Then look at the alarms

Pull thirty days of alarm history and sort by frequency. In an unmaintained building this list is usually dominated by a handful of alarms firing hundreds of times, which is why nobody reads any of them. Fixing the top few restores the alarm system as a usable channel — and tells you a great deal about what has actually been going wrong.

Write it down as you go, not at the end

Keep the inventory in a shared location, not on your laptop. The point is that the next person finds it.
Photograph panel interiors, nameplates and terminations as you open them. Two minutes now, hours saved later.
Record what you didn't finish. A documented gap is far more useful than a silent one.
Note anything you deliberately left alone, and why.

The building you inherit undocumented is the building someone else will inherit from you. The difference between those two handovers is entirely a matter of what you chose to write down while you were learning it.

Go deeper

The method behind this, chapter by chapter

Every sensor, drive and control loop in the building — how it works, how to prove it with a meter, and how it fails. BAS Field Fundamentals is the method this article uses, with 20 field cases and a browser diagnostic simulator to practice on.

Get BAS Field Fundamentals

Found a wrong number or a broken link? Tell me and I’ll fix it.