Workspace / Pawston Cat Foods
Reports

Pawston Cat Foods Ltd

Everything here is generated from your inventory, so it always matches the dashboard. Your analyst prepares and signs off each report before release.

Your report

The generated outputs for this engagement.

Methodology report

The analyst-reviewed GHG inventory artefact. Analyst-signed, version-pinned, reproducible. Every figure carries a calculation trace back to the source record.

Analyst-signed·What this report covers
Data quality report

Pedigree score per record, tier breakdown, and coverage by source. Opens as a live view on the Footprint page, so it always matches the current data.

Reduction recommendations

Ranked actions with an estimated emissions saving, a cost band, and a recommended owner. Opens the Reduce page, where any action can be turned into a target.

Inventory export (Excel)

A working workbook of the inventory for offline review. Unsigned and provisional, not analyst-reviewed. Cover, summary, per-scope, per-category, per-supplier, monthly, and transaction sheets.

Auditor and assurance pack

Everything a third-party verifier needs.

Marquee artefact · auditor handoff

Audit pack

A ZIP for your auditor. It bundles the methodology data, the append-only audit log with its chain-check result, the cited emission factor versions, the full override history, boundary application, and a manifest carrying the SHA-256 of every file. The bundled script re-checks those hashes on any machine, so your auditor does not need a Hemera account.

Download audit pack ZIP
hemera-audit-pack-pawston-cat-foods-ltd.zip · 20.3 KB
~/Downloads $
$ python3 verify_pack.py hemera-audit-pack-pawston-cat-foods-ltd.zip
OK audit_log.json
OK audit_log_verification.json
OK boundary_application.json
OK verify_pack.py
Pack format version : 2
VERIFIED. 13 artifacts, all hashes match.
$ echo $?
0

The bundled verify_pack.py uses Python 3 stdlib only (no pip install) and needs no network. It re-computes the SHA-256 of every file, compares against manifest.json, and exits 0 when all hashes match. The audit log's hash chain is checked server-side when the pack is built; that result ships as audit_log_verification.json.

View manifest · 14 files in pack
Pack root
  • ├──audit_log.json78 KBAppend-only audit log export, 234 events
  • ├──audit_log_verification.json74 BHash-chain check result, computed server-side when the pack is built
  • ├──boundary_application.json343 BHow the boundary was applied: included vs excluded transaction counts and tCO₂e
  • ├──excluded_transactions.json2.0 KBEvery excluded transaction with its exclusion reason
  • ├──factor_versions_used.json441 BEmission factor versions cited by the inventory (DEFRA UK 2024 v1, version-pinned)
  • ├──materiality_quadrant.json726 BMateriality screening by category
  • ├──methodology_data.json1.3 KBWorkspace, sites, boundary decisions, and inventory totals behind the methodology report
  • ├──override_history.json871 BFull analyst override history with per-change impact
  • ├──principle_statuses.json730 BGHG Protocol principle statuses at build time
  • ├──verify_pack.py1.9 KBOffline verifier (Python 3 stdlib only, no pip install). Re-hashes every file against the manifest
  • ├──cbam/cbam_declaration_2025_q1.csv675 BLatest quarterly CBAM declaration as CSV
  • ├──cbam/cbam_declaration_2025_q1.json2.5 KBThe same CBAM declaration as JSON
  • ├──cbam/cbam_methodology.md586 BCBAM methodology notes for the declaration
  • └──manifest.json2.1 KBSHA-256 and byte size of every file, plus engine version pins
Send to auditor

Draft a prefilled email to your verification body. Download the audit pack ZIP above, attach it, and send.

Ready

Framework disclosures

Standards-specific views, shown when relevant.

CBAM declaration

Carbon Border Adjustment Mechanism rollup and quarterly declaration for CBAM-relevant goods. Your Hemera analyst prepares CBAM declarations for you; the preview shows the working screen they use.

Analyst-prepared
Open CBAM →
ESRS E1 climate disclosure

ESRS E1 is the climate chapter of the EU's CSRD reporting rules. If you are in scope, this is the disclosure you file, built from your inventory and narrative inputs.

Draft available
Open ESRS E1 →
Sign-off
Every published artefact is signed off by your lead analyst before release. In your workspace this section shows who signed the current version.

Every published artefact is immutable once signed off. Corrections create a new version that supersedes the old. The audit pack carries the working data behind the report and a script that re-checks the pack's file hashes offline.

H
Your Hemera analyst
Message us