Garages lose damage disputes because they can't prove what the car looked like when it arrived. Software can fix that, but only if logging is faster than the chalk it replaces.
That means photos at intake, one tap for each job step, and a job history nobody can edit afterwards. Get this right and a dispute that used to cost a repaint takes ten seconds.
This guide explains why most garage software fails, what to build instead, and why this matters even more in Algerian workshops.
Why do garages lose damage disputes?
A car arrives at a body shop for a scratch on the rear door. Four days later, the owner collects it and points at a mark on the front wing.
They say it was not there before. The shop owner is sure it was. Nobody has any proof.
The shop owner pays, nearly every time. Not because they are wrong, but because they can't prove they are right. And in a neighbourhood where reputation travels faster than any invoice, arguing with a customer is a losing trade even when you win.
That loss is not rare. It is quietly absorbed, month after month, and almost nobody calls it a software problem.
Why does most garage software fail?
Picture what usually happens. A developer builds a job management system with a long form: vehicle, customer, parts, labour, condition on arrival, photos. It is complete and correct.
A month later, the shop is still running on chalk.
The failure is not technical. The developer treated the worker's time as free.
The man doing tsbiga (painting) has paint on his hands and wears gloves. He stands next to a car under lights, and is judged on cars finished per day. A form with fourteen fields is a tax on the only thing he is paid for.
So he fills it in at the end of the day from memory, badly, or not at all.
That data is fiction. And fiction in a dispute is worse than nothing, because it looks official.
Meanwhile the chalk works. A number on a windscreen and a note on a wall cost no time and never reject your input. Anything that replaces chalk has to beat it on speed, not on completeness.
The rule: recording a step must take a few seconds, with one thumb, dirty hands and no typing.
How do chalk, form apps and a one tap timeline compare?
| Chalk and memory | Form heavy app | One tap, unchangeable timeline | |
|---|---|---|---|
| Time to record a step | Seconds | Minutes of typing | Seconds, one tap |
| Who records it | Whoever remembers | Usually nobody | The worker, at the moment it happens |
| Data after a week | Gone | Written later from memory | Timed and intact |
| Proof of damage on arrival | None | A blank field | Photos tied to arrival time |
| Outcome of a dispute | The owner pays | The owner pays | The owner shows the timeline |
| Tracking parts | In someone's head | Typed if convenient | Recorded when fitted |
| Do workers use it? | Always | Hardly ever | Yes, because it is faster than chalk |
The middle column is where most software for traditional trades dies. It asked a man holding a spray gun to become a typist.
What should garage software record, and how?
Store what happened, step by step, never just the current status.
The common mistake is one job record with a "status" that keeps getting overwritten: received, then in progress, then painting, then done. Each change erases the one before. At the end you know where the car is, but nothing about how it got there, which is exactly what a dispute needs.
Instead, keep a timeline that can only be added to.
Car received at 08:12 with four photos. Bumper removed at 09:40. Filler at 11:05.
Painted at 14:20 by this worker. Ready at 16:50. Nothing is ever edited.
When the customer points at the front wing, the owner opens the 08:12 photos, and the conversation is over.
Think of it like a football match report. It does not just say the final score. It lists every goal, with the minute and the player.
If anyone argues later, the report settles it.
What makes garage software harder in Algeria?
Payments are cash, and often partial. Say a customer leaves 10,000 DZD as an advance on a 35,000 DZD job, pays 15,000 DZD when they see the primer, and the rest on collection, sometimes. No card, no bank record. If the system keeps one amount that people overwrite, whoever typed last wins.
Parts are the bigger risk. A bumper, a headlight, a set of clips, bought in cash and fitted to one car. If the link between a part and a job lives only in a worker's memory, the owner can't tell a part fitted from a part broken or a part that walked out the door.
Workers are not hired for software. Many prefer Arabic or Darija to French, and turnover is real. A system that needs reading a busy screen excludes the people who hold the information. Icons, photos and one tap buttons are not decoration here. They decide whether you get data at all.
The law already values unchanged records. For a merchant's books, article 11 of the Algerian Commercial Code requires keeping them in date order "without blanks or alterations of any kind" (Commercial Code, Book I). A job history that can't be edited follows the same spirit.
What should you build for a garage?
| Feature | How it works | Why |
|---|---|---|
| Photo intake | The first screen is the camera: four to six photos on arrival, stamped with time and job | Settles most "it wasn't there before" disputes |
| One tap steps | Big buttons: Received, Stripped, Filled, Primed, Painted, Assembled, Ready | Faster than chalk, so workers use it |
| Parts tiles | Parts the shop uses shown as photo tiles, tap to attach to the job | Tracking a part costs less effort than not tracking it |
| Payments as events | Each cash payment added to the same timeline | The balance owed calculates itself |
| Owner view | One screen: cars in the shop, their stage, money outstanding | What the owner actually needs |
| Works offline, in Arabic | Saves on the phone and syncs when the signal returns, right to left | Workshops lose signal |
And never build an Edit button. If a step or a payment is wrong, the worker adds the correct one after it, and the timeline shows both.
The owner's notebook already worked this way, with a crossed out line and a new number beside it. I explain the database pattern in never edit a money record.
This is close to what I built in AutoTrack, an internal tool for a car business. It tracks staff, tasks and client history, and is shown on my homepage.
What mistakes do garage software projects make?
- Starting with a complete form. Start with the camera and a few buttons.
- Storing only the current status. Store every step instead.
- Letting anyone edit the past. Add corrections as new events.
- Designing for the owner's laptop. Design for a worker's phone with gloves on.
- Ignoring parts. For many shops, missing parts cost more than lost labour.
What should you do this week?
- Today: count last month's disputes about damage, and what each one cost you.
- This week: start photographing every car on arrival with a phone, even without software.
- This week: list the seven steps every job goes through in your shop.
- This month: test a one tap timeline with one worker for one week.
- Then: add parts tiles and cash payments to the same timeline.
If your shop still tracks everything on WhatsApp and paper, read when WhatsApp and Excel stop working first.