The decommissioning signal chain: how BSEE filings reveal work before execution

Ask a Gulf of Mexico BD manager how they find decommissioning work and you will hear familiar answers: relationships, the operator’s annual plan, a friendly engineer, a rumor on the crew boat. Those channels matter. They are also difficult to scale and hard to verify.

There is a slower, more structured source. Every abandonment and removal on the federal outer continental shelf leaves a regulatory trail with the Bureau of Safety and Environmental Enforcement. BSEE publishes much of that record as downloadable data. It does not name the winning contractor. But the sequence can show that activity is progressing, roughly how much observable scope remains, and whether execution has been reported.

Why there is no award feed

Federal decommissioning regulations require lessees and owners of operating rights to plug wells, remove facilities and clear the site under defined circumstances. BSEE regulates whether those obligations are met, not which marine, lifting or P&A contractor is hired. The commercial agreement remains private.

That limitation is important: no reported work start does not mean no contract exists. The useful point is narrower. Regulatory records can surface activity before physical work is visible in the field. A filing or status change gives a BD team a reason to investigate earlier than waiting for a public announcement that may never come.

The chain, dataset by dataset

The sequence below is a working commercial interpretation, not a statement that every asset follows the same path.

Step	What it may mean commercially	Where it appears
Lease assignment / ownership change	Responsibility may have moved; the liability chain warrants review	Lease assignment and ownership records
Production ceases	Idle-infrastructure or end-of-lease requirements may become relevant	Lease production data
Wells remain idle	A visible obligation remains and may become part of a P&A campaign	Borehole status
Well-work filing submitted	Regulatory approval is being sought; procurement status is unknown	eWell records
Removal application filed	A structure-removal scope is entering the regulatory process	Platform and removal records
Filing approved	Execution is possible, subject to operator schedule and other dependencies	Same records, status change
Work commenced	Execution has been observed; related scope on the lease may remain	End-of-operations or structure status records
Permanently abandoned / removed	The recorded obligation for that item has advanced to completion	Borehole status and structure records
Cost estimate	BSEE’s modeled view of regulatory exposure, not a tender value	Decommissioning cost estimates

The useful information is often in the transition: filed to approved, idle to permanently abandoned, standing to removed. A record that appears unchanged day after day is context, not a fresh lead.

Where the investigation window sits

Before a filing, ownership changes, production cessation and accumulating idle wells create a watch situation. That is a reason to research the asset and build the right relationship—not evidence that a bid is imminent.

Between filed and work commenced, GOMDecom treats the record as an investigation window. Planning is visible, while reported execution has not begun. A capability note, budgetary conversation or vessel-availability update may be timely here, but the operator may already have procured the work or may defer it for months.

Filed and not started is a reason to investigate—not evidence of an open tender.

After work commences, the item is in execution. Related scope can still remain: wells may be plugged before a structure is removed, or several assets may form a phased campaign. But the record now points to an active delivery relationship that a late entrant needs to understand.

Read by opportunity, not by record

BSEE data is row-shaped. Pursuits are not. One campaign can appear across well records, structure records, pipeline permits and a lease history. Reading one row at a time turns a possible campaign into disconnected fragments.

Group the evidence around one operator, one area, the remaining observable scope and the history behind it. Five idle wells with approved filings, two standing structures with removal activity and no reported commencement may represent one opportunity. It may also represent separate packages or already-awarded work. The grouping helps a team decide where to call; it does not replace account knowledge.

Every interpretation should remain traceable to its source rows. That is the distinction between evidence-backed intelligence and a rumor. GOMDecom’s methodology explains how change detection, lifecycle stages and commercial scoring are kept separate.

What the record cannot tell you

• No awards. “No work start observed” never means “no contract awarded.” Verify procurement status through your own channels before committing pursuit resources.
• Cost estimates are not tender values. BSEE’s estimates are regulatory exposure models. They indicate scale, not price.
• Filings can lag operations. A recent status change may relate to a vessel or rig contracted earlier.
• Grouping is interpretive. Adjacent leases, shared facilities and unit agreements complicate relationships across datasets.
• Not every obligation moves on the same clock. Asset condition, lease status, approvals and enforcement all affect timing.

The public record is still one of the earliest structured sources available to a Gulf decommissioning team. Read as a sequence—and paired with account intelligence—it provides a better basis for prioritization than a pile of unconnected rows.

Sources

• Electronic Code of Federal Regulations, 30 CFR Part 250, Subpart Q — Decommissioning Activities.
• Bureau of Safety and Environmental Enforcement, public data portal.
• GOMDecom, methodology: sources, change detection, lifecycle stages and scoring.