Guardrail & Barrier Audit Logger
Roadside barrier audit — rail height, post condition, end terminals, impact damage and MASH-era hardware flags; GPS-pinned, offline-first.
New guardrail run inspection
Run a corridor audit annually and a damage check after every reported run-off-road crash; terminals deserve their own look each cycle.
Field guide: Guardrail & Barrier Audit Logger
Guardrail only works at the geometry it was crash-tested at. A W-beam that has settled 100 mm low, posts rotted at the ground line, or an obsolete turned-down terminal can convert a survivable run-off-road into a vaulting or spearing crash. This audit logger walks a run end-to-end: rail height (the modern MGS target is ~787 mm to the top, older systems ~730 mm), post and blockout condition, splice lap direction, and — most critically — what's on the ends.
Terminals get their own field because they're the highest-severity component: blunt ends and turned-down terminals are flagged with a warning right in the picker. Impact-damaged sections are logged as their own condition class since damaged rail has, by definition, already spent its design deflection and must be queued for repair regardless of how it looks.
Field tips
- Measure rail height from the travel-way surface, not the soil at the post — pavement overlays are the silent height killer.
- Sight down the run: a snaking rail line reveals leaning posts faster than checking each one.
- After any strike, check 25 m beyond visible damage; W-beam transmits tension and hidden splice damage travels.
Records are stored only in this browser (localStorage) — export regularly. This tool aids field documentation; it does not replace your agency's official inspection procedures or engineering judgment.
Disclaimer: This tool is for general informational and estimation purposes only and is not professional financial, tax, accounting or legal advice. All figures are estimates — verify with a qualified professional before making decisions. Read the full disclaimer.
Guardrail & Barrier Audit Logger — Roadside barrier audit — rail height, post condition, end terminals, impact damage and MASH-era hardware flags; GPS-pinned, offline-first. Free, offline-first and GPS-aware: open it on any phone, log in seconds, and hand your GIS team clean GeoJSON.
About Guardrail & Barrier Audit Logger
Guardrail only works at the geometry it was crash-tested at. A W-beam that has settled 100 mm low, posts rotted at the ground line, or an obsolete turned-down terminal can convert a survivable run-off-road into a vaulting or spearing crash. This audit logger walks a run end-to-end: rail height (the modern MGS target is ~787 mm to the top, older systems ~730 mm), post and blockout condition, splice lap direction, and — most critically — what's on the ends.
How to use Guardrail & Barrier Audit Logger
- 1Enter the route & run reference and tap 📍 GPS to pin the guardrail run's exact location (or type coordinates).
- 2Work through the guardrail run checklist — every field matches what a real inspection program records.
- 3Pick a condition on the Functional / Deficient / Impact-damaged / Non-functional scale; actionable findings are tallied automatically.
- 4Add notes and log the inspection — it saves instantly to your device, even with zero signal.
- 5Export the round as CSV for your asset system, GeoJSON for the GIS, or print a clean report.
Why use Guardrail & Barrier Audit Logger?
- ✓100% free, no sign-up — built for crews, not per-seat licences
- ✓Offline-first: records save to your device instantly and survive dead zones
- ✓One-tap GPS tagging with accuracy capture on every record
- ✓Exports CSV for asset systems, GeoJSON for GIS, and print-ready reports
- ✓Checklist and guidance aligned with AASHTO MASH
Frequently asked questions
What height should W-beam guardrail be?+
Modern MGS-type W-beam is installed at about 787 mm (31 in) to the rail top; many legacy systems were 706–730 mm. After repeated overlays, rail effectively 'sinks' — below roughly 670 mm, vehicles can vault, and most agencies program height restoration or replacement.
Why are turned-down end terminals flagged?+
Turned-down (ramped) ends, common decades ago, can launch an impacting vehicle or roll it. They were phased out under NCHRP 350 and MASH crash-test criteria in favor of energy-absorbing terminals. Any inventory still containing them deserves a programmed upgrade list — this audit builds exactly that.
Does minor impact damage really need repair?+
Yes. Barrier is a sacrificial system: deformed rail and displaced posts have consumed part of the deflection distance the next crash needs. Many DOTs require repair assessment within days of a reported strike; until then, the run protects less than the asset register claims.
What does splice lap direction mean?+
Rail sections overlap like roof shingles and must lap in the direction of traffic so a vehicle slides across the joint instead of catching an exposed edge. A reversed lap, usually from a hurried repair, is a snag hazard that's nearly free to fix once found.
Embed Guardrail & Barrier Audit Logger on your website
Want Guardrail & Barrier Audit Loggeron your own site? Paste this snippet into any HTML page — it's free, with no API key or sign-up. The tool loads in an iframe and keeps working exactly as it does here.
<iframe src="https://tooljolt.com/tools/guardrail-audit-logger" width="100%" height="640" style="border:1px solid #e5e7eb;border-radius:12px;max-width:680px" title="Guardrail & Barrier Audit Logger — ToolJolt" loading="lazy"></iframe>Related GIS tools
Shapefile to GeoJSON Converter
Convert ESRI shapefiles (.shp + .dbf or zipped) to GeoJSON in your browser — attributes preserved, nothing uploaded. Free, no size games.
● LiveShapefile Viewer
Open and inspect ESRI shapefiles online without ArcGIS or QGIS — feature counts, attributes and GeoJSON preview, 100% in your browser.
● LiveKMZ to KML Converter
Extract the KML from any KMZ file in your browser — see bundled icons/overlays too. No upload, no Google Earth install needed.
● Live