Partner
Field edition · September 2026

The field-data playbook for carbon projects

Five stages, four evidence rules and one review loop. How to collect farmer data that still stands when a verifier opens it.

Download the playbook I have an access code

A carbon credit from a smallholder project is a long chain of claims. At the far end of that chain is a surveyor standing on a farm with a tablet. If what they record is incomplete, unverifiable or impossible to connect to the same farmer six months later, nothing further up the chain can fix it. This playbook is about that first link.

Who this is for. Project developers, field coordinators, cooperative and NGO staff who run surveyors, and the people who build tools for them. It is a guide to the craft of field data collection. It does not replace your methodology, your registry's rules or your verifier's requirements. Those come first, and where they are stricter than anything here, follow them.
Step 2 of 2 · Registered readers only

Enter your partner access code

The eight parts of this playbook, and the PDF download, are for registered Carbon Field partners, sponsors and reviewers. Your code unlocks them here in your browser. Nothing you type is sent to us. No code yet? Register first.

Step 1 of 2 · Register

Register to download the playbook

Downloads are for registered partners, sponsors and reviewers. Fill this in and your mail app opens with a pre-written registration email. Send it, and we reply with your personal access code. Step 2 is entering that code above to unlock and download.

Nothing is sent from this page. The email opens in your own mail app, addressed to info@qsoftwares.org, so you can read it before you send it.

About this playbook

This playbook comes out of building Carbon Field, an offline-first mobile app and sync backend for carbon project field data, developed by QSOFTWARES Ltd. The app is still in development, and we are looking for engineering, infrastructure and field partners, for sponsors of specific build milestones, and for blunt feedback.

Help us finish it

Disagree with something here? We would like to hear it: info@qsoftwares.org.