# Permits and well events

Source: https://developers.novilabs.com/data/tables/permits-events/

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

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`.

## PLANNED_WELL

Permitted wells, sourced from state and other public drilling permit filings. 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.

| Column | Description |
| --- | --- |
| `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. 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. There is no published table to join it to. |
| `NAME` | Human-friendly planned well name (e.g., operator naming). 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. |

## WELL_PERMIT

Regulatory drilling permit records associated with a wellbore. 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.

| Column | Type | Unit | Description |
| --- | --- | --- | --- |
| `WELLBORE_KEY` | string |  | Foreign key to wellbore.wellbore\_key that this permit applies to, resolved from the permit's api10. Every emitted well\_permit row links to an existing wellbore; permits whose api10 does not resolve to a wellbore are not represented. |
| `PERMIT_ID` | string |  | Regulatory permit identifier as issued by the state/agency. Not unique on its own, a regulator id recurs across states/datasets/permit revisions; the per-row grain is (permit\_id, wellbore\_key). |
| `OPERATOR_ID` | integer |  | Operator that filed for or holds the permit (foreign key to operator.operator\_id). Optional, omit (do not send null) when the filing operator cannot be resolved. |
| `PROPOSED_TVD` | number | ft | Proposed true vertical depth as declared in the permit application, in feet. The as-built value is wellbore.tvd\_td once drilled. |
| `EXPIRATION_DATE` | date |  | The expiry date filed with the permit. 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_AT` | timestamp |  | Timestamp the permit record was created. |
| `UPDATED_AT` | timestamp |  | Timestamp of the most recent update. |

## WELL_EVENT

Ledger of lifecycle milestones and state changes for wells and wellbores (planning -&gt; drilling -&gt; completion -&gt; production -&gt; workovers -&gt; P&A). 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.

| Column | Description |
| --- | --- |
| `WELL_EVENT_ID` | Surrogate key for the event row. |
| `WELL_KEY` | Well-level scope for the event. 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`). 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). May be null for planned events. |
| `EFFECTIVE_DT` | Business-effective timestamp for determining status transitions and economics (e.g., when production eligibility starts). 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. 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. |
