Skip to content

As-Built Drawings and Asset Registers: The Complete Guide

A wildfire protection system is not truly complete when installation ends. Owners, property managers, service contractors and emergency personnel need accurate records showing what was installed, where it is located, how it is connected and what each component is expected to do. As-built drawings and asset registers turn a completed installation into an understandable, maintainable and verifiable property system.

What As-Built Documentation Should Accomplish

As-built documentation should represent the final installed condition rather than the original design intent. It should allow a qualified person who was not involved in construction to locate equipment, understand system relationships, isolate components, perform service and verify whether future changes have altered the approved configuration.

  • Show final equipment and piping locations
  • Identify deviations from design documents
  • Record concealed and buried infrastructure
  • Link field components to unique asset identifiers
  • Support testing, maintenance and emergency operation
  • Provide a reliable baseline for future modifications

Design Drawings Are Not As-Built Drawings

Issued-for-construction drawings describe what was intended to be installed. As-built drawings document what was actually installed. Markups that simply state “installed per plan” are not enough when routing, elevations, equipment, valve locations, wiring or controls changed during construction.

Recommended As-Built Drawing Set

The final set should be scaled, dated, revision-controlled and coordinated across disciplines. Depending on the property, the package may include:

  • Overall site plan
  • Protected-structure and node layout plans
  • Water-source and storage plans
  • Pump-room or equipment-vault plans
  • Piping plans, profiles and riser diagrams
  • Valve, drain and isolation maps
  • Electrical single-line diagrams
  • Control wiring and communications diagrams
  • Sequence-of-operation diagrams
  • Backup-power and transfer arrangements
  • Details for concealed, buried and inaccessible work

Overall Site Plan

The site plan should establish the complete property context. It should show structures, access roads, gates, water sources, tanks, pump equipment, major piping routes, electrical sources, communications equipment, protected areas and interfaces with existing property systems.

Underground and Concealed Infrastructure

Buried or concealed work is among the most important information to preserve because it becomes difficult and expensive to reconstruct later. Records should include horizontal dimensions, depth or elevation, pipe material and size, fittings, sleeves, tracer wire, warning tape, thrust restraint, vaults, cleanouts, drains and points where the route changes direction.

Photographs taken before backfill or enclosure should be indexed to drawing locations and asset identifiers.

Water Sources and Storage

As-built records should identify every water source and its relationship to the wildfire system, including:

  • Cisterns, tanks, wells, pools and approved alternate sources
  • Usable and gross storage volumes
  • Normal operating levels and low-level cutoffs
  • Fill, overflow, drain and suction connections
  • Isolation and diversion valves
  • Backflow or cross-connection protection
  • Level sensors and alarms
  • Water-quality and filtration interfaces

Pumps and Hydraulic Equipment

Record the final pump model, quantity, duty point, motor data, controller or drive, suction and discharge piping, pressure tanks, relief devices, check valves, gauges, test connections and bypass arrangements. The drawing set should clearly show how equipment can be isolated, drained, tested and returned to service.

Distribution Piping

Piping drawings should identify final size, material, joining method and routing. Pipe transitions, reducers, branches, high points, low points, drains, flush points and freeze-sensitive sections should be shown. Where the system uses dry standby, compressed air or leak detection, the as-built set should show air-source connections and monitored sections.

Nodes, Valves and Discharge Devices

Each operating node should have a unique identifier used consistently on drawings, control screens, labels, test forms and the asset register. Record the associated control valve, nozzle or discharge-device model, orifice, orientation, elevation and protected exposure.

Coverage intent should be understandable without relying solely on field memory. Roof, eave, wall, vegetation and tank-cooling devices should be distinguishable.

Electrical and Backup Power

The final electrical record should identify:

  • Service source and panel location
  • Breaker, disconnect and conductor information
  • Motor and controller circuits
  • Control-power sources
  • Generator, battery or hybrid backup systems
  • Automatic and manual transfer arrangements
  • Critical-load priorities
  • Grounding and bonding
  • Emergency shutdowns and local disconnects

Controls, Sensors and Communications

Control documentation should show the final architecture rather than a collection of product manuals. Include controller locations, input and output assignments, valve addresses, sensor identifiers, communications pathways, network equipment, remote-access interfaces, alarm routing and fail-safe states.

Sequence of Operation

The as-built package should contain the approved final sequence of operation. It should explain what occurs during automatic activation, manual activation, power transfer, loss of communications, low water, pump fault, sensor failure, freeze alarm and emergency shutdown.

What Is an Asset Register?

An asset register is the structured inventory of maintainable system components. Drawings show relationships and locations; the register records the identity, specification, service history and lifecycle information for each asset.

