Surface use agreement obligations for land teams

A surface use agreement is signed once, usually by a land agent negotiating with a single landowner, and then governs operations on that tract for as long as the asset produces and often for years afterwards. It sets what gets paid and when, where equipment may sit, which gates and routes may be used, what notice the landowner receives before a crew arrives, and what the surface has to look like when operations end.

None of that is complicated in isolation. The difficulty is that a land position is not one agreement, it is several hundred, negotiated over decades by people who have since left, with terms that vary tract by tract because they were negotiated tract by tract. The recurring payments are small enough individually to be invisible and numerous enough collectively to matter. The operational restrictions are the terms field crews most need and least often see.

This datasheet sets out which surface use provisions generate ongoing obligations, why payments and notifications drift, how restoration duties should be carried forward into decommissioning, and what happens to all of it when an asset changes hands. It is written for land administration, operations and the contract teams supporting both.

The obligation families

Surface use terms sort into five families, and each one needs a different monitoring shape. Treating them as a single category of land paperwork is why most of the drift happens.

• Payment obligations, annual or periodic surface damage and rental payments, sometimes indexed to an inflation measure or subject to periodic renegotiation on a defined cycle.
• Notification duties, advance notice before entry, before new construction, before workover activity and sometimes before contractor changes, each with its own notice period.
• Operational restrictions, permitted access routes and gates, setback distances, seasonal and time-of-day limits, livestock and water protections, noise and lighting constraints.
• Restoration commitments, reclamation standards, completion periods measured from cessation of operations, revegetation requirements and any landowner sign-off condition.
• Structural terms, term and renewal mechanics, successor and assignment language, consent requirements and the survival of specific duties beyond termination.

The five families have different owners. Payments belong with land administration and finance. Notifications and restrictions belong with operations. Restoration belongs with environmental and eventually with decommissioning. Structural terms belong with commercial during any transaction. No single function sees the whole agreement, which means the agreement itself has to be the integration point rather than any one team calendar.

Where surface use compliance fails

The failures below are operational rather than deliberate. In almost every case the agreement was clear and the information did not reach the person who needed it.

• Restrictions never reach the crew. Access routes, setbacks and seasonal limits sit in the land file while mobilization is planned from a well location, so compliance depends on individual memory.
• Notice periods are missed by days. Notification duties with short windows fail when the operational decision to mobilize is made inside the notice period, which is a planning sequence problem.
• Payments survive reorganizations poorly. Recurring low-value payments are the first thing lost in a system migration or a land department restructure, and the loss is silent until a landowner calls.
• Restoration is treated as future work. Reclamation duties that are not recorded as standing obligations with cost bases are rediscovered at decommissioning, alongside the environmental commitments they interact with.
• Acquired positions are inherited unread. Package transactions bring hundreds of agreements with varying assignment and successor terms, and clause-level review rarely happens after closing.

Building the land obligation register

Step 1, Inventory agreements against the land position

Reconcile the executed agreement set against current surface occupancy tract by tract. Gaps run both ways. Tracts occupied without a current agreement are an exposure, and agreements still being paid on tracts no longer used are a recoverable cost, and both are common in positions assembled over decades.

Step 2, Extract obligations at clause level

Pull payment amounts and escalation bases, notice periods, access restrictions, restoration standards and assignment terms into structured fields per agreement. AI extraction handles the retrieval, and land review is needed on the restriction language because negotiated accommodations are often written narratively rather than as clean terms.

Step 3, Route restrictions to operations

Publish access routes, setbacks, seasonal limits and notice requirements into the systems operations actually use for mobilization planning, keyed to location rather than to agreement number. A restriction that requires someone to open a land file before a site visit will not be honored consistently.

Step 4, Schedule payments with escalation logic

Create recurring payment obligations with the escalation basis and next escalation date recorded, not just the current amount. Alert on the escalation date as well as the payment date, since the failure mode is paying on time at the wrong amount rather than missing the payment entirely.

Step 5, Carry restoration forward

Record reclamation duties as standing obligations with their trigger, completion period, standard and cost basis, and make them visible in decommissioning planning and in any divestment data room. These are the obligations most likely to be valued incorrectly in a transaction because they are the least well documented.

What happens at transaction time

Surface use obligations are consistently under-examined in asset transactions, and the reason is structural rather than careless. Diligence is organized around reserves, title, environmental liability and material contracts, and a few hundred small surface agreements do not read as material contracts individually. Collectively they carry the recurring payment stream, the operational constraints that determine how the asset can actually be worked, and the restoration liability that will eventually be funded. They also carry assignment language that varies agreement by agreement, meaning some obligations transfer automatically, some require landowner consent and some require renegotiation with a counterparty who now has leverage. An acquiring operator that receives the position as a document set rather than as a clause-level obligation register inherits all of this without being able to state it, and typically discovers the shape of it over the following two years through landowner contact. Building the obligation register before divestment, or immediately after acquisition, is the only point at which the work is cheap.

Monitoring model by family

The table below shows the tracking shape for each obligation family, with the owner and the signal that should trigger attention. The split of ownership is the point, because a single owner for all five is what causes the operational terms to stay in the land file.

Surface use agreements are the clearest example of contract value that is entirely post-signature and almost entirely operational. Nothing about the negotiated text protects the relationship with a landowner. What protects it is paying the right amount on the right date including the escalation nobody noticed, giving notice before a crew arrives, respecting a setback that was agreed fifteen years ago, and restoring the surface to the standard that was promised. Each of those is a tracked obligation with a named owner, and each one is far cheaper to record now than to reconstruct during a dispute or a sale.

For related guidance, see Pipeline right of way easements, tracked properly, Exclusive use clauses and how violations get missed and Farmout agreement earning obligations: a land team guide.

Aavenir Oil, Gas & Mining PracticeLand and operations contract guidance from the Aavenir energy practice.