Signing an employment contract electronically — what the law allows

Under Regulation (EU) No 910/2014, article 25(1), no electronic signature may be denied legal effect and admissibility as evidence solely for being electronic; US practice under the ESIGN Act, 15 U.S.C. §7001(a), mirrors this. A qualified signature can only carry more weight where a specific rule requires it for a given contract type.

The practical floor, pre-signing: deliver the paper trail the offer already promised. For the parties, the evidence pack you keep — who viewed, who signed, when — is stronger if it carries the full ceremony trail: sent on X, opened on Y, signed on Z, and completed with the PAdES level the signing service actually reached.

The three moving parts: identity binding (the signer’s key, annexed to their legal identity through ceremony evidence), content binding (a digest that covers the entire agreed text, so an alteration re-verifies wrong), and verifiable time (an RFC 3161 timestamp; qualified where the authority provides one). A PAdES signature with those parts survives a challenge that a paper file cannot self-resist.

Portugal adds warmth: Decreto-Lei n.º 12/2021 article 3(2) attaches a presumption of veracity to the qualified electronic signature, and article 3(5) treats electronic documents signed with the admissible electronic signature schemes as any ordinary document under article 376 of the Civil Code.

Labour-specific rules live outside all of this: if a country requires a given form for one claim (a clerk’s witness, a stamped form, an employment card), that form stays regardless of e-signing. Check that on a case-by-case basis; nothing here replaces it.

Assemble the contract bundle (contract + policy acknowledgment + any annex). Upload the PDF, add counters, set the role list: you as the firm side, the candidate as the employee side. The candidate receives a one-time link over TLS, verifies identity with a 6-digit code (SMS or email), draws their signature, and the session records the signing trace, truncated IP address and device details as the ceremony trail. Order works in both directions — parallel routing to both sides at once, so two signers are not waiting on each other.

Each signing embeds a PAdES signature; when an RFC 3161 authority answers, it is B-T. The service records B-LT only when both the certificate chains and their revocation evidence were embedded and the result re-validated. Verification is public (no account needed), and CS-verification is a one-click public URL for the HR archive.

Mass-produced template with no offer trail: candidate resists because the offer letter they saw is not the contract they signed. Keep the audit trail consistent from offer to signed version.

Handing the ceremony to a sequence the signer cannot control: incorrectly typed name, old number, missed code. Split a signing across phases; the signature ceremony is the contractual sum, so treat it as one.

Assuming coverage: no platform substitutes notarial acts, and the product does not emit qualified certificates; where the mandate demands one, use the trust service provider that does.