Skip to content
All articles

Orphan Wells

How to read a plugging bid packet in twenty minutes

4 MIN READ

Shawn Azdam

Founder

Warm document pages unfolding into teal schematic grids over dark slate.
On this page

The average county bid packet runs forty pages, no two alike, and the clause that disqualifies you is never on page one. After ingesting thousands of these packets into the queue, we have converged on a twenty-minute routine that catches what matters. It is written for estimators, but owners who want better bids should read it too — every confusion this routine resolves is a question your bidders will otherwise ask at the pre-bid meeting.

Minutes 0–5: the skim that decides everything

Read four things first, in this order: the due date and delivery method (electronic portal, sealed envelope, or the dreaded "either, but..."), the well count and county, the mandatory pre-bid date if any, and the completion window. Kentucky's KASTOW Lincoln County #001 package, awarded January 14, 2026, is a clean example of the form: defined scope, dated milestones, a 365-day completion clock. If any of the four fails your filters — wrong geography, impossible window, pre-bid you cannot attend — stop here. The packet gets no vote.

Write the four answers on one index card, physical or digital. Every downstream decision references them, and packets that scatter them across thirty pages are testing your process, not your luck.

Minutes 5–12: the scope section is the contract

The scope of work is the only part of the packet that describes what you will actually do, and it is where fixed-price bids are won or lost. Read for inclusions and exclusions with equal attention: plugging intervals and cement specs, fluid handling and disposal responsibility, site reclamation depth (grade-and-seed versus full restoration), access and road obligations, and who owns the permits. Then read the measurement and payment section to learn how the owner converts scope into money — per well, per foot, lump sum, unit prices for overruns.

The expensive mistakes live in the gaps between scope and payment. A packet that scopes fluid disposal to the contractor but pays per well with no disposal line item is asking you to bury $18,000 in a lump sum and hope. Our cost analysis found fluid handling adding a median $18,000 per well — price it explicitly or decline explicitly, but never absorb it silently.

Minutes 12–17: the forms that disqualify

Most disqualifications are administrative, which means they are preventable. Check the bid bond or bid security requirement (percentage, acceptable forms, whether it must accompany the bid), the signature blocks (who signs, whether notarization is required), the mandatory forms checklist (non-collusion affidavits, EEO certifications, equipment lists), and the addendum acknowledgment — every addendum issued must be acknowledged in the bid, and missing one is the single most common disqualifier we see.

Then check whether the pre-bid meeting is truly mandatory. Some packets say "mandatory" and mean "strongly encouraged"; others disqualify no-shows without appeal. Either way, know what actually happens at the meeting before you drive out. Ohio's county packages routinely require attendance at the well site itself, not at an office across the state. Treat "mandatory" as literal until proven otherwise.

Minutes 17–20: the plat check

Close with the map. Count the well markers on the plat and compare against the scope table's well count — about one packet in eight disagrees, and the disagreement is where change orders are born. Note access routes, neighboring structures, and anything the plat shows that the scope does not mention: the flooded access road, the second wellhead, the pipeline crossing. Flag every mismatch in your written questions, because the answers become part of the contract record and the unasked questions become your problem.

Our extraction pipeline performs exactly this reconciliation at scale, and the mismatch rate above comes from its logs, not from theory.

What we think at Terrabillion

Bid packets should be structured data, and every hour an estimator spends hunting for the due date is an hour not spent pricing the work. Until packets arrive structured, routine beats heroics: the same twenty minutes, in the same order, on every package, with written questions filed early enough to matter. The queue exists to compress the first five minutes into five seconds — structured dates, counts, and locations on every listing — so estimators can spend their twenty minutes on judgment instead of archaeology. Go/no-go discipline is a competitive advantage, and it compounds.

Orphan-well intel, monthly

Contact sales