← All articles

Campus As-Built Drawings: Building a Record Your Team Can Use

Higher EducationFacilitiesAs-Built DrawingsBest Practices

A campus is a building archive that grew one project at a time. The chemistry building was drawn in the 1960s, its wings were added in the 1980s, the roof was replaced twice, and last summer a lab on the third floor was gutted and rebuilt. Each of those projects was supposed to leave behind as-built drawings. Ask a facilities office where those drawings are today and you will usually get a pause, then "let me check with someone who's been here a while."

That pause is the problem. Campus as-built drawings are the working memory of the physical plant: where the chilled water main runs under the quad, which panel feeds the east stairwell, what is actually above the ceiling in a room you are about to renovate. When they are scattered across a shared drive, a flat file in the basement of the facilities building, and one retiring employee's laptop, every small project starts with a scavenger hunt.

This guide covers what campus as-builts are, why they go missing on a university campus in particular, and a practical way to build an as-built record that the next person can actually use.

Why campus as-builts go missing

Higher education has a few habits that make as-built records harder to keep than in a single-owner commercial portfolio.

Many buildings, many decades. A mid-sized campus mixes buildings from every era, drawn in different formats, with different naming schemes. A 1965 hand-drafted set and a recent project delivered as a native PDF set may sit in the same folder with nothing connecting them to the same building.

Many project types, many owners of the paperwork. Large capital projects go through a formal capital office. Small renovations, such as a lab fit-out, a department move or an HVAC replacement, are often run by a facilities shop or a department with its own contractor. Those small jobs are exactly the ones where closeout drawings never reach the central archive.

Staff turnover. Universities depend on long-tenured people who know where things are. When one of them retires, the filing system leaves with them. A new hire inherits folders but not the logic behind them.

Seasonal construction. Most work is compressed into summer, when staff are stretched and closeout is the first thing to slip. The building is occupied again in August, and the as-builts become "we'll get to them in the fall."

Shared drives that quietly become the system. Nobody decides to use a shared drive as the archive. It just happens, one project folder at a time. We covered why that pattern breaks down in how to organize construction drawings.

What counts as an as-built, and what to collect

"As-built" is used loosely, so it helps to be specific about what your campus record should contain. For a deeper definition, see As-Built Drawings: What They Are and How to Manage Them. For a campus, a useful closeout record for each project generally includes:

  • Marked-up or revised drawings showing the work as installed, by trade: architectural, structural, mechanical, electrical, plumbing, fire protection.
  • Final specifications and addenda that describe what was actually furnished.
  • Approved submittals for major equipment, so a model number is a lookup, not a guess.
  • O&M manuals and warranty documents, linked to the equipment they cover.
  • Utility and site drawings for anything buried or routed outside the building envelope.
  • Photos taken before walls were closed, which are often the most useful record of concealed conditions.

If you are not sure where the line falls between a record drawing and a marked-up field copy, settle it in your closeout requirements before the next project starts.

A six-step approach to a usable campus as-built archive

1. Decide the unit of organization

Pick one structure and use it everywhere. For a campus, the natural hierarchy follows the physical plant: campus or site, then building, then floor, then trade. A drawing's home should be obvious from what it shows, not from who filed it. If a new engineer cannot find the Level 2 electrical plan for a building without asking someone, the structure is not working yet.

2. Standardize building names and numbers

Campuses collect aliases. The same building may be "Science Hall," "SH," "Bldg 14" and "Old Chem" depending on who drew the sheet. Build a single list of buildings with one authoritative name and number, and note the common aliases beside it. This one table does more for searchability than almost anything else.

3. Write closeout requirements into every contract

The cheapest time to get as-builts is before final payment. Put specific deliverables in the project requirements: file format, naming convention, what must be included, and who receives it. A consistent file naming convention makes deliverables from different firms land in the same shape. Make the facilities archive, not the project folder, the named destination.

4. Make one person responsible for receiving them

Closeout fails when everyone assumes someone else is filing the drawings. Name a role, not just a person, responsible for confirming that the deliverables arrived, are complete and are placed in the right building. A short checklist helps:

  1. Drawings received for every trade involved in the project
  2. Specs, addenda and approved submittals attached
  3. O&M manuals and warranties attached
  4. Files named and placed per the convention
  5. Superseded versions retained, current version clearly marked
  6. Project marked closed in the register

5. Rescue the existing records in priority order

Do not try to migrate the whole campus at once. Rank buildings by how much work they are likely to see: the ones with active renovation plans, the ones with aging mechanical systems and the ones with the thinnest records. Bring those in first, a building at a time. Our guide to migrating a legacy drawing archive walks through gathering files, using any index you already have and verifying a sample before moving on.

6. Give outside firms controlled access

Every renovation brings consultants and contractors who need the existing drawings. Emailing a ZIP creates a copy that is out of date the day it is sent. Scoped, time-limited access to the live record is safer and simpler. Giving contractors access to drawings without losing control covers how to do it.

Keeping the record current after the first push

Getting the archive started is the easier half. Keeping it current takes a few standing habits:

HabitWhat it prevents
Closeout is a gate before final paymentDrawings that never arrive
One receiving role per campusEveryone assuming someone else filed it
Small jobs follow the same rules as big onesA lab fit-out that leaves no record
Superseded sheets are kept, not deletedLost history during a dispute or demolition
Annual spot-check of a few buildingsSlow drift that nobody notices

The annual spot-check is the cheapest of these. Pick three buildings and try to answer a real question using only the archive: "What feeds this room?" If you can answer it in a couple of minutes, the record is healthy. If you cannot, you have found your next cleanup target.

How ArchiveView handles it

ArchiveView is built as the permanent, owner-side home for this kind of record. Files are organized entity, site, building, floor and trade, so the structure follows your campus instead of an ad hoc folder tree. Every upload is OCR'd, which means a search for a room number or panel name reaches the text on a scanned sheet, not just the filename.

Bulk Import brings in an existing archive from a CSV index or from the title blocks themselves, and duplicate detection checks content so the same drawing filed under three names is caught. Full version history keeps superseded sheets without letting anyone grab them by accident. Contractor access is $199 one-time per project and does not use your user seats, and access ends with the job. Per-file permissions, audit logs and MFA are built in.

Pricing is flat: Starter is $149/month for up to 10 users and Professional is $499/month for up to 50, so the whole facilities group can be in the system. For how this fits a university, see our page for higher education facilities teams.

Start with one building

A campus as-built archive is not a single big project. It is a building at a time, a closeout rule that sticks and a short list of habits that keep it current. Pick the building with the most work coming and begin there.

Start a free trial and bring in one building this week, or request a demo and we will walk through it with your own drawings.

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.