Is a written agreement legally binding? What makes a signed document hold up

What makes a written agreement legally binding

A contract is legally binding when the parties reach agreement (an offer met by an acceptance), intend legal consequences, have capacity and pursue a lawful purpose. Common-law systems such as England and the US also require consideration, something of value given in exchange, unless the promise is made by deed. In most legal systems writing is not on that list: a written agreement is evidence that the contract exists and of its terms. TrueScreen certifies the signed file with an official digital seal and a qualified timestamp, so the agreement’s date and integrity can be checked later.

Writing is mostly about proof: the agreement binds the parties, and the document shows what they agreed. A verbal deal can be just as binding and far harder to enforce, since each side remembers the terms that suit it. Are written contracts legally binding when they are informal? Usually yes. A signed letter or an email exchange confirming a price can record a contract if it shows offer, acceptance and intent to be bound, whereas a letter of intent marked “not binding” generally cannot.

When writing alone is not enough: formalities, witnesses and notaries

Some contracts need more than the parties’ signatures to be valid or enforceable. Formal requirements are the exception, kept for transactions where the law wants extra certainty or extra protection for one side. In most legal systems they cover real estate transfers, guarantees and some consumer contracts, such as consumer credit, and in many common-law jurisdictions a statute of frauds requires sales of land and guarantees to be evidenced in a signed writing.

In many jurisdictions, a notary public verifies the signer’s identity and witnesses the signature without confirming that the document’s statements are true; in civil-law countries the notary often drafts the deed and checks that it is lawful. Does a contract need to be notarized, then? Usually not, unless a specific law says so. The simple, advanced and qualified levels in the table are an EU scale under eIDAS, which US law does not use.

Electronic agreements and e-signatures: eIDAS, UNCITRAL and ESIGN

An electronic signature is legally binding under the main international frameworks. Under eIDAS, Regulation (EU) 910/2014 as amended by Regulation (EU) 2024/1183, an electronic signature cannot be denied legal effect or admissibility as evidence solely because it is electronic (art. 25(1)), a qualified electronic signature has the equivalent legal effect of a handwritten one (art. 25(2)), and electronic documents enjoy the same non-discrimination (art. 46). In the US, the ESIGN Act and the UETA, adopted in nearly all US states, follow the same principle. TrueScreen offers simple and advanced electronic signatures in the TrueScreen App on all plans, and does not offer qualified electronic signatures.

An e-signed agreement binds the parties in the same situations as a handwritten one, and what it proves depends on how the signer was identified and how the file was protected. eIDAS leaves contract formation and form requirements to national law, and the guide to the advanced electronic signature under eIDAS explains the middle level.

The UNCITRAL Model Law on Electronic Commerce (1996) and the UNCITRAL Model Law on Electronic Signatures (2001) are models that many states have adopted in national law. Under the 1996 text, a data message meets a writing requirement if it stays accessible for later reference (art. 6), and an electronic method meets a signature requirement if it identifies the person and shows their approval (art. 7). Its weight as evidence depends on how reliably it was generated, stored and communicated, how its integrity was kept and how its originator was identified (art. 9).

In the United States, the ESIGN Act provides that a signature, contract or record “may not be denied legal effect, validity, or enforceability solely because it is in electronic form” (15 U.S.C. 7001(a)), with exceptions such as wills, family law matters and certain notices. The Uniform Electronic Transactions Act lets electronic records and signatures meet writing and signature rules when the parties have agreed to deal electronically.

Why written agreements get challenged: signature, date, content

Written agreements are attacked on three fronts: the signature, the date and the content. Most disputes go after the evidence rather than the contract law, so whoever relies on the document must be ready to prove its origin, date and integrity. Those disputes increasingly involve files: according to the 2025 EU Justice Scoreboard, nine Member States now allow evidence to be submitted digitally in civil, commercial, administrative and criminal cases, up from six in 2024.

Who signed

