Is a signature created in AviSignature legally valid?

Legal effect depends on the document, consent, identity controls, evidence, process, and jurisdiction. The browser workflow supports simple electronic-signature evidence; no universal validity or enforceability claim is made.

Does AviSignature create a qualified electronic signature under eIDAS?

Not through a drawn, typed, or image signature alone. A qualified electronic signature requires a qualified certificate, a qualified signature-creation device, and a qualified trust-service context. Any such deployment must be confirmed separately.

What does the SHA-256 hash prove?

The hash is a fingerprint of the file used at that point in the workflow. Comparing hashes can help detect a change, but the hash alone does not prove who signed, when they signed, or whether the record was retained correctly.

Which signature methods are available?

The reviewed browser workflow supports drawing a signature, typing it, or using an image. The organisation should decide which methods are acceptable for each document type.

Does AviSignature verify a signer’s identity?

Entered names, email addresses, and audit events are not automatically strong identity verification. If a document requires identity proofing, authentication, or a qualified trust service, those controls must be specified and confirmed separately.

AviSignature - PDF Signing Evidence Workflows

Q: Can several people sign the same PDF?

Yes. The workflow can add multiple signers in an intended order and place a signature area for each person on the relevant page. The reviewed browser workflow does not enforce that signing sequence.

AviSignature PDF electronic-signature workflow

Book AviSignature demo

Stage 3: Document & Control

PDF Electronic-signature Workflow

Prepare, place, and evidence PDF signatures in one process

AviSignature is a PDF electronic-signature workflow solution. It lets users upload a PDF, calculate a SHA-256 document hash, register signers in the order entered, position signature fields, capture drawn, typed, or image signatures, and export the signed file with an audit record. The browser workflow creates evidence for a simple electronic signature; it does not enforce a sequential signing route or automatically create a qualified electronic signature.

Serves
- Operations, administration, HR, quality, and sales teams handling routine PDF approvals
- Document-control teams coordinating simple electronic signatures
- Legal, compliance, and information-security owners who define document eligibility and evidence needs

What it helps you do

1. Start from the PDF being approved

Upload the document and calculate its SHA-256 hash so the workflow can retain a fingerprint of the original file. A hash can help reveal a later change; it is not by itself proof of identity or an immutable archive.

2. Define signers and the intended order

Enter signers in the intended order and assign each person to the relevant field. The list makes ownership clear, but the reviewed browser workflow does not block a later signer from signing early.

3. Place signature fields on the page

Position a signature area for each person on the relevant PDF page. This reduces ambiguity about where a signature or approval belongs.

4. Capture a simple electronic signature

Allow a signer to draw a mark, type a signature, or use an image where that method is appropriate. Consent, identity assurance, and legal suitability must be designed for the document and jurisdiction.

5. Retain a readable event history

Record timestamps and workflow events associated with document preparation and signing. The audit record helps a reviewer reconstruct the process without treating it as independent legal verification.

6. Export the document and evidence

Produce the completed PDF with its supporting audit material and export audit information in the supported format. Retention, access control, and integration with a document system depend on the deployed configuration.

Scope and important limits

AviSignature supports a simple electronic-signature workflow; it does not itself create a qualified electronic signature and does not enforce sequential signing among registered signers. The required certificate, identity-assurance, and qualified trust-service arrangements must be confirmed and licensed separately for each document class before deployment.

PDF Electronic-signature Workflow

Prepare, place, and evidence PDF signatures in one process

What it helps you do

1. Start from the PDF being approved

2. Define signers and the intended order

3. Place signature fields on the page

4. Capture a simple electronic signature

5. Retain a readable event history

6. Export the document and evidence

Scope and important limits

Suggested bundle: Digital Approval

AviSignature

AviManuals

SGCD

Frequently Asked Questions.