Introduction
Understanding and acting on test outcomes has long been a crucial part of maintaining standards and reducing risk in our workflows. However, interpreting these outcomes and knowing exactly what to do next hasn’t always been as straightforward as it should be.
That’s why this recent improvement is so important: Resolution Protocol in Meridia Verify provides clearer, more actionable guidance, helping both desk-based and field teams respond with confidence and precision.
In this tutorial, we’ll walk through how these new resolutions work, where to find them, and how they help you handle outcomes more effectively.
How to Use the Resolution Protocol
1. Locating the Resolutions
Results tab: From the Results tab, you’ll be directed to the summary display, which allows you to view the information and resolutions for the tests that contribute most to the critical risk profile, helping you take the necessary mitigation actions.
Tests & Resolutions tab: You can get a full overview of the resolutions for each test by selecting the 'Info and Resolution' tab.
3. Using Resolution Protocols for Broader Guidance
Beyond individual actions, there are now four structured resolution protocols available.
The protocols are designed to address and resolve common issues in a holistic and structured way, ensuring that users can apply them effectively. They help move from reactive responses to best-practice approaches for problem resolution.
The protocols include the following
Protocol 1: Dataset Record Review Protocol: Problems are addressed through data cleaning and standardisation, but some require referral to the source team for clarification or correction.
Protocol 2: Desk-Based Geo-Data Corrections Protocol: Problems that can be reviewed without going into the field.
Protocol 3: Farm plot remapping protocol: Field teams' activities requiring coordination with local stakeholders, visiting farmers, and working with the necessary equipment to map farm plots.
Protocol 4: Performing Compliance Reviews: Key corrective actions to take when deforestation or legality risks are identified.
4. Understanding the Details
You’ll now find specific, actionable guidance tailored to each risk profile. For example, medium-risk issues come with distinct actions and expectations compared to critical ones, reflecting the practical realities of how they should be addressed.
Clear, concrete actions directly linked to identified issues
Practical follow-up steps for both field and office teams
Supporting materials for deeper understanding and ongoing learning
5. Following Clear, Actionable Steps
Each issue now comes with clearly described steps for mitigation. Whether it's something like resolving an overlap of a protected area.
You’ll see who is responsible for the scope (desk team or field team) and the type of action that needs to take place (correction or prevention).
Please check below what the tags describe:
Issue Type
Desk team: Refers to staff who handle issues remotely, typically using software or data tools in the back office, without needing to visit the field.
Field team: Refers to staff who carry out on-the-ground checks to verify results, collect additional evidence, or remap farm records when major issues are found in previous mapping or data collection.
Action Type
Correction: Refers to remediation after identifying particular issues with the data
to ensure data validity and reliability.
Prevention: Refers to measures taken during data mapping to ensure quality is
met while avoiding errors during the process
5. Sharing and Collaboration
The updated structure makes it much easier to share relevant details with colleagues or support teams, especially with the ability to copy any test's resolution details for convenient sharing. Because responsibilities and actions are clearly defined, there’s less room for confusion and delays.
By following this new structure, you’ll find that resolving risks becomes significantly more straightforward. You’ll spend less time trying to interpret the outcome and more time focused on action. Teams will benefit from better clarity, improved collaboration, and ultimately faster, more effective mitigation of risks. This leads directly to higher confidence across both field and desk teams.
⚠️ Note: Important Considerations
These are high-level guidelines designed to support managers in communicating required actions to third parties. However, they should still be critically assessed and adapted to the specific context.
There is no single, linear workflow. The sequencing of actions may vary depending on the circumstances.
Each of the farm plot risks requires different actions and is now clearly separated.
Actions are tied to specific roles (desk or field), removing ambiguity.
Protocols offer structured, repeatable processes for common issues.
Clear documentation makes it easier to involve support teams when needed.
Summary
This update marks a significant improvement in how users interpret and act on test outcomes. With clearer guidance, structured protocols, and role-specific actions, your teams can resolve issues more efficiently and confidently.
Whether you’re in the office or out in the field, this new approach will help ensure nothing falls through the cracks, making your work more reliable and less stressful!