Introduction
Resolution Report helps you turn assessment results into a structured report that is easier to review, share, and act on. It is designed for teams working with suppliers, co-operatives, internal reviewers, or field teams who need a clearer way to understand test results and prioritise next steps.
With Resolution Report 1.1, exports are now more flexible and more practical for day-to-day workflows. You can choose which tests and risk levels to include, export both PDF and Excel together in a single ZIP file, and use an improved summary structure to review findings more quickly. This builds on the earlier version, which focused mainly on generating a structured PDF report from dataset, test, or filtered farm plot views.
Why is this useful?
Resolution Report is built to make follow-up work easier after running an assessment.
It helps you:
focus only on the tests and risk levels that matter for your workflow,
share findings in a readable PDF format,
analyse and track results in Excel,
and communicate actions more clearly with suppliers or field teams.
This is especially useful for teams handling large datasets or supplier-facing workflows, where long static reports can be difficult to use at scale.
What’s new in Resolution Report 1.1
Resolution Report 1.1 introduces several improvements to make exports more useful in practice:
ZIP export (PDF + Excel) Each export now includes both file formats in a single download.
Configurable exports Users can choose which tests and risk levels to include before generating a report.
Default configurations for admins Admin users can save a preferred configuration as the default for their organisation.
Redesigned summary The PDF now opens with a clearer test-by-test summary for faster review.
“How to Use This Report” page A dedicated page explains how to read the report and interpret the results.
More readable test output Test outputs are presented in a clearer format for non-technical readers.
How to generate a Resolution Report in Meridia Verify Portal
Step 01: Generate a Report
From within the application, you can generate a Resolution Report for an entire dataset or for a smaller, more specific scope, depending on what you need to review.
Option 01: Generate a report from the dataset summary
You can start the Resolution Report generation flow from the 'Summary' tab at the dataset level. In the dataset overview section, click 'Generate Report (.zip)'. This will open the report configuration window, where you can choose which tests and risk levels to include before generating the report.
Option 02: Generate a report for a specific test (Top Compliance Issues/Top Data Quality Issues)
You can also generate a Resolution Report for farm records related to a specific test, such as DEF04. This option is available from the Summary tab. Navigate to the relevant test section and click Generate Report. The report can then be configured based on the tests and risk levels you want to include.
Step 02: Configure the Report
Once you click 'Generate Report (.zip)', the 'Report configuration' window will open.
Here, you can choose how the report should be generated by selecting one of the available report types.
Option 01: 'Default configuration'
Use this option to generate the report using the default report settings saved by your organisation’s admin user. This means the report will follow the configuration that has been set as default for your organisation, including which tests and risk levels are included.
This option is useful if your team wants to apply the same report setup consistently across datasets.
Option 02: 'Select specific tests'
Use this option if you want to create a custom report by selecting only certain tests. You can add the tests you want to include, then choose the risk levels to show for each selected test.
Option 03: 'Critical results only'
Use this option to generate a report that focuses only on critical findings. This is useful when you want to prioritise the most urgent issues and keep the report focused on the highest-risk results.
Option 04: 'All tests'
Use this option to include all available tests in the report. You can still review and adjust which risk levels to include before generating the report.
Select tests and risk levels
Below the report type options, you can further define the report scope.
Depending on the report type selected, you can:
include or remove tests,
select all tests at once,
and choose which risk levels to include, such as critical, high, medium, or low.
Save the configuration as default
If needed, tick 'Save report configuration as default' before generating the report.
This allows admin users to save the selected setup as the default configuration for future exports.
Generate the report
Once the configuration is ready, click 'Generate Report' to create the export.
Step 03: Understand the Report Structure
Once generated, the export is delivered as a ZIP archive containing two separate files: a PDF report and an Excel file.
The PDF report includes several useful sections:
Cover page
Introduces the report with the report title and visual cover.
Table of contents
Helps readers navigate the report more easily. It includes links to the main sections and each test section.
Report summary
Provides a high-level overview of the dataset, including key information such as dataset name, commodity, origin, creator, methodology profile, number of farm plots in the report, and number of tests included.
Tests summary
Shows all tests included in the report in a clear table format, together with the number of affected farm plots. Readers can use this section to quickly identify where the main issues are.
‘How to use this report’ page
Explains how to review the report, how to prioritise findings by risk severity, how to read test sections, how to evaluate farm plot tables, and how to take corrective or preventive action.
Test details
Each test section explains the severity thresholds, test information, short description, and technical details, so readers can understand what the test checks and how the result should be interpreted.
Affected farm plots
Lists the farm plots affected by a given test and risk level, together with the relevant output details shown in a more readable format.
Actions
Provides recommended correction and prevention actions to help users respond to the issue and support follow-up work.
The Excel file is provided separately
The Excel file is included as a separate file in the same ZIP export.
It contains the report data in a spreadsheet format, making it easier to:
filter results,
track affected farm plots,
support operational follow-up,
and use the data in internal workflows or automation.
The Excel file follows the same selected report scope, so it only includes the tests and results configured during report generation. At the end of this process, you receive a structured export package that is easier to review, share, and act on. The PDF supports communication and guided review, while the Excel file supports filtering, tracking, and operational use.
Important considerations
Reports can be configured to include only the tests and risk levels relevant to your workflow.
Each export is delivered as a ZIP archive containing two separate files: a PDF report and an Excel file.
The PDF is suitable for review, sharing, and supplier-facing communication.
The Excel file is useful for filtering, tracking, and operational follow-up.
The Excel file follows the same selected report scope, so it only includes the tests and results configured during report generation.
Admin users can save a preferred report setup by ticking 'Save report configuration as default' before generating the report.
Summary
Resolution Report 1.1 makes report exports more flexible, more structured, and easier to use in practice.
By combining configurable report generation with separate PDF and Excel outputs, it helps teams review findings faster, focus on the most relevant issues, and support follow-up work more effectively.
This makes Resolution Report more useful for day-to-day operations, especially for teams working with large datasets, supplier communication, and ongoing risk tracking.