Reports and exports

Exports carry their provenance

An export is not a stripped-down copy of what is on screen. It carries the same context the interface shows:

• units on every column
• the observation or production-day basis the figures use
• quality state, so a flagged value stays flagged in the file
• for derived volumes, the inputs and sources they rested on

A number that leaves the platform should still be defensible after it lands in a spreadsheet, which means the spreadsheet has to receive more than the number.

Missing stays missing

An export preserves the distinction between zero and missing. A null does not become an empty cell that a spreadsheet will helpfully treat as zero when someone sums the column.

Scoping applies to exports

What a user can export is bounded by the same company grants that bound what they can see. There is no export path that reaches assets the interface would not show.

Deep links

Report and data views have URLs that survive a refresh and can be sent to someone else. Scope, filters and date range are carried in the URL, so “look at this” does not require a screenshot or a list of instructions.

The recipient still only sees what their own grants allow.

What this does not claim

The platform produces exports and reports. It does not claim that any particular state agency form, EPA report or regulatory obligation is thereby satisfied.

That distinction is deliberate. Producing a file containing the right numbers and discharging a specific regulatory obligation are different things, and only one of them is something software can promise. Whether an export meets a given filing requirement is a question for whoever is responsible for that filing.

Similarly, the measurement vocabulary used throughout — GOV, VCF, GSV, BS&W, NSV — describes what the platform calculates. It is not a claim of conformance to a named measurement standard. See volume correction.