Facility Asset Records: Facility Teams Verify 8 Essential Fields

A facility asset record is the authoritative file for one piece of equipment: its identity, location, maintenance history, and lifecycle status. Start today by choosing a minimal field set and validating every record against source documents such as warranties and commissioning reports. Standards like COBie, ASTM E2604, and FIMS/FRPP guidance show what to capture, and we built Firmanager so you can pilot the whole workflow.

TL;DR:

• Use ASTM E2604’s essential fields first: unique ID, name and type, manufacturer, model and serial, installation date, location, status, custodian, and linked work orders.
• For new projects, specify COBie delivery milestones and required fields in contracts, then make validated, complete records a condition of handover acceptance.
• Set the smallest maintainable level before inventorying, then standardize fields and collect signed source documents, nameplate photos, tags, and locations in structured forms.
• Require technicians to confirm location, status, and serial data before closing work orders, then reconcile each change against independent source documents.
• Run recurring spot checks away from reporting deadlines using random samples and independent documents; retire replaced assets without deleting their repair history.

Table of Contents

• What does a facility asset record contain?
• Why do asset records drift out of date?
• Which standards should your records follow?
• How do you create accurate asset records step by step?
• How do you keep records accurate over time?
• What does a minimal asset record template look like?
• Where should teams focus first?
• How can an integrated platform make record-keeping practical?
• FAQ
• Sources

What does a facility asset record contain?

Each record answers four questions: what is this item, where is it, what has happened to it, and what should happen next. That makes it the backbone of maintenance planning, lifecycle decisions, warranty claims, and compliance proof. When a boiler fails, the record tells you who installed it, whether it is under warranty, and what was done to it last spring.

ASTM E2604 splits equipment asset data into essential and optional elements. Essential elements should always be present for efficient asset management, while optional ones depend on what your organization needs. That split is a useful rule for your own template: lock down the essentials first, then add extras only where someone will actually use them.

Essential fields:

• Unique ID or asset tag
• Asset name and type
• Manufacturer, model number, and serial number
• Installation or acquisition date
• Current location, including space and coordinates
• Current status and condition
• Assigned custodian or responsible party
• A pointer to maintenance history, meaning linked work orders

Useful optional fields:

• OEM manuals and spare-parts SKUs
• Vendor contact details
• Performance metrics such as runtime or energy draw
• Procurement information and cost center

A record with the essentials filled in and verified beats one with many half-empty columns.

Why do asset records drift out of date?

Records rarely fail all at once. They erode through small gaps between what technicians do in the field and what reaches the database.

Common causes:

• A technician swaps a pump and nobody updates the record
• Naming and hierarchy differ between buildings, so the same chiller appears under three descriptions
• Contractor spreadsheets are never reconciled with your system
• Staff turnover takes tacit knowledge with it
• Project handovers arrive late, incomplete, or in whatever format the contractor preferred

ASHRAE 1801 RP guidance notes that handover documentation often arrives in non-standard formats, which is exactly why mapping it to a structured schema matters.

The errors surface in predictable places. A work order describes an asset differently than the record does, so nobody is sure it is the same unit. A preventive maintenance task is missed because the asset was never scheduled. A warranty dispute stalls because the install date is wrong. Capital plans get built on replacement dates that were never true.

Two mitigations pay off quickly. Require a photo of the nameplate and tag whenever a record is created or changed. And require signed, dated source documents at handover, so a record without paperwork is treated as unfinished.

Pro Tip: Make record updates part of work-order closeout. If a job cannot be closed until the asset’s location, status, and serial data are confirmed, drift stops at the source.

Which standards should your records follow?

Standards turn a pile of spreadsheets into machine-readable, comparable data. A few matter especially for facilities teams.

• COBie: COBie organizes maintainable asset data into 19 tables and serves as a standardized digital handover deliverable that populates operations and maintenance systems. Specify it early in a project, schedule data drops at milestones, and require delivery at handover.
• ASTM E2604: It defines which data elements belong in an equipment asset record and which are optional. Use it to justify a lean minimum set when stakeholders push for everything.
• FRPP and FIMS guidance: The FRPP data dictionary lists defined real-property elements, including replacement value, repair needs, location fields, unique identifiers, and utilization metrics. The FIMS validation training manual adds the process side: validate each data element against an independent, authoritative source document and record the result on a Data Validation Reporting Form.

You do not need to be a federal agency to borrow the discipline. The principle is simple: a value is only trustworthy if you can point to a document that proves it.

To put standards to work, write them into contracts. List required fields, delivery milestones, and responsible parties in the scope of work. Add data deliverables to commissioning checklists, and make complete, validated data a condition of handover acceptance. Without that, you will receive an incomplete spreadsheet at the last minute and no leverage to fix it.

