The agreement history is fragmented
Drafts, executed agreements, amendments, exhibits, acquisition files, and inherited contracts may sit in different repositories with inconsistent names.
Connect agreements, amendments, dedication clauses, exhibits, land descriptions, wells, and GIS context so teams can answer coverage questions with evidence before development or commercial decisions move forward.
Which agreements cover Section 18, T2N R6W?
Overlap requires review
Two effective agreements reference part of the requested section with different priority language.
North Basin Gathering Agreement
Primary candidateAmendment 04 · Exhibit B · Gas
Sec. 18 listed on page 27
Legacy Midstream Services Agreement
Secondary candidateOriginal agreement · Exhibit A
S/2 acreage reference on page 41
Resolved context
2 agreements · 1 amendment
4 related wells · 2 lateral intersections
1 priority exception · 0 missing exhibits
Bidirectional search
Move from agreement to acreage or acreage to agreement
Time-aware coverage
Preserve amendments, releases, terms, and priority
Evidence-first review
Keep every mapped result connected to contract language
A dedication is not just a polygon. It is a contractual obligation whose meaning depends on the governing language, amendments, scope, product, priority, term, and evidence.
Teams often have the information they need, but it is divided across contracts, exhibits, land systems, GIS layers, well records, and institutional knowledge. The workflow has to connect those sources without flattening the distinctions that affect the answer.
Drafts, executed agreements, amendments, exhibits, acquisition files, and inherited contracts may sit in different repositories with inconsistent names.
Coverage may be defined by leases, tracts, sections, wellbores, units, areas of mutual interest, products, depths, or future-acquired acreage.
Legal descriptions, GIS features, units, wells, laterals, and source-system identifiers require normalization before spatial comparison is dependable.
An inherited obligation, overlapping dedication, amendment, or priority right may surface during a tie-in, acquisition, forecast, or negotiation.
Search by section, tract, lease, unit, well, or geometry and return candidate agreements with the clause, exhibit, amendment, term, product, and coverage basis.
Move from an agreement to its normalized sections, tracts, leases, wells, laterals, and mapped geometry while retaining the original description and source pages.
Resolve the well and its relevant spatial context, compare it with effective coverage, and distinguish confirmed coverage from ambiguous or incomplete evidence.
Compare agreements by effective period, product, priority, contract type, and scope to surface potential conflicts, secondary rights, white space, and review needs.
Document intelligence prepares the language and exhibits. Identity and GIS services connect the operating context. Deterministic logic applies approved time and scope relationships. Qualified people approve the conclusion.
Inventory agreements and versions
AutomatedIngest executed agreements, amendments, exhibits, maps, and approved source data while preserving file provenance, version relationships, permissions, and package structure.
Output
Governed agreement package and document history
Extract dedication logic
AI assistedIdentify dedication clauses, defined terms, products, priorities, exclusions, release language, effective periods, acreage additions, and references to exhibits or schedules.
Output
Candidate contract terms with page-level evidence
Structure exhibits and land descriptions
AI + validationConvert tables and descriptions into typed locations, tracts, leases, units, wells, depths, and relationship records without discarding the original language.
Output
Normalized dedication table with source values
Resolve spatial and asset identity
Rules + matchingMatch locations to canonical geography, properties, leases, units, wells, and laterals using identifiers, aliases, effective dates, and GIS context.
Output
Candidate entity and geometry links with confidence
Build effective coverage
DeterministicApply approved amendments, additions, releases, terms, products, and priority relationships to build a time-aware coverage model rather than one flattened map.
Output
Effective-dated contract coverage and lineage
Analyze questions and exceptions
Agent assistedAnswer bounded contract-to-acreage and acreage-to-contract questions, compare candidate obligations, and prepare overlaps, gaps, conflicts, or missing evidence for review.
Output
Source-grounded answer and decision package
Review, publish, and monitor
Human controlledCommercial, land, legal, and GIS owners approve the interpretation and spatial representation before it informs negotiations, tie-ins, development, forecasting, or system updates.
Output
Approved coverage, audit history, and monitored events
Spatial analysis can focus attention and accelerate research. It does not replace the agreement language, effective history, or qualified interpretation governing the obligation.
Every material coverage result can point back to the governing agreement, amendment, clause, exhibit row, and original description.
Additions, releases, expirations, assignments, and amendments change the model over time without erasing historical truth.
Product, depth, priority, wellbore, lease, tract, section, AMI, and other scope types are not collapsed into one generic dedicated flag.
Search and overlap analysis prepare evidence. Qualified reviewers remain responsible for contractual interpretation and consequential action.
The workflow can support tie-ins, development planning, acquisitions, divestitures, forecasts, and negotiations. Start with the measurable research burden; evaluate commercial value separately using your own decision history.
Illustrative research-capacity model
Replace the assumptions with a measured baseline from your commercial and land teams.
Modeled annual capacity
360
annual research requests
648
hours redirected
81
eight-hour workdays
$58,320
equivalent labor capacity
Current modeled research workload: 1,080 hours annually. This model excludes commercial value from avoiding conflicts, improving negotiations, or accelerating development decisions.
Approved dedication intelligence becomes shared context for commercial, land, development, GIS, engineering, acquisitions, and finance workflows.
Available integrations and write-back depend on the source systems, permissions, data quality, and approved operating boundary. Sense keeps document and transformation lineage visible.
Turn lease packages into connected terms, approved records, and monitored obligations.
Explore workflow
GuideA practical framework for connecting instruments, entities, evidence, obligations, and review.
Explore guide
It is a controlled process for identifying dedication obligations in agreements and amendments, structuring the covered acreage or assets, connecting that scope to canonical land and GIS context, and preparing answers or exceptions for qualified review.
Sense can assemble the relevant agreements, amendments, mapped coverage, well and lateral context, effective dates, products, and competing obligations. The workflow can identify candidate coverage and conflicts, while the final contractual conclusion remains with authorized commercial, land, or legal reviewers.
Each instrument is preserved as evidence and connected to the agreement it affects. Approved additions, releases, assignments, or term changes can update an effective-dated coverage model without overwriting the earlier state.
Not every question requires a polygon, but spatial context materially improves coverage analysis. Sense can connect normalized legal descriptions and dedication rows to existing geography, tract, unit, well, and lateral data when those sources are available and authorized.
Yes. The data model and review policy can preserve priority, product, scope, term, exclusions, and other contract-specific distinctions rather than treating dedication as a single yes-or-no field.
Use representative executed agreements, amendments, complex exhibits, historical descriptions, acquisitions, overlaps, releases, and known edge cases. Measure clause evidence, exhibit-row extraction, location normalization, asset matching, spatial accuracy, exception burden, and reviewer acceptance.