botminds.aiRequest a demo
WorkflowEnvironment, Emissions & Regulatory

Flaring and Venting Compliance

Flaring and venting reporting that finds the flare log nobody wrote, from the meter itself, and leaves each cause, notice and filing to a named person.

See the demoBook a demo
Follow one missed flare log from 05:10 to 10:00 ↓
The problem

Flaring and venting reporting starts from a log written hours late

The operator deals with the alarm first and writes the flare log later, usually at handover, if another call does not pull him away. The meter has recorded every minute of it. Nobody puts the two side by side until the monthly filing, so a missing entry surfaces weeks later with its cause half remembered.

Meanwhile the limit gets worked out by hand, if at all. On the logs alone a month can look comfortably under, while the meter says the flare will pass its monthly volume before the weekend. Neighbors call the community desk at night, and nobody has tied the call to an event.

Built forField operatorsField supervisorsRegulatory filing analystsCommunity liaisons

The Problem Today

Flare logs are written by hand, hours later, and nobody checks them against the meter until a filing is due.

393 h
a year spent rebuilding event logs, at 20 minutes an event our estimate
91.1%
of methane destroyed by flares in one study, against 98% assumed published

Matched up by hand today

  • Meter data
  • Shift notes
  • Calls
  • Filings
  • A limit crossed unseenThe logs look safe while the meter says otherwise
  • Neighbors call firstA call in the night, and hours before anyone answers

The Solution

  1. Spot the missing logEach log is drawn over the meter; a spike with no bracket stands out
  2. Draft from the shift noteQuotes the note, sums the readings; with no note, the cause stays blank
  3. Forecast the limitMonth so far plus the rest at the routine rate, labeled a forecast
  4. People decideOperator submits, supervisor confirms, liaison signs the neighbor notice

Built-in controls

  • A sign-off counts only openings by the signer
  • Agents never write a log, send or file
  • Safety questions reach a named person and get no data

What You Get

Field teams see a crossing days ahead, neighbors hear from a person, and each filed line opens to its events.

  • Rulings that travelEach reaches the log, the limit track and the export
  • Filings tied to eventsA filed volume opens to the events behind it
  • Notice before the crossingTwo signatures, with the true times in front of both
One flare, one morning

A flare log nobody wrote, and a neighbor notice signed 60 hours ahead

A vapor recovery compressor on a pad tripped in the night when a cooler fan belt broke, and low-pressure flash gas went to the flare for three hours and forty minutes. The operator is holding over for well work. The flare log is not written yet.

