Skip to main content
Projects using protocols with storage modules may require regular submission of monitoring reports to comply with module requirements. Certify supports creation of monitoring submissions through either the UI or API. Monitoring requirements are defined by the storage modules included in your protocol. Monitoring submissions are currently configured for projects using the following storage modules:

​
Storage sites

Monitoring submissions are added for specific storage sites, which must be created prior to submitting monitoring data. If using a supported storage module for your project, you can create, edit and delete storage sites directly in Certify from the Storage sites page. To add a site, use the + Add dialog providing the following information:
  • Site name
  • A unique reference ID
  • The latitude and longitude of the site
  • (Optionally) a description
You can also create, delete or update storage site data via the Certify API.

​
Monitoring requirements

Monitoring requirements are a list of criteria defined by your protocol and storage modules. These detail the monitoring data that needs to be submitted for ongoing project validity. Each requirement has the following attributes:
  • Monitoring phase (Operation, Pre-operation or Post-operation)
  • Parameter name
  • Frequency (e.g. Every day, Once, Monthly, Optional)
Monitoring requirements are generated automatically for each storage site when it is created, based on the storage modules in your project. Some requirements have a frequency that you set yourself for each site or permit; where this applies, use the Set frequency action on the requirement to specify it.

​
Monitoring submissions

Once monitoring requirements are defined on your project, you can add data submissions to meet your project requirements. To add a submission in Certify, click the action link on the monitoring requirement and then the + Add submission button. The submission dialog will allow you to upload a data source file, set the validity period of the submission and add any guidance notes for the verifier to pay attention to, for example a specific page number within a multi-page report.
Ensure to set the date range of the validity period to the full extent of the dates that the monitoring submission is valid for. This will ensure that the data is linked to any GHG statements within that period.
Monitoring submissions can also be automatically created via the Certify API.

​
Including monitoring submissions in your GHG statement

Monitoring submissions will be automatically included in the data package for a GHG statement if the validity period of the submission falls within the reporting period of the GHG statement. This means that the submission of monitoring data can be independent from the preparation of removals and GHG statements. The view of your GHG statement in Certify includes a Monitoring tab. Each monitoring requirement in the tab will have one of the following statuses:
  • Valid: monitoring submissions have been uploaded covering the full reporting period
  • Partial: monitoring submissions have been uploaded covering part of the reporting period
  • Missing: no submissions have been uploaded within the reporting period