Digital Signatures in Reports: Ensuring the Legal Validity of Water Analysis Certificates
Table of contents
Why does a test certificate need a digital signature — isn’t an exported PDF enough?
A results report exported to PDF from a spreadsheet or word processor carries, by default, no cryptographic guarantee. It’s a snapshot of the content at the moment of export, but nothing stops anyone from opening it again, changing a figure, and saving it back under the same name. For an accredited laboratory, that’s a fundamental problem: the value of a test certificate lies not just in the result it contains, but in the guarantee that the result is exactly what the technical signatory validated and signed.
A digital signature solves this differently from a scanned handwritten signature. Technically, it applies a cryptographic function to the document’s content and binds it to the signer’s digital certificate. If a single character in the report changes after signing, the signature becomes invalid and any verifier — human or automated — detects it immediately. It isn’t a matter of trusting that nobody touched the file: it’s a mathematical check.
What’s the difference between signing “by hand and scanning” and signing digitally?
A scanned or image-inserted handwritten signature is, in practice, just another image on the document: it can be cropped from one PDF and pasted into another without leaving any trace. It doesn’t uniquely identify who signed, doesn’t prove it was created under their exclusive control, and above all doesn’t detect later alterations to the document. It serves a visual purpose — it looks like a signed report — but delivers none of the legal guarantees required of a compliant electronic signature.
The three tiers of electronic signature and which one fits a laboratory report
Most e-signature frameworks don’t require always using the highest tier. They define three tiers with distinct guarantees and use cases, and the right choice depends on the legal risk associated with the document being signed.
| Signature tier | What it guarantees | Typical use in a laboratory |
|---|---|---|
| Simple (SES) | Expresses intent to sign, without uniquely binding the signer or guaranteeing the document’s later integrity | Low-risk internal confirmations; not recommended as the sole signature on a test certificate |
| Advanced (AES) | Uniquely identifies the signer, is created under their sole control, and detects any later alteration to the document | Standard recommended level for test certificates issued from a LIMS |
| Qualified (QES) | Same guarantees as advanced, but with a qualified certificate and device; legally equivalent to a handwritten signature | Cases of maximum legal exposure: expert witness reports, certain public contracts, or agencies that explicitly require it |
For most water testing laboratories, the advanced signature is the point of balance: it unambiguously identifies the technical signatory, detects any later tampering, and carries full evidentiary value, without requiring the administrative overhead of a qualified certificate. A qualified signature is reserved for scenarios where an agency or judicial procedure explicitly demands it.
What accreditation bodies require for an electronically issued report to be valid
General accreditation criteria under ISO/IEC 17025 are explicit about electronic reports: when a laboratory issues simplified reports or certificates under its accreditation mark, it must guarantee, among other elements, laboratory identification, the results themselves, and the signature of the responsible party — or verifiable assurance that the report was actually issued by them, in the case of an electronic document.
Spain-specific case study: ENAC, Spain’s national accreditation body, applies this same standard to itself — it digitally signs its own accreditation certificates and technical annexes, and adds a verification code that lets anyone check in real time whether the accreditation is still valid. Equivalent bodies such as A2LA and NELAP in the US, or UKAS in the UK, apply comparable integrity and verifiability requirements to their own accredited documentation.
It’s the same principle a laboratory must apply to its own test certificates: it isn’t enough for a document to look official — it has to be verifiable. The latest edition of ISO/IEC 17025:2025 reinforces this direction by introducing specific provisions on information technology, networked instrumentation, and data automation in laboratories, explicitly recognizing the role systems like a LIMS play in generating and issuing reports.
Digital signature and audit trail: two distinct layers of document integrity
It’s common to confuse the digital signature with a result’s complete traceability, but they protect different moments in the process. The digital signature certifies the final document: who signed it, and that nobody has touched it since. On its own, it says nothing about whether the data in that report was manipulated before it reached the technical signatory who signed it.
That second layer is the audit trail’s responsibility: the append-only record that documents every action on a sample and a result, from its capture on the instrument through to validation. The first four ALCOA+ principles — attributable, legible, contemporaneous, and original — depend on that internal traceability, not on the signature of the final report. A report can be flawlessly signed digitally and still contain data that was altered before validation, if the system that generated it doesn’t maintain an equally rigorous audit record.
That’s why a report’s digital signature only closes the loop when combined with role-based access control, complete traceability from the instrument, and an immutable audit record: each of these layers protects a different point in the data’s chain of custody.
How the digital signature should be integrated into a LIMS workflow
The difference between signing a report “at the end of the process” versus “as part of the process” matters more than it seems. In a well-designed workflow, the report is generated automatically from already-validated results, digitally signed within the same system at the moment of issuance, and locked against modification from that point on. Any later correction doesn’t edit the original document — it generates a new version, with its own signature and its own reference to the previous version, which remains available in the history.
Zendo LIMS supports digitally signing the results report, including scenarios where several responsible parties take part in the validation process, each with their own digital certificate. Reports also include QR codes that allow the result to be verified online, and the system maintains version control of issued certificates together with an audit trail — with independent request, test, and user auditors — that documents every action with date, time, and responsible party.
| Criterion | Manual process (Word/Excel + scanned signature) | LIMS with integrated digital signature |
|---|---|---|
| Signer-document binding | None: the signature image can be copied between documents | Cryptographic: the signature is invalidated if the content changes |
| Detection of later alterations | Does not exist | Automatic, within the signed document itself |
| Correcting an already-issued report | The same file is edited and resent, with no version control | Generates a new signed version, referencing the previous one |
| Validity before an accreditation auditor | Depends on additional justifications outside the document | The document self-justifies: signature, date, and traceability |
| Signature from multiple responsible parties | Requires printing, signing, and re-scanning | Each responsible party signs with their own digital certificate |
Zendo LIMS lets you digitally sign results reports with the certificates of one or several responsible parties, embed verification QR codes, and maintain version control of every certificate issued — all within the same validation workflow.
See how Zendo LIMS locks in the legal validity of your test certificates
Frequently asked questions
Do I need a qualified signature certificate to sign laboratory reports?
In most cases, no. An advanced electronic signature already uniquely identifies the technical signatory and detects any later alteration, meeting what accreditation bodies require for an electronic report. A qualified signature is only necessary when an agency, a client, or a specific judicial procedure expressly requires it.
Can a report signed with an advanced signature be rejected as evidence in court?
Not automatically. Under frameworks such as the EU’s eIDAS Regulation (and comparable provisions in the US and UK), evidentiary value cannot be denied to an electronic signature solely because it is electronic or not qualified. Its weight as evidence depends, as with any evidence, on the full set of technical guarantees behind it.
What happens if a report that was already signed and sent to the client needs to be corrected?
The original report should not be edited or overwritten. The correct approach is to issue a corrected version, signed again, that explicitly references the version it replaces. The original, incorrect version is retained in the system’s history — not deleted — as part of the laboratory’s documentary traceability.
Does the digital signature replace the accreditation mark on the report?
No, they’re complementary elements. The accreditation mark indicates that the test falls within the laboratory’s accredited scope. The digital signature guarantees the authenticity and integrity of the specific document being read. An accredited report should include both elements — one doesn’t substitute for the other.
Susana Martín Castaño
International Sales Consultant
With over 20 years of experience in the UK and Spain, she is a laboratory IT expert specialising in Zendo LIMS implementations. As the current head of international sales, she has optimized operations for around 40 laboratories in nearly 50 countries.
