← All articles

Document Management for Hospital Facilities: The Archive of a Building That Never Closes

HealthcareFacilitiesDocument ManagementOwners

A hospital is never finished. A wing opens, a department relocates, an imaging suite is gutted and rebuilt around a new machine, a boiler is replaced, a corridor is re-rated. Each of those projects hands the facilities department another stack of drawings — and the campus keeps running the whole time.

That is what makes document management in healthcare facilities a different problem from a commercial office or a school district. The archive isn't a record of a building. It's a record of fifty years of continuous surgery on a building that never closed.

Here's what that means in practice, and what a system has to do to keep up.

Why hospital drawing archives are harder

Renovation is continuous, not periodic. In most building types, a floor plan stays true for a decade. In a hospital, the "current" plan for a given floor may be assembled from six projects across twenty years, each of which drew only its own scope. Nobody ever issued the plan. Knowing which sheet is current for a given room is a research task.

The campus is many buildings of many ages. A medical center is typically a dozen structures — original hospital, towers added by decade, a parking structure, a central plant, leased clinical space across town — connected by tunnels and bridges that appear on nobody's drawings. Structure, systems, and naming conventions change at every seam.

The building is occupied around the clock. When a valve needs to be found during a leak, or a circuit traced before a shutdown, the person asking is standing in a corridor with a phone, and the answer has a clock on it. "It's somewhere on the share drive" is not an acceptable answer at 2 a.m.

Outside firms come and go constantly. A busy campus may have dozens of contractors and consultants a year, each needing a slice of the archive for a few weeks. Each one needs the current set — and needs to lose access when the job closes.

Much of the archive is scanned paper. The oldest and often most important drawings — original structure, buried utilities, the things nobody wants to core-drill through — exist as scans of prints, with no searchable text unless someone adds it.

The four questions the archive has to answer

Strip away the specifics and a hospital facilities team asks the same four things over and over:

  1. The outage question — "What does this feed, and where do I isolate it?" Needs the current mechanical, electrical, or plumbing sheet for a specific room, fast.
  2. The survey question — "Show me the life safety drawing for this floor." When a surveyor or inspector asks for a document, the operational reality is simple: you produce it now, or you explain why you can't. Whatever your specific obligations are, the drawing has to be findable on demand.
  3. The renovation question — "What's actually above that ceiling?" Every project starts by trying to reconstruct existing conditions from as-builts of varying age and trustworthiness. The better the archive, the fewer surprises and change orders.
  4. The handover question — "Where do the closeout documents from the last project go so the next one can find them?" If as-builts land in a project folder that's abandoned when the project closes, the archive quietly stops being current.

A shared drive answers none of these well. A project-management platform answers the fourth for one project at a time, then loses interest. The facilities archive is a permanent, owner-side record, and it needs a system built for that.

What a hospital archive actually needs

A hierarchy that mirrors the campus. Site, building, floor, and trade — so a drawing's home is obvious and a new engineer can find the Level 3 electrical for the east tower without a tour. We've written up the folder structure that scales in detail.

Current versus superseded, made unmistakable. Every sheet keeps its full revision lineage in one place, with the latest on top. Nothing is deleted — you'll want the 1994 revision during a dispute or a demolition — but nobody should be able to grab it by accident.

Search that reads inside the files. Scanned prints need OCR so a search for a room number, an equipment tag, or a panel name finds the sheet even when the filename is SCAN_0047.pdf. Here's how document search should work for drawings specifically.

Contractor access that is scoped, reversible, and cheap. A sub working on one floor of one building sees that project and nothing else, under their own login, with access that ends at closeout. The right way to give contractors drawings is a link to the live document, not a ZIP in an email.

Pricing that fits a large, occasional-use group. A facilities department may have sixty people who each open a drawing a few times a month. Per-seat pricing punishes exactly that pattern, and on a public or nonprofit budget it becomes indefensible. We've laid out the real cost of per-seat software.

An audit trail and single sign-on. IT will ask who opened what, and whether people are provisioned and removed through the identity provider. Have the answer before they ask.

Nothing clinical. This is a facilities record — drawings, O&M manuals, equipment data, closeout packages. It should never contain patient information, and a system that keeps facilities documents in their own lane makes that boundary easy to hold.

How to get there without a two-year project

The mistake is treating the archive as one giant migration. Instead:

  • Pick one building — ideally the one with the most active projects — and bring its drawings in first. That's a few weeks, not a year, and it proves the structure.
  • Ingest first, perfect later. Get files in with the metadata you have; let OCR and AI title-block reading fill the rest. See our guide to migrating a legacy drawing archive.
  • Change the handover rule immediately. From today, every project's closeout drawings land in the facilities archive, not in a project folder. This single policy stops the drift.
  • Onboard your next contractor through the system, not by email. One project. See how it goes.

How ArchiveView handles it

ArchiveView was shaped by exactly this environment. A hospital system runs its facilities archive on it today — roughly 28,600 drawings across 10 sites, organized entity → site → building → floor → trade, with OCR'd search across decades of scanned prints.

The pieces above are built in: automatic folder placement from metadata, version control that never deletes a revision, full-text and AI search, offline access for drawings in basements and mechanical rooms, single sign-on for your own staff, and contractor access at $199 per project rather than a monthly seat.

Pricing is flat: $499 a month covers 50 users, so the whole facilities and engineering group can be in the system, not just the three people who could justify a license.

If you run facilities for a hospital or medical campus, we'd like to show you the structure against your own buildings. Request a demo or learn more about facility document management.

Put this into practice with ArchiveView

Automatic folder creation, drawing sets, version control, AI search, and per-project contractor access — built for construction and facilities teams.