3 offshore record layers
Block and lease identity separated
Verified August 10, 2026
Offshore leasing research has a chronology problem: a planning notice, a sale result, and a lease record may describe the same geography at different points in time. Reading them as one event can create a false status.
Offshore Leasing Data 2026: Measured findings from the cited authority
BOEM’s 2024 combined leasing report lists 58,320 offshore planning blocks totaling 318,792,157 acres. It counts 2,353 active leases covering 12,746,315 acres, including 498 producing leases covering 2,498,520 acres. The totals combine Gulf, Pacific, and Alaska regions and are reported as of the monthly update. Source: BOEM Combined Leasing Report 2024. For land work, the active-versus-producing gap is the measured reason to keep lease status and production status as separate fields.
Fields worth preserving
The following fields keep the Offshore Leasing Data 2026: 3 Record Layers question narrow enough to audit without hiding the original publisher’s terminology.
| Field |
What to retain |
| Planning area |
sale area or program reference |
| Block identity |
area, block, and map datum |
| Lease number |
executed lease identifier when present |
| Status date |
effective, expiration, relinquishment, or update date |
| Document link |
source file or BOEM record used |
Reading the evidence
Data sources and methodology
Begin with the BOEM document that states the question’s geography. Record its area and date, locate the matching block or lease, and only then compare the status with a later publication. A map view is a locator; the cited record supplies the evidence. Offshore Leasing Data 2026: 3 Record Layers uses a separate evidence boundary.
Do not replace a missing observation with a guessed value in Offshore Leasing Data 2026: 3 Record Layers. For boem-offshore-lease-data-2026, retain the publisher label, identifier, date, and unit beside every normalized value. For boem-offshore-lease-data-2026, conflicting observations remain side by side with their definitions and dates.
Topic-specific interpretation notes
Planning area deserves its own review note in Offshore Leasing Data 2026: 3 Record Layers: retain sale area or program reference, state why the field matters, and identify the condition that would make the observation unreliable.
Block identity deserves its own review note in Offshore Leasing Data 2026: 3 Record Layers: retain area, block, and map datum, state why the field matters, and identify the condition that would make the observation unreliable.
Lease number deserves its own review note in Offshore Leasing Data 2026: 3 Record Layers: retain executed lease identifier when present, state why the field matters, and identify the condition that would make the observation unreliable.
Status date deserves its own review note in Offshore Leasing Data 2026: 3 Record Layers: retain effective, expiration, relinquishment, or update date, state why the field matters, and identify the condition that would make the observation unreliable.
Document link deserves its own review note in Offshore Leasing Data 2026: 3 Record Layers: retain source file or BOEM record used, state why the field matters, and identify the condition that would make the observation unreliable.
Frequently asked questions
Is the item a planning document, a sale record, or an executed lease?
BOEM planning documents identify proposed areas and timing assumptions.
Does the block reference use the same area and coordinate convention?
Lease-sale material records bids, awards, or related sale information rather than ongoing operations.
Which date controls the status conclusion being considered?
The active lease layer is the place to check current identity and status fields, subject to the publisher’s update cycle.
Evidence packet review before handoff
Before this record set is used in a land workflow, review the planning area, block, sale or lease identifier, record type, status date, coordinate convention, and retrieval date. Preserve each value exactly as the publisher displays it before adding a normalized copy. The normalized field may help with matching, but it should never overwrite the source label or conceal a conflict.
Open each cited source again from the saved locator. Confirm that the identifier, jurisdiction, date meaning, geography, and unit apply to the question being reviewed. Record whether the link opens a specific record, a search interface, or only a general program page. A general entry point can guide further research, but it is not evidence that a particular tract, lease, well, owner, order, or transaction was found.
Keep missing results visible. Note the query used, the coverage available through that interface, the date searched, and the next authorized source or reviewer. Do not convert a blank value into zero or infer an event between two published observations. If two systems disagree, retain both source values and describe the difference without deciding which one controls.
The handoff should separate source observations, administrative normalization, unresolved exceptions, and reviewer decisions. That structure lets another researcher reproduce the search and lets the authorized land, legal, regulatory, accounting, engineering, or commercial reviewer resolve questions within their role. It also prevents a workflow note from being mistaken for a title conclusion, operational determination, or assurance about source completeness.
Limits of the record
BOEM’s 2024 combined totals are area and lease-status aggregates. They do not prove a particular block’s current operations, development approval, title position, or commercial availability.
Reference register
These are the distinct public record layers used to frame Offshore Leasing Data 2026: 3 Record Layers; each link should be checked for its own definition and update schedule.
- BOEM Leasing: public record entry point; check the source's definitions, coverage, and update schedule before use.
- BOEM Lease Query: public record entry point; check the source's definitions, coverage, and update schedule before use.
- BOEM Mapping: public record entry point; check the source's definitions, coverage, and update schedule before use.
- BOEM National OCS Program: public record entry point; check the source's definitions, coverage, and update schedule before use.
- BOEM Regulations: public record entry point; check the source's definitions, coverage, and update schedule before use.
- BOEM eWell: public record entry point; check the source's definitions, coverage, and update schedule before use.
- BOEM ArcGIS: public record entry point; check the source's definitions, coverage, and update schedule before use.
- Federal Register BOEM: public record entry point; check the source's definitions, coverage, and update schedule before use.
- NOAA ENC: public record entry point; check the source's definitions, coverage, and update schedule before use.
- FERC Offshore: public record entry point; check the source's definitions, coverage, and update schedule before use.
Additional reading notes
Observation 1. BOEM planning documents identify proposed areas and timing assumptions.
Observation 2. Lease-sale material records bids, awards, or related sale information rather than ongoing operations.
Observation 3. The active lease layer is the place to check current identity and status fields, subject to the publisher’s update cycle.
Conclusion
Use the BOEM block, lease, and status-date fields as separate evidence lines; Book a free consultation if an offshore file needs reconciliation.