What to do if a customer says "I never signed that"

This is uncomfortable in the moment, and the instinct is often to just resend the signed PDF and hope that settles it. It usually doesn't, because the signed document alone isn't actually the evidence that matters here. Here's the sequence I'd actually follow.

Evidence to pull first

Before responding to the customer at all, pull the full audit trail for that specific document, not just the final signed PDF. A proper e-signature tool generates this automatically, and it should show: the exact email address the signing link was sent to, timestamps for when the document was sent, opened, and signed, the IP address and device used at signing, confirmation of which specific document version was presented (important if the contract was revised at any point before signing), and a technical integrity check confirming the signed document hasn't been altered since. If you used any identity verification step, an SMS code or ID check, pull that record too. This is the evidence that actually answers "did this person sign this document," far more than the signed PDF on its own.

Also worth checking: whether the email address the document was sent to is genuinely the customer's own, controlled address, or something shared, outdated, or possibly accessed by someone else, since that's relevant to whether their denial might actually have merit.

Steps to take

1. Clarify exactly what they're disputing. "I never signed that" sometimes genuinely means "I don't recall agreeing to this specific clause" rather than "I never interacted with this document at all." Ask directly what they're disputing before assuming it's a full denial of the signature event.
2. Review the audit trail calmly before responding. Confirm for yourself what it actually shows before you present anything to the customer, so you're not caught off guard by a gap in the evidence you didn't know about.
3. Present the specific evidence, not a general assurance. Rather than saying "our system shows you signed it," share the actual details: the email address, the date and time, confirmation the document matches what was sent. Specific evidence is harder to argue against than a general claim.
4. Stay factual, not defensive. This can feel personal, especially with a client you've worked with, but the conversation goes better focused on what the record actually shows rather than on whether you trust them.
5. Involve a lawyer if the stakes justify it. For a high-value contract, or if the customer is suggesting legal action or refusing to pay based on the dispute, get a lawyer involved early rather than trying to resolve a genuinely contentious dispute entirely on your own.
6. Document the resolution either way. Whether it's resolved by the audit trail settling the question, or by some other agreement you reach, keep a record of how it was resolved.

How to prevent it happening again

• Send to a specific, verified individual's email, never a shared or generic inbox, which removes a lot of ambiguity about who actually received and signed the document.
• Add identity verification for higher-stakes contracts, an SMS code or ID check, so you have stronger proof of identity, not just access to an inbox, if a dispute comes up later.
• Confirm consent to electronic signing explicitly, a simple statement in the contract or signing flow, rather than assuming it's implied.
• Keep the audit trail attached to every signed document, not stored separately where it could get lost or disconnected from the file it supports.
• Walk through the document with the signer before sending it for anything significant enough that a later "I didn't realize what I was agreeing to" dispute would actually hurt you, since prevention here is often about clarity at signing time, not just evidence after the fact.

The part worth knowing

A genuine signature dispute is rarer than people fear, and most "I never signed that" moments resolve quickly once a specific, factual audit trail is put in front of the person, because it's hard to argue against a timestamp and an email address that are genuinely theirs. The cases that actually escalate tend to be the ones where the underlying e-signature process was weak in the first place, a shared email address, no real identity check, a document that got revised without a clear record of which version was actually signed. That's exactly why the prevention list above matters more than any clever thing you could say in the moment of a dispute. For how a court weighs this kind of evidence, see what makes an e-signature valid in court.

A worked example

Say a client refuses to pay a final invoice, claiming they never actually signed the change order that added the extra scope you billed for. You pull the audit trail and find it shows the document was sent to the client's general company inbox, info@theirsite.com, rather than to a specific named person, and the signature event itself has no name attached beyond "signed via link." This is a genuinely weaker position than you'd want, because it's harder to pin down exactly who at the company took that action, which is precisely the kind of gap a client disputing in bad faith could exploit. Compare that to a case where the change order went specifically to the project lead's named, verified email, with an SMS code confirming their phone number at the moment of signing. That second scenario resolves the dispute almost immediately, because the evidence of who specifically agreed is concrete rather than ambiguous. The lesson isn't that the first scenario makes the contract invalid, it's that the quality of your evidence, not just its existence, is what determines how quickly and cleanly a dispute like this actually gets resolved.

When the dispute is really about something else

Worth naming honestly: sometimes "I never signed that" isn't really about the signature at all. It can be a way of expressing "I'm unhappy with this outcome and I'm looking for any lever to push back," especially around payment disputes. If the audit trail is airtight and the customer still won't accept it, that's often a sign the actual disagreement is about the work, the price, or the relationship, not genuinely about whether a signature happened. Recognizing that early changes how you respond, from relitigating the signature evidence over and over, to addressing what's actually bothering the customer directly, which is often a faster and less adversarial path to resolving things.

A quick self-check when a dispute first comes in

Before responding to the customer, ask yourself: do I actually have the complete audit trail for this document in front of me, or am I about to respond from memory? Is the email address on file genuinely theirs, not a shared or outdated one? And is there any chance this is really a dispute about the work or the price, dressed up as a signature question? Answering these three honestly, before you say anything to the customer, keeps you from either overreacting to a weak position or underreacting to a genuinely contentious one.

How I'd approach this

When I set up a client's signing process, I treat "what happens if this gets disputed" as a design question from the start, not an afterthought. That means making sure the audit trail is genuinely complete, the recipient is specific and verified, and identity verification is switched on for anything that would actually hurt if it were challenged later. Most disputes I've seen resolve in minutes once someone pulls up a complete, specific audit trail. The ones that drag on are almost always the ones where that record was thin to begin with, or where the real disagreement was never actually about the signature in the first place.

A final practical note

I'd rather a client bring me a thin signature dispute early, before they've already responded to the customer defensively, than after things have escalated based on an incomplete read of the evidence. The sequence above, pull the record first, clarify the real dispute, respond with specifics, works whether the audit trail turns out to be airtight or genuinely weak. What doesn't work is skipping straight to a response built on assumption rather than the actual record in front of you.

Frequently asked questions