Skip to content
Developers
Get an API token

Permits and well events

Drilling permits, permit filings, and the well lifecycle event timeline.

View MarkdownOpen in Claude(opens in a new tab)

Views live in NOVI_DATA_ACCESS.NOVI_WELLS. Column descriptions are from the Wells data dictionary, release 26.4.3. Type is the data model’s logical type, and unit appears where the model declares one. For Snowflake column types, query NOVI_DATA_ACCESS.INFORMATION_SCHEMA.COLUMNS.

15 columns

Permitted wells, sourced from state and other public drilling permit filings.

More about this view

One row per permit. This is the public record of what operators have filed, not Novi Labs' own view of drilling inventory. Most rows describe wells that have since been drilled: where that has happened, status is COMPLETED and materialized_well_key points at the resulting well row in well / wellbore. Rows with status PROPOSED or PERMITTED are the forward-looking subset.

Sample query
SELECT PLANNED_WELL_ID, MATERIALIZED_WELL_KEY, OPERATOR_ID, PAD_ID, NAME
FROM NOVI_DATA_ACCESS.NOVI_WELLS.PLANNED_WELL
LIMIT 10
Columns15
PLANNED_WELL_ID
Stable, immutable identifier for this planned well.
MATERIALIZED_WELL_KEY
Foreign key to well.well_key once the permitted well has actually been drilled.
More

Non-null on the majority of rows, because most permits on file correspond to wells that already exist. NULL while the permit is still forward-looking or was cancelled.

OPERATOR_ID
Current operator.
PAD_ID
Always NULL in this product: no pad entity is published, and pads are not derived from coordinates.
More

There is no published table to join it to.

NAME
Human-friendly planned well name (e.g., operator naming).
More

Not a key.

COUNTY
County or parish where the planned well is located.
TARGET_FORMATION
Intended target formation/bench for the lateral (e.g., 'Wolfcamp A').
LATERAL_LENGTH
Planned horizontal lateral length in feet.
STATUS
Planning lifecycle status.
PLANNED_SPUD_DATE
Scheduled spud date.
BASIN
Basin name (e.g., Permian, Eagle Ford).
SUBBASIN
Subbasin name (e.g., Delaware, Midland).
SOURCE_ID
Foreign key to source.source_id for data lineage.
CREATED_AT
Timestamp the plan was created.
UPDATED_AT
Timestamp of the most recent update.
10 columns

Regulatory drilling permit records associated with a wellbore.

More about this view

One row per permit filing; captures the permitted operator and the proposed wellbore depths as declared in the application. Permit lifecycle milestones (submitted / approved / amended / cancelled) are recorded as PERMIT_* events on well_event, linked via well_event.permit_id.

Joined from
WELL_EVENT
Sample query
SELECT WELLBORE_KEY, PERMIT_ID, OPERATOR_ID, PROPOSED_TVD, EXPIRATION_DATE
FROM NOVI_DATA_ACCESS.NOVI_WELLS.WELL_PERMIT
LIMIT 10
Columns10
WELLBORE_KEYstring
Foreign key to wellbore.wellbore_key that this permit applies to, resolved from the permit's api10.
More

Every emitted well_permit row links to an existing wellbore; permits whose api10 does not resolve to a wellbore are not represented.

PERMIT_IDstring
Regulatory permit identifier as issued by the state/agency.
More

Not unique on its own, a regulator id recurs across states/datasets/permit revisions; the per-row grain is (permit_id, wellbore_key).

OPERATOR_IDinteger
Operator that filed for or holds the permit (foreign key to operator.operator_id).
More

Optional, omit (do not send null) when the filing operator cannot be resolved.

PROPOSED_TVDnumberft
Proposed true vertical depth as declared in the permit application, in feet.
More

The as-built value is wellbore.tvd_td once drilled.

EXPIRATION_DATEdate
The expiry date filed with the permit.
More

