Library · Guides
Reviewing
How the Petroleum Commission decides operator returns and works the review queue of rule findings and AI questions. Nothing in review changes a figure; accepting a return sets off the recompute that does.
Deciding a return
Submissions waiting for a decision are those that validated cleanly.
- 1
Open it from Today or Submissions
The page shows the file as filed and its SHA-256, every finding by month and field, flags on the facility and period, the history, and the processing stages. - 2
Read the warnings and the operator's notes
A warning alone is not a reason to return a submission. A large movement with a note that explains it is usually a real event. - 3
Accept, or return for revision
Start from a note template and adapt it to the case. A return needs a note the operator can act on. Accepting promotes the rows to the inventory — superseding, never overwriting — and sets off the recompute, the AI screening and the alert rules, each as its own job.
The review queue
Rule findings and AI questions, ordered by priority, with the basis of the ordering stated.
- 1
Filter to what is yours
By status, by who raised it, by facility, by severity. - 2
Read the explanation and the series
An AI question carries the signals that raised it — the robust z-score, whether the isolation forest corroborates — and the series around the month. - 3
Decide with a note of at least ten characters
Accept as an issue, mark explained, dismiss, or mark under investigation. The note and the state before and after go to the audit trail.
- J / K
- Next / previous item
- N
- Write a note
- A
- Accept as an issue
- E
- Mark explained
- X
- Dismiss
An AI question is not a finding. A shutdown, a compressor trip, a well coming on and a mis-keyed column look alike to a detector. Explained is often the right answer, and it is what keeps the reviewer agreement figures honest.