Scheme (Framework)
The methodology-neutral rulebook: 12 scheme + 5 governance + 3 VVB + 3 annexes. Defines the floor; pathways operate above it.
Provider Pathways
Each provider's pathway annex documents its declared choices on the variation surface (A–E thresholds, benchmark, database, engine, gap-filling, QA method). Currently one applicant pathway (Eaternity EOS), preparing for the initial validation engagement.
Feedback & Complaints
Submit feedback or file a formal complaint about an environmental assessment issued under the EmpCo scheme.
Scheme Design Research
Which conformity-assessment standards were adopted or set aside and why, how the European conformity-assessment-body landscape was mapped, and how a validation/verification body (VVB) can assess its own fit.
EmpCo Specification
The authoritative version is maintained in the public repository. The compiled PDF includes all 25 normative documents.
Framework PDF is the strict, methodology-neutral scheme. Framework + Pathway is the same framework with the Eaternity EOS applicant pathway annex appended — the actual submission document for the validation engagement (provider content, not normative framework). Both reflect the same underlying scheme version. The normative floor (§1.4.1) is published for ESFC EmpCo Working Group review; changes follow GOV-02 stakeholder consultation.
The Technical Reference Card is a condensed reference of EmpCo scheme requirements — quick-lookup companion to the framework PDF. The Provider Onboarding Guide covers sector fit, simplification options, and the onboarding roadmap for providers preparing for certification. Both are informative companions; the framework PDF is authoritative.
Document Map
| ID | Document |
|---|---|
| Scheme (EmpCo-01 to EmpCo-12) | |
| EmpCo-01 | Scope |
| EmpCo-02 | Normative References |
| EmpCo-03 | Terms and Definitions |
| EmpCo-04 | Rating Criteria |
| EmpCo-05 | Methodology |
| EmpCo-06 | Data Requirements |
| EmpCo-07 | Assessment Process |
| EmpCo-08 | Label Usage |
| EmpCo-09 | Non-Compliance |
| EmpCo-10 | Complaints & Appeals |
| EmpCo-11 | Surveillance |
| EmpCo-12 | Change Management |
| Governance (GOV-01 to GOV-06) | |
| GOV-01 | Open Access Policy |
| GOV-02 | Stakeholder Consultation |
| GOV-03 | Impartiality Policy |
| GOV-04 | Governance Structure (incl. Certification Committee charter) |
| GOV-05 | Certification Committee Rules of Procedure |
| GOV-06 | Scientific Review Process (Layer 1/2) |
| Validation/Verification Body (VVB-01 to VVB-03) | |
| VVB-01 | VVB Requirements |
| VVB-02 | Engagement Team Competencies |
| VVB-03 | Engagement Methodology Companion |
| Technical Annexes | |
| Annex C | Data Quality |
| Annex D | Characterisation Factors (EF 3.1 / IPCC AR6) |
| Annex G | Trader Pass-Through Clauses |
| Annex F | Document History |
| Provider Pathways | |
| Template | Canonical PA-01..PA-08 structure for any pathway annex |
| eaternity-eos | Eaternity EOS pathway annex (applicant, v1.3.1-draft) · canonical source |
Annexes A (Rating Thresholds), B (Benchmark Data), and E (EOS Architecture) were moved to provider pathway annexes in v0.3.4-draft, since rating systems and calculation engines are provider-defined under the methodology-neutral framework. The previous content is preserved at git tag archive/v0.3.3-eaternity-monolithic.
Version History
| Version | Date | Type | |
|---|---|---|---|
| 0.5.9 | 2026-08-18 | Minor | View |
| 0.5.8 | 2026-08-18 | Minor | View |
| 0.5.7 | 2026-08-06 | Correction | View |
| 0.5.6 | 2026-08-05 | Correction | View |
| 0.5.5 | 2026-08-04 | Major | View |
| 0.5.4 | 2026-07-29 | Minor | View |
| 0.5.3 | 2026-07-29 | Minor | View |
| 0.5.2 | 2026-07-25 | Minor | View |
| 0.5.1 | 2026-07-25 | Minor | View |
| 0.5.0 | 2026-07-21 | Minor | View |
| 0.4.1 | 2026-07-14 | Minor | View |
| 0.4.0 | 2026-07-08 | Major | View |
| 0.3.8 | 2026-06-16 | Minor | View |
| 0.3.7 | 2026-05-01 | Minor | View |
| 0.3.6 | 2026-04-28 | Minor | View |
| 0.3.5 | 2026-04-28 | Minor (superseded) | View |
| 0.3.4 | 2026-04-27 | Major | View |
| 0.3.3 | 2026-04-21 | Major | View |
| 0.3.2 | 2026-03-27 | Minor | View |
| 0.3.1 | 2026-03-07 | Non-subst. | View |
| 0.3.0 | 2026-02-06 | Major | View |
| 0.2.0 | 2026-02-06 | Major | View |
| 0.1.0 | 2026-02-06 | Initial | View |
Key Changes
- 0.4.0: Validation/verification architecture: scheme rebuilt from ISO/IEC 17065 certification to ISO/IEC 17029 + ISO 14065 (ISO 14067 product scope) via the Regulation (EC) No 765/2008 accreditation mechanism; certification-body/ replaced by verification-body/ (VVB-01 to VVB-03); CB certificate replaced by a label licence issued by the scheme's Certification Committee plus validation/verification statements issued by the VVB; Certification Committee charter added to GOV-04
- 0.3.8: Working-group feedback round (topic 312): AR5-era input data admissible when re-characterised to EF 3.1 and flagged (§2.6.1 + new Annex D.6.0, reporting floor unchanged); §2.7 renamed "Data Sources" with Annex C cross-reference; standards positioning — §2.5.3 ISO/IEC 17011 accreditation chain and §2.5.4 EmpCo classified as an ISO/IEC 17067 Type 6 scheme (certification of the provider's assessment process/service with surveillance); §1.2.1 systemic-review / data-flow-check framing; reciprocal §12.5↔§11.4 coverage cross-references; future-scope labelling pass on non-climate indicators. No §1.4.1 floor item changed.
- 0.3.7: Trader binding architecture (Enhanced per-trader licence vs Standard provider-AGB pass-through; new Annex G + PA-10); CB-03 reframed as informative companion (CB defines its own evaluation procedure under ISO 17065 §7.4); public regression display required on each pathway's verification page; leanness pass on §6/§7/§8/§11.4 (~16% framework PDF reduction)
- 0.3.6: Floor consolidated: LCIA = EF 3.1, rating = A–E, functional unit = DFU — all uniformly mandatory in §1.4.1; claim type reframed as scope/roadmap; ≥ 300-item regression suite minimum in framework
- 0.3.5: Superseded. Transitional version with four-dimension recognised-options menu; rolled back in 0.3.6 because the LCIA and rating menus opened abuse paths (AR6 raw without EF 3.1 sub-indicators; "none" rating)
- 0.3.4: Methodology-neutral framework; provider pathway annexes; EF 3.1 / IPCC AR6 mandatory; evidence file structure (§6.5)
- 0.3.3: Scheme ownership transferred to ESFC; LCIA method updated to EF 3.1
- 0.3.2: Verbosity reduction; benchmark recalculated (3,728 g CO2eq/DFU)
- 0.3.0: Assurance levels replace Score/Gastro; change management (EmpCo-12); outcome-based QA
Provider Pathways
Each organisation operating a calculation system used to produce environmental assessments under EmpCo submits a provider pathway annex declaring its choices on the variation surface (A–E thresholds, benchmark, LCI database, calculation engine, gap-filling logic, QA delivery method). The framework defines a normative floor — EF 3.1 LCIA method, DFU functional unit, A–E rating system, cradle-to-grave, ISO 14044 cut-off, QA outcomes, change management — that is uniformly mandatory; provider pathways operate above it.
Governance note. The normative-floor items above (LCIA method, functional unit, rating system) are draft framework-level requirements proposed by ESFC and are subject to ESFC EmpCo Working Group consultation (6 May 2026 and beyond). Any change goes through GOV-02 stakeholder consultation.
Registered pathways
| Pathway | Provider | Status | Resources |
|---|---|---|---|
|
Eaternity EOS eaternity-eos · v1.3.1-draft |
Eaternity AG (Zurich, CH) Climate · DFU · A–E rating · EF 3.1 |
Applicant — in validation preparation | Overview · Annex PDF · EDB Changelog · Regression · Benchmark · Branch |
Feedback & Complaints
Any party with a legitimate interest may submit feedback or file a formal complaint. Acknowledgement within 5 business days, resolution within 30 calendar days.
| # | Action | Timeline |
|---|---|---|
| 1 | Acknowledgement of receipt | 5 business days |
| 2 | Initial assessment and classification | 10 business days |
| 3 | Investigation | 20 business days |
| 4 | Response with findings | 30 calendar days |
| 5 | Corrective actions (if needed) | Per EmpCo-09 |
| 6 | Final closure notification | 10 business days |
Compliance: compliance@esf-coalition.org
Stakeholder Engagement: stakeholder@esf-coalition.org
Post:
European Sustainable Food Coalition
Attn: Compliance
(address available on request via esf-coalition.org)
Certification Status
Public certification information per Section 11.
Are you a validation/verification body (VVB)? The scheme is anchored on ISO/IEC 17029 + ISO 14065 (with ISO 14067 product scope), via the accreditation mechanism of Regulation (EC) No 765/2008 — not ISO/IEC 17065. A 2026-07-08 register review confirmed 18 bodies with this scope in the nine registers checked (a lower bound) (16 DAkkS + 2 ACCREDIA (RINA, TÜV Italia; Certiquality a probable third)). For why this route was chosen over the alternatives, how the European conformity-assessment-body landscape was mapped, and a self-assessment of how your accreditation scope maps to EmpCo, see Scheme Design Research and the VVB RFP context. The RFP document bundle (RFP-2026-07 rev B, SHA-256 manifest) was finalised on 23 Jul 2026 around the consolidated ESFC Rulebook v0.3; the Rulebook itself is delivered to bidders by the scheme owner. Expressions of interest: stakeholder@esf-coalition.org.
Stakeholder Consultation
Major changes require a minimum 60-day public consultation. All outcomes are archived here.
Open Consultation
Major-change proposal (GOV-02 §5.2): the three method items of the §1.4.1 floor would become provider-declared choices behind hard guardrails (AR6-generation LCIA mandatory; on-label functional-unit disclosure + comparability classes, DFU as default and anchor; published thresholds/benchmark with an ambition floor for scheme-defined terms). ISO 14067 alignment stays on the floor. No floor item changes unless adopted; the first pathway's declarations are unaffected either way.
Read the proposal Submissions log (001: AR6 vintage hierarchy) Submit a commentConsultation Archive
empco-scheme-with-pathway.pdf). (6) The first provider's customer terms went live on 2026-07-14 implementing Annex G (register clause, acceptance by use). A new CI guard keeps the framework provider-neutral. No floor item (§1.4.1) and no computational constant changed.Consultation Requirements
| Change type | Consultation |
|---|---|
| Major | 60-day public comment + 6 month notice |
| Minor | Stakeholder notification |
| Non-subst. | Published in changelog |
Subscribe to Notifications
Register as stakeholderRegression Test Suite
Every certified provider pathway maintains a regression test suite. Each release is validated against the suite to ensure changes do not materially alter assessment outcomes. The framework defines materiality thresholds; the suite size and composition are provider-declared (PA-07 in the pathway annex).