Are Your Wells Where You Say They Are?


Confirm the field footprint before you approve the next pad, road, or infill plan.

Pad planning depends on accurate location data.

Before an operator approves an infill program, lays out a new pad, extends an access road, adds facilities, or changes development sequencing, the team needs a reliable view of the asset.

That view often comes from several sources. Internal databases, inherited well files, public records, subscription platforms, GIS layers, planning maps, and field knowledge may each show a slightly different version.

A well may appear in one system and be missing from another. Coordinates may conflict. A pad may have expanded since its boundary was drawn. An access road may have moved. Surface facilities may occupy space the planning layer still shows as available.

Those differences matter once the next development plan depends on them.

BasinIQ compares internal records, public data, subscription datasets, and SynMax high-resolution proprietary satellite imagery. Teams can see where the sources agree, where they conflict, and which locations need review before capital is committed.

Request a Development Validation Demo

A Development Plan Can Be Precise and Still Start From the Wrong Map

Location data changes as assets move through development, acquisitions, system migrations, and ownership transitions.

Well records may be copied between databases without every field being updated. Public sources may contain incorrect or incomplete coordinates. Pad boundaries may reflect original construction rather than the current footprint. Roads and facilities can change without those changes reaching every internal system.

The planning layer may look complete. The underlying records may still carry enough uncertainty to affect:

  • Infill well placement
  • New pad design
  • Pad reuse or expansion
  • Road and facility planning
  • Development sequencing
  • Surface access
  • Permitting
  • Cost estimates
  • Acquired-asset integration

A location discrepancy that caused no immediate problem during production can become material when the next well or facility is designed around it.

For planning teams, the concern is simple: can this plan be defended if the field does not match the map?

Where Asset Location Data Breaks Down

Location problems often appear when teams inherit data or work across multiple systems.

Common issues include:

  • Acquired well data spread across files, databases, spreadsheets, and legacy systems
  • Internal well coordinates that do not match public or subscription data
  • Wells present in one source and missing from another
  • Pad boundaries that are incomplete, outdated, or manually interpreted
  • Planned pad dimensions that do not match the visible surface footprint
  • Access roads that have been rerouted, extended, or omitted
  • Facilities and surface equipment missing from the planning layer
  • Subsurface assumptions tied to surface locations that have not been confirmed
  • Pad reuse or expansion decisions based on stale information
  • Future development plans that overlook current surface constraints

Each issue creates another question for engineering, planning, GIS, land, and operations to resolve. When several occur together, teams can spend more time reconciling the asset than evaluating the development program.

BasinIQ Creates a Reconciled View of the Field

BasinIQ brings the available records and current field evidence into one validation workflow.

Teams can compare well files, internal databases, public records, subscription data, GIS layers, planning files, and satellite imagery. BasinIQ highlights matches, conflicts, missing information, and visible features that may affect the plan.

The review helps teams determine:

  • Whether wells are located where the records say they are
  • Whether pad footprints match current field conditions
  • Whether planned pad dimensions fit the visible site
  • Whether access roads follow the expected route
  • Whether nearby facilities limit available space
  • Whether inherited records support future development
  • Which locations are ready for planning
  • Which locations require field, GIS, land, or engineering review

The result is a clearer starting point for the next development decision.

Validate Well Locations

A well can have different coordinates across internal systems, public sources, and commercial datasets.

BasinIQ compares those records and organizes the discrepancies for review. Teams can identify wells with:

  • Conflicting coordinates
  • Missing source records
  • Incomplete well files
  • Questionable public locations
  • Unclear relationships to the visible pad
  • Acquired data that has not been independently checked

Some discrepancies may be minor or administrative. Others can affect spacing, pad design, infill planning, and surface layout. BasinIQ helps teams find the differences that deserve attention.

Confirm the Pad Footprint

Pad boundaries often change after initial construction.

A site may be expanded, reshaped, connected to additional wells, or modified for new facilities. An old planning polygon may no longer represent the area visible in the field.

BasinIQ uses satellite imagery and available planning data to review:

  • Four-corner pad alignment
  • Current pad dimensions
  • Planned versus visible footprint
  • Expansion areas
  • Adjacent equipment and facilities
  • Available space
  • Potential reuse constraints
  • Surface changes since the planning layer was created

This gives teams better information when considering pad reuse, expansion, redesign, or additional well placement.

Check Roads and Surface Access

