> For the complete documentation index, see [llms.txt](https://open-carbon-protocol.gitbook.io/ocp-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-carbon-protocol.gitbook.io/ocp-handbook/projects/third-party-validation-and-verification/dmrv-digital-monitoring-reporting-and-verification.md).

# dMRV: Digital Monitoring Reporting and Verification

* During the Project Proposal, the Project Developer schedules' monitor/issuance' dates throughout the project time frame (can be more frequent than annual) and specifies who is responsible for collecting monitored data: dMRV partner(s) or internal measurement. 
* On the 'monitor/issuance' date, data is requested from dMRV providers (ideally via API, but it can be manual) and inputted into the equation provided by the methodology.
* If dMRV has already been validated, data is internally duly assessed, and credits are automatically issued.
* If the data comes from the PD, we re-verify the data using the evidence they provide.
* Monitoring dates should include addressing material leakage risks. 

### Digital MRV (dMRV)

* We encourage all project developers to use digital monitoring & reporting techniques in their project design (where possible) to ensure the highest degree of data accuracy and transparency. 
* We're exploring how direct data streams from digital measurement sources (e.g. satellites or sensors) can be pre-verified during the project validation stage, and then credit issuance can be automated as true impact data is received via API.