Sample report
What the report actually contains
Seven fixed sections, in HTML and PDF. The structure does not change between certificates, so a reviewer knows where to look.
Microcrystalline Cellulose, excipient
Issuer ExciPharma Solutions Ltd. (a fictional company), batch MCC-2026-0614-A. Automated outcome: Conditional, evidence required before use. Produced 24 August 2026 by the current engine; the version package is printed in the report.
The certificate is synthetic: a fictional issuer written to exercise the checks. Nothing in it belongs to a real supplier. The report is exactly what the product produced from it.
| Section | Purpose |
|---|---|
| Report identity | Which document, which batch, which run, and the software and source versions behind it. A report that cannot name its issuer does not claim identity checks out. |
| Final outcome | One of four: accepted, conditional, non-compliant, or insufficient data. Insufficient data is a real outcome, not a failure to produce one. |
| Client decision summary | What a procurement officer or QA manager needs in order to act, in plain language. |
| Comparison against requirements | Each test with its printed limit, the official limit, the reported result and the outcome. The limit comparison is shown separately from the result comparison. |
| Supplementary evaluation | Document-level checks that are not a single test row: signatures, authorisations, internal consistency. |
| Open findings | Everything unresolved, each with the requirement, the evidence, the reasoning and the action that would close it. |
| Scores and sources | The scoring, and every source cited with the version used. |
See it on your own document
No card required, and the report is yours to keep.