The monitoring plan explains how a project will collect, check, store and report the data needed to issue credits. It should connect directly to the PDD, methodology and real operating workflow. A beautifully written PDD is not enough if the monitoring plan cannot be executed by the people running the project.
Think of the monitoring plan as the bridge between project design and verification. The VVB is not only asking whether the project has impact. It is asking whether the evidence is complete, consistent and auditable.
What validators look for
- Clear responsibility: who collects each data point, who checks it and who signs it off.
- Frequency: when data is collected, uploaded, reviewed and backed up.
- Source evidence: surveys, meter readings, photos, GPS points, lab certificates, inventory records or sales logs.
- QA/QC: how errors, missing values and outliers are identified and corrected.
- Chain of custody: how field records connect to the final monitoring report.
Match the plan to project reality
Distributed projects such as cookstoves and safe water need different monitoring discipline from a single industrial facility. A cookstove project may need household sampling, usage monitoring, serial numbers and repair records. A biochar project may need feedstock logs, production temperature evidence, lab results and sales or application records. A forestry project may need plot data, remote sensing, survival checks and GPS evidence.
This is where many projects create their own delay. The PDD commits to a monitoring approach that sounds reasonable, but the field team cannot actually maintain it. By the time verification begins, the project is trying to reconstruct evidence that should have been captured live.
Write for the first verification
A good monitoring plan should be boring in the best way. It should make the first verification cycle feel like a controlled evidence review, not a rescue operation. Use simple templates, stable naming conventions, timestamped files and a clear folder structure. Treat every number in the monitoring report as something an auditor may trace back to source.
Useful kit and systems
For field-heavy projects, monitoring quality often depends on mundane equipment: GPS units, phones, cameras, data loggers, sample bags, labels, PPE and power banks. The Field Kit section is useful because weak equipment workflows become weak evidence workflows.
Use the full tool alongside the PDD guide and feasibility model so monitoring cost is not treated as an afterthought.
Open the full verification workflow →