demoThe field, its pads, the crew, the households and every reading here are sample data.

  1. 0105:10, opened 09:20

    Five brackets on the trace, one spike with none, and the month at 104%

    Field operator

    At 05:10 the agents found meter movement with no log entry and drafted one, unasked. Opening the trace at 09:20, the operator sees the spike flagged No log and the limit track landing at 104% of the monthly volume. Beside it, on the logs alone: 89.4%. The track is labeled a forecast, with the cause not yet confirmed.

  2. 0209:20

    The draft flare log quotes his own shift note, line by line

    Field operator

    The draft is tagged a draft, not a log yet. Its cause comes from his note: alarm at 01:10, cooler fan belt broke, gas to the flare through the pressure control valve as designed, pilot lit. New belt on at 04:50. At 05:30 he wrote that the flare log was not written yet. He can edit the cause before it goes on.

  3. 0309:20

    22 meter readings add up to 186.0 Mcf, with no estimate in it

    Field operator

    Opening the flare meter shows the ten-minute totals from 01:12 to 04:52. The sum is on the screen: 186.0 Mcf over 3 h 40 m, an average of 50.7 Mcf/h and a peak of 54.0. Where a meter exists the agents sum it. A second meter on the compressor discharge cross-checks the lost gas.

  4. 0409:30

    Submitted, and the operator gets no way to check his own entry

    Field operator

    He submits it to the field supervisor. The panel now reads that it waits for her, and that he cannot check his own entry. His next step moves on to the Pad 5 flare, where the agents found no note for the window and left the cause blank. Only he can say what happened there.

  5. 0509:30

    Opened one source of two, and the confirm button stays grey

    Field supervisor

    The supervisor's view counts what she has opened herself: the shift note, not yet the meter. Openings by anyone else do not count. Send back sits beside the locked confirm, and so does not flared gas, which needs a technician's meter check showing a fault. The check on this meter says it reads true, so that route is closed here.

  6. 0609:48

    Confirmed at 09:48, and the bracket goes onto the trace

    Field supervisor

    With the note and the meter both opened, she confirms the cause. The entry stops being a draft. Her ruling reaches the log, the limit track and each export, and the track changes its tag to cause confirmed. If new facts come in she can reopen it, giving her reason.

  7. 0709:48

    17 households on the notice list, 36 hours to sign

    Community liaison

    With the cause confirmed, the neighbor notice is ready for her. Four clocks run across the top from the same sum: now, due at 10:00 p.m. the next day, the forecast crossing a day later, and 36 h 12 m left to sign. She opens the list first: each parcel, and how each household asked to be told.

  8. 0809:54

    Her signature sends nothing until the supervisor signs second

    Community liaison, then the field supervisor

    Having opened the list and the log entry, she signs at 09:54. The notice now waits for a second signature. The letter says the site will pass its monthly volume, as a forecast and not a measurement, and keeps the 24-hour promise. Its facts come from the record. She can only add one agreed line, never free text.

  9. 0910:00

    Sent at 10:00, 60 hours before the forecast crossing

    Field supervisor

    She opens the letter and the log entry herself, then countersigns. Out goes the notice 60 h before the crossing and 36 h before it was due. The record states that nothing has been crossed. On the next screen sit the decisions this 104% has started, each with an owner and a clock.

How one pad flare gets to 104% of its monthly volume

The flare's month as the limit track adds it up. Only the last line is a forecast.

Routine flow so far, 620 hours at 1.0 Mcf/h620.0 Mcf
Five logged events383.0 Mcf
The spike with no log186.0 Mcf
So far95.1% of the 1,250 Mcf in the site approval1,189.0 Mcf
Rest of the month, 111 hours at the routine rate111.0 Mcf
Forecast for the month104.0%; on the logs alone, 1,117.7 Mcf or 89.4%1,300.0 Mcf

demoSample data, from the working solution.

Around the flare

Limits, the October log, unlit checks, sign-off, filings and a correction

Once the notice is out, the supervisor and the filing analyst turn to these. Pick any screen to read it full size.

Decisions the 104% startedThe sum, then five decisions with owners and clocks: the tank hatch safety report, the plan for 104%, the regulator notice, sulfur dioxide and a silent meter.
This month's log so far91 records across 42 sources, with tabs for no log, a field missing and complete. Search finds a work order or a cause.
Unlit flare checksWhen a pilot signal drops while gas flows, a person checks what covers the window. Gas nobody can account for counts as vented.
Month sign-offRows with a complaint, a typed value, a hatch or a meter gap are all read, plus a random draw with its seed on the trail.
What stops the October filingEach open spike, missing field, unsigned decision and silent meter is listed, and the filing preparer stops on any of them.
A correction after filingA wrong gas table read low by a factor of 1.095. Each affected volume is shown before and after, with the first version kept.

demoSample data, from the working solution.

Who rules on a flare event, and what each opens before ruling

One person makes each decision and another checks it, and only the checker's own openings count.

Field operator
Sees
His own spikes, the draft built from his note, and any blank cause the agents left
Signs
Submits the log entry; cannot check it
Field supervisor
Sees
The shift note and the meter, opened by her own hand
Signs
Confirms the cause, signs second on each notice, signs the month on a sample
Community liaison
Sees
The notice list and the confirmed log entry
Signs
Signs each neighbor notice first, and records calls
Regulatory filing analyst
Sees
What blocks the filing, each filed line's events and the site terms
Signs
Prepares filings and corrections; proposes term changes for the supervisor to sign
Internal auditor
Sees
Each step and ruling, and the evidence file
Signs
Nothing; reads and downloads
The agents