It does not mean the permit expired. If the well was spudded, or a later permit was approved, the date is moot. A permit lapsed unused when this date has passed and WELL_EVENT has no SPUD and no later PERMIT_APPROVED event. The PERMIT_CANCELLED event in WELL_EVENT (emitted when the regulator's permit status is Cancelled or Expired, joined on PERMIT_ID; a permit merely past this date under another status has no event) carries this date as EVENT_DT. NULL when no expiry date was filed.

BASIN
Basin name (e.g., Permian, Eagle Ford).
SUBBASIN
Subbasin name (e.g., Delaware, Midland).
SOURCE_ID
Foreign key to source.source_id for data lineage.
CREATED_ATtimestamp
Timestamp the permit record was created.
UPDATED_ATtimestamp
Timestamp of the most recent update.
13 columns

Ledger of lifecycle milestones and state changes for wells and wellbores (planning -> drilling -> completion -> production -> workovers -> P&A).

More about this view

New events are appended in normal operation, except event types documented as one row per well, which are updated in place when a newer occurrence is reported; physical retractions are allowed only to handle source-side corrections (e.g., when an event's underlying source field is cleared). Use event_dt for when something happened, effective_dt for when it should count for status/economics. Payload captures event-specific fields without changing the schema.

Key columns
Sample query
SELECT WELL_EVENT_ID, WELL_KEY, WELLBORE_KEY, PERMIT_ID, EVENT_TYPE
FROM NOVI_DATA_ACCESS.NOVI_WELLS.WELL_EVENT
LIMIT 10
Columns13
WELL_EVENT_ID
Surrogate key for the event row.
WELL_KEY
Well-level scope for the event.
More

Provide either well_key or wellbore_key (or both) depending on applicability.

WELLBORE_KEY
Wellbore-level scope for the event (e.g., SPUD, TD_REACHED, COMPLETED for a specific lateral).
PERMIT_ID
Foreign key to WELL_PERMIT.PERMIT_ID, the regulator-issued permit associated with this event (primarily permit-class events: PERMIT_SUBMITTED, PERMIT_APPROVED, PERMIT_REJECTED, PERMIT_AMENDED, PERMIT_CANCELLED, PERMIT_ISSUED).
More

NULL when the event has no associated permit. PERMIT_ID alone is not unique in WELL_PERMIT, whose grain is (PERMIT_ID, WELLBORE_KEY): join on both columns.

EVENT_TYPE
Event code indicating the lifecycle milestone or change.
EVENT_DT
Timestamp when the event actually occurred (if known).
More

May be null for planned events.

EFFECTIVE_DT
Business-effective timestamp for determining status transitions and economics (e.g., when production eligibility starts).
More

Often equals event_dt but may differ due to backfills or corrections.

PAYLOAD
Event-specific attributes, keyed by event_type, captures details that vary by event without adding sparse top-level columns.
More

The keys expected for each event type are documented on that event_type value (see the event_type enum). Payload keys are validated/typed via conditional schemas for OPERATOR_CHANGE, WELLBORE_TYPE_CHANGE, PERMIT_SUBMITTED, and the completion events (COMPLETION_STARTED / COMPLETED / DRILL_OUT); for other event types the payload keys are documented but not statically typed, so their value domains (e.g., operator_calculated is an operator.operator_id; wellbore_type_normalized is a WELLBORE_TYPE_NORMALIZED value; wellbore_type_reported is the type as the source reported it, at whatever granularity the source supplies) apply by convention. On permit events wellbore_type_reported carries a coarse classification (Oil, Gas, Service or Unknown), because permits have no filed code.

BASIN
Basin name (e.g., Permian, Eagle Ford).
SUBBASIN
Subbasin name (e.g., Delaware, Midland).
SOURCE_ID
Foreign key to source.source_id for data lineage.
CREATED_AT
Timestamp when this event record was created.
UPDATED_AT
Timestamp of the most recent update to this event record.