Peatland Code Market and Investment Forum

Share

Fen meadow at How Hill

Fen meadow at How Hill. Credit Tom Barrett, Broads Authority.

Peatland Code Market and Investment Forum

Peatland Code logo

This forum serves as a platform for feedback, comments and information exchange relating to Peatland Code’s development. It aims to support continuous development whilst retaining distance from parties with a vested interest in directly steering decision-making in relation to the Peatland Code process.  Membership is open to project developers, end buyers, brokers and retail aggregators registered on the UK Land Carbon Registry and meetings are held quartley 

If you wish to become a member, please contact peatlandcode@iucn.org.uk

Peatland Code Project Developer Meetings

2025

Agenda

  1. Peatland Code general update
    1. Staffing update
    2. Project statistics
  2. Peatland Code development update
    1. Accreditations
    2. Additional projects
    3. Code development timeline
  3. Peatland Code Technical Advisory Board update
  4. Peatland Code Q&A session
    1. Carbon costs calculator
    2. Consultation process
    3. Verification survey – ‘Walk north’
    4. Peatland Code development timeline

Agreed actions:

  • Peatland Code team to share information on all the above items with project developers once able to do so.
  • Peatland Code team will publish all TAB and Quarterly Project Developer Q&A meetings on the new Peatland Code website - [Completed July 24]
  • Peatland Code team to improve Field Protocol guidance on practically mapping flat bare and hagg gully.
  • Peatland Code team to ensure that the agenda item raised by TAB Member on aligning the GHG inventory and mapping linear features and adding a 1-2 metre buffer will be raised at the next TAB.
  • Peatland Code team to liaise with Jack Brennand (carbon costs calculator developer) to address bugs and usability issues raised above. Peatland Code team to liaise with Jack Brenn and to produce further, clearer guidance and an explainer video [In progress].
  • Peatland Code team to internally discuss opportunities for further engagement with project developers.