March 2026 — ESG reporting readiness edition

ESG reporting season is upon us and, depending on your footprint, that might mean CSRD, SEC climate disclosures, or one of a dozen national equivalents. This issue is focused on the mechanics of getting ready without a spreadsheet holy-war.

• Plan editor — marketing copy fields (tagline, highlights, CTA) owner-editable, no redeploy needed.
• Public pricing API — /api/public/pricing-tiers with ISR hydration into marketing /pricing.
• Quotas + SLAs — per-plan audit retention, data-residency regions, SLA tier surfaced in plan limits.
• Interactive API explorer — curl-builder for list / create / transition / bulk-load endpoints.

The two regimes converge on the same three questions: what is your exposure, how are you governing it, and can you produce the underlying data on demand. QEHS is not a reporting engine by itself, but it is the transactional system of record for the operational data most reporting tools need to pull.

• Scope 1 — stationary + mobile combustion events captured via the Emissions module with source-level calibration factors.
• Scope 2 — utility bills ingested via the generic CSV / API importer, mapped to location.
• Water + waste — existing Water and Waste modules produce the audited totals plus variance-from-baseline.
• Governance — management-review minutes, audit trails, and incident-rate trends are already in-app and exportable.

Establishments with 20+ employees in an industry covered by §1904.41 must submit 300A data to OSHA via the ITA portal by March 2. If you’re running the OSHA Recordable template, the annual reminder cron has already fired (30-day + 7-day + 1-day).

• Double-check: establishment NAICS code is present on each site record.
• Double-check: average employees + total hours worked are populated — 300A cannot submit without them.
• Pro-tip: the 300 log export on /reports/osha-300 filters by NAICS so you can assemble per-establishment packets quickly.

The ESG Reporting handbook (72 pages) is live in /resources/ebooks. It walks through the data model, governance, third-party assurance prep, and a 90-day pilot plan. No login wall, just a name + work email.