Infrastructure Condition Surveys: What Gets Recorded and Why

An infrastructure condition survey is a structured, repeatable inspection that records the physical state of a built asset at a fixed point in time. It applies to bridges, tunnels, retaining walls, and road pavement, and increasingly to distributed hardware like EV charging stations or shared micromobility fleets. The output is not an opinion about whether something looks fine. It is a dataset: a geotagged photograph, a measured defect, a severity code, and a timestamp that lets the same asset be compared against its own history years later.

What belongs in that dataset is not arbitrary. Germany's DIN 1076, France's IQOA methodology, and the US ASTM D6433 pavement standard each define, in detail, which fields an inspector must record and how often. They differ in cycle length and scoring scale, but they agree on the underlying logic: a condition record only has value if it is specific, comparable, and traceable to a point on the asset and a moment in time.

This piece walks through what gets captured, why each field exists, how the major EU and US frameworks compare, and where the same data architecture — geotagged photo, structured attributes, independent verification — shows up in commercial contexts far from civil engineering, from EV charging networks to shared fleet hardware.

What Exactly Gets Captured in a Condition Survey?

A condition survey record is built from a small set of recurring fields, regardless of whether the asset is a motorway bridge or a parking garage retaining wall. Each defect gets an identifier, a location tied to a specific structural component, a severity rating, a photograph, and a date. Germany's DIN 1076 formalizes this into a defined workflow: visual survey, defect identification, component classification, a severity rating, and a resulting condition grade that drives a maintenance recommendation (geocadra, 2025) [1]. The per-defect severity rating, known as the S-V-D system, is applied consistently whether the inspector is looking at a bridge deck or a gabion retaining wall, which is what makes condition data comparable across an entire national stock rather than just within one structure (geocadra, 2025) [1].

France's IQOA framework — Image de la Qualité des Ouvrages d'Art — builds the record in two stages. The first is a documentary study: construction year, materials, prior maintenance actions, and existing structural drawings get logged before anyone visits the site. The second is the field inspection itself, a rapid visual survey that records corrosion, cracking, spalling, potholing, and calcite leaching as distinct defect categories (OverView, 2018) [3]. That second stage is explicitly not a diagnosis. It is, by design, a visual state-of-play that feeds a classification, not an engineering judgment about remaining service life (OverView, 2018) [3].

A condition survey, defined precisely, is a repeatable observational protocol that converts visible defects into a structured, comparable score — distinct from a structural diagnosis, which requires destructive or instrumented testing to establish cause and remaining capacity. Confusing the two is one of the most common and most consequential errors in asset management, because a "good" survey score does not rule out a latent structural problem that a visual pass cannot see.

Why Do Inspection Cycles and Rating Scales Differ by Jurisdiction?

The frequency and granularity of inspection is not a stylistic choice between countries. It reflects how each jurisdiction weighs failure consequence, traffic exposure, and the cost of over-inspecting a very large asset stock. The table below lays out the three most-cited frameworks side by side.

Jurisdiction / Framework	Inspection Cycle	Rating Scale	Escalation Trigger
Germany — DIN 1076	Major inspection every 6 years; annual visual checks; 3-year interim inspection (biberger.de, 2025)	Per-defect S-V-D rating feeding a component-level "Zustandsnote" (geocadra, 2025)	Severity rating determines maintenance category and access-restriction decisions
France — IQOA (Cerema/SETRA)	At least once every 3 years (IESF, 2018)	Five classes: 1, 2, 2E, 3, 3U (Cerema, 2026)	Class 3U signals urgent risk to users; triggers priority repair funding
United States — ASTM D6433 / NBIS	Sample-based network surveys; bridges typically on a 2-year federal cycle	PCI 0–100 across seven verbal categories, from "Good" to "Failed" (Wikipedia, 2026)	Scores below roughly 40 trigger major rehabilitation rather than preventive maintenance (ifactoryapp, 2025)

Switzerland's federal roads office and the Netherlands' Rijkswaterstaat run broadly comparable structured inspection regimes for national road and bridge stock, though neither publishes condition breakdowns with the same public granularity as France's IQOA tables. Belgium's regional road authorities follow a similar pattern, with inspection responsibility split by region rather than centralized nationally. Inspection frequency is not a matter of bureaucratic preference; it is a calibrated response to failure consequence, traffic exposure, and the size of the asset stock being managed.

Why Do Public Datasets Fall Short for Asset-Level Decisions?

Public condition registries answer policy questions well. They answer operational questions poorly. France's own asset managers acknowledge this: a national survey of 65 départements covering 112,893 structures — 62,389 bridges and 50,504 retaining walls — found that departmental indicators are "variable d'un département à l'autre," meaning the same defect can be scored differently depending on which local authority is doing the scoring (IESF, 2018) [4]. The state's own IQOA tool is uniform. What sits below it, in practice, is not.

The US picture has the same shape at a different scale. ASCE's 2025 Report Card aggregates the entire national bridge stock into a single letter grade — bridges held a C, with 6.8% of the inventory in poor condition, down from 7.5% in 2021 and 12% in 2011, against a projected $373 billion repair funding gap over the next ten years across roughly 623,000 bridges (Gordian, 2025) [7]. That number is genuinely useful for national infrastructure policy. It tells you almost nothing about which specific structure in your portfolio needs attention next quarter, because the report card is a rollup, not a per-asset record.

