Manual · Chapter 7

Export & evidence

In the end, what counts is what you can put on the table. easo exports every released document as long-term-stable PDF/A — with a title block carrying all control data, and a verification annex an auditor can check without easo.

All screenshots show sample data from Berger Präzisionsteile GmbH — a fictitious company (CNC precision manufacturing, 12 people) used to show every easo feature honestly, open gaps included.

The title block: all control data on page one

ID, version, status, author, approver, next review, process, addressed ISO clauses, company details — everything a controlled document must state sits up front, followed by a table of contents. Headers carry the ID and status on every page.

Page 1 of the exported PDF PRO-006 “production control (traveller)”: the title, below it a metadata block with author, approver, next review, process, addressed clauses and Berger's company details, followed by the table of contents. — The exported PDF: the complete document-control title block on page one. Interface shown in German.

The verification annex: checkable without easo

The last page discloses what the document rests on: the release tag in the QMS repository, the SHA-256 content hash, who signed when, and the key fingerprint. Below it, the “verify without easo” instructions — three steps using standard tools (git show, shasum, ssh-keygen). Your evidence doesn't depend on our product: that's revision safety in practice.

The PDF's verification annex page: release tag, SHA-256 content hash, signed by, signed at and key fingerprint, below it the three-step “verify without easo” instructions with the git show, shasum and ssh-keygen commands. — The verification annex: hash, signature and verification instructions that need nothing but standard tools. Interface shown in German.

See for yourself

The document shown is available here in the original — a real easo export PDF from the Berger sample QMS, signed with a demo key:

Download the sample PDF (PDF/A, 83 KB)