Practical guide

How to send contracts for electronic signing?

Short answer

eIDAS Regulation (EU) No 910/2014, Art. 25 — a qualified signature has the same effect as a handwritten one; an electronic signature cannot be denied as evidence solely for being electronic.
Romanian Civil Code art. 1240 — consent may be validly expressed in electronic form.
Law no. 455/2001 on electronic signatures — national legal framework for validity.
GDPR art. 6 — processing signatory personal data requires an explicit legal basis.
Law no. 135/2007 — electronic archiving of documents with legal standing.

IT services contract sent for simultaneous signing by 3 directors from different companies.
New employee contract completed and signed remotely before the first working day.
Non-disclosure agreement (NDA) sent to an external freelancer with a 24-hour deadline.
SaaS maintenance contract with SLA clauses, signed by both parties through a link, in a single workflow.

Sending a contract without setting a deadline — signatories postpone indefinitely.
Not defining the signing order when legal approval must precede commercial sign-off.
Using an incorrect signatory email without prior verification — the entire workflow stalls.
Not saving the final negotiated version before sending — signatories receive an incomplete draft.

Each signatory receives an individual secure link — no app installation required.
A signature certificate as PDF, with the IP address, time of signing and SHA-256 fingerprint of the document.
Contract templates with fields to fill in, drafted on the basis of Romanian law.
Reminders for signatories who have not signed yet.
Archive in your account, with the event history of each contract.

Contract templates, simple electronic signature, review and signing flow and archive — one subscription.