Standard Setting Procedure

1. Development Phase 

   1. The development or revision of a Standard document may be triggered by one or more of the following four (4) situations.
   1. Standard Development/Revision Proposition. Based on strategic objectives and/or the feedback collected from stakeholders such as Developers, VVBs, external experts and other ERS Entities, the Secretariat may submit a Standard Development/Revision Proposition to the TAB. The Proposition must thoroughly detail all the new rules, requirements, procedures or changes proposed for the Standard and its affiliated documents. The Secretariat may draft the Propositions in collaboration with other ERS Entities. 
   2. Standard Development/Revision Mandate. The TAB may also mandate the Secretariat to draft a Standard Development/Revision Proposition. This mandate must include the following guidelines:
   • The identification number of the Development/Revision;
   • The aim and rationale for the Development/Revision; 
   • The scope of the Development/Revision; 
   • A provisional timeline for the Development/Revision;
   • If applicable, the expected risks associated with the proposed Development/Revision;
   • The duration of the expected Public Comment Period, if different from the standard thirty (30) days. 
   3. Regular updates. All Standard’s documentation shall be reviewed at least every two (2) years or as requested by the TAB. The revisions can be specific to a document (such as Programme) or the entire Standard, as deemed appropriate by the TAB. 

2. Review Phase

   1. Review. The TAB must review and respond to Standard Development/Revision Propositions within thirty (30) consecutive days or any other pre-defined timeline. If the TAB fails to respond within this period, the proposition is considered rejected. Based on their review, the TAB may:
      1. Accept the Standard Development/Revision Proposition; 
      2. Request the Secretariat for further revisions. A Standard Development/Revision Proposition can be sent back to the Secretariat up to five (5) times, after which it will be deemed rejected;
      3. Reject the Standard Development/Revision Proposition.
   2. Justification. In every case, the TAB must provide a written justification for its decision. 
   3. Public Comment Period. 
      1. Depending on the subject of the Development/Revision, a Public Comment Period might be required to account for Stakeholders' comments and feedback. 
      2. This Public Comment Period is mandatory when the Standard Development/Revision Proposition:
   • Modifies existing Standard documents in a way that significantly alters its requirements, procedures or concepts;
   • Introduces a new Standard document, with contents not previously included in any Standard document.  
   4. Call for Public Comment. If necessary, the Secretariat must organise and launch a Public Comment Period for at least thirty (30) consecutive days, unless a different period is mandated by the TAB. 
      1. The Call for Public Comment will be published on the ERS website and social media. 
      2. The Secretariat must proactively reach out to identified key Stakeholders, including local Stakeholders where Projects are certified. 
      3. ERS must strive to include diverse views from ecologists, carbon market experts, and livelihood experts.
   5. Consultation Digest. The Secretariat assesses all comments, feedback and suggestions received during the consultation and summarises them in a Consultation Digest, which must include:
      1. A structured review of all suggestions, with the Secretariat’s response on whether or not these suggestions will be implemented;
      2. A justification for each comment or suggestion that is accepted or rejected.
   6. Timeline. The Secretariat must publish the Consultation Digest no more than 75 business days from the closing date of the Call for Public Comment on the ERS website and social media. If this timeline is exceeded, ERS must issue a public justification for the delay.

3. Approval Phase

   1. Final Standard Revision. If no Public Comment Period is required, the Secretariat will directly submit the Final Standard Revision to the TAB. If a Public Comment Period was required, the Secretariat must integrate its feedback into the Final Standard Revision and send it to the TAB along with the corresponding Consultation Digest. 
   2. Final Standard Revision. The TAB can:
      1. Accept the Final Standard Revision.
      2. Deem the Final Standard Revision incomplete and send it back to the Secretariat for further revisions. This can be done an unlimited number of times. If a Public Comment Period is required, the TAB can deem its feedback was not properly integrated. 
   3. Public disclosure. The Secretariat then publishes the final version of the Standard and/or its affiliated documents on ERS’ website.