Every building accumulates paper that matters. Warranties, as-builts, commissioning reports, roof guarantees, elevator certificates, fire panel test records, vendor contracts, tenant estoppels, the letter from the city about the sidewalk. Almost none of it is needed this week. All of it is needed eventually, usually urgently, and usually by someone who does not know it exists.

Ask where it lives and you get a shrug and a folder path. That is the real state of building document management for property managers: solved in theory by a shared drive, unsolved in practice because a shared drive answers "where is the file" and never answers "what do we have".

Storage was never the problem

Nobody in this industry lacks somewhere to put a PDF. Buildings have SharePoint, Dropbox, a network share, a folder on the desktop of a laptop that was replaced in 2023.

The problem is that a folder only tells you where a file is. A file called Elevator_Cert_final_v2.pdf in a folder called Compliance tells you nothing about which elevator, which building, when it expires or who signed it. To learn any of that somebody has to open it, and because opening it is work, nobody does until the day the information is needed at speed.

The four questions a document system has to answer

Not "where is the file". These:

What do we have for this asset? Every document attached to the chiller, the roof, the lift, the suite. Not a search, a list.
What expires, and when? Certificates, warranties, contracts and insurance all have dates, and a date in a PDF is invisible.
Which version is current? The third amendment, not the original lease. The as-built, not the tender drawing.
Who is allowed to see it? A vendor needs the equipment manual. They do not need the rent roll.

A document nobody can find in the ninety seconds available is functionally the same as a document you never had, and that is usually discovered during diligence.

Structure beats search

Search is what you reach for when structure has failed. It works when you remember roughly what the file was called and roughly when it arrived, which describes the person who filed it and nobody else on the team.

The alternative is unglamorous: documents hang off the thing they describe. A warranty attaches to the asset it covers. A certificate attaches to the vendor and carries its own expiry. A notice attaches to the lease it was served under. Once that holds, the folder structure stops mattering, because nobody navigates to a document any more, they open the asset and see what is there.

Diligence is the moment this becomes expensive

A sale, a refinance or an insurance review turns a filing habit into a valuation input. The request list is always the same and always urgent: maintenance records, compliance certificates, warranties, service contracts, capital work documentation.

Teams that can produce them in a day look like teams that run their buildings well, and the diligence period stays short. Teams that spend three weeks reconstructing a folder from three people's inboxes create doubt about everything else, and doubt in diligence is priced.

The handover problem, again

Building knowledge does not usually leave in a dramatic way. It leaves when a chief engineer retires, a property manager moves firms, or a management agreement changes hands and a new team inherits a share drive with no map.

What survives a transition is what was attached to something structural: the asset, the vendor, the lease. What does not survive is what lived in a naming convention only one person understood, and that is most of it in most buildings.

What to fix first

Do not start with a migration project. Nobody finishes those, and a half-migrated archive is worse than an unmigrated one because it creates two places to look.

Start at the point of arrival. From today, every certificate that comes in attaches to its vendor with an expiry date. Every warranty attaches to its asset. Every signed contract attaches to its counterparty. Then backfill the categories that carry a date, because those are the ones that hurt when missed, and let the rest of the archive stay where it is until somebody needs it.

Drawings are their own problem

As-builts, floor plans and mechanical drawings behave differently from the rest of the archive. They are large, they are versioned badly, and they are consulted under pressure by someone standing in a plant room.

Three habits cover most of it. Keep one current set per building and mark it as current, instead of trusting a filename to communicate that. Record what changed after every capital project, because the drawing that no longer matches the building is more dangerous than no drawing. And keep a phone-readable version of the floor plans, since the person who needs to find a shutoff at eleven at night is not carrying a plan table.

Email is not a filing system, but it is the intake

Almost every document a building receives arrives as an email attachment, which means the archive is downstream of somebody's inbox and inherits its habits.

The realistic fix is to make filing take one action at the moment of arrival instead of five later: forward it to a place that attaches it to the vendor or the asset, or upload it from the phone that received it. Anything that requires opening a laptop, navigating a folder tree and renaming a file will be done on Friday, or not at all, and "not at all" is what produces the folder nobody trusts.

Retention, and the part people get wrong

Keeping everything forever feels safe and is not. Old tenant files carry personal information you have no reason to hold, and holding it is a liability instead of a precaution.

The practical version for a property team: keep compliance and capital records for the life of the asset plus the statutory period, keep lease documents for the term plus the limitation period, and set a disposal date on tenant personal data instead of keeping it because deleting felt risky. Write it down once, apply it at the point documents arrive, and stop making the decision file by file.

Access is part of the design

A vendor should reach the equipment manual and the site rules without a mailbox round trip, and should never see a lease. A tenant should reach their own documents and nobody else's. A regional manager should see every building; a site team should see theirs.

Most buildings solve this today by emailing PDFs, which is the least controlled option available: once sent, the document is everywhere, permanently, in a form nobody can withdraw.

One last test, and it is worth running this week. Pick a piece of equipment somebody would panic about, the main switchgear or the fire panel, and ask a colleague to produce its warranty, its last service record and the name of the contractor who commissioned it. Time them. Whatever that number is, it is also your diligence answer, your insurance answer and your two-in-the-morning answer, because they are all the same question asked with different amounts of pressure.

Where BuildingHub fits

Smart Record Storage in Operations Hub attaches documents to the asset, vendor or lease they belong to, tracks the ones that expire, and keeps vendor-facing material separate from anything commercial. Certificates of insurance are handled as records with dates instead of files in a folder, which is the difference between tracking and hoping. Related: COI tracking for commercial buildings.

Where building documents go to die