A monitoring plan is the part of the project design document that describes which parameters are measured, with which instruments and how often, who is responsible for the data and how its quality is controlled. Monitoring reports are prepared according to this plan, and it is against this plan that the verifier checks the project's actual data.
Why a monitoring plan is needed
Without a plan approved in advance, the verifier has nothing to compare the collected data against. The plan makes the reduction calculation reproducible: anyone reviewing it, using the same input data and formulas, should arrive at the same result. This requirement underpins MRV (see What is MRV) and ISO 14064-2:2019.
Structure of the plan
- List of parameters. For each one: symbol, unit of measure, source (meter, document, reference source), frequency of measurement and recording, and the calculation method if the parameter is not measured directly.
- Fixed parameters. Values determined at validation that do not change during monitoring — for example, emission factors from the chosen source.
- Metering equipment. Type, accuracy class, installation location, and the calibration procedure and interval.
- Roles and responsibilities. Who takes the readings, who checks them and who approves the report.
- Quality control (QA/QC). Reconciling meter readings with supplier invoices, checking for gaps and outliers, and the procedure for filling in missing data.
- Data storage. Where records and primary documents are stored and for how long.
Sample parameter table
For a project replacing a gas-fired boiler house with a heat pump:
| Parameter | Unit | Source | Frequency |
|---|---|---|---|
| Heat pump electricity consumption | kWh | Dedicated meter | Monthly |
| Residual gas consumption | m³ | Commercial metering point | Monthly |
| Heat output | kWh | Heat meter | Monthly |
| Degree-days | °C·day | Weather data | Monthly |
| Grid emission factor | kg CO₂e/kWh | Reference source, fixed at validation | Per period |
Strictly speaking, the heat meter is not needed to calculate emissions, but it lets you check plausibility: if the heat pump's coefficient of performance (COP) for a month falls far outside the typical range, that signals a meter fault.
How to handle data gaps
Gaps are inevitable: a meter breaks down, readings are not taken. The plan must define a conservative approach in advance: missing data are filled in such a way that the reduction is not overstated. For example, if the heat pump's electricity meter was not working, the maximum observed consumption is used for the missing period, not the average. It is important to describe this before monitoring starts rather than invent a rule after the fact.
Common mistakes
- The project meter is not separated from the facility's overall metering, so the effect cannot be isolated.
- There are no calibration records for the meters.
- Readings are copied by hand without primary documents (see Data quality).
- Emission factors change from report to report without any basis in the plan.
- The actual measurement frequency is lower than the plan specifies.
How it works in the platform
- The MRV contour is still in development and is marked “Soon” in the platform: monitoring plans, climate projects and monitoring reports are not yet handled in it.
- Many of the plan's requirements can already be put into practice on facility data in the GHG contour. In Data entry, electricity, heat and gas are entered month by month — purchased energy either from an invoice or certificate of completion or from meter readings — and invoices, certificates of completion and photos of meter readings are attached to the records. The collection procedure is described in the article on collecting energy and fuel data.
- The platform shows a month with no data as incomplete: you either enter the consumption or mark the month “No consumption.” Before a facility's year is closed, the platform checks that the data are complete.
- The year's “Change history” shows who changed what and when, and a closed year is read-only.
Frequently asked questions
Can the monitoring plan be changed after the project is registered?
Yes, but following the procedure set by the program: changes are described, justified and usually reviewed by the verifier. Deviating from the plan without documenting it is a common cause of findings.
Is a separate meter on the project equipment mandatory?
That depends on the methodology. In practice, separate metering makes verification much easier and reduces uncertainty.
How often should a monitoring report be prepared?
The project owner chooses the monitoring period within the program rules. Data are still collected at the frequency specified in the plan — usually monthly or more often.