What goes into a Malvern applications report
Written by: Debbie Huck-Jones
As part of my job I write reports for the analysis of customer samples on a regular basis. This type of applications analysis is a very important stage in our dialog with a customer. They have sent the samples for analysis as they are looking for guidance regarding the viability of using a particular technology to meet their needs. Consequently we aim to provide full application reports that are clearly laid out and tailored to these individual requirements. So depending on the complexity of the samples and the length of the analysis, the report writing can take a while.
A typical report is set out in a standard scientific format, as below:
Summary – one page overview of the whole report.
Introduction – sample and application information stating customer requirements.
Methodology – what we did.
Findings – what we found.
Conclusions – marrying the findings with the customer requirements and any recommendations.
This helps us to get across all the potential benefits a particular technology can provide for them for their application as well as providing information and explanation about the technology itself. This is particularly important when the technology involved is still relatively new, such as the Morphologi G3 and the Morphologi G3-ID, which are the instruments that I work with.
We have recently been working on providing some specific appendices for the Morphologi systems that will be added to every report we do to provide this extra information, should it be required by the customer. This should also make my life slightly easier as it will save writing the same things repetitively in every report I have to do! Below is an example page at the start of the Morphologi G3-ID document as a taster.