43 CFR 3173.9 wants an inventory of every seal at the end of every month, with each seal number and the point it sits on — and a record of every seal broken and replaced in between. Most operators can produce a run ticket and a memory. This keeps the register, the full break-and-reseal chain, and the printable month-end inventory in one app that works on a phone with no signal.
One-time purchase. No subscription. No account. Works offline.
Sales valves, load-out valves, water-drain valves, LACT sample probes, sampler volume controls and meter components — registered per lease and tank battery with the seal number currently fitted and the date it went on.
A broken seal is not a problem. A broken seal nobody replaced is. Any point sitting unsealed shows the hours or days it has been that way, who broke it and why, at the top of the register where it cannot be missed.
Pick a month, pick a location, and get every point with its seal number, its status at month end, and every event recorded during the month — printable as a dated report and exportable as CSV.
Warns when the same seal number is recorded as live on two points, and flags any point whose last verification predates the current month — the two findings that turn a tidy log into a bad inspection.
Operators on Federal and Indian leases must keep a record of each seal used, and must inventory all seals at the end of each month. Sections 3173.2 through 3173.4 set out what has to carry a seal in the first place: sales and load-out valves, water-drain valves, LACT sample probes and sampler volume controls, and meter or CMS components.
Section 3173.5 puts the responsibility for a broken seal on the party that broke it — the purchaser or transporter, not automatically the operator — until the point is resealed. That only helps you if the person and company who broke it are actually written down.
The seal numbers are on a clipboard in the CTB. The break-and-reseal detail is scattered across run tickets in the purchaser's system. The month-end inventory is rebuilt from memory the day someone asks for it. Nothing ties a seal number to a point, to a date, and to the person who touched it last.
This app is that tie. One register, one event chain per point, and a month-end inventory generated from the record rather than reconstructed from it.
Every registered point sits in exactly one band, so the register reads top down and the exposure is always on the first screen.
Facility or lease, well or tank battery ID, what the point is, its component type, and the seal number currently on it.
Broken, applied, verified intact, or found tampered — with the date and time it happened, not the date someone wrote it up.
The person, and whether they were there as operator, purchaser, transporter or BLM. That is what § 3173.5 turns on.
Truck load-out for sale, water draining, hot oiling, completion work, routine inspection or meter proving — plus a free note for the run ticket number.
Every point's status computed as at the last second of the chosen month, not as at today, so a report run late still reports the month correctly.
Full JSON export and re-import so the register moves between devices and survives for the retention period. CSV for the inventory itself.
Built to the same shape as our other field-compliance logs, so if your crew already uses one, this one reads the same on day one.
It does not file anything with BLM, does not decide which points on your facility must be sealed, and does not replace 43 CFR part 3173, your approved site facility diagram, or your operator's own procedure. It records what was sealed, what was broken, by whom, when and why — and prints that record in a form an auditor can read.
Everything stays on your device. Nothing is uploaded, no account is created, and the app keeps working when the lease road has no bars.