With the latest update to the Meridia Verify application, we’re excited to introduce a more streamlined and integrated Farmplot Reclassification workflow. This feature was built in direct response to feedback from users seeking a transparent workflow to manage reclassification of a farm plot through verification of farm plot data.
The primary goal of this update is to empower users, whether in the field or office, with tools that allow them to flag, verify, and finalise farm plot data more efficiently without the usual back-and-forth between teams.
1. Introducing the Farmplot Reclassification Interface
One of the most visible changes comes from an enhanced Farm Plot page interface. Users can now manage reclassification tasks directly from the farm plot table. These updates are designed to integrate with existing tools and provide intuitive access across interfaces.
Query Builder: Filter by risk level (e.g., 'Critical' or 'High') and isolate the exact farm plots that require reclassification.
Map View: Reclassification can be initiated directly by clicking on a plot from the map, allowing spatial review alongside the data.
Table View: Plots can be flagged for reclassification directly from the dataset table, offering a fast way to triage and assign next actions.
This new interface simplifies the first step of the reclassification process: identifying and marking plots that may require a second look.
2. Farmplot Reclassification Details
Once a farm plot is flagged, users can open its detail view to access the farm plot details panel. The details panel displays all key farm plot metadata. This can be accessed from the 'Details' tab.
It includes the following:
Reclassification tags
Add Evidence
Reclassification status
Reclassification outcome
2.1 Reclassification Tags
Plots can be tagged with labels depending on the type of verification and action needed. More than one tag can be selected. This helps assign responsibility and keep things organised.
Data Fix: Indicates that the plot likely contains incorrect or outdated data that needs to be corrected.
Desk Verification: Assigned when the verification can be handled remotely or through system-based checks.
Ground Verification: Used when physical field validation is required to confirm the status of the farm plot.
Tags also allow you to group plots via the Query Builder (e.g., see all 'Ground Verification' plots), and filtered plots can be downloaded in GeoJSON for Excel or external sharing or field team planning.
You can also view these particular farm plots filtered under the recalssification tag (e.g., see all 'Ground Verification' plots) on the Map view.
The farm plot detail card, showcasing all the information connected to this farm plot can be accessed directly from there. The user can also modify the details from this dispaly.
2.2 Add Evidence
After tagging the farm plot with the label, users can also add supporting evidence to justify the reclassification request.
This ensures all necessary context is stored centrally and accessible to all stakeholders. All saved evidence is time-stamped and linked to the user who submitted it.
The fields in the 'Add Evidence' section enable users to build a strong case to support their reclassification request. Additionally, the portal allows file uploads up to 25MB, supporting formats such as .pdf, .doc, .docx, .jpg, .jpeg, .png, .gif, and .zip.
Even drone footage can be added as an attachment!
2.3 Reclassification Status
Users can view where a plot stands in the process using intuitive status markers from the Reclassification bar on the Table view.
Flagged: The plot has been marked for secondary review by a user due to concerns found in metadata or map analysis.
Evidenced: Supporting documentation—such as notes, links, or files—has been attached to justify the reclassification. This will appear after submitting and saving it to the system.
Concluded: A final decision has been made, and the plot has an official reclassification outcome.
Farm plots under a particular reclassification status can also be filtered via the Query Builder (e.g., see all 'Evidenced' plots). This helps users display and manage actions required for farm plots at the same stage for the status tag.
2.4 Reclassification Outcome
Once the verification is complete, users choose one of three clear outcomes.
False Positive: The investigation has determined that the result on the Verify system is incorrect.
For example, a farm plot may be flagged in the Verify Portal as overlapping with a deforested area. However, if desk research and ground verification confirm there is no overlap, the plot should be reclassified as compliant, as it represents a 'False positive'.
Risk Mitigated: The risk previously identified in the farm plot has been addressed or reduced to an acceptable level through specific actions, making it no longer a significant issue.
For example, a farm plot may initially be flagged for deforestation risk due to apparent overlap with a deforested area. Upon further investigation, the farmer provides satellite imagery and legal documentation showing that the area is designated for cultivating the commodity in question. Based on this evidence, the risk is considered addressed, and the status is updated to 'Risk Mitigated'.
No Change indicates that, after review or investigation, the classification of a farm plot remains the same because no new evidence or justification has been provided to warrant an update.
For example, a farm plot is flagged for deforestation risk. If no additional evidence is submitted or the submitted evidence does not justify reclassification, the plot retains its original status. Therefore, its classification remains 'No Change'.
3. Audit Trail
To keep the process fully transparent, an Audit Trail feature has been added. This allows users to track every action—who flagged the plot, who attached evidence, who finalised the decision, and when it all happened.
This is especially useful for collaborative teams or regulatory reporting, as it guarantees accountability at each step.
4. Synchronised Reclassification Results
One key advantage of this system is that reclassification decisions automatically sync across all instances of the same farm plot ID.
If a plot appears in multiple datasets or over different periods, the outcome will be consistent everywhere.
This synchronisation is also logged in the audit trail, ensuring nothing gets lost or duplicated.
⚠️ Note:
Case 01: If a farm plot with the same farm_plot_ID is processed in multiple datasets using the same profile version:
the reclassification outcome set in the earlier dataset is automatically applied to the new instance;
the table and detail card will indicate that an outcome was inherited (e.g. “Inherited from dataset X1”);
users may reopen the reclassification (add/remove evidence, change outcome) from any dataset using the same profile version;
changes to the outcome apply to all datasets using that same profile version.
Case 02: if a farm plot with the same farm_plot_ID is processed in a dataset using a newer (or different) profile version:
the reclassification outcome is not inherited. The reclassification status will return N/A in all reclassification-related information;
the farm plot must be flagged again before a new reclassification_outcome can be set;
any previous outcomes and evidence are stored for context;
once reclassified under the new version, this outcome becomes the active once for that profile version.
It is strongly recommended to maintain consistency in the use of farm_plot_IDs when managing farm records.
5. How to Access & Use Farmplot Reclassification Feature
The Meridia Verify portal has introduced a new permission type called Reclassification Access. This access specifically governs a user's ability to interact with the farmplot reclassification feature, such as flagging plots, applying reclassification tags, submitting outcomes, and uploading supporting evidence.
Reclassification Access determines whether a user can:
View and modify reclassification details within the farmplot interface.
Submit or edit reclassification outcomes.
Track and review changes via the audit trail.
This access is project-specific and only available when the farmplot dataset is enabled for that project.
Below is a description of the permissions per role:
Admin
Has full permissions by default.
Can view, edit, flag, and reclassify all farm plots.
Can manage user roles and permissions.
A project admin must explicitly grant Reclassification Access via the Project Settings > Team Access Controls. Without this permission, users will not see the reclassification options in the interface, even if other farmplot data is visible to them.
Reach out to the Admin of your project to activate your access to this feature.
Creator
Can perform basic actions (depends on assigned permissions).
Optional: May be granted Reclassification Access via an invite from the admin.
If enabled, the creator can:
Flag farm plots.
Make final decisions on reclassification outcomes.
Actions are limited to their assigned permissions (e.g., by country or commodity).
Viewer
Can view all farm plot information.
Cannot edit, flag, or reclassify anything.
6. Summary
This reclassification workflow is designed to make your data verification easier:
Less back-and-forth coordination
Centralised evidence management
Clear accountability through the audit trail
Reliable updates across the system
We hope this update not only improves your workflow but also builds greater trust in the data and the decisions made around it.