Connect your registration
Your workspace is provisioned against your regulatory identity — for Texas operators,
the RRC P-5 operator number; for other states, the equivalent registration.
That identity scopes everything: your users, your assets, your calendar. Sign in, rotate
the bootstrap credential, invite your filers with admin, filer,
or viewer roles.
New to a state? The catalog knows the onboarding gates too — in Texas, the
MEFC, RAMP DA, and SAD filings that unlock agency
systems appear on your calendar the moment you record beginning operations.
Import your assets
Wells, leases, and facilities load from the exports you already have. Each asset carries its jurisdiction, identifiers (API number, lease number), and operating attributes — and the deadline engine does the rest:
- Applicability rules decide which forms each asset owes — a producing Texas lease owes
monthly
PRs; a permitted-but-undrilled well owes nothing yet, and that's correct. - The engine generates a 12-month rolling horizon of obligations in advance, each with its computed due date and legal basis.
- Lifecycle events keep it current: a completion arms the completion-report window; a
transfer raises the
P-4; a spud is checked against the permit gate before it's accepted quietly.
File and confirm
Work the calendar top-down. Open an obligation, and the form renders from its versioned schema with agency-mirroring validation live in the fields.
An obligation's life:
- Blocking errors stop the submission cold — the API answers
422with the findings and writes nothing. Fix and resubmit; the bad attempt never pollutes your record. - Warnings ride along — recorded with the submission for reviewer judgment.
- Accepted payloads render to the agency's channel: EDI file download where the agency takes EDI, portal-ready output otherwise. You submit under your own agency credentials.
- Paste the agency's confirmation number back in — only then does the obligation
flip to
acceptedand leave the calendar. Agency acceptance is the source of truth, not our optimism.
And it stays current
Every night the horizon regenerates and statuses refresh against the clock. Catalog changes flow through the verification ledger with their sources. Every transition lands in the audit trail. The question "are we current?" stops being a meeting and becomes a glance at a calendar that is empty above today's line.