Results & evidence
Evidencebefore adoption.
The most useful performance claim is one that answers the right question, under the right conditions, with evidence you can interrogate.
Our approach to results starts by defining the application and what a successful outcome actually means.
What we measure starts
with what matters.
- 01Define the requirementAgree the cleaning task, materials, operating conditions and relevant outcome.
- 02Design the testSelect an appropriate method, baseline or comparison and evaluation criteria.
- 03Record the observationsCapture relevant performance data and context, including limitations and conditions.
- 04Review the evidenceAssess whether the findings support a conclusion—and how far that conclusion can reasonably extend.
Not all evidence says
the same thing.
- 01Development hypothesisSomething we believe is worth investigating. It is not proof.
- 02Application observationA result observed under defined conditions. It may not transfer to a different process.
- 03Validated application conclusionA finding supported by a suitable test approach and documented review for a defined use.
- 04General product claimA broader statement requiring sufficiently robust evidence across the scope of the claim, with any limitations made clear.
The detail behind
a decision.
Where available and relevant, we can discuss testing methods, application notes, performance summaries and supporting technical information. Some information is confidential or requires a technical discussion before it can be shared.
Request technical informationResults in context.
Evidence is shared in context. We're prioritising relevant, application-specific discussions over publishing results without the detail needed to interpret them. Tell us what you're evaluating and we'll discuss the technical information available.
Ready to test a
real requirement?
Let's define the question before we jump to an answer.