An injury matter may involve electronically signed engagement agreements, authorizations, declarations, releases, settlement documents, medical-record requests, or other records. A typed name, image of a signature, platform certificate, email, checkbox, and downloaded PDF can carry different information. The signed file must be tied to the person, authority, version, attachments, and signing process actually used.

An electronic-signature packet should connect the signer, authority, exact document version, attachments, signature event, security procedure, certificate, delivery record, later change, and unresolved attribution question.

Identify the exact record before evaluating the signature

  • Document title, matter, parties, sender, intended signer, document ID, page count, attachments, exhibits, revision date, and version label
  • Native platform file, signed PDF, unsigned preview, email attachment, portal copy, certificate, audit log, and printed copy preserved separately
  • File name, byte size, creation and modification information, download date, source account, and file hash recorded when available
  • Difference in text, page count, attachment, initials, signature field, or effective date placed in a version comparison rather than assumed immaterial

Do not treat electronic form as the only legal question

North Carolina's Uniform Electronic Transactions Act addresses electronic records and signatures under its scope. Section 66-315 states that the Article does not require electronic use and applies to transactions between parties that agreed to conduct them electronically. Section 66-317 provides that a record or signature may not be denied legal effect solely because it is electronic. Other applicable law, the parties' agreement, document content, authority, consent, and circumstances still matter.

Build the signer-attribution record

  • Signer's legal name, role, capacity, organization, relationship to the injured person, and authority claimed
  • Account identifier, email or telephone used, authentication step, access code, identity question, security procedure, device or network information when lawfully available, and person who supplied access
  • Date, time, time zone, sequence of views or consents, signature adoption, initials, completion, cancellation, decline, or failed attempt
  • Shared device, forwarded link, proxy, guardian, estate, business, minor, language assistance, or accessibility accommodation identified for legal review rather than resolved by assumption

Section 66-319 addresses attribution and effect, including whether an electronic record or signature was the act of the person and the role of security procedures, context, circumstances, and agreement. Preserve the evidence of the act; do not state that a platform label by itself resolves identity, authority, consent, or legal effect.

Keep the certificate and audit trail with the signed file

  • Envelope or transaction ID, document ID, signer and sender events, timestamps, authentication method, status, completion certificate, and platform version
  • Delivery email, access link, reminder, expiration, bounce, resend, download, completion notice, and receipt confirmation linked to the same transaction
  • Certificate file and audit export retained in their native form rather than copied only as screenshots
  • Missing event, inconsistent time zone, altered PDF, detached certificate, regenerated download, or platform correction retained as a visible issue

Verify attachments and incorporated terms

  • Every exhibit, schedule, disclosure, authorization, fee term, scope description, signature page, and referenced policy listed by exact version
  • Initial or acknowledgment fields tied to the text shown at that point in the workflow when the platform preserves it
  • Attachment added, removed, replaced, or corrected after the initial transmission documented with a new version and notice record
  • Counterpart signatures, later amendment, revocation, termination, or superseding document linked without overwriting the earlier packet

Preserve errors and correction steps

  • Wrong signer, wrong email, incomplete field, misspelled name, omitted attachment, duplicate envelope, expired link, rejected signature, or accidental submission recorded
  • Date and method of notice, person contacted, instruction received, withdrawal or cancellation, corrected document, and new transaction ID
  • Original erroneous record retained unless lawful policy requires another treatment, with access limited as appropriate
  • No conclusion that a correction automatically cancels, validates, or replaces an earlier record without reviewing the applicable law and agreement

Distinguish authentication from the ultimate dispute

North Carolina Rule of Evidence 901 addresses evidence sufficient to support a finding that a matter is what its proponent claims. A signature packet can preserve identifying characteristics, witnesses, system events, and source files, but it does not by itself decide admissibility, enforceability, authority, consent, scope, or whether the document controls the dispute.

North Carolina Rule of Professional Conduct 1.5 includes writing and signature requirements for contingent-fee agreements. The related engagement-agreement guide explains how to read the parties, scope, authority, fees, expenses, communication, and termination terms. This page owns only verification of the electronic signing record and exact version.

Rosensteel Fleishman Car Accident & Injury Lawyers provides general information about North Carolina personal-injury matters involving disputed electronic records. The legal effect of a signature or document depends on the applicable law, actual transaction, authority, content, and evidence.

Sources