PHMSA federal · applies in all states
Create operator admin / compliance
Create system for the selected operator · admin / compliance
Welcome to SEAL — set up your first operator guided, about 10 minutes. You can close this any time and set up manually from the top bar instead.
Step 1 — Find your operator in the RRC data. Type the operator name or its 6-digit RRC operator number.
Step 2 — Confirm the suggested systems. One system per county is suggested from the operator's own counties. Uncheck any county to leave it out.
Step 3 — Confirm and import.
Done.
System health from the system digest + calendar summary
Ask SEAL plain-language answers from your own computed data — exposure, plug plan, SEAL Score, deadlines, filings. Nothing is invented; unanswerable questions say what is missing.
Answers are computed directly from your data. AI status is shown after your first question (or check the system status endpoint).
Pick a system (top bar) and ask — for example “which wells do I lose if I do nothing?” or “what is my SEAL Score?”
Compliance snapshot
Attention needed deadlines due-soon / overdue
P-5 guard Not checked yet
Continuous P-5 monitoring: Delinquent blocks all new drilling permits at the operator level. A guard of “Unknown expiry” means the P-5 is Active but no renewal date is on file — no expiry is assumed.
Loading P-5 guard states…
Not legal advice — confirm current P-5 standing with the Railroad Commission of Texas before acting.
OQ watch expiring / expired qualifications
Exposure charts wellbores only — one API number counts once
SEAL Score 0–100 compliance health — components shown, never a black-box number
Pick a system (top bar) and load its score. Missing data lowers confidence visibly — it never produces a silent perfect score.
Dollars saved by Extension Rescue granted outcomes after rescue filings only — no estimates, no projections
Every granted extension after a rescue filing adds that well's plug cost to this running total. Reconcile reads the outcome database; an entry cites the well, the outcome record and the cost figure, so the total reconciles. A granted well with no plug cost on its record is listed with no amount added — never $0.
Pick a system (top bar) and load the ledger.
Extension Rescue wells entering the 90-day window before their threshold get a draft automatically
On each RRC data refresh, wells entering the 90-day window before their binding SB 1150 threshold get an extension-request draft in the filing queue for review. Re-running never duplicates a draft. A run that finds nothing new says so plainly.
No rescue run yet for this system in this session.
Add asset admin / compliance
Bulk import admin / compliance
CSV import — columns: type,name,length_mi,class_location,material,tvc_status,notes
GeoJSON import — each Feature becomes an asset
Asset register
Inactive wells — Texas SB 1150 view: all roles · import & plans: admin / compliance
Well inventory
CSV import admin / compliance
CSV columns: api_number,operator_name,lease_name,well_status,completion_date,last_production_date,latitude,longitude,total_depth_ft + optional: days_produced_12mo, boe_12mo (NM low-producing test), avg_boe_per_day_12mo (UT at-risk test), ta_status
Dates are YYYY-MM-DD. The first row is the header (any column order). Every rejected row is reported below with its row number and reason; nothing is silently dropped.
Exposure report all roles — estimates, not quotes
Record a plug completion
A plugged well leaves the live liability — exposure, planner, and SEAL Score exclude it and disclose it (“N wells plugged — $X liability retired”). The well stays in the evidence chain (flagged, never deleted). The record generated is a preparation document, not a filing.
Plugged wells in this system
Loading plugged wells…
Actual vs RRC-estimated plug costs
Plug plan builder admin / compliance
Deal check all roles — read-only screening
Bond / financial-assurance calculator estimates from the state rule pack
RRC statewide inactive wells Texas only · public RRC data · read-only
Who to call first prospect ranking from statewide RRC data · Texas only
Plug-first action plan ranked from statewide RRC data · Texas only · read-only
Extension-denied wells first — but the action follows the RRC's recorded denial reason (retest, file test, renew P-5…), never a blanket plug order. Then earliest binding date, cheapest RRC est. cost wins ties.
The history path is assessed from your declaration only — a single
IWAR snapshot cannot show a return-to-production history, and this tool never claims to verify it from IWAR.
Enter an RRC operator number and choose “Assess paths”.
Cash flow all roles — read-only; Texas (RRC IWAR) operators
Bond cost is a required operator-stated input — the tool never assumes it. All money figures are ESTIMATES.
Watched operators alerts fire on an IWAR refresh when a watched operator gains newly-past wells, new extension denials, removals, or a P-5 change — newly-approaching alone never sends an alert
New watches are filed under the system selected in the top bar (System picker). Leave emails blank to use the server's default alert recipients (PC_ALERT_EMAILS), when set.
IWAR data refresh downloads the current RRC Inactive Well Aging Report, converts + dedupes it, diffs it against the saved snapshot, then swaps it in — a failed or stale download changes nothing and is recorded as failed
Loading refresh status…
Recent changes per-operator diffs recorded at each refresh
Loading…
Alert history (outbox) every alert ever dispatched, with its literal delivery status — “sent” only when the SMTP server accepted the message
Loading…
Annual test reports — §89.050 tracker Texas only
For the system selected in the top bar (System / sysSel).
Periods start on each well's first completion anniversary (+15 years, then yearly) on or after Sept 1, 2027, when the RRC rules implementing SB 1150 take effect — no earlier period is counted as due.
A period shows filed only when a filing was recorded below.
Choose a system in the top bar, then “Load tracker”.
This tracker records filings a user has entered. An item shows filed ONLY when a filing was recorded here — absence means not recorded, not necessarily not filed with the RRC.
Record a filing
Tip: use a row's “Record” button in the tracker to pre-fill API + due date for that period.
Bulk deal screening paste API numbers → liability summary · Texas RRC data only
Matches each API against the RRC Inactive Well Aging Report (as of the date shown) and evaluates
it as of Sept 1, 2027 under SB 1150. Max 5,000 APIs per run.
Screens inactive-well exposure only — not a title search, and not a substitute for full due diligence.
Well map exact sites where coordinates were supplied · county circles where only a county is known
hits threshold
approaching
compliant
insufficient data
● exact well site (coordinates supplied)
◯ county circle, sized by due wells — plotted at county center — RRC data carries county, not coordinates
Circle size = wells that hit the threshold or are approaching it (evaluation status hits-threshold or approaching); compliant and insufficient-data wells are not counted in the size. Click a county circle or a county row to filter the wells list to that county.
Extension-request drafts v5.2 · drafts from the well record — not filings
One draft per well approaching or past the line (wellbores only). Production history, test status and evaluation come from the well record; future utility comes only from operator-supplied input — anything not supplied is listed as missing, never invented.
Choose a system in the top bar, then “Load drafts”.
Filing queue — done-for-you v5.2 · generated drafts wait for operator review/approve · nothing here is sent or filed
No queue items loaded yet.
Approval is a recorded sign-off (who/when). An approved item is still not sent and not filed — filing with the regulator remains a separate, manual, operator act.
Filing outcomes v5.2 · operator-recorded only — never inferred
Aggregates show district / reason counts only — they never identify an operator.
Undo / correction v5.3 · tombstone deletes — rows are kept so the evidence chain still verifies
Deleting a well hides it from every total but keeps its chained row — the chain still verifies. Undoing an import removes exactly the wells that import added. Both refuse when work was recorded against a well afterwards (plug, test report, filing). Every delete is written to the audit log. Deleting a system refuses when any of its wells has recorded work.
Not loaded yet.
No import history loaded yet.
Compliance calendar computed from recorded evidence — NO DATA means no record exists
Capture field record admin / compliance / field
Recent records chain hash (short)
Monthly field visit list touch-friendly · saves through the existing record + photo flow
One row per asset for the system selected in the top bar. A tick is for this visit only and is not saved to the server — saving a visit creates a normal chained record (pick a rule from the list) and an attached photo goes through the existing photo endpoint. Visits already recorded in the chosen month show as visited.
Choose a system in the top bar, then “Load visit list”.
Add personnel admin / compliance
Add qualification admin / compliance · 192 Subpart N
Qualification matrix
Log test 49 CFR Part 199 · admin / compliance
MIS reminder
Test log
Regulatory deadlines incl. per-segment TVC status
Regulatory watch RRC rulemaking tracker — Texas SB 1150
Detects page changes; does not interpret legal text. Confirm milestones manually. A page change is a signal to look — never a legal conclusion.
Monitored pages sha256 of normalized page text
No in-app scheduler — point an external cron atPOST /api/rulemaking/check (admin/compliance).
Mark milestone admin / compliance — manual confirmation only
Milestones flip only by hand. The tracker can tell you a page changed; only a person can say what it means.
Monthly change digest per operator · built only from recorded refresh diffs
After an IWAR refresh, build the digest for one operator: it names exactly the wells that changed (crossed the line, extension denied / denial cleared, removed) — unchanged wells are never named. A digest is stored once per refresh run; rebuilding returns the stored one.
No digest loaded yet — run a refresh, then build one.
Peer benchmark anonymized aggregates only — no other operator is ever identified
Compares this operator with other operators of a similar size (same inactive-well count band) operating in the same counties / districts, using the shipped statewide RRC data. Averages only; the output names no peer operator.
No benchmark loaded yet.
Permit-block warning P-5 standing — delinquency blocks new drilling permits
Checks whether this operator's P-5 standing would block new drilling permits. Only a Delinquent P-5 is called “blocked”. Any other non-Active P-5 is shown as “unverified” — the well record cannot verify what it means for a specific permit. Not legal advice; confirm standing with the RRC.
No check run yet.
SMS deadline alerts STUBBED — no provider configured, nothing is sent
30-day and 7-day deadline alerts are plumbed but stubbed: no messaging provider is configured and no credentials exist. An alert below is recorded to the SMS log with status “not-configured” and is never sent. Provider selection, credentials, and recipient opt-in are a later decision.
SMS is stubbed — the log will show “not-configured” for every attempt.
Deadline command center every system, every deadline source, one sorted rollup
Digest cumulative windows: 7 ⊂ 30 ⊂ 90 days
Escalation check admin / compliance — one alert per item at the overdue / 30 / 7 / 1-day marks, deduped via the outbox
No in-app scheduler — point an external cron at
POST /api/command-center/check (admin/compliance). Already-recorded alerts are skipped, never re-sent.Plug-vs-extend planner v5.2 · plug N wells per year — year-by-year liability, cash, and §89.050 burden
Uses the system selected in the top bar. One API number counts as one wellbore (duplicate rows merged first). Money is labeled with its cost basis: RRC per-well cost where present, else the $75,000 planning default (an ESTIMATE, not a quote). Tick “RRC costs only” to surface wells with no RRC figure as unpriced instead of defaulting them.
No plan built yet.
Value-pricing helper v5.2 · DISPLAY ONLY — no charge, invoice, or subscription is created
Managed liability is the flagged wellbores (hits-threshold + approaching, deduped by API) priced RRC-first / $75,000 default. Rates are yours to enter — the helper holds no price list. The annual liability rate is entered as a percent (2 = 2%/yr).
No pricing computed yet.
Bond-gap alert v5.2 · bond on file vs required assurance — wraps the state bond calculator
Texas has no verified bond calculator in this build, so the Texas alert says so and estimates nothing. For states with a verified calculator (NM, UT), enter the bond currently on file plus the calculator's inputs as JSON (operator-supplied counts — e.g. NM: {"well_count":10,"inactive_count":1,"approved_ta_count":0,"expired_ta_count":0,"low_producing_count":1}).
No bond-gap check run yet.
Report incident admin / compliance — the clock starts at discovery
49 CFR 191.5: telephonic notice to the NRC (800-424-8802, telephone only since Apr 2026) no later than 1 hour after confirmed discovery; 48-hour revise/confirm (191.5(c)); written report within 30 days (191.9 / 191.15 / 195.54). In Texas a second 1-hour clock runs to the RRC at (512) 463-6788.
Incidents discovery facts are hash-chained
Annual report worksheet preparation — not the filing
Pre-fills what the app knows from your asset register and records, and flags every field it cannot answer. Verify each line against the PHMSA Portal instructions before filing.
Dec 1 readiness — §89.049 preparation package preparation — not a filing, not legal advice
Guided flow for the first RRC report under §89.049: the Commission's report to the governor, lieutenant governor and legislature — not an operator filing, nothing is due from the operator on this date. The flow is general: Dec 1, 2026 is the first instance; change the date for the recurring annual instance. Anything SEAL cannot verify is listed as operator-confirmed, never assumed.
Pick a system (top bar) and check readiness. Operator-confirmed items are ticked in the checklist before saving.
Lender documents one-pager · quarterly certificate · lender dashboard · read-only for viewers
Uses the operator selected in the top bar. One-pager and certificate open as printable pages in a new window. A viewer linked as a lender sees only their linked borrowers in the dashboard; an unlinked viewer sees none.
Record retention per-record schedule
Rows marked VERIFY have no retention period encoded — check the live eCFR before destroying anything. "Eligible for review" means the retention period has passed, not that the record should be deleted.
Anomalies derived from your records — review each one
Derived automatically when records are saved: CP readings below −850 mV, overdue inspections, expired OQ qualifications. Confirm real issues, mark false positives — the audit pack carries the review state.
Mock PHMSA audit self-assessment in the inspector's language
Auto checks run against your records and calendar; the rest need your attestation. Attestations never override computed results (except N/A).
Portfolio all clients · past-line exposure at Sept 1, 2027 · costs are RRC estimates · unpriced wells are never counted as $0
Pitch pipeline ranked IWAR prospects · real RRC data · all costs are RRC estimates
My operators in-store clients · well counts from your systems
Transfer pack (A&D) one pack per well set — exposure, extension status, test history — to hand a buyer · printable
The pack covers exactly the wells selected — matched wells, unmatched APIs and unparseable inputs are all listed, never dropped. Costs are labeled by basis (RRC estimate vs operator estimate); wells with no cost figure are counted as unpriced, never as $0.
Buyer screening — per-report paste a seller's well list → liability + red flags as one shareable report · distinct from bulk screening
One report per run, printable from the button below the results. Not a title search and not a substitute for full due diligence.
Marketplace — foundations only transfer-ready listings + inquiries · no matching, no transactions, no fees in this release
Foundations only: a listing flags a well set as available for transfer and carries its transfer pack; an inquiry records a message of interest. Nothing here buys, sells, matches, or prices a well.
Generate audit pack admin / compliance
Regulatory frameworks read-only · 49 CFR Parts 192 / 195
RRC data refresh v5.3 · guarded — a bad file never replaces the live data
SEAL checks the public RRC IWAR source itself. A refresh refuses — with a clear reason — when the source is unreachable, the file is malformed, the file is stale, or it has fewer rows than the current snapshot. The previous snapshot is retained before any swap. Denial reason codes are shown only when the current file actually carries them.
Not loaded yet.
Audit log admin / compliance
Backup admin only
User management admin only
Consultant branding admin / compliance · text only — no logo upload (the PDF writer has no image support)
Partner tier admin / compliance · per-client report branding + revenue-share bookkeeping (no payments)
Select an operator first (top bar).
Record a revenue share bookkeeping only — no payment is made or linked