How do you prove a fuel site inspection happened?
Not with a memory of the walkthrough. With a record built to survive the inspector asking for twelve months of them.
Answered in short
5 things that decide this
- 01Federal rules require a walkthrough inspection of underground storage tank spill prevention and release detection equipment at least every 30 days, and the records must be kept for one year, per 40 CFR 280.36(b).
- 02The record has to name each area checked, whether it was acceptable or needed action, and a description of what was done to correct it. A single pass or fail for the whole site does not satisfy the requirement.
- 03A missing record is treated as a missed inspection, regardless of whether the walkthrough actually happened. The record is the compliance artefact, not the walkthrough itself.
- 04A record that can hold up needs four properties: timestamped at capture, not at upload; photo-backed; immutable, with corrections as new versions rather than overwrites; and honest about gaps, showing a missed period as a gap rather than hiding it.
- 05TankAware, our petroleum site platform for Sutherland Excavating Ltd. in Canada, builds exactly this: scheduled, per-asset, per-site inspections captured on a phone, with deficiencies escalated to a work order a contractor closes with evidence.
Every 30 days, per area, in writing
The obligation sounds simple until you read it closely. Every 30 days, at every site, someone checks specific equipment. Spill prevention gear for damage, liquid, debris or a blocked fill pipe. Release detection equipment for proper operation. What the rule then asks for is not a summary of the visit. It's a record naming each area you checked. It notes whether that area was acceptable or needed action, plus a description of what you did to fix any issue found.
That per-area structure is where paper logs and single-checkbox apps both fail you. A binder marked "inspected, OK" for the whole site answers an easier question than 40 CFR 280.36(b) actually asks.
Four properties an inspector's questions will test
An inspector doesn't ask whether the walkthrough happened. They ask you to show them, and the record either holds up or it doesn't.
- 01Timestamped at capture, not at sync: an offline inspection at 9am synced at 5pm has to record 9am as the time, held apart from the sync time, or it looks late.
- 02Photo-backed: evidence attached to the specific area you checked, not one photo standing in for the whole visit.
- 03Immutable: a correction creates a new version instead of overwriting the original, so an edit can't be mistaken for the record itself.
- 04Gap-honest: a missed 30-day window shows as a gap, not a quietly backfilled entry. That gap is exactly what a regulator looks for.
- 05Deficiency-to-work-order: an area marked as needing action links to a work order and its close-out, so "noted" isn't the end of the story.
- ScheduleRecurring, per asset, per site
- CapturePer-area result, photo, time of the visit itself
- StoreImmutable; a fix is a new version
- EscalateA deficiency becomes a work order
- ExportTwelve months, on demand, with any gap visible
TankAware runs this loop today. It's exactly what we mean by the record being the product.
Some of the systems we have shipped
Related questions
01What does a compliant 30-day walkthrough record actually contain?+
A list of each area you checked. Whether each one was acceptable or needed action. A description of the corrective action taken. And delivery records, where spill prevention equipment is checked less often than every 30 days because deliveries are infrequent. That's the exact content 40 CFR 280.36(b) asks for.
02How long do we have to keep the records?+
One year, per 40 CFR 280.36(b). Retain longer where you can, since other obligations and disputes reach back further, and check your state's implementing agency, which often sets a stricter rule than the federal floor.
03Does a paper binder satisfy the requirement?+
It can, if it's complete and per-area. In practice, binders get gaps, get backdated, and can't be searched when an inspector asks for twelve months at once. The requirement is about content and availability, not format. Either way, your paper record has to survive the same tests a digital one does.
04What happens if the inspection happened but the record is missing?+
As far as the agency is concerned, it did not happen. The record is the compliance artefact. A missing record is the violation, independent of what actually occurred at the site.
05Can Hashlogics build this into our existing system?+
We build the scheduling, capture, immutability and escalation layer. During the audit, we confirm exactly what your current ATG, ERP or operator portal already exposes, so we design to it instead of guessing.
Related
- Site monitoring for fuel and oilfield →The inspection engine, and proving the negative.
- What should a tank monitoring system alert on? →The other half of the compliance picture: alarms, not records.
- Packaged tank monitoring vs a custom site platform →When a vendor portal already covers this, and when it doesn't.
- Oil and gas →The hub: all eight areas, and which page owns each one.
