Lease operators and pumpers
Run the daily route, gauge tanks, read meters and record seal changes, usually on a rugged tablet or phone with patchy coverage.
Energy / Field Operations App
Oil and gas industry app for lease operator rounds and run tickets
Gauge sheets on clipboards and readings typed in at the end of the week leave production accounting guessing. Agnotic Technologies builds the offline field app your lease operators use on every round, and the measurement records behind it, so tank gauges, run tickets and seal changes reach allocation complete and on time.
Offline
Works with no signal
Run tickets
Complete before they close
Cut-off
Readings in before allocation
Trusted by global innovators
Industry Overview
What is an oil and gas field operations app?
An oil and gas field operations app is the mobile tool lease operators use on daily rounds to record tank gauges, meter readings, run tickets and seal changes, often with no signal. Agnotic Technologies builds it with offline capture, checks on the device and a full edit history, so readings reach production accounting before the allocation cut-off.
Who uses it
Who touches a field reading?
One gauge reading passes through several hands before it becomes a reported volume. The app gives each role the screen and permissions it needs.
Field foremen
Assign routes, see which stops were missed and approve corrections before they leave the field.
Production accountants
Need complete, on-time volumes and tickets for daily allocation and month-end reporting, with a record of every change.
Purchasers and haulers
Take the load and sign the run ticket, so their copy and the operator's copy must carry the same numbers.
Measurement and regulatory staff
Answer audits on federal, Indian, state and fee leases from the same records the field created.
Industry Challenges
Where do field readings go wrong?
This failure-point list is what we check first when we review an operator's current rounds. Each item is a data problem the app has to prevent, not a training issue.
Duplicate readings after offline sync: a round is saved twice on a device that lost signal, or two operators gauge the same tank, and both records post.
A tank gauge entered against the wrong tank or the wrong calibration chart, so the observed volume is calculated from another tank's strapping table.
A run ticket closed without the numbers of the seals removed and installed, or without S&W and observed gravity, which leaves the sale unsupported.
Readings that arrive after the daily or month-end allocation cut-off, so production is allocated on estimates and corrected a month later.
Edits made in the office with no record of the original value, who changed it or why.
Gauges taken before the tank has settled, or with temperatures missing, so the volume cannot be corrected to standard conditions.
Our Approach
How should an operator design field data capture?
Three design choices decide whether the app helps accounting or just moves the clipboard onto a screen.
Check at the tank, not in the office
Required fields, tank and chart selection and range checks run on the device, so a missing seal number is fixed while the operator is still on the pad.
Make every reading unique before it syncs
Each reading carries an ID created on the device, plus the round and the tank, so a second sync of the same record updates it instead of creating a duplicate.
Work to the accounting calendar
The app shows which readings are due before the daily and month-end cut-offs and flags late ones, so allocation runs on measured volumes.
Capabilities
What do we build into an oil and gas field app?
Modules for lease operators and the production accounting team behind them. Sensor telemetry and HSE inspections are separate builds; this app is for manual measurement.
Route and round planner
Each operator's wells, tanks and meters in stop order, with what is due today and what was missed yesterday.
Tank gauging screens
Opening and closing gauges, temperatures and samples, with observed volume calculated from each tank's own calibration chart.
Run ticket capture
Uniquely numbered tickets with S&W, gravity, seal numbers and signatures, closed only when every required field is present.
Seal log
Every seal installed or removed, the valve or meter it sits on, the position it was sealed in and the reason it came off.
Well and meter readings
Pressures, meter totals, chemical levels and downtime reasons, entered once per stop.
Offline sync with conflict rules
Records queue on the device and sync on reconnect; two readings for the same tank and time go to the foreman instead of both posting.
Edit history
Office corrections keep the original value, the new value, who changed it and why.
Allocation export
Validated daily volumes and tickets sent to your production accounting system on its schedule.
Engineering Stack
Which systems and rules sit behind the app?
The measurement rules, devices and back-office systems the build has to fit.
Measurement rules
43 CFR 3174 oil measurement43 CFR 3173 seal and inventory recordsAPI MPMS Chapter 18 tank gaugingState production reporting forms
Mobile
iOS and Android rugged devicesOffline-first local databaseBarcode or QR scanning of tanks and sealsPhoto evidence for gauges and seals
Back office
Production accounting systemHydrocarbon allocationERP and purchaser statementsSCADA on automated wells
Platform
Role-based access by lease and routeSync service with idempotent writesAudit log of every create and editAWS, Microsoft Azure or Google Cloud
Run ticket
What does a complete tank gauging run ticket hold?
On federal and Indian leases, BLM lists the fields a tank gauging measurement ticket must carry. We build each one into the app with a check that runs on the device before the ticket can close.
| Ticket field | Why it matters | Check the app applies |
|---|---|---|
| Unique ticket number, opening and closing dates and times | Makes each ticket traceable and orders the readings | Number issued per device, so offline tickets never collide |
| Lease, unit PA or CA number | Ties the volume to the right royalty and allocation point | Picked from the operator's assigned leases, never typed |
| Unique tank number and nominal capacity | Selects the tank's own calibration chart | Tank chosen from the facility list or scanned; chart version shown |
| Opening and closing gauges and temperatures | The volume removed comes from the difference, corrected for temperature | Closing gauge must be below opening; both temperatures required |
| Observed volume from the calibration chart | A wrong chart gives a wrong volume | Calculated by the app from the selected tank's chart, not entered by hand |
| Observed API gravity and temperature, and gravity at 60 °F | Needed to correct the volume and price the sale | Range check against the lease's recent tickets |
| S&W content percent | Separates merchantable oil from sediment and water | Required; values outside the lease's usual range ask for confirmation |
| Number of each seal removed and installed | Shows the tank valves were controlled before and after the load | Each seal scanned or entered; a removed seal must match one on record |
| Names of the gauger and the operator | Records who measured and for whom | Taken from the signed-in user and the lease record |
Measured Impact
What should field data capture measure?
Measures we report to the foreman and the production accountant, not to the operator's manager alone.
Round completion
Stops visited on schedule
Wells and tanks visited as planned, and the ones missed.
Ticket completeness
Tickets closed with every field
Run tickets that needed no follow-up from accounting.
Cut-off hits
Readings in before allocation
Readings received before the daily and month-end cut-offs.
Edit rate
Office corrections per route
How often field values are changed later, and why.
Use Cases
Where do operators start?
First releases scoped to one route or field.
01
Tank gauging and run tickets
Gauges, samples and tickets on the device, with checks before close.
02
Seal log
Seal installs and removals recorded against each valve and meter.
03
Daily well readings
Pressures, meter totals and downtime reasons per stop.
04
Month-end inventory
End-of-month gauges scheduled and captured inside the allowed window.
05
Hauler hand-off
Matching the operator's and the purchaser's copies of each ticket.
06
Downtime and deferment reasons
Structured reasons for wells that did not produce.
Integrations
Which systems does the field app send data to?
Where validated field data goes after sync.
Volumes and tickets
Production accounting system
Daily allocation
Allocation engine
Revenue and purchasers
ERP
Automated wells
SCADA
Ticket matching
Purchaser and hauler systems
Lease and facility data
Lease and land records
Photos and signed tickets
Document storage
Compliance-First Development Services Backed by Global Standards
We build secure, scalable products designed for privacy, interoperability, and regulatory readiness from day one across every sector we serve.
Information Security Management
Adhering to the international gold standard for managing information security risks.
Quality Management Systems
Ensuring consistent quality in software delivery and operational process optimization.
Our Edge
Why Global Leaders Choose Us
We combine deep technical expertise with industry-specific knowledge to deliver solutions that aren't just functional, but transformational.
Enterprise-Grade Security
We implement rigorous security protocols and compliance standards (HIPAA, GDPR, SOC2) across all industrial solutions to protect sensitive data.
High-Performance Scaling
Our architectures are built to handle massive data loads and user bases, keeping performance steady whether you're serving ten or ten million.
Accelerated Time-to-Market
Using our suite of internal tools and proven frameworks, we cut setup work so your first release reaches users sooner.
Embedded AI Integration
Beyond simple wrappers, we build deep-learning integrations and predictive analytics directly into the core of your industry-specific workflows.
Engagement Model
How does a field app engagement run?
Oil and gas industry app solution services from Agnotic follow the same path. It depends on scope; we agree a fixed first release on the scoping call.
01
Form and route review
We go through current gauge sheets, run tickets and seal logs, and the cut-offs your accountants work to.
02
Offline design
Record IDs, conflict rules and the checks that must run with no signal are agreed before screens are drawn.
03
Fixed-scope first release
Tank gauging, run tickets and the seal log for one route or field, syncing to a staging copy of your accounting import.
04
Parallel run
Paper and app side by side, reconciled by your accountants before paper is retired.
05
Roll out and support
More routes, readings and interfaces, with rule changes under agreed change control.
Facts and sources
Measurement rules the app is built around
BLM rules for federal and Indian leases. State rules and your own procedures may add more.
After oil is measured by tank gauging on a federal or Indian lease, the operator, purchaser or transporter must complete a uniquely numbered measurement ticket, on paper or electronically, with the tank number, opening and closing gauges and temperatures, observed gravity, S&W content and the number of each seal removed and installed.
Source: 43 CFR 3174.12(a) (eCFR)BLM requires tank gauging at a facility measurement point to follow API MPMS Chapter 18.1 or 18.2, and the tank must be isolated for at least 30 minutes, with its isolating valves closed and sealed, before gauging starts.
Source: 43 CFR 3174.6(b) (eCFR)For each seal, the operator must keep a record of its unique number and the valve or meter component it is used on, the date it was installed or removed, the position the valve was sealed in and the reason the seal was removed.
Source: 43 CFR 3173.9(b) (eCFR)The operator's end-of-month inventory records the total observed volume in storage, measured to the nearest half inch, and a gauged inventory must be taken within 3 days either side of the last day of the calendar month.
Source: 43 CFR 3173.9(a) (eCFR)Records relevant to the quality, quantity and disposition of production from federal leases, including source records, must be kept for seven years after they are generated.
Source: 43 CFR 3170.7(a) and (c) (eCFR)
Voice of success
We don't just build products; we forge lasting partnerships. See how we've helped industry leaders transform their vision into technical reality.
“I can clearly see how Agnotic has a unique way of handling end-to-end development. They are always active on quick chat and provide support quickly.”
Aaron Phelan
Founder, Benchmark
“Agnotic combines deep technical expertise with strong domain knowledge. They understand the business context, anticipate challenges, and make collaboration smooth and effective.”
John Pasmore
Founder, Latimer
“Agnotic is the best technical team we evaluated. Their engineering excellence made our work dramatically easier and allowed us to stay focused on what matters most for maternal care outcomes. They took full ownership of the technical execution, and we are always happy to continue working together.”
Kim Smith
Founder, My Lauren
Related pages
Related oil and gas software
This page covers manual field measurement. These pages cover telemetry, safety and the wider operation.
Energy software development
The energy industry hub: grid, asset and energy data software Agnotic builds for utilities and renewable operators.
Oil and gas asset monitoring
Sensor telemetry, historian integration and equipment health for upstream and midstream assets.
Production optimization software
Analytics on SCADA rates and well tests to reduce deferred production.
Rig safety inspection app
Offline HSE checklists, permits and hazard reporting for rig crews.
Oil and gas HSE compliance software
Incident, audit and compliance workflows for oil and gas safety programs.
Oil and gas AI agent development
AI agents for asset and field teams, built on the data your operation already holds.
Field service management software
Scheduling, dispatch and work orders for field crews and contractors.
More in Energy
More Energy Solutions
Explore other production-grade engineering platforms we deliver across energy.
Frequently Asked Questions
Yes. Rounds, gauges, tickets and seal changes are saved on the device and synced when a connection returns. Each record carries its own ID, so a sync that runs twice updates the record instead of creating a duplicate reading.
A rig inspection app records HSE checklists, hazards and corrective actions. This app records measurement: tank gauges, run tickets, seals and well readings that become reported production. They can share sign-in and offline sync, but not data models.
Yes. We load each tank's calibration chart, keep its version history and calculate observed volume from the gauge the operator enters. The operator picks the tank, never the chart, which removes a common source of wrong volumes.
No. The app captures and checks field data, then sends validated readings and tickets to your production accounting or allocation system in the format and on the schedule it expects.
No. BLM's measurement rules shape the run ticket and seal log for federal and Indian leases, and we add the fields your state forms and your own procedures need for state and fee leases.
The number of routes and facility types, the readings and tickets in scope, offline and device needs, and the accounting, ERP and SCADA interfaces. We explain these drivers on the scoping call instead of quoting a fixed price.
It depends on scope; we agree a fixed first release on the scoping call. Most operators start with tank gauging, run tickets and the seal log for one route, run beside paper until accounting is satisfied.
Yes. Smaller operators and new entrants often start with one field's gauging and run tickets and an export to their accountant, then add well readings and allocation feeds as they grow.
Industries