What Data Should Facility Teams Collect During Site Assessments?

It's tempting to collect everything during a site visit, more data feels safer than less. In practice, an unfocused site assessment produces a pile of notes nobody structures afterward, while a well scoped one produces exactly what's needed to support the decisions that come next. The difference comes down to knowing what to collect, and why.

The Core Categories

What. A description of the asset or condition being documented, equipment type, material, or system, specific enough that someone unfamiliar with the site could identify it later from the record alone.

Where. Location down to the building, floor, and room or zone, ideally captured automatically via GPS rather than written from memory afterward.

Size and quantity. Dimensions, capacity, or count, whatever unit actually matters for the asset in question, a chiller's tonnage, a lighting fixture's wattage, a roof's square footage.

Age and condition. Install date or approximate age, and a consistent condition rating, since age alone doesn't tell you whether something is about to fail or has years of useful life left.

Operating status. Whether the asset is functioning as designed, and whether it's meeting the needs of the people relying on it, a system can be technically operational while still underperforming.

Maintenance history. Repair records, replacement parts and specifications, and any evidence of recurring issues, data that turns a repair or replace decision from a guess into an evidence based call.

Remaining useful life. An estimate of how much longer an asset can be expected to perform before replacement, the single data point capital planning depends on most.

Who Should Collect It

Data collection responsibility usually falls to whoever has the closest operational knowledge of a system, in house facilities staff for routine inventories, a third party auditor or engineer for specialized assessments requiring technical judgment. What matters more than who collects it is that everyone collecting it uses the same structure and definitions, so a record from one site can be compared meaningfully to a record from another.

When to Collect It

Some data belongs in a baseline inventory, gathered once and updated only when something changes. Other data, condition ratings, operating readings, needs to be refreshed on a recurring cycle to stay useful. Treating every field as if it needs the same collection frequency either wastes effort verifying things over and over that rarely change, or lets genuinely time sensitive data go stale.

Structuring It So It Stays Useful

The single biggest failure mode isn't under-collecting, it's collecting data that never gets organized into a usable format. A site assessment's value comes from being accessible later, for an emergency response, a long term capital plan, or a routine audit, not from the thoroughness of the walk through itself. Structuring data consistently at the point of collection, using standardized digital forms rather than free text notes, is what makes that possible. Our field data collection checklist puts these categories into a practical, ready to use format.