Minimum Asset Register Fields

  • Unique asset ID
  • Asset category and description
  • Manufacturer and model
  • Serial number
  • Installed location
  • Drawing reference
  • System or node association
  • Installation and commissioning date
  • Installer or responsible contractor
  • Design duty or operating setpoint
  • Power requirements
  • Normal valve position or operating state
  • Inspection and maintenance interval
  • Warranty expiration
  • Recommended spare parts
  • Manual, submittal and test-record links
  • Current status and open deficiencies

Which Assets Should Be Registered?

Register any component that requires inspection, testing, maintenance, configuration, replacement or identification during an emergency. Typical assets include tanks, pumps, motors, variable-frequency drives, controllers, filters, valves, pressure tanks, generators, batteries, transfer equipment, sensors, communications devices, compressors, drains and discharge devices.

Asset Identification and Field Labels

Asset IDs should be permanent, legible and coordinated with drawings and software. A practical naming system indicates system, location and component type without becoming so complex that field personnel cannot use it.

Labels should resist ultraviolet exposure, moisture, heat and cleaning. Concealed equipment should have visible access labels.

Digital Asset Registers

A spreadsheet may be adequate for a small system, but larger estates, ranches, communities and multi-structure properties benefit from a searchable digital register. The system should allow photos, manuals, test results, deficiencies and service events to be linked to each asset.

Linking Drawings, Records and Assets

The greatest value comes from using the same identifiers across the entire documentation system. A pump shown as P-01 on the drawing should be P-01 in the asset register, commissioning report, maintenance record, control screen and spare-parts list.

Verification Before Acceptance

As-built documents should be field-verified before final acceptance. Verification should compare drawings with installed equipment, trace representative concealed routes, confirm labels and test the relationship between asset IDs and control addresses.

Change Management

As-built documents describe a moment in time. Any later modification that changes equipment, routing, settings, sequence, power or protected coverage should trigger an update. Redlined field copies should be incorporated into the controlled record rather than becoming the permanent system of record.

Document Control

Every drawing and register should include revision date, revision description, responsible party and approval status. Owners should retain both current and superseded versions so the history of system changes can be reconstructed.

Recommended Turnover Package

  • Stamped or approved design documents when applicable
  • Final as-built drawing set
  • Editable native drawing files when contractually required
  • PDF record set
  • Asset register
  • Equipment submittals and manuals
  • Commissioning and integrated test reports
  • Inspection and maintenance schedules
  • Warranties and service contacts
  • Photos of buried and concealed work
  • Control backups and configuration records
  • Owner training records

Good, Better and Best Documentation Programs

Good

Final PDF drawings, basic equipment schedule, field labels and organized manuals.

Better

Field-verified multi-discipline drawings, complete asset register, indexed concealed-work photos, linked commissioning records and controlled revision history.

Best

Survey-grade or digitally mapped assets, searchable cloud register, QR-linked field labels, current control backups, integrated maintenance history and formal change-management procedures.

Common Documentation Mistakes

  • Submitting design drawings without verified field changes
  • Omitting underground routes and depths
  • Using inconsistent equipment names across documents
  • Failing to record serial numbers and setpoints
  • Providing manuals without identifying which installed asset they apply to
  • Leaving control addresses undocumented
  • Failing to update records after modifications
  • Keeping the only record on a contractor’s private system

As-Built and Asset Register Checklist

  • Final site and system plans completed
  • Underground and concealed infrastructure documented
  • Water, power, controls and communications coordinated
  • All maintainable assets assigned unique IDs
  • Field labels installed and verified
  • Asset register populated with required fields
  • Commissioning records linked
  • Photos indexed
  • Revision and ownership responsibilities assigned
  • Owner received current digital and offline copies

Technical FAQs

Can contractor redlines serve as final as-builts?

Redlines are an important source document, but final as-builts should incorporate them into a clean, coordinated and field-verified record set.

Should asset registers include inexpensive components?

Include components whose failure, location, setting or replacement matters to operation. Commodity fittings generally do not need individual records, but control valves, sensors, nozzles and other functional devices usually do.

Who owns the final records?

The property owner should receive and control the final records, with access provided to authorized managers, service contractors and design professionals.

How often should records be updated?

Update them whenever a change affects installed condition, configuration, sequence, coverage or service requirements. Periodic audits should confirm the record still matches the field.

Are digital twins a replacement for drawings?

No. A digital twin can improve visualization and asset access, but it should complement controlled drawings, schedules and technical records rather than replace them.

Build a Reliable Property Record

A Property Assessment can identify missing drawings, undocumented assets, inconsistent labels and incomplete turnover records before those gaps create service or emergency-response problems.

Request a Property Assessment