Meters and shift notes go to seven agents, and none writes a log

They find, draft, sum and forecast. Each stops where a person has to decide.

Meter watcher

Reads each flare and vent meter every night and on any alarm, and finds movement with no log.

  • Never writes a log
Log matcher

Draws each entry over its meter and checks seven fields.

  • Never fills a field; proposes with a source
Shift note reader

Reads shift notes, work orders, round sheets and rig reports for the window, and quotes them.

  • Never guesses a cause
  • No note means a blank field
Volume calculator

Sums meter readings, cross-checks a second meter and computes sulfur dioxide.

  • Never estimates when a meter exists
Limit forecaster

Adds the month so far to the rest at the routine rate, for each source.

  • Never reports a forecast as measured
Notice drafter

Drafts the neighbor notice from the confirmed log and the forecast, with true times.

  • Never sends
  • Never signs
Filing preparer

Builds each filing line from its events and stops on any open item.

  • Never files
  • Never changes a filed number

What stays with the field crew, the liaison and the analyst

These calls are made by named people, and the screen shows who made each one.

No cause without a personWith no note for the window, the cause stays blank and the operator is asked.
Real gas cannot be ruled awayNot flared gas needs a technician's meter check showing a fault, opened by both signers.
Neighbors hear from two peopleThe liaison signs first and the supervisor second, each after opening the letter's sources.
Safety comes before the logA spike with an open safety report cannot be confirmed, and safety questions reach the supervisor with no data.
A plan does not lower the forecastHolding the rest of the month under is a decision with an owner, and the notice stays owed.

What field and regulatory teams ask about flaring and venting reporting

What is flaring and venting reporting here?

Flaring and venting reporting is keeping each flare and vent event on record with its time, duration, volume, cause and complaints, then filing the month. This solution lays each flare log over the meter, drafts the entries nobody wrote, forecasts the monthly limit and builds filings that open to their events, with people making each ruling.

What sets this apart from flare management software that logs events?

A logging form holds what a person types. Here the meter comes first: each log entry is a bracket over its spike, so a spike with no bracket is a missing log. The draft quotes the shift note and sums the meter readings, and a person confirms the cause.

What happens when there is no shift note for a spike?

The agents leave the cause blank and say so. The operator is asked, and the entry cannot be submitted with filler or keyboard mash in its place. Whatever he types shows to the supervisor as typed words, never as a match.

Does flare event tracking cover vents and unlit flares?

Yes. Tank hatches and dehydrator stills are tracked as vent points beside the flares. When a pilot signal drops while gas flows, a person records what covers the window, and gas nobody can account for counts as vented.

How does the monthly limit forecast work?

It adds the month so far from the meter to the rest of the month at the routine rate, and labels the result a forecast everywhere. The notice clock starts from that forecast. A plan to stay under is a signed decision, and it does not lower the number.

Can it feed fuel, flare and vent reporting for the filing?

It prepares each filing line from its events and lists what stops the month, from an open spike to an unsigned decision. The analyst files through the customer's own channel. A filed number changes only through a correction with a reason and a second signature.

What do neighbors receive, and who decides it?

A letter drafted from the confirmed log and the forecast, with the times and the site's promise. The community liaison signs after opening the notice list and the log entry, and the field supervisor signs second after opening the letter. Only then does it go.

How does this support venting and flaring compliance audits?

Each ruling, opening and signature sits on the audit trail, and the evidence file carries the logs, rulings, limit track, notices, decisions, unlit checks, corrections and sign-off rows. A month's sign-off states which rows the signer opened and which she did not.

Environment, Emissions & Regulatory

More flare, emissions and environment solutions

All 7 solutions →
Permit Condition Compliance

Conditions read as written, with the proof tested against their own words.

1-min demoPetroleum License Compliance

Ask before the work: every consent, date and duty tied to its clause.

1-min demoStakeholder Commitments Register

Promises found, owned and proved, even after the person who made them leaves.

1-min demo

Bring one month of one flare
with its meter and its logs.

We’ll lay your own log over your own meter and show you which spikes have no entry.

Book a demoBrowse solutions