Available now

Compliance

Compliance that keeps its own calendar.

FastDragon works out what each site owes from what the site actually is. Pressurised piping gets an annual line tightness test. Suction piping gets one every three years. The calendar puts the overdue work first, and the proof is filed against the record when you mark it done.

Illustrative screen. Sample figures, never a real customer.

The problem

The rules do not remind you.

A missed test is rarely a decision. It is a date nobody was holding, on a site nobody was watching, found by somebody official.

  • Due dates living in one person’s head and one person’s spreadsheet
  • Proof that exists somewhere, in a binder, at a site, in a truck
  • A tank quietly losing product between the readings nobody totals
Compliance

Three screens do most of the work.

What the tanks are doing, what the last walk found, and where the proof lives.

Tanks

Two leak tests, run every single day.

A daily reading is checked against the state allowance and against the federal monthly test at the same time. A tank can pass one and fail the other, so FastDragon runs both and reports the worse of the two. When a tank fails, the clock to report it starts on screen.

  • Daily variance against the state allowance on tank capacity
  • The federal monthly test on throughput, run alongside it
  • A countdown to the reporting deadline, still shown after it passes
  • A tank with no capacity on file says so instead of showing a pass
Inspections

Walk the site. Leave with the punch list.

Inspect against a checklist on your phone at the pump island. Photograph what is wrong as you find it. The failures become a punch list before you are back in the truck, and the photos are already filed against the site.

  • Checklists you can edit, per site type
  • Photo evidence attached where you took it
  • A score, with the pass mark you set
  • Failures become tracked issues with an owner and a date
Records

The proof, where the question gets asked.

Certifications, licences, financial responsibility, test reports, and fines all sit against the site they belong to. Marking a requirement done asks for the document, so the file builds itself as the work gets done.

  • Operator certifications by person, with expiry dates watched
  • Test reports and evidence filed against the requirement they close
  • Fines and issues tracked to a resolution, not to a folder
  • One search from “show me” to the document
What you get

Compliance, run like the rest of the business.

An inspection stops being an event.

  • A per site calendar built from the site’s own tanks, piping, and state
  • Evidence filed against the record when you mark something done
  • Daily and monthly tank leak tests, with the worse result reported
  • Release reporting clocks that keep counting after the deadline passes
  • Inspections on a phone, with photos, scoring, and a punch list
  • Certifications, licences, financial responsibility, and fines in one place
  • Runbooks for the work that has steps somebody has to follow
  • The same login and the same people as the rest of FastDragon

2

leak tests run per tank, per day

24h

reporting clock, on screen and counting

1 click

from “show me” to the filed proof

0

separate logins to keep

Want to see your own sites on this calendar?

Book a walkthrough. Bring one difficult site and we will set it up on the call, tanks, piping, state and all, then show you what it owes.