Home · Oil and Gas Software · End of Well Report Software

NWE WellReport™ · Reporting — Close-Out

End of well report software that assembles the whole job.

The end-of-well package is where a well's record either holds together or falls apart. NWE WellReport generates the formal end-of-well report from the same record the well kept every day: as-built surveys, the plan-vs-actual summary, BHA and run history, the daily archive, failure reports, and the field ticket rollup — six sections, ready at total depth, because none of it had to be rebuilt.

Explore the live platform See the entire-well platform

The close-out problem

The last report of the well is the first one built from scratch.

At total depth, somebody inherits every gap the daily workflow left — and spends days closing them.

The as-builts are in one system, the daily reports in a folder, the BHA history in a spreadsheet, the failure story in an email thread, the tickets in a drawer. The end-of-well package becomes an excavation: numbers re-derived, runs re-argued, and a final document that restates the well instead of reporting it.

It does not have to work that way. If the record was kept daily — surveys accepted once, runs closed with their reports, tickets logged against the work — the end-of-well package is a generation, not an excavation. That is the entire design premise of the platform, and this report is where it pays off.

The package

Six sections, one source.

The daily archive is the package's backbone.Every daily drilling report the well produced is archived in the record as issued — so the end-of-well package can roll the well up day by day without re-deriving a single number, and any figure in it can be traced back to the day it was reported.

01 / THE SECTIONS

As-builts, actuals, and history — as recorded.

The package opens with the as-built surveys from the accepted ledger and the plan-vs-actual summary measured against the stage-based plan, then carries the full BHA and run history — every assembly, every run's depths, hours, footage, and reason out — with its per-run BHA and Motor reports behind it.

As-built surveys from the ledger
Plan-vs-actual summary
Complete BHA and run history

Live NWE WellReport workspace showing the well record the package generates from

02 / THE HARD PARTS

Failures and tickets, rolled up honestly.

The package does not skip the expensive days. Failure reports — equipment failures with their photographs and accounts — are part of the record and roll into the close-out, and the field ticket rollup carries the job's tickets with their NPT treatment as recorded, so the commercial story and the operational story close together.

Failure reports in the package
Field ticket rollup with NPT as recorded
Daily archive, day by day

Live NWE WellReport Directional Drilling workspace with the full well record

The close-out workflow

Kept daily. Generated at TD.

Drill on one record.

Surveys, runs, costs, tickets, and failures are recorded as they happen, all well long.

Runs close with reports.

Each BHA run files its BHA Report and Motor Report as it ends — the history writes itself.

Generate at TD.

At total depth the formal package generates from the record: six sections, all sourced.

Review and issue.

The professional reviews the package — every figure traceable to its day — and issues it.

Deliverables

Six sections. Zero excavation.

Generated from the record, not rebuilt from memory.

Every section below is produced from data the well recorded while it was drilled — which is why the package can be ready when the well is, instead of weeks after.

As-built surveys
Plan-vs-actual summary
BHA and run history
Daily report archive
Failure reports
Field ticket rollup
Per-run BHA & Motor reports
Combo plot

The whole job · in one package

Where it stands

In founding field testing now.

The formal package shipped in the October build.The end-of-well report — all six sections — is part of the platform our founding testers run end to end on the demo well: they drill the well in the record, close its runs, and generate the package at the end. Founding tester seats are open until October 25.

Honest about the source.The package reports the record — it does not improve it. If a day was never entered, the archive shows the gap rather than papering over it; that honesty is the point of keeping the record daily, and every auto-filled value in it remained overridable by the professional who owned it.

Common questions

Questions, answered straight.

What is end of well report software?

End of well report software produces the formal close-out package for a completed well — the as-built record of what was drilled, how it performed, and what it cost. In NWE WellReport, the package generates from the well record at total depth in six sections: as-built surveys, plan-vs-actual summary, BHA and run history, the daily archive, failure reports, and the field ticket rollup.

What is in the end-of-well package?

Six sections, all sourced from the record: the as-built surveys from the accepted ledger; the plan-vs-actual summary against the stage-based plan; the complete BHA and run history with each run's BHA Report and Motor Report; the daily report archive as issued day by day; the failure reports recorded during the well; and the field ticket rollup with NPT treatment as recorded.

Where does the package's data come from?

From the same record the well kept daily — the accepted survey ledger, the run records closed at each lay-down, the daily reports, the field tickets, and the failure reports. Nothing is re-entered or re-derived at total depth, which is why every figure in the package can be traced back to the day it was recorded.

Does it include failures and field tickets?

Yes — deliberately. Failure reports, with their photographs and accounts, roll into the close-out, and the field ticket rollup carries the job's tickets with each ticket's NPT inclusion or exclusion as the directional driller recorded it. The commercial and operational stories close in the same document, saying the same things.

Is the package rebuilt at total depth, or generated?

Generated. The daily archive means the well's reporting was completed as it went; the end-of-well package assembles those issued records plus the as-builts, history, failures, and tickets into the formal six-section report. The professional's job at TD is review, not archaeology.

One platform

Close-out is one module of the entire well.

The package is the last thing the record produces — and the proof of everything it kept. Explore the family:

The hub

Oil and Gas Software

The entire well in one application — every module below, one survey record underneath all of it.

See the platform Reporting

BHA Reporting Software

The per-run records and reports the package's history section is built from.

See the guide Costs

Drilling Cost Tracking

The daily costs and tickets behind the package's commercial rollup.

See the guide Data

Drilling Data Management

The Master Well File — where the finished package and its record live on.

See the guide Reporting

Daily Drilling Report Software

The daily reports that form the package's archive, generated from run data.

See the guide

Founding pilots now open

Put it on real wells.

Bring your current workflow, your survey exports, and your field team. We verify the math against your current software before your team relies on it in the field, train your DDs, review what works, and make anything that does not work right.

$5,000First year · up to 5 wellsTalk to us about a pilot Explore the live platform