A fruit sorting trial report should show whether a tested configuration supports a defined grade decision under stated conditions. It is not a brochure, a single accuracy percentage, or a promise that every fruit condition will behave the same way in production.
Read the report as a chain of evidence. It should show what fruit was tested, which rule or condition was assessed, how the reference assessment was made, what the system decided, where each result went, and what remains outside the evidence. If one link is missing, an impressive outcome figure can be misleading.
Use it when comparing suppliers, preparing configuration, or setting up a later FAT or SAT review.
Start With the Trial Question
Read the stated trial question before reviewing result tables. It should describe the decision that the test was intended to examine, for example:
- separation by an agreed size or weight rule;
- application of a stated color or visible-appearance category;
- distinction between a specified surface condition and normal variation under stated presentation conditions;
- assessment of an internal-quality target using an agreed reference method; or
- routing of an agreed result to the intended grade outlet, manual-review point, hold area, or approved alternative handling route.
“The fruit sorter was tested successfully” is not a sufficient trial question. It does not define the fruit basis, grade rule, reference method, or commercial consequence of the decision.
A visible-color trial does not demonstrate internal-quality capability. A test with one variety, handling condition, or small set of grades cannot automatically cover a different crop, storage history, or market rule.
Check the Fruit Basis Before Reading the Outcome
A trial outcome is meaningful only in relation to the fruit used. Check whether the report identifies the fruit type, variety, lot or sample groups, and conditions relevant to the inspection question.
| Fruit-basis item | Why it matters |
| Fruit type and variety | Appearance, shape, skin condition, and internal behavior can differ by variety. |
| Lot or sample-group origin | Shows whether the sample represents one lot or a wider range of commercial variation. |
| Condition at assessment | Storage, temperature, moisture, waxing, washing, drying, and handling can affect the observation. |
| Presentation condition | Orientation, spacing, surface visibility, and carrier or conveyor condition can affect inspection. |
| Sample-group definition | Separates normal commercial, non-conforming, borderline, manual-review, and unassessed fruit. |
Before relying on a reported percentage, check the sample basis, reference method, exclusions, and route evidence. A high sample count does not make a trial representative if it contains only obvious premium fruit and obvious rejects. Look for normal commercial fruit, clearly non-conforming fruit, and cases near the grade boundary.
The report should identify important variation that was absent. That does not invalidate the test; it identifies the evidence still needed before the result is extended into a wider configuration or acceptance claim. For practical preparation of sample groups, refer to What to Prepare for a Fruit Sample Test.
Identify the Grade Rule Behind Each Result
Each category in the report needs a commercial definition. Labels such as “good,” “defect,” “reject,” or “Grade A” are not enough unless the corresponding rule is stated.
Ask five questions for every category:
1. What specific condition or measurement is being assessed?
2. Where is the boundary between acceptable and non-conforming fruit?
3. Who supplied or approved that rule?
4. Is the decision based on size, weight, color, visible appearance, internal condition, or a combination?
5. What should happen downstream when that category is identified?
This matters when reports from different suppliers are compared. The word “defect” can describe a narrow visual feature in one proposal and a broader commercial grade decision in another. The percentages may look comparable even though the underlying rules are different.
For visible conditions, distinguish the condition itself from the route decision. A surface mark may be acceptable for one buyer program but require a different saleable grade or an approved alternative handling route for another. External-quality inspection categories should therefore be tied to the market rule, not treated as an automatic reject in every case.
Review the Reference Assessment Separately
Before judging whether the equipment made the right decision, check the reference assessment used for each sample or sample group.
A reference assessment is the agreed basis for comparison. Depending on the question, it may be a measurement, assessor record, labeled photograph, manual review, cut-fruit result, laboratory work, or another documented method. It does not make every judgment absolute; it makes the comparison basis visible.
| Reference-assessment question | What to look for |
| How was the fruit classified? | A stated method appropriate to the grade or condition. |
| Who made the assessment? | Assessor role, agreed reviewer, technical specialist, or laboratory where relevant. |
| Was the result linked to the sample? | Individual ID where needed, or a documented group-level limitation. |
| Were uncertain cases recorded? | Borderline, disputed, unassessed, or outside-scope status. |
| Was reassessment possible? | Recheck record and any change to the initial assessment. |
For internal-quality targets, the method must be especially clear. Surface images do not confirm internal condition. If the reference uses cut fruit, measurement, laboratory analysis, or another procedure, the report should state the method and whether it relates to individual fruit or a sample group. The supporting logic is explained in How to Validate Internal-Quality Inspection.
For visible external conditions, photographs can support the record only when linked to a sample ID and an agreed viewing method. Light, moisture, wax, shadows, contamination, and fruit orientation can change what is seen.
Separate the System Decision From the Route Result
A sorting trial answers at least two different questions:
1. Did the system make the agreed classification decision?
2. Did the fruit reach the intended physical route?
Classification evidence alone may miss an outlet, conveyor, buffer, control, or packing-interface problem. Outlet counts alone may not show whether the correct fruit arrived there. Review both the decision and physical outcome.
| Review area | Buyer check |
| Sorting decision | Was the sample assigned to the intended category under the agreed rule? |
| Outlet or route | Did the fruit reach the intended grade outlet, hold point, manual-review path, or approved alternative handling route? |
| Count or weight record | Does the reporting unit match the stated basis: pieces, weight, batch, or packed output? |
| Downstream handoff | Could the assigned route be received, accumulated, packed, labeled, or otherwise handled as intended? |
| Exception handling | Were diversions, jams, manual interventions, and unassessed samples recorded separately? |
A false accept may put non-conforming fruit into a premium route. A false reject may remove saleable fruit from it. A cross-grade result may send fruit to the wrong market program. These outcomes have different commercial consequences and should not be hidden inside one headline percentage. For the downstream planning question, see How to Connect Grade Outlets to Packing.
Read Counts and Percentages in Context
Percentages are useful only when their denominator and test basis are clear. Check the total number of assessed samples, samples in each category, excluded or unassessed samples, reporting unit, and stated operating condition.
A limited set of difficult samples can guide the next validation step, but does not establish a full-season result. A broad average can hide weakness in a low-volume premium or buyer-specific route.
Focus on the error type and consequence, not just the number. A minor difference in a low-value alternative route may need a different response from a small number of false accepts entering premium pack-out. Untested fruit must remain identified as untested; it cannot be included in a wider capability claim.
Look for Exceptions, Not Only Successes
A credible report records what was not fully assessed. Examples include fruit outside the agreed sample scope, disputed labels, fruit that changed before reference assessment, missing traceability, presentation conditions that differed from the intended line condition, or categories with too few representative samples.
An exception does not automatically mean the trial failed. It tells the buyer what cannot yet be concluded. Check whether the report gives an appropriate next action: additional samples, a revised reference method, route review, configuration discussion, or later acceptance test. An exclusion must not quietly become a capability statement.
Use the Report to Compare Proposals Fairly
Use the same reading framework for each supplier. Ask them to clarify the fruit and sample basis, grade rules, reference method, inspection scope, exclusions, operating condition, reporting unit, outlet evidence, and items still subject to validation.
This exposes whether two proposals address the same decision, rather than merely using similar terminology. It separates an early demonstration from a project-ready basis for configuration and acceptance.
Before FAT or SAT, agree which results will be reviewed again, the sample basis, operating condition, grade definitions, route records, responsibilities, and treatment of disputed or unassessed samples. Sample Testing & Acceptance provides the project-planning context for that discussion.
Frequently Asked Questions
Does a high trial percentage prove the same result in production?
No. Read it with the fruit basis, target rule, reference method, exclusions, operating condition, and route evidence. Production may introduce wider variation or constraints not represented in the test.
What is the most important section of a trial report?
No single section is enough. The value comes from the connection between the trial question, fruit basis, reference assessment, system decision, route result, and limitations.
Should disputed samples be removed from the report?
No. Record them separately, with status and reason. Removing them without a record can make the result appear stronger than the evidence supports. Their treatment should be agreed before the report is used in an acceptance discussion.
Can a trial report be used as an acceptance report?
It can inform acceptance planning, but it is not automatically FAT or SAT evidence. Acceptance requires an agreed sample basis, operating condition, grade definition, route record, responsibilities, and treatment of exclusions for the relevant project stage.
Review the Acceptance Framework
If you are reviewing a fruit sorting trial or comparing proposed sorting configurations, share the fruit type and variety, target grade rules, inspection question, sample basis, current packing routes, and any report format already used in your project.
SORTTURNKEY can help structure an initial acceptance-framework discussion around reference assessment, sample conditions, reported results, route evidence, exceptions, and the points that require further validation before configuration or acceptance.
Request an Acceptance-Framework Review through the Contact Us page.