Bridge Inspection Report Retention Software: 7-Year Guide

By Corin Hale on October 8, 2026

bridge-inspection-report-retention-software-7-year-guide

Bridge inspection reports are the engineering and legal memory of every structure in an owner's inventory. Each routine, fracture critical, underwater, and special inspection adds photos, element ratings, sketches, load rating inputs, and follow-up actions that must stay findable for years. When a report cannot be produced during a federal review, a claim, or a repair design, the inspection loses most of its value. This guide explains how to build a seven-year-plus retention discipline around the National Bridge Inspection Standards, and how a CMMS can keep inspection records connected to the bridges and work orders they describe.

Bridge RecordsNBIS Retention

Bridge Inspection Report Retention Software: A 7-Year Guide for Bridge Owners

Keep every inspection report, photo, load rating, and follow-up action retrievable for seven years and well beyond, with each record tied to the bridge, the finding, and the work that closed it.
01
Inspect
Field data and photos captured
02
Review
Team leader and program sign-off
03
Submit
Inventory data reported
04
Act
Findings become work orders
05
Archive
Locked, indexed, retained
06
Retrieve
Produced on request
The Records Problem

Inspection Data Rarely Disappears All at Once

Bridge programs seldom lose records in one dramatic event. The loss is gradual, through staff turnover, shared drives, consultant hand-offs, and photo folders named by date instead of structure number.

1
Reports held by the consultant
Final PDFs arrive by email and live in one inbox. The owner cannot produce the full set when the contract ends.
2
Photos detached from findings
A crack photo exists, but nobody can say which element, which inspection cycle, or which rating it supported.
3
Findings closed without evidence
A repair was made, yet the record shows no completion date, crew, or verification at the next inspection.
4
Drafts mixed with finals
Superseded versions sit beside signed reports, so the authoritative record is a matter of opinion.
5
Retention by habit
Files are deleted during a drive clean-up because no schedule says otherwise.
Record Inventory

What Belongs in a Bridge Inspection Record

A complete bridge file is more than a report PDF. Each item below should be stored against the structure and the inspection date it belongs to.

RecordWhat It ContainsWhy It Matters Later
Inspection reportCondition ratings, element data, narrative, recommendationsPrimary evidence of the structure's condition at a point in time
Photographs and sketchesTagged images of defects, access conditions, and overall viewsShows deterioration trends between cycles
Load rating recordsCalculations, assumptions, posting decisionsSupports posting and permit decisions
Scour recordsScour evaluations and plans of action for scour critical bridgesDrives flood-event response
Underwater inspection filesDive reports, channel profiles, substructure findingsFills the long gap between underwater cycles
Critical finding follow-upNotifications, interim actions, closure documentationProves timely response to urgent defects
Inspector qualificationsTeam leader credentials and training evidenceSupports the validity of each report signature
Repair and maintenance historyWork orders, costs, materials, completion evidenceLinks condition changes to the work that caused them
Regulatory Frame

NBIS Inspection Types and the Records Each One Creates

The National Bridge Inspection Standards, codified in 23 CFR Part 650 Subpart C, set inspection frequency and qualification expectations. Each inspection type produces a different record set, and the intervals determine how long a report stays the current reference.

Inspection TypeTypical IntervalRecords Created
InitialWhen a bridge enters the inventoryBaseline condition, inventory data, first load rating
RoutineGenerally up to 24 months, adjusted by approval or conditionCondition ratings, element data, photos, recommendations
Fracture critical memberGenerally up to 24 monthsHands-on findings for steel tension members, special procedures
UnderwaterGenerally up to 60 monthsDive findings, channel and substructure condition
Damage, in-depth, specialAs events or conditions requireEvent reports, targeted testing, engineering assessments
Intervals differ by owner approval and bridge condition. Confirm the current requirements and your agency's approved intervals in the rule text and with your program manager.
The 7-Year Question

Seven Years Is a Floor, Not a Ceiling

No single number fits every bridge owner. State records schedules, agency policy, litigation holds, and federal expectations set the real period, and many owners keep bridge files for the life of the structure.

Years 0 to 2
Working tier
Current-cycle reports and open findings. Needs fast retrieval and field access from a phone or tablet.
Years 2 to 7
Reference tier
Prior-cycle reports and closed work orders. Needed to compare condition across cycles and answer review questions.
Life of structure
Lifecycle tier
Design records, load ratings, scour plans, major repairs, and critical finding history. Never schedule for routine deletion.

Confirm Before You Configure

Ask your records officer or counsel which schedule applies, then set retention by record class rather than by folder. This page is operational guidance, not legal advice.

Report Lifecycle

Six Controls That Keep a Report Defensible