Road access affects construction, logistics, permitting, cost, and field execution.

BasinIQ compares internal road data with satellite-visible road traces. The review can identify:

  • Missing road segments
  • Rerouted access
  • Road extensions
  • New connections
  • Abandoned routes
  • Nearby surface disturbance
  • Access assumptions that need field confirmation

A road discrepancy may change the construction plan or cost estimate. Finding it during validation gives the team more room to respond.

Review Nearby Infrastructure and Constraints

Existing infrastructure can limit where future work fits.

Tanks, batteries, pipelines, roads, facilities, and nearby pads may affect the available surface area. These features may be absent from older planning layers or represented differently across systems.

BasinIQ helps teams review the surrounding field context before approving:

  • New infill locations
  • Pad expansions
  • New drills
  • Facility additions
  • Road construction
  • Development sequencing changes

The analysis can show where a plan may require relocation, redesign, additional access work, or further field verification.

How the Validation Workflow Works

1. Connect the asset records

Provide BasinIQ with approved well files, coordinates, GIS layers, pad plans, road data, and other relevant development information.

2. Compare the sources

BasinIQ evaluates the internal records alongside public data, subscription datasets, and current SynMax satellite imagery.

3. Resolve the planning gaps

Your team receives a prioritized view of confirmed locations, conflicting records, missing data, visible constraints, and sites that require further review.

BasinIQ supports the technical workflow already in place. Engineers, geoscientists, GIS specialists, land teams, and field personnel retain control of final interpretation and approval.

Questions Teams Can Ask BasinIQ

BasinIQ can help answer questions such as:

  • Do our internal well locations match public and subscription data?
  • Are the acquired wells located where the files say they are?
  • Which wells have conflicting coordinates?
  • Which wells are missing from one or more systems?
  • Does the visible pad footprint match the planning layer?
  • Are the four pad corners aligned with the current surface footprint?
  • Has the pad expanded since the planning data was created?
  • Does the planned pad size fit the visible site?
  • Does the internal access-road layer match the route visible in satellite imagery?
  • Are there tanks, facilities, roads, or other constraints near the proposed development?
  • Which pads appear suitable for reuse or expansion?
  • Which locations need redesign or additional field confirmation?
  • What discrepancies should be resolved before the infill plan is approved?
  • Which sites are ready for development planning?
  • Which sites still carry material uncertainty?

These questions help the team focus on the location issues most likely to affect the plan.

Why Location Accuracy Matters

Bad location data can create expensive development problems.

A well plotted in the wrong place can distort spacing assumptions. An outdated pad boundary can make a site appear larger than it is. A missing road or facility can change the construction plan. A surface constraint discovered late can force engineering work to be repeated.

The consequences may include:

  • Pad redesign after planning is underway
  • Road changes late in the development cycle
  • Incorrect reuse or expansion assumptions
  • Conflicts with existing facilities
  • Additional surveys or field work
  • Permitting delays
  • Rework across GIS, engineering, land, and operations
  • Cost estimates based on incomplete conditions
  • Capital decisions tied to an inaccurate asset footprint

These risks increase after an acquisition. The buyer may inherit several disconnected systems, inconsistent coordinates, and limited information about which source reflects current field conditions.

BasinIQ helps teams find those gaps early enough to address them.

Move From Inherited Data to Confident Planning

For planning teams, location validation provides a more reliable basis for sequencing and development design.

For drilling and completions teams, it improves the surface context available before execution.

For GIS and technical data teams, it identifies records that need correction.

For land teams, it clarifies where access and surface constraints may require attention.

For operations and facilities teams, it creates a clearer view of what is already present.

For asset leaders, it improves confidence that the development program reflects current field conditions.

The team can approve the plan knowing which locations are confirmed, which assumptions have been tested, and which issues still require action.

Built for Teams Responsible for Development

BasinIQ supports:

  • Development planning
  • Drilling and completions
  • Operations
  • Reservoir engineering
  • Production engineering
  • Land
  • GIS and technical data teams
  • Facilities
  • Asset teams
  • A&D and corporate development

Verify the Field Before You Commit the Capital

BasinIQ helps operators move from assumed locations to validated development plans.

Teams can compare well records, pad footprints, four-corner boundaries, access roads, nearby infrastructure, and satellite-visible field conditions before planning future infill, new drills, or pad redesigns.

Reliable development planning starts with an accurate view of the asset.

Request a Development Validation Demo