Learn about PDR outcomes and how to action the results
Your Program Data Review (PDR) Report leverages Monitor's remote sensing insights to compare farmer-reported practices with satellite-based practice observations at the field level. Each row in the report represents one field enrolled in the program and includes:
-
Farmer-reported data including field information and tillage, cover crop & main crop practices
-
Monitor data including tillage, cover crop & main crop practices corresponding to farmer-reported practices
-
Evaluation status for each practice evaluated indicating agreement and conflicts between Monitor & farmer data
-
Overall risk score for the field, based on the combination of conflict statuses to enable prioritization of highest-risk fields
How to Read the Report
-
Columns: Each practice (post-harvest tillage, cover crop, pre-plant tillage, and commodity crop type) has a side-by-side comparison of farmer-reported and Monitor data.
-
Conflict Status: Shows whether the farmer’s report and Monitor agree, partially agree, or conflict.
-
Risk Score: Fields with more conflicts or more severe conflicts as it relates to soil carbon & GHG outcomes will have higher risk scores. Fields with higher risk scores should be prioritized for collecting additional proof of practice.
Conflict statuses
A conflict status is the result of the evaluation logic comparing Farmer and Monitor data for a given practice. Conflict statuses can show agreement which indicates a verified practice, or a conflict that may range in severity depending on the practice and the confidence in the Monitor data.
Cover crop conflict statuses
Evaluation status | Description | Outcome |
Practice verification not applicable (no cover crop intervention) | No cover crop intervention or practice was reported. Practice verification is not required for cover cropping on this field |
✅ Verified No further action needed. |
Verified cover crop practice | Farmer reports a cover crop practice and Monitor detects the presence of a cover crop. |
✅ Verified No further action needed. |
Verified cover crop practice (cover crop species observed) | Monitor's CropID commodity detection model detected a commodity crop that can also be grown as a cover crop (such as winter wheat, rye, barley, triticale, millet). This status is applied when Monitor detects a commodity that is the same crop the farmer reported planting as a cover crop. |
✅ Verified No further action needed. |
Conflict (no cover crop observed) | Farmer reported a cover crop, but Monitor did not detect one. |
‼️ Conflict Additional verification or proof-of-practice needed. |
Warning (potential cover crop observed) | Monitor detected vegetation signals consistent with a possible cover crop, but the strength of the crop emergence and persistence indicate a cover crop that failed to thrive, weeds, volunteers or commodity regrowth. |
⚠️ Potential conflict Additional proof-of-practice needed, or farmer context needed. |
Warning (perennial crop observed) | Monitor's CropID commodity detection model detected that a perennial crop was growing on the field, indicating the unlikeliness of a separate cover crop practice. |
⚠️ Potential conflict Additional proof-of-practice needed, or farmer context needed. |
[Low confidence] | Monitor may make an assessment of practice agreement, but when confidence in the Monitor practice is low, it will be indicated in the conflict status. |
🏳️ No reliable eval. Alternative verification method suggested. |
Insufficient satellite imagery (no Monitor cover crop determination) | Monitor could not determine cover crop status due to cloud cover, snow, or limited clear remote sensing data available to evaluate. |
🏳️ No data Alternative verification needed. |
Tillage conflict statuses
In Regrow's MRV, farmers report discrete tillage events (for example, a tillage pass on the field on X day, to a depth of Y cm). Monitor evaluates fields for the impact of tillage activity of a field at key times in the cultivation cycle (post-harvest and pre-planting). To align farmer tillage events to Monitor determinations, the most intense tillage event for the post-harvest or pre-plant period is selected for evaluation.
PDR logic evaluates tillage activity during these time periods even when a farmer does not report a tillage event. This is to ensure that tillage activity outside of farmer-reported practices is not missed.
Evaluation status | Description | Outcome |
Verified tillage practice | Farmer-reported tillage practice matched Monitor’s determination. |
✅ Verified No further action needed. |
Verified tillage practice (farmer reported tillage is more conservative) | Farmer reported a more conservative practice than Monitor observed (e.g., farmer said no-till, Monitor saw reduced till). The more conservative practice is accepted. |
✅ Verified No further action needed. |
Conflict (farmer reported no till, Monitor observed conventional till) | Farmer reported no-till or did not report a tillage event, but Monitor detected conventional tillage. This is the most severe tillage discrepancy. |
‼️ Conflict Additional verification or proof-of-practice needed. |
Conflict (farmer reported no till, Monitor observed reduced till) | Farmer reported no-till or did not report a tillage event, but Monitor detected reduced tillage. |
⚠️ Conflict Additional proof-of-practice needed, or farmer context needed. |
Conflict (farmer reported reduced till, Monitor observed conventional till) | Farmer reported reduced tillage, but Monitor detected conventional tillage. |
⚠️ Conflict Additional proof-of-practice needed, or farmer context needed. |
[Low confidence] | Monitor may make an assessment of practice agreement, but when confidence in the Monitor practice is low, it will be indicated in the conflict status. |
🏳️ No reliable eval. Alternative verification method suggested. |
Insufficient satellite imagery (no Monitor tillage determination) | Monitor could not determine tillage practice due to limited clear, cloud/snow free imagery. |
🏳️ No data Alternative verification needed. |
Commodity conflict statuses
Evaluation status | Description | Outcome |
Verified main crop | Farmer-reported crop matched Monitor’s crop determination. |
✅ Verified No further action needed. |
Low risk conflict (similar crop observed) | A different but agronomically similar crop was observed by Monitor. Crops are assigned this status when they disagree, but are within Monitor's known crop confusions and are crops with similar phenology and spectral signatures (ex: barley and winter wheat). |
✅ Verified No further action needed. |
Conflict (different crop observed) | Farmer-reported crop did not match Monitor’s observation of a distinctly different crop. |
‼️ Conflict Additional verification or proof-of-practice needed. |
Warning (fallow field observed) | Monitor detected no crop activity (fallow field), but a crop was reported. |
⚠️ Conflict Additional proof-of-practice needed, or farmer context needed. |
[Low confidence] | Monitor may make an assessment of the commodity crop type, but when confidence in the Monitor practice is low, it will be indicated in the conflict status. |
🏳️ No reliable eval. Alternative verification method suggested. |
Insufficient satellite imagery (no Monitor tillage determination) | Monitor could not determine commodity crop type due to limited clear, cloud/snow free imagery. |
🏳️ No data Alternative verification needed. |