1
Schedule against the asset
Each bridge carries its own due dates, so no inspection depends on someone's calendar.
2
Capture in the field
Findings and photos are entered against the element on site, not rebuilt from notes later.
3
Review and lock
Sign-off freezes the final version and preserves a clear approval trail.
4
Convert findings to work
Recommendations become corrective work orders linked back to the finding.
5
Verify at next inspection
Completed repairs are checked against the original defect and the evidence is attached.
6
Retain and retrieve
Records follow the retention schedule and can be produced by structure, date, or finding.
Retrieval Stress Test

Four Moments When Missing Records Hurt Most

Federal compliance review
Reviewers sample bridge files and ask for inspection reports, qualifications, and evidence that findings were handled on time.
Claim or dispute
Counsel needs the condition history, the inspection that flagged an issue, and the response that followed.
Repair or replacement design
Engineers need prior ratings, photos, and repair history to scope work and avoid repeating past mistakes.
Flood or impact event
Crews need the scour plan of action and the latest substructure findings within hours, not days.

Test Your Own Bridge Files Against These Four Moments

Set up a handful of structures in Oxmaint and see how quickly a complete record can be produced.
Audit Readiness

A Retention Checklist for Bridge Program Managers

Record Completeness

Every bridge has a unique, stable identifier across all files
Final reports are marked as final and drafts are archived separately
Photos carry structure, element, and inspection date tags
Load rating and scour records sit in the same file as inspections
Inspector qualifications are linked to each signed report

Retention Controls

Retention period is set by record class and reviewed yearly
Deletion requires approval and respects legal holds
Consultant deliverables are copied into the owner's system
Open critical findings cannot be archived until closed
A quarterly retrieval test pulls a random structure's full history
Before and After

Shared Drives Versus a Records-Linked CMMS

Folder-Based Records
Reports found by searching file names
Photos stored apart from the findings
Follow-up tracked in a separate spreadsheet
Retention depends on who manages the drive
Gaps discovered during the review
Records Linked to Assets and Work
Full history opened from the bridge record
Photos attached to inspection entries
Findings generate and track work orders
Retention rules applied by record class
Gaps flagged before the review begins
Oxmaint Workflow

How Oxmaint Supports Bridge Record Retention

Oxmaint is maintenance management software, so it works best as the system that links inspection records to assets and work. Confirm your specific export and records-schedule needs during a demo.

CapabilityRetention Job It Performs
Asset managementGives each bridge one record that holds its history, documents, and linked work
InspectionsStructures recurring inspection checklists and stores completed results with the asset
Work ordersTurns findings into corrective work and keeps completion evidence attached
Scheduling and preventive maintenanceGenerates due dates so intervals are not tracked by memory
Mobile workflowsLets crews and inspectors record findings and photos on site
Compliance recordsKeeps sign-offs, dates, and documentation in one searchable place
Reporting and dashboardsShows overdue inspections, open findings, and records awaiting review
Measure It

Retention KPIs Worth Tracking

Set your own targets from your schedule and risk profile. These measures show whether the discipline holds.

Retrieval time
Time to produce one bridge's full file during a test
File completeness
Share of bridges with every required record class present
Open finding age
Days critical and priority findings stay unresolved
Overdue inspections
Bridges past their due date by inspection type
Untagged photos
Images missing structure or element tags
Consultant intake lag
Days between report delivery and archive in your system
Trends

Changes That Will Increase Your Record Volume

Updated inventory data structures
FHWA's move to the Specifications for the National Bridge Inventory changes how data is coded and reported, so mapping old and new records matters.
Drone and high-resolution imaging
More images per inspection mean storage, tagging, and retention rules must scale.
AI-assisted defect review
Machine-generated findings still need a reviewer's sign-off and a preserved audit trail.
Aging inventory
Older structures carry decades of history that new inspectors must be able to find quickly.
FAQ

Bridge Inspection Retention Questions

Is seven years the required retention period?

It depends on your state schedule and agency policy, and many files are kept for the life of the structure. Treat seven years as a minimum and book a demo to map your schedule.

Which records should never be deleted?

Load ratings, scour plans, major repair history, and critical finding records are usually lifecycle records. Confirm with your records officer.

Can a CMMS replace our bridge inventory system?

Not usually. It complements inventory systems by linking inspection records to assets and work orders. Get started with a pilot group of bridges.

How do we handle consultant-produced reports?

Require delivery of final reports and photos into your own system, tagged to the structure and inspection date.

How often should we test retrieval?

A quarterly test that pulls a random bridge's full history exposes gaps early and costs very little.

Build a Bridge Records Program That Holds Up Under Review

Link every inspection, photo, finding, and repair to the bridge it belongs to, and retain it on your schedule.

Share This Story, Choose Your Platform!