Digital signature

TAOM Digital Signature

Sign test evidence – no paper, no media break.

Whoever is responsible for a test signs the evidence directly in TAOM. Every signature is bound to the person, the role and exactly this version.

A signing round starts from a test record. TAOM proposes the signatories from the project organisation, notifies them one after another by email and, after the last signature, creates a signed version with its own document seal – verifiable by anyone who holds the document.

Download sample Arrange a meeting

Part of the add-on licence Testing and verification in test management · Feature matrix

Process

From test record to signed version in four steps

The round is based on the evidence TAOM creates after the test run. Content, result and evidence are fixed in it – exactly this state is signed.

Start the roundChoose the roles in the test record, for example tester, test manager, quality assurance and business department. TAOM proposes the people from the project organisation.

NotifyThe first role receives an email with a link to the customer account. The PDF itself is not sent – it stays in the protected area.

SignLog in, review the evidence, confirm with the password. Then it is the next role’s turn; the person who started the round sees every step.

Signed versionAfter the last signature, a new document is created with completed signature lines, its own document number and a new document seal that refers to the original.

Anyone who does not want to sign declines with a reason. The person who started the round is informed, and the process remains traceable in the log.

In the video

A round with four roles – from the email to the authenticity check

Two minutes: create the evidence, start the round, the roles’ emails, signing with password, signed version and checking the seal on taom.ai.

Test record TN-00024 is signed by four roles; this produces the signed version TN-00025 with document seal. Demo data, email addresses made unrecognisable.

Security in the process

A signature only counts when everything matches

TAOM checks every signature on the server. Anything that does not match is rejected and logged.

Password for every signature

The logged-in person confirms every signature again with their password. After five failed attempts, signing is locked for 15 minutes.

Only with confirmed responsibility

Only someone who has confirmed the role in the project organisation can sign – for the tester, having carried out the last test run is sufficient.

Exactly this version

A checksum records the state at the start. If the document has been changed since then, no signature is possible.

Four-eyes principle

Your company’s four-eyes rule also applies to signing rounds. If a confirmed responsibility is missing, TAOM points this out as soon as the round starts.

Permissions and classification

Viewing and downloading test evidence is a permission of its own. In addition, TAOM checks the classification of every model concerned – Information protection.

Licence checked

The digital signature is part of the “Testing and verification” add-on licence. Without it, rounds can neither be started nor signatures given.

Document seal

Check authenticity – without access to TAOM

Every test record carries a document seal with document number and QR code. The verification page shows document type, issuer and date and detects whether the details match the original. Even a single changed digit makes the seal invalid.

Original test recordEvidence of a test run with result, evidence and empty signature lines – the basis of the round.

Signed versionIts own document number and its own seal. It confirms the original and the signatures; the note “Signed version of …” refers to the original record.

Verify document →Trust Center →

Reporting

At a glance: what is signed and what is missing

In reporting under Tests, TAOM shows which test records are fully signed and filed and which role is still missing for the others – with a direct link to the signed version. In the customer account, the “Signatures” area guides you through open rounds and your own tasks.

Testing and verification →Information protection →Feature matrix →

Download

Sample: signed test record with document seal

This is what the result looks like: the signed version TN-00025 of a test run from our own test management, with four signatures and document seal.

What the sample shows

Test run with steps, result and evidence images
Signature lines with role, name and time
Document seal with document number and QR code
Note referring to the original test record

Demo data of the fictitious company “Muster TAOM.ai AG”.

PDF206.8 KB

Sample: signed test record with document seal (TN-00025)

We will send you the download link by email.

Digital signature

Evidence that holds up – in audits too

For GxP, medical technology and everyone who not only carries out tests but also has to take responsibility for them and prove them.

Arrange a meeting Feature matrix