Skip to main content
The project Control page lists pre-audits for the organization. Each entry shows the audited period separately from the date and time the run was requested, and the requesting user.

​
Run metadata

The authenticated application endpoints POST /v2/pre-audit/runs, GET /v2/pre-audit/runs, and GET /v2/pre-audit/runs/{run_id} return these fields on each run: Access requires organization membership and the pre_audit::run permission. These are application endpoints; this guide does not imply availability through the public API-key integration. When an existing or cached run is returned, its original requester and timestamps are preserved. A completed run means its checks finished; it does not mean the data has no findings. COMPLETED_WITH_ERRORS means some checks failed and the report may be incomplete.

​
Category comparisons

Each category card compares the audited period with the previous-year window using its own scale. Heights cannot be compared across categories. Years, emission values, and changes remain visible. Categories with records in either comparison window remain visible even when their emissions sum to zero. A zero in the current period is a prompt to review possible missing data, not proof that data is missing or emissions have improved. Categories without records in either window are not added automatically.