This is a worked example, not a real person’s case. The people, the dates and the amounts are made up. The way the record is built is not — that part is how these disputes actually run.
Money & services · raised by the account holder
A phone that came back three times
The question this answers
“What should I write down when a repair keeps failing?”
Three repairs, three separate job numbers, and the same fault written down the same way each time — that repetition is what turned three unrelated visits into one continuing problem.
The situation
Nadia paid $340 to have a phone repaired in early March. It was shutting itself down without warning, usually within an hour of coming off the charger.
It came back three times over six weeks. Each visit was booked as a new job, with its own job number and its own job sheet, and each one was handled by whoever was on the counter that day.
By the third visit she was explaining the whole history from the start, to someone who had no reason to know any of it.
Which way round
She is the one raising it. The shop is not refusing anything — nobody has said no. The problem is that three visits sitting in three separate files don't look like a pattern to the person reading one of them.
A repairer, a customer and a workshop all keep the same kind of record. What changes is who has to show the sequence — and in a record, the sequence is the whole argument.
The record — 9 items over 6 weeks
as it sits in the register
Item
Their side — the repair shop
Your side — Nadia
March 2026
001 Mar 3
Your side — Nadia
First repair booked in
Job number written down at the counter · $340 paid · itemized receipt kept
002 Mar 3
Their side — the repair shop
Job sheet handed over
"Battery replaced, tested OK"
003 Mar 11
Your side — Nadia
Fault returns
Note written the same evening — what it did, what time, what she'd been doing
004 Mar 12
Your side — Nadia
Second drop-off
New job number · asked at the counter for it to be linked to the first job
005 Mar 14
Their side — the repair shop
Collected
Job sheet reads "no fault found on test"
Nothing logged for 9 days, Mar 14 to Mar 23
March–April 2026
006 Mar 23
Your side — Nadia
Fault again, photographed
Screen at the moment of shutdown, clock visible in the frame
007 Mar 24
Your side — Nadia
Third drop-off — in writing this time
Email rather than the counter · both earlier job numbers quoted
008 Apr 2
Their side — the repair shop
Email reply
Offers to look at it again · no reference to either previous job
009 Apr 8
Your side — Nadia
Summary sent
All three job numbers and dates, in order, on one page
What three of those entries actually did
Most items in a record do nothing on their own. These three carried it.
001 + 004 + 007
The three job numbers
Each visit had its own number, and to the shop that made them three unrelated jobs. Written down together in one place, in date order, they stop being three visits and become one six-week problem. Nothing else in the record does that. The numbers were the cheapest thing to keep and the only thing that connected anything.
006
The photo with the time in the frame
"It keeps shutting down" is a description. A photograph of the screen at 7:41pm is a thing that happened. She took it because she was tired of describing it, not because she thought she'd need it.
007
Moving off the counter and into email
Everything before this exists only in two people's memories. From here on, every exchange has a date on it and a copy at both ends. It is the single cheapest change anyone in this situation can make, and it costs nothing but the decision to make it.
What was missing
1 gaps. None of them sank it, and all of them were avoidable.
01
Nothing written down about the second drop-off conversation
She asked at the counter for the second job to be linked to the first. The job sheet doesn't show it was, and there's no note anywhere saying she asked. Two lines typed into her phone on the walk back to the car would have covered it. A counter conversation nobody wrote down is, as far as any record is concerned, a conversation that didn't happen.
How it ended
Settled at the counter. The shop replaced the handset rather than attempt a fourth repair.
What moved it was the one-page summary — three job numbers, three dates, the same fault described the same way. Nobody had disputed anything; the shop simply had never seen the three jobs side by side. The record didn't win an argument. It ended one that nobody had actually been having.
What to take from it — either side of this dispute
Write down the job or reference number every single time, and keep them all in one place. Each visit gets its own number, and that is exactly what makes a repeat problem invisible to the business.
Photograph the fault happening, with something in the frame showing the time. A description is your account of it; a photograph is the thing itself.
Move to writing the second time the same thing happens. Not the first — the second. That's the point at which you're dealing with a pattern rather than an incident.
A counter conversation you didn't write down didn't happen. Two lines afterwards is enough, and it takes less time than the walk to the car.
Worked example · no real person’s case · no statute cited · education on documenting, not legal advice Case 001 · published 2026-09-13 · reviewed 2026-09-13