> ## Documentation Index
> Fetch the complete documentation index at: https://docs.isometric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Storage monitoring [beta]

> Create monitoring submissions for projects using storage modules to comply with regular reporting requirements through UI or API

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.

<Note>
  **Storage monitoring submissions via Certify are currently in beta.**

  This feature is currently supported for the following protocols:

  * [Biomass Geological
    Storage](https://registry.isometric.com/protocol/biomass-geological-storage/1.1) projects
  * [Bio-oil Geological
    Storage](https://registry.isometric.com/protocol/bio-oil-geological-storage/1.1) projects

  To enable this feature, please contact support. Some subsequent setup steps also currently require
  configuration by the Isometric team or use of the API.
</Note>

## Storage locations

Monitoring submissions are made for specific storage locations, which must be set up prior to
submitting monitoring data.

To set up a storage location, send the following details to your account team:

* Storage location name
* Project using the location
* Latitude and longitude of the site
* (Optional) Internal ID used for the location

You can also create, delete or update storage location data via the [Certify
API](/api-reference/certify/post-storage-location).

## 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 must be configured by Isometric's team for your project. Once you have
created your storage locations, contact us to apply the requirements for your project.

## 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 <Icon icon="arrow-right" /> 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.

<Tip>
  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.
</Tip>

Monitoring submissions can also be automatically [created via the Certify
API](/api-reference/certify/post-monitoring-submission).

## Including monitoring submissions in your GHG statement

Monitoring submissions will be automatically included in the data package for a [GHG
statement](/user-guides/certify/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