When the inspector asks for records, this is what you hand over
One PDF binder, exported on demand for any date range. Every record in it was timestamped by the server at the moment of capture and locked from that point on — which is exactly what makes it worth handing over.
What is in the PDF binder
Cover page
- Facility name and address
- Report date range
- Generation timestamp
- Count of overdue obligations as of export
Inspection records
- Obligation type and regulatory citation
- Scheduled frequency
- Completed timestamp (server-set, not user-supplied)
- Performed by and signature name
- All checklist items with pass / fail / needs-action results
- Notes per item
- Embedded JPEG evidence photos
Corrective actions
- All corrective actions resolved in the period
- Count of open corrective actions as of export date
- Source (inspection finding, logged event, or NOV)
- Resolution note and timestamp
Operator training (§280.245)
- All designated Class A, B, and C operators
- Training records per operator with date and trainer
- Covers §280.243 initial training and §280.244 annual refresher
Why the records are defensible
A paper checklist filled in the night before an inspection looks exactly like one filled in on time — and inspectors know it. These records carry proof of when they were made, and no one can change them afterward. That is the difference between a stack of paper and evidence.
Server timestamp at capture
Completion time is recorded by the server when you submit — not your device clock. Records cannot be backdated by editing a form field.
Database-level immutability
A database trigger prevents any modification or deletion of a completed inspection record after the fact. The record is locked.
Audit trail on every record
Every inspection stores who performed it, when, and with what signature. Every corrective action stores who resolved it.
Federal obligations covered
30-day spill-prevention and release-detection equipment walkthroughs (§280.36), the per-delivery spill check with delivery records, annual containment-sump and hand-held release-detection checks, 3-year spill-bucket, containment-sump, and overfill tests (§280.35), release-detection monitoring on the cadence your method requires (§280.41, §280.43), the annual release-detection operability test (§280.40(a)(3)), cathodic protection testing and 60-day impressed-current inspections (§280.31), piping release-detection for pre- and post-2016 piping, post-repair and post-install follow-up deadlines (§280.33, §280.31(b)(1)), and Class A/B/C operator training records (§280.243–245).
State-specific requirements are not tracked at launch. Release reporting, permanent closure, and financial responsibility obligations are out of scope.
14-day free trial · $39 per facility per month