How do you create accurate asset records step by step?

Follow this sequence for a handover or a standalone inventory project.

1. Choose your Lowest Maintainable Level (LML). LML is the smallest component you will repair, replace, or track history against. Set it too high and a failed fan motor gets logged against the whole air handler. Set it too low and you drown in records. Pick it per system before collecting anything.
2. Fix the field schema. Map your minimal fields to COBie tables or your system’s columns before anyone touches a clipboard, so every crew collects the same thing.
3. Collect source documents. Gather as-builts, commissioning reports, OEM manuals, and warranties. Keep dated, signed copies, since FIMS guidance expects source documents to be authoritative and finalized.
4. Capture in the field. Take a photo of the nameplate, apply a tag, and record the location. Structured forms beat free text. For tagging, QR-based asset management offers practical guidance on codes and scan tracking.
5. Import and reconcile. Load the data, run validation reports, and compare mismatches against source documents rather than against another export of the same data.
6. Assign owners and pilot. Name a data steward per system, pilot on one high-impact system, fix what breaks, then roll out to the rest.

Handover paperwork from installers is where many records go wrong. Installer covers how to keep signed installation documents organized so warranty claims do not stall.

Pro Tip: Schedule your validation pass outside any annual reporting deadline. Corrections made in a rush before a due date tend to be guesses.

How do you keep records accurate over time?

Accuracy is a routine, not a project. Build the routine around independent verification.

• Validate against source documents. FIMS validation practice uses independent source documents for each data element, a limited random sample, and a subject-matter expert who manages the documents. A sample check can catch systemic problems without auditing every asset.
• Audit on a schedule you control. Spot checks timed away from reporting deadlines leave room to correct what you find.
• Know your retention rules. NARA’s GRS 5.4 sets retention and disposition schedules for facility, equipment, vehicle, property, and supply records, including maintenance logs, inspection records, and work orders, with exceptions. Check the schedule that applies to you before you delete anything, and keep what audits and lifecycle reporting need.
• Log lifecycle events. When equipment is replaced or disposed of, retire the record rather than deleting it. Note the date, reason, and replacement unit’s ID.
• Preserve history. Keep past repairs attached to the right asset so failure patterns and replacement timing stay visible.

A retired record with its full history often answers the question “should we replace or repair?” better than any new report.

What does a minimal asset record template look like?

Copy this field set and adapt it. Every field is something a technician can verify on site or from a source document.

• Add vendor contacts, spare-parts references, and performance metrics only once someone has a use for them.
• Map the template to your handover data so imports line up the first time.

Where should teams focus first?

My view: treat data handover as a contract deliverable and enforce it before the building opens, because it is far cheaper than reconstructing records later. Resist the urge to chase exhaustive fields. A well-chosen LML and honest validation against source documents will do more for reliability than another dozen columns. Then pilot on one high-impact system, prove the routine works, and scale it.

— KaiosMedia

How can an integrated platform make record-keeping practical?

Good habits fail when they live across multiple tools. We built Firmanager so asset and facility records, work orders, and documents sit behind one login, synced in the cloud so field and office see the same data.

What that simplifies in the workflow above:

• Attaching source documents and photos to the record
• Linking work orders to assets so history builds automatically
• Scheduling recurring preventive maintenance tasks
• Updating records from the field on any device
• Sending SMS and email notifications when work changes

You can start small: our Free plan costs $0, Pro is $19 per month, and Business is $49 per month. Pilot one system, then open the app and set up your first records today.

FAQ

What are the different types of facility management reports?

Common types include maintenance and work-order reports, asset inventory and condition reports, compliance and inspection reports, and cost or budget reports. Each one is only as reliable as the asset records behind it.

What are 5 examples of assets?

Typical facility assets include HVAC units, boilers, elevators, generators, and fire-suppression systems. Each should have its own record with an ID, location, and maintenance history.

What should an asset list look like?

An asset list should have one row per item, with a unique ID, name and type, model and serial number, location, install date, status, and custodian. Following ASTM E2604’s essential elements is a solid starting point.

How often should asset records be validated?

Validate on a recurring schedule, using a small random sample checked against independent source documents. Time the checks away from reporting deadlines so you can correct what you find.

Sources

• E2604 Standard Practice for Data Characteristics of Equipment Asset Record
• Facilities Information Management System (FIMS) Validation Training
• 2025 GUIDANCE FOR REAL PROPERTY INVENTORY REPORTING

Recommended

• OSHA Lockout Tagout: 6 Steps, Checklist & Tracking for Field Service
• Best Compliance Management Software for 2026: Top 8 Picks
• Avoid Unenforceable Service Level Agreements for Service Managers