Tank gauges & water cuts, transfers and injection — the engine computes oil/water production after each autosave. Any past day stays editable; every save keeps a revision.
The field ↔ office message board, kept with the month's records — instead of a daily phone call. Field notes on the left, office messages on the right. Enter posts, Shift+Enter for a new line; signed with the Operator name box above.
Pick a well, then fill its tests. Existing wells usually test once or twice a month (AER Directive 017); a new well tests daily for its first week — use + Add test on the well.
Daily proration: every well's theoretical (latest test rate × hours on, 24 h unless a downtime exception is recorded) vs the battery actual. Watching PF daily catches a bad test or a missed down-day the same day — not in a month-end hunt. D017 expects PF near 1.
By well (month to date)
By day
One row per ticket. Another load the same day → + Ticket, same day; first load of a new day → + Ticket, new date.
Injectors run every day — wells across the top, one row per day. + Add day appends the next date for all injectors at once.
Battery gas produced (treater + FWKO meters on Battery Reporting) has to go somewhere: fuel (treater burner — write the disk readings and the engine computes gas = factor × √(diff × (static + 101.325)), or type the volume directly), flare (HP stack) and the tank-top vent estimate burning on the LP flare line. Δ checks produced vs disposed daily (AER D060 / Petrinex FUEL·FLARE·VENT).
Informal log — what happened and a cost estimate, so the office has an expectation before invoices arrive. Exact numbers not required.
Submission readiness
Volumetric worksheet
Well-level prorated production, injection, gas fuel/flare/vent and facility inventories/dispositions — the numbers the monthly Petrinex submission needs. Verify the column mapping against your Petrinex batch template before uploading.