Ohio Admin. Code 3745-95-06
The city kicks the test back three weeks later — wrong form.
You tested nine devices on Tuesday. The carbons rode around in the truck until Friday. Two came back illegible, one had last year's gauge serial on it, and the water authority wants all nine resubmitted before it will clear the account.
Read it yourself — primary source, not a vendor summary:
https://codes.ohio.gov/ohio-administrative-code/rule-3745-95-06
01 / The inspection
Tap through it the way a certified tester would.
8 items, about forty seconds. Mark one as a fail and watch what the Device record does.
Device recorded as failed — retest required
The failing reading, the repair note and the photo stay attached to the device. When it is repaired and retested, the passing record links back to the failure, so the account reads as one history instead of two loose sheets.
02 / The record log
“Send me the tests for 114 Euclid in March.”
Every finished inspection lands here, searchable by Device, Tester, record number or date. Try BF-104.
03 / What it would cost
One price. No per-seat math.
- —Readings entered at the device, timestamped where you stood
- —Gauge serial and calibration date carried onto every test automatically
- —A failed device stays flagged until a passing retest links to it
- —Search by device, address, tester or date
- —Export one test or a whole account as a PDF the authority accepts
- —Photo of the gauge face attaches to the reading
- —Works offline in a mechanical room and syncs when you get signal
This page is the prototype. If the workflow above is close to yours, tell me what is wrong with it and I will change it before you pay anything.
Email me what is wrong with it