Skip to main content
Book a call
Practice 03 — Reporting

Investor-ready. Audit-ready.
Both, by design.

Sustainability reports, GHG inventories, ESIAs — and the underlying data architecture that makes them defensible. Aligned to GRI, IFRS S1/S2, ESRS, and BRSR. Built so your assurance provider doesn't have to refactor everything before signing.

01 Reports we produce

Three reporting services

Each engagement designed so the assurance provider on the other side doesn't have to refactor the data architecture before signing.

  • 01

    Sustainability reports

    Full-cycle delivery — materiality refresh, data collection design, narrative development, stakeholder review, design coordination — for GRI, IFRS S1/S2, ESRS, BRSR, or hybrid structures.

  • 02

    GHG inventory (Scopes 1, 2, 3)

    Boundary-setting, source mapping, calculation engine build (with audit trail), Scope 3 screening, base-year alignment, recalculation methodology — all under GHG Protocol & ISO 14064-1.

  • 03

    ESIA & scoping

    Environmental and social impact assessment for capital projects, infrastructure, and industrial expansion — IFC PS, EBRD PR, World Bank ESF aligned.

02 Why most reports fail assurance

Six structural problems we fix early

  • 01

    Boundary creep

    Reporting boundary doesn't match the consolidation boundary in financial statements. Causes immediate qualified opinion.

  • 02

    No calculation reproducibility

    Numbers in the report can't be recreated from source data without going back to the original analyst.

  • 03

    Mixed methodologies in the same KPI

    Year-on-year comparisons that don't actually compare like-for-like. Quietly fatal.

  • 04

    Estimated data without disclosure

    Estimation flagged by assurance review, treated as misstatement when not transparently disclosed.

  • 05

    Source documents that can't be retrieved

    Email-based data submission from operating units with no central repository.

  • 06

    Materiality drift

    Reported topics don't match the materiality assessment that underlies them.

03 How we structure reporting cycles

Reporting is a 12-month cycle, not a four-month sprint. We design the data architecture, the working-paper structure, and the assurance-readiness check at the start of the year — so the four-month sprint becomes a controlled production phase, not a fire-fight.

Engage on this practice

Thirty minutes. We figure out if there's a fit.

We don't pitch on the call. We listen, ask sharp questions, and tell you honestly whether reporting is what you need — or what else might be.

Book a discovery call