Photographic evidence is the other gap. Most public condition registries store a score and a date, not an image tied to that score. Without a photograph bound to a timestamp and location, a condition rating cannot be independently re-checked later — it has to be taken on trust. Building that evidentiary layer correctly is exactly the discipline covered in our field survey methodology piece on sampling, routing, and QA, and the same logic around verifiable, non-repudiable field evidence runs through how photo and video evidence is made to hold up in other field-data contexts.

What Does a Condition Record Look Like in Practice?

Consider a real example drawn from a published load-testing and structural health monitoring study of a prestressed concrete box girder bridge, built in 1972 and refurbished in 1978 after construction defects were discovered (arXiv, 2024) [9]. According to its 2018 and 2021 inspection reports, the structure showed no or only minor defects: a 0.01 m height offset at the expansion joint, and concrete cracking in the caps and frame corners (arXiv, 2024) [9]. Notice what is and is not in that record. There is a precise measurement — not "minor settlement" but 0.01 metres. There is a specific component — the expansion joint, not "the bridge." There is a build year, a refurbishment year, and two inspection dates, which together let an engineer compute a defect progression rate rather than a single snapshot.

That level of specificity is not incidental. It is what makes the record useful ten years later to someone who has never visited the site. A condition survey schema that only records "fair" or "needs attention" produces a dataset nobody can act on past the next budget cycle.

How Does the Same Schema Apply Beyond Bridges and Roads?

The architecture — geotagged location, structured attributes, a timestamped photograph as evidence — is not specific to civil structures. It is the same architecture used to document EV charging infrastructure, and it scales the same way. Teampl ran a nationwide field program covering more than 1,500 EV charging stations across the Netherlands, recording station name, operator, address, number of charging points, connector types, charging capacity, and pricing as a structured dataset, with on-site photographic evidence for every location. The survey deliberately covered urban, suburban, and rural areas across the entire country rather than sampling major cities only, because a charging-network dataset that only covers cities misrepresents the actual state of the infrastructure a driver encounters outside them.

Micromobility fleet documentation follows the same logic again: condition, placement compliance, and damage on shared e-scooters and e-bikes are observational facts best captured the same way a retaining wall defect is captured — photo, geotag, attribute, timestamp — rather than through self-reported operator data. Shelf and planogram audits run on an almost identical schema too, which is why the field-capture pipeline described in our planogram audit piece will look structurally familiar to anyone who has read a bridge inspection manual.

What Makes a Condition Record Legally and Operationally Defensible?

A condition score without provenance is just an assertion. The international standard for asset management, ISO 55000, puts this plainly in its underlying principle: asset management requires accurate asset information, and an asset management system is built around exactly that requirement, not just a database of scores (ISO, 2014) [8]. The standard itself has evolved to reflect this emphasis — ISO 55000 launched in January 2014 and was revised into a second edition in 2024, refining its vocabulary and principles around how asset data should be governed (Wikipedia, 2026) [8].

In practice, defensibility comes down to four things: a timestamp that cannot be altered after capture, a GPS coordinate tied to the specific structural element, an inspector identifier linking the record to a named, accountable person, and a photograph that shows the defect being scored. Remove any one of those four and the record becomes difficult to defend in a dispute, an insurance claim, or a funding audit. Teampl standardises and quality-checks field-collected infrastructure data for exactly this reason, so that every record carries a consistent structure and supporting photographic evidence rather than a number that nobody can trace back to a moment and a place. Photographic evidence bound to a timestamp and coordinate is not a stylistic flourish on a condition record. It is the structural requirement that makes the score independently auditable years after the inspector has left the site.

What Are the Limits of a Condition Survey?

Visual condition surveys have known, well-documented limits, and treating them as more than they are is a recurring failure mode. First, a visual inspection is not a diagnosis — France's own guidance is explicit that the inspection is confined to a visual state-of-play and does not establish structural cause (OverView, 2018) [3]. Second, even standardized scales carry subjectivity. ASTM D6433's distress catalog was built for walking inspections, and many of its distress items still rely on subjective evaluation, which brings with it low repeatability between inspectors (Pavemetrics, 2025) [10]. Third, inspection cadence is only as good as the funding behind it — ASCE's $373 billion bridge funding gap means a documented six-year or three-year cycle on paper does not guarantee it happens on schedule in every jurisdiction (Gordian, 2025) [7]. Fourth, standardization is uneven even within a single country: France's own departmental survey found indicators varying from one département to the next despite a uniform national tool existing (IESF, 2018) [4].

None of this makes condition surveys unreliable. It means a condition score is only as trustworthy as the schema, the cadence discipline, and the evidence chain behind it — and those three things are exactly where custom field programs earn their keep relative to a static public register.

Where This Leaves the Reader

None of this is complicated in theory. The schema is the same whether you're scoring a motorway bridge deck or a charging connector: location, attribute, severity, photo, timestamp. It gets complicated in practice — recruiting inspectors who apply the same severity scale consistently, keeping that schema identical across hundreds of sites and several countries, and proving the photo was actually taken where and when the record says it was. Public standards tell you what good data should look like. They don't run the field program for you. Your next hire isn't a vendor. It's a data team.

Want the operational detail behind how programs like this actually get run — recruiting, quality control, chain of custody? That's what we do day to day.

Frequently Asked Questions