Examinations
Electronic signature disputed: how do you prove who signed, and what does a forensic examiner check?
An electronic signature has legal effect, but the party that relies on it must show that it was the act of the person named. In Fabian v. Renovate America (Cal. Ct. App. 2019) a contract marked "DocuSigned by:" with an identity verification code was not enough, because nobody explained how the signature got there. In Espejo (2016) a declaration that described the login, the password reset and the IP address was enough.

Is an electronic signature legally valid?
Yes. Under 15 U.S.C. 7001(a) a signature or contract may not be denied legal effect solely because it is in electronic form. Validity of the form does not prove who made the signature.
The federal E-SIGN Act states the rule in two parts. A signature, contract or other record relating to a transaction in or affecting interstate or foreign commerce "may not be denied legal effect, validity, or enforceability solely because it is in electronic form". A contract may not be denied legal effect "solely because an electronic signature or electronic record was used in its formation." Section 7001(b)(2) adds that the statute does not require any person to agree to use or accept electronic records or electronic signatures.
The definition is broad. Under 15 U.S.C. 7006(5) an electronic signature is "an electronic sound, symbol, or process, attached to or logically associated with a contract or other record" and "executed or adopted by a person with the intent to sign the record." The California version of the Uniform Electronic Transactions Act uses nearly the same words in Civil Code section 1633.2(h). A typed name, a click on a button and a drawn squiggle all fit, as long as a person adopted them with the intent to sign.
Both definitions assume that a particular person executed or adopted the symbol or process. Whether that happened is a question of fact.
Who has to prove that the person signed?
The party that relies on the signature. Under California Civil Code section 1633.9(a) an electronic signature is attributable to a person if it was the act of the person, which may be shown in any manner.
Section 1633.9(a) is the attribution rule of the Uniform Electronic Transactions Act as California enacted it. An electronic record or signature is attributable to a person "if it was the act of the person." The act of the person "may be shown in any manner, including a showing of the efficacy of any security procedure" applied to determine the person to whom the record or signature was attributable. Under subdivision (b) the effect of an attributed signature "is determined from the context and surrounding circumstances" at the time of its creation, execution or adoption.
The statute defines a security procedure in section 1633.2(n): a procedure employed for the purpose of verifying that an electronic signature, record or performance is that of a specific person, or for detecting changes or errors in the information in an electronic record. It includes a procedure that requires the use of algorithms or other codes.
California courts have set out the order of proof in disputes over arbitration agreements. In Espejo v. Southern California Permanente Medical Group and in Fabian v. Renovate America, Inc. the party seeking arbitration met its initial burden by attaching the signed agreement. Once the other side challenged the signature, that party had to prove by a preponderance of the evidence that the signature was authentic. The Fabian court noted, quoting Ruiz, that the burden of authenticating an electronic signature is "not great".
What was missing in Ruiz v. Moss Bros.?
An explanation. As the Espejo opinion recounts, the employer's business manager asserted that the employee had electronically signed the agreement and did not explain how she reached that conclusion. The signature, name and time stamp were not enough.
Ruiz v. Moss Bros. Auto Group, Inc. (2014) 232 Cal.App.4th 836 is the decision the later California cases start from. This article relates it as the Espejo and Fabian opinions describe it. As the Espejo court summarized it, the employer's business manager "summarily asserted" that the employee electronically signed the arbitration agreement and "did not explain how she arrived at that conclusion." The employee claimed that he did not recall signing the agreement.
On that record the electronic signature, the name and the time stamp were "insufficient to support a finding that the electronic signature was, in fact, 'the act of' Ruiz." The Espejo opinion also records what the employer could have explained: that the signature could only have been placed on the agreement by a person using the employee's "unique login ID and password", and that the date and time printed next to the electronic signature indicated when it was made.
What evidence was enough in Espejo?
A declaration by a systems consultant that walked through each step: credentials given by phone, a forced password reset, the opt-in to sign electronically, the typed name, and the date, time and IP address recorded on the document.
Espejo v. Southern California Permanente Medical Group, No. B262717, was decided by the California Court of Appeal, Second Appellate District, Division Four, on April 22, 2016. The plaintiff recalled signing his employment contract electronically but said that he did not recall seeing or signing the dispute resolution procedure that the employer presented with the contract through its online applicant page.
The employer's declarant, Tellez, a systems consultant who maintained the online system for physician employment contracts, described the process. A unique username and password were provided "directly and orally to the applicant" by telephone. The applicant had to reset the password to one of his own choosing before he could proceed. He had to opt to complete the documents with an electronic signature. The linked documents could be reached only after logging in with those credentials. He typed his name, and the entry populated the signature line. The document was finalized with his name, the date, the time and the IP address where he signed: May 22, 2011, at 3:16 p.m., the same IP address as on the employment contract.
From those steps she concluded that the name "could have only been placed" on the documents by someone using his unique username and password. The court held that the declaration established that the signature was "the act of" Espejo under section 1633.9(a) and called the description of the security precautions the "critical factual connection that the declarations in Ruiz lacked." The Court of Appeal reversed the order that had denied the petition to compel arbitration and remanded the remaining issues to the trial court.
Why did a DocuSign contract fail in Fabian v. Renovate America?
Because the company offered the marked contract and a conclusory declaration, with no evidence of who sent the contract, how the signature was placed, who received it or how identity was verified.
Fabian v. Renovate America, Inc., No. D075519, was filed by the California Court of Appeal, Fourth Appellate District, Division One, on November 19, 2019, and certified for publication on December 4, 2019. The plaintiff sued over solar panels and alleged that the company had "signed" her name on a financing agreement and never gave her documents to sign.
The company moved to compel arbitration on a contract dated February 28, 2017. The contract bore the printed name of the plaintiff, the words "DocuSigned by:", a 15-digit alphanumeric character and the line "Identity Verification Code: ID Verification Complete." Its only other evidence was a declaration of a senior director of compliance operations.
The court found a "critical gap in the evidence". The company offered no evidence about the signing service: who sent the contract, how it was sent, how the signature was placed, who received it, how it was returned or how identity was verified. The declaration "summarily asserted" that the plaintiff had entered into the contract, did not state anywhere that she actually signed it, and did not explain the significance of the 15-digit characters or of the words "DocuSigned by". The order denying the motion to compel arbitration was affirmed.
The opinion contains no general ruling on the reliability of the signing service. The court wrote that the marks on the contract, standing alone, were not sufficient to compel a result in the company's favor as a matter of law, and it called the company's DocuSign authentication argument unsupported and unpersuasive.
How is a signing record authenticated under the Federal Rules of Evidence?
By evidence sufficient to support a finding that it is what the proponent claims: testimony or a certification describing the system. Rule 902(13) lets a qualified person certify a record generated by an electronic process.
Rule 901(a) sets the standard, and Rule 901(b)(9) gives the example that fits a signing platform: "Evidence describing a process or system and showing that it produces an accurate result." Rule 901(b)(4) adds the distinctive characteristics of the item, taken together with all the circumstances.
Rule 902(13) makes self-authenticating "A record generated by an electronic process or system that produces an accurate result", as shown by a certification of a qualified person that meets the certification requirements of Rule 902(11) or (12). The proponent must give the adverse party reasonable written notice before the trial or hearing and make the record and certification available for inspection.
The 2017 committee note marks the limit of such a certification. It must contain information that would be sufficient to establish authenticity if the person testified at trial. And it establishes authenticity only: in the note's example of a web page, the certification proves how the page was retrieved, while the defendant may still argue that someone else posted the statement. For a spreadsheet the note says that "the authentication establishes only that the output came from the computer." A certified signing log proves that the log is the platform's record. Who sat at the keyboard is a separate question.
What does a forensic examiner check in a disputed electronic signature?
The record of the steps the platform required, whether the document offered in court matches the stored one by hash value, and what the person's devices hold about who logged in and when.
The first object is the platform's record of the transaction. Espejo and Fabian name the points a court looks for: who sent the document and how, what credentials or codes were required, whether the signer had to set a password of his or her own, what the signer did on the page, and the date, time and IP address recorded at signing. The IAE digital forensics page names two checks that apply to any such record: which tool and version extracted the data, and whether the timestamps were read in the right time zone.
The second object is the document. An electronic record can be compared with a later copy by hash value: under the 2017 committee note to Rule 902(14), identical hash values for the original and the copy reliably attest that they are exact duplicates. The note adds the reverse: if the hash values are different, the copy is not identical to the original.
The third object is the signer's side: the phone or computer and the account that was used. The IAE page describes this work as establishing what a device stored and who logged in, by event logs and browser history.
A log ties a session to an account. Section 1633.9(a) lets the act of the person "be shown in any manner", so the question of who was using the account is decided on all the evidence. In Espejo the answer came out of the procedure: credentials given orally to the applicant and a password that the applicant had to reset to one of his own choosing.
What can a person who denies signing do?
State the denial in a declaration, request the platform's records and the company's evidence of its signing process in discovery, and have the devices and accounts of the relevant date examined.
In the California cases the challenge began with the person's own declaration. In Ruiz, as the Fabian opinion describes it, the employee claimed in his opposing declaration that he did not recall signing the agreement. Fabian declared that she "did not sign the Contract physically or electronically." Once she had declared that, the company had to prove by a preponderance of the evidence that the electronic signature was authentic.
The records are obtained under Rule 34 of the Federal Rules of Civil Procedure in a federal case. The request must describe each item with reasonable particularity, and electronically stored information is produced in the form in which it is ordinarily maintained or in a reasonably usable form. A request can therefore ask for the transaction log and the stored document as files, in addition to the printed certificate. Under Rule 34(c) a nonparty, such as the signing service, may be compelled to produce documents as provided in Rule 45.
The person's own devices are evidence of the same kind as the company's records. The IAE page lists what an examiner reads on them: what the device stored and who logged in, by event logs and browser history.
What must the examiner's report contain in federal court?
All opinions with their basis and reasons, the facts or data considered, exhibits, qualifications, prior testimony and compensation, under Rule 26(a)(2)(B). The testimony must meet Rule 702.
Rule 26(a)(2)(B) requires from every retained expert a written report prepared and signed by the witness. The facts or data considered are one of its required parts. For a forensic report the IAE page names what a reviewer looks for there: matching hash values for the image and the source, the tool and version that extracted the data, and the time zone in which the timestamps were read.
Under Rule 702 the party offering the examiner must show the court that it is more likely than not that the testimony is based on sufficient facts or data, is the product of reliable principles and methods and applies them reliably to the facts of the case. The IAE page ties the last of those conditions to the review of an opposing report: the reviewer checks whether each conclusion follows from the data.
A report intended solely to contradict or rebut the other side's expert on the same subject is due within 30 days after that side's disclosure, absent a stipulation or a court order, under Rule 26(a)(2)(D).
What does IAE do when an electronic signature is disputed?
IAE prepares a digital forensics expert report on the client's questions about the record, the document and the devices, or a review of the opposing forensic report. The signed PDF follows in up to 5 business days.
The IAE digital forensics page lists what the examiner works with: creation and modification dates from document and file system metadata, traces of editing in PDFs, comparison of a copy with the original by hash value, and what a device stored and who logged in, from event logs and browser history. IAE frames the questions by the device, the application and the event the case needs to establish, and confirms the questions, the devices and how the data reach the examiner before work starts.
The secretariat confirms receipt the same day. IAE then confirms the format, the cost, the deadline and the specialist from its registry, and the client approves the candidate and the CV before work starts. The signed PDF is issued in up to 5 business days after the format and cost are confirmed, depending on the volume of data; cases with tight deadlines have a 48-hour rush.
Every specialist is a member of the public IAE registry and can be verified by Member ID or QR code, and confirms in the document that he or she has no interest in the outcome of the case. IAE is not a law firm and does not advise on case strategy; whether to subpoena the signing service is a question for the client's attorney. A report is evidence that the court weighs with the rest of the record, and neither IAE nor the examiner guarantees the outcome.
Sources
- 15 U.S.C. 7001, General rule of validity (LII, Cornell Law School)
- 15 U.S.C. 7006, Definitions (LII, Cornell Law School)
- California Civil Code section 1633.2, definitions (California Public Law)
- California Civil Code section 1633.9, attribution of electronic record or signature (California Public Law)
- Espejo v. Southern California Permanente Medical Group, No. B262717 (Cal. Ct. App. Apr. 22, 2016) (Justia)
- Fabian v. Renovate America, Inc., No. D075519 (Cal. Ct. App. Nov. 19, 2019) (Justia)
- Federal Rules of Evidence, Rule 901, Authenticating or Identifying Evidence (LII, Cornell Law School)
- Federal Rules of Evidence, Rule 902, Evidence That Is Self-Authenticating, with 2017 committee notes (LII, Cornell Law School)
- Federal Rules of Evidence, Rule 702, Testimony by Expert Witnesses (LII, Cornell Law School)
- Federal Rules of Civil Procedure, Rule 26 (LII, Cornell Law School)
- Federal Rules of Civil Procedure, Rule 34 (LII, Cornell Law School)
Read also
All articles
How do you authenticate social media posts for court, and what does a forensic examiner add when the account is disputed?
A printout of a social media page proves that the page existed. It does not prove who wrote the post. In 2014 the Second Circuit vacated a conviction
Spyware on a phone: how does a forensic examiner find it, and what can the evidence be used for?
A forensic examination for spyware establishes whether a monitoring app is on the phone, when it appeared, what it collected and where it sent
Forensic image authentication: how does an examiner show that a photo was edited?
A photograph offered in federal court must be shown to be what the party claims it is, under Rule 901(a) of the Federal Rules of Evidence. WhenExpert examinations
Ready to discuss your case?
Send the materials: the secretariat will confirm the format, cost, deadline and the specialist within one business day.

