Question 1

Is this a qualified electronic signature (eIDAS)?

Accepted Answer

No. This case study covers **graphical signing** on a tablet — the operator confirms the signer’s identity before signing. It is operational e-signing in process, not a legal substitute for qualified signatures.

Question 2

Do we have to drop print and scan?

Accepted Answer

No. **Desktop keeps the proven path** print → sign → upload. Tablets get the signing session. Backward compatibility was a deployment requirement.

Question 3

Does this require a separate document system?

Accepted Answer

Not where we start. The point is **wiring into existing attachments and statuses** — the final PDF lands where the scan did and triggers the same business rules.

Question 4

How do you add more document types?

Accepted Answer

Through a **definition registry**: template, signing roles, attachment type, start guard. The same pattern as other integrations in an operational system — not a parallel module.

Question 5

What about audit and security?

Accepted Answer

The session stores **PDF hash before and after signing**, signer metadata and separate signature files per role. The final PDF includes an **audit page** — answering what exactly was signed.

Question 6

Does this reveal the client or industry?

Accepted Answer

No. We describe the **problem and solution pattern** without company name, industry specifics or details that could identify the organisation.

Document signing in the field when the operational system stops at “print and upload a scan”