A customer signature proves that someone signed. On its own, it doesn't prove what was done, what was found, or what the customer agreed to pay for. Real proof of service is a signature plus a record of the work: a completed checklist, before-and-after photos, notes on what was found, and the time it happened, all tied to the job. When a charge is disputed months later, that full record is what you'll need.
Most service businesses learn this the hard way.
The dispute that starts with "I never agreed to that"
It's March. A customer's card company sends a dispute notice for a $640 repair from December. The customer says the work wasn't done, or that they only agreed to the $149 diagnostic, not the repair.
You pull the job. There's a signature on it. You feel better for about ten seconds, until you realize the signature is on a blank completion screen. It doesn't say what was repaired, what the customer was told, or what they approved. It shows that somebody in the house tapped a phone.
That's the gap. A piece in Contractor Magazine put it plainly:
"A signature answers one question: was someone there. It doesn't answer any of the questions that matter in a dispute: what broke, what was done about it, how long it took, or which parts got consumed doing it."
(Contractor Magazine, August 2026.)
What card disputes actually ask for
If a customer disputes a card charge, the decision is made by their bank, not by you or your payment processor. Stripe's dispute reason code guide says so directly: "The cardholder's bank, not Stripe, decides the outcome of each dispute."
For a claim that services weren't received, the evidence that guide suggests includes "Proof of service completion: Provide appointment records, work logs, or check-in confirmations." Where the customer signed for or confirmed the service, that acceptance is listed as evidence too.
Notice the order. The work record comes first. The signature supports it.
What real proof of service looks like
For a trade business, a job record that holds up has five parts.
1. What was agreed before the work. A signed quote, or at least a written scope the customer saw. If the job grew on site, a record that the customer agreed to the change.
2. What was checked and done. A completed checklist tied to that job: inspection items, readings, what passed and what didn't. "Replaced capacitor" is a note. A checklist with the measured values before and after is proof.
3. What it looked like. Before-and-after photos, taken on the job and attached to the job. The corroded fitting. The new one. The model and serial tag.
4. When it happened. Times on the job, photos and completion. A record written three days later from memory is worth much less.
5. That the customer saw it. A signature on a sign-off that states what was done. Or, if they wouldn't sign, a record that they refused and why.
Any one of these is weak on its own. Together, they tell the story without you having to.
Why paper and separate apps lose this
The carbon-copy ticket has all five parts in theory. In practice it's half filled in, written on the tailgate, stuffed in the truck and illegible by February.
A separate form app is better, but it has its own problem. The form lives in one system and the job in another. When the dispute arrives, someone has to find the right form for the right job and hope the times line up.
The record is strongest when it builds itself as the work happens, on the job.
Make the record automatic, not optional
The hardest part isn't knowing what to capture. It's getting it captured on the ninth job of a long day.
- Attach the checklist to the job, not to a clipboard. The tech sees it when they open the job.
- Make the important ones required. If a tech can close the job without the checklist, sometimes they will.
- Ask for the signature at the end, on the same record. The customer signs next to what was done.
- Handle refusals honestly. "Customer refused: tenant not authorized to sign" beats a blank line or a scribble.
- Keep photos on the job, not in the tech's camera roll.
We cover what to put on the form itself in job completion form: what to include, and what to do when there's no signature in when a customer refuses to sign.
A ten-job audit you can do this week
Before you change anything, find out where you stand. Pull ten completed jobs from last month at random, and for each one ask:
- Could you tell, from the record alone, what the customer asked for?
- Could you tell what the tech found and what they did?
- Is there a photo of the finished work?
- Is there a signature, and does it sit next to a description of the work?
- If the job changed on site, is there a record the customer agreed?
- Could you find all of it in under two minutes?
Most shops score well on the first question and badly on the last three. That's normal, and it tells you what to fix first. If photos are the gap, make them part of the checklist. If signatures sit on blank screens, change the sign-off so it lists the work. If the records are scattered, get them onto the job.
Run the same audit a month after you change the process. The difference is usually obvious, and it's the best argument you'll have for the techs who think the new form is extra paperwork.
What this doesn't do
Better records don't make every dispute go away, and nothing guarantees how a bank will decide. What they do is give you something to send, fast, instead of a signature on a blank screen and a tech trying to remember a job from December.
They also stop a lot of disputes from starting. A customer who signed a sign-off listing the repair is less likely to claim it never happened.
How FSM Navigator handles it
FSM Navigator is one app for the whole customer lifecycle, from first booking to renewals: the signed quote, job, invoice and payment already live together. Job forms and signatures, on the Pro and Enterprise plans, add the rest of the record to the same job:
- Your checklists attach to jobs by job type, or when you approve a service request for a pricebook service, or by hand.
- A job can't be completed with a required form unfinished. Owners and managers can override with a written reason, and the override goes into the audit log.
- Turn on "Require customer signature to complete", and the customer signs on the tech's phone after seeing the agreement sentence. If they won't, the tech records the refusal and reason.
- Photo items ask for pictures the tech took on the job, so the before and after sit next to the check they prove.
- Submitted forms print on a signed-forms page of the job's invoice PDF, and customers see them in the customer portal.
The mobile app saves answers and signatures on the phone when there's no signal, and syncs them when the connection comes back.
FAQ
Is a customer signature proof of service?
It shows someone signed. Combined with a completed checklist, photos and timestamps on the same job, it is much stronger evidence of what was done.
What evidence helps with a card dispute for a service?
Records that the service was completed, such as appointment records and work logs, and any confirmation from the customer. The cardholder's bank decides the outcome, not you or your payment processor.
Should the sign-off say what was done?
Yes. A signature next to a list of the work is worth far more than a signature on a blank screen.
What if the customer wasn't home to sign?
Record that the signature wasn't collected and why, then make the rest of the record strong: a finished checklist, after photos and a plain note of what was done.