A paper signature can be denied, and an electronic one invites the claim that someone else used the account or the phone. Your position depends on how the signer was identified, and a disputed signature often becomes a question of who has to prove what.

When it was signed

A typed date is only the parties’ own statement, and the real date matters for deadlines, for priority over a later agreement and toward creditors, where backdating is a familiar argument. Showing that a file existed on a certain date takes independent proof, such as a qualified timestamp.

Whether the text changed

A PDF can be edited, and two inboxes can hold two versions that both look final. Courts look at how the integrity of the information was preserved, and a copy with no verifiable history faces authenticity challenges that a protected original avoids.

Use case

Digital signing of documents and contracts with legal validity

With TrueScreen you prepare the agreement in the Portal and the signer signs in the TrueScreen App, with simple or advanced e-signatures.

Discover more →

How to make a written agreement legally binding and harder to dispute

To make a written agreement legally binding, check that it records a real contract and respects any form the law requires, then sign and store it in a way you can prove later. A binding agreement comes from the contract basics, while one that holds up in a dispute comes from the evidence you collect at signing.

1. 1

   Write down every element of the contract

   Identify the parties fully and set out what each one promises, the price or other consideration, the deadlines and how the agreement ends, then date the document and give each party a signature block.

2. 2

   Check whether the law requires a special form

   Real estate, guarantees, some consumer contracts and documents for public registers may need a specific form, witnesses, a notary public or, in some EU countries, a qualified electronic signature. In those cases, talk to a lawyer in the relevant jurisdiction before anyone signs.

3. 3

   Use a signature method that identifies the signer

   A typed name shows intent but says little about who typed it. A signature method that identifies the signer, for example with a one-time code (OTP) or a video check, links the signature to an identified person and leaves a record of the signing process.

4. 4

   Fix the date and integrity of the final file

   Under eIDAS, a qualified timestamp enjoys a presumption that its date and time are accurate and that the data it is bound to is intact (art. 41), and like any presumption it can be rebutted. Digital notarization with TrueScreen applies an official digital seal and a qualified timestamp to the file, or to its hash alone (hash notarization) when the file must not leave your systems. It fixes the file’s certain date and makes any later change detectable. It proves the file existed in that form from that moment on, not who wrote it.

5. 5

   Keep the evidence together

   Store the signed file, its certification, the signing record and the related messages in one place, and work from the certified original rather than forwarded copies. An intact digital provenance lets you show, years later, that the document in court is the one the parties signed.

How can you prove when a signed agreement existed and that it has not changed?

TrueScreen, the Data Authenticity Platform, helps document both: the TrueScreen Portal prepares the agreement and sends the signature request, the signer signs in the TrueScreen App after being identified with a one-time code (OTP) or with video signature, and the certification carries an official digital seal and a qualified timestamp, recognized internationally.

Signing records who agreed, and the certification with seal and timestamp records when the file existed and whether it has changed since.

Signature in the TrueScreen App

The TrueScreen digital signature service offers simple and advanced electronic signatures on all plans for signing contracts and documents. You prepare the document in the Portal and send the request, and the signer signs in the App, which links the document to the signer’s identity.

Digital notarization in the TrueScreen Portal

Digital notarization in the TrueScreen Portal works on any file from your computer. When the file must not leave your systems, hash notarization certifies only its hash. When you certify a file, every certification comes with a technical report that a third party can read and check independently.

What it does not prove

Digital notarization is not a notarial act and does not replace a notary’s authentication, and TrueScreen is neither a notary nor a trust service provider nor a certification authority. The certification makes later changes detectable without preventing them, and it does not prove who wrote the document or that its content is true. Where national law requires a qualified electronic signature or a notarial deed, you need other tools. Any evidence can be challenged, and its weight is for the court to decide.

Example: a payment plan with a client

A small business agrees a payment plan with a late-paying client, prepares it in the Portal, and the client signs in the App with a one-time code. If the client later denies signing or claims different installments, the business can show who signed and how they were identified, when the file existed, and that it has not changed since.

Conclusion