Garage Operations Guide · Updated August 2026
How Customer Estimate Approval Should Work in a UAE Garage
Approval is not a formality at the start of a job. It is the record that settles who pays when the final invoice is larger than the estimate — and in most workshops it is the weakest part of the process.
In short
A workable approval process does four things: it prices the scope beforework starts, it captures the customer's agreement against a specific version of the estimate, it treats any revision as a fresh approval rather than an update, and it keeps the whole exchange attached to the job cardrather than on a service advisor's phone. Most disputes at collection trace back to one of those four being missing.
This guide is about the operating process. If you are looking at software for it, Avance GMS sends estimates and approval requests on WhatsApp and logs the response against the job card.
Key takeaways
- Approval attaches to a version of the estimate, not to a job in general.
- The revised estimate after strip-down is where most of the disputed money sits.
- A written approval tolerance stops small revisions from halting the bay.
- On insurance and LPO work the approver is often not the person holding the keys.
- An approval on a personal phone is a record the workshop does not own.
- "Waiting for approval" is a job state worth tracking, because it occupies a bay.
- Showing net, VAT and gross on the estimate removes a routine argument at collection.
What approval actually has to prove
When a customer questions an invoice weeks later, the workshop is being asked a narrow question: what did this person agree to, and when? Everything else in the file — the inspection photographs, the technician's notes, the parts issued — is supporting material. The approval is the thing being tested.
That means a useful approval record carries four elements. Drop any one of them and the record becomes an assertion rather than evidence.
| Element | Why it matters |
|---|---|
| Which estimate | Jobs are re-priced. An approval that does not name a version cannot be matched to a figure. |
| Who approved | The driver, the owner, the fleet supervisor and the insurer are different people with different authority. |
| Through which channel | WhatsApp, in person on a signed document, or a phone call noted by the advisor — each carries different weight. |
| Date and time | An approval logged after the work started answers the wrong question. |
The four points where approval is needed
Workshops tend to think of approval as one event. In practice a job passes through several decision points, and each one is a place where the customer's exposure changes.
| Point | What is being agreed |
|---|---|
| Check-in inspection | The vehicle's condition on arrival, signed before anything is touched — this is what closes off "that damage was already there". |
| Diagnosis charge | Whether the customer is paying for diagnostic time if they decline the repair. Cheapest thing to agree upfront, most commonly skipped. |
| Initial estimate | The priced scope: parts, labour hours, sublet work, VAT treatment. |
| Revised estimate | Additional work found once the job is open. Needs its own approval, not an amendment to the first. |
The diagnosis charge is worth singling out. A workshop that spends two hours finding an intermittent electrical fault, quotes the repair, and then hears "no thank you" has either agreed a diagnostic fee at check-in or absorbed the cost. That conversation is straightforward at the counter and awkward afterwards.
The revised estimate is where the money is lost
An inspection sees what can be seen with the vehicle assembled. Once the wheels are off and the caliper is out, the picture often changes. This is normal work, not bad estimating — but it produces the single most common dispute in a workshop, because the customer approved one figure and is asked to pay another.
A brake job that grew, and what the record needs to show
Inspection estimate: pads + labour = AED 1,450 net · VAT 72.50 · gross 1,522.50
Customer approves on WhatsApp, Tue 09:40 — logged against JC-0148
Strip-down: discs below limit, one caliper seized
Revised estimate: AED 2,780 net · VAT 139.00 · gross 2,919.00
Second approval requested Tue 11:05 — job held until received
The workshop that holds the job for 40 minutes and gets a second approval invoices AED 2,919 without an argument. The workshop that carries on because "the customer already approved the brakes" has a conversation at collection about a figure that nearly doubled, and often discounts its way out of it.
The discount is the real cost. A workshop that gives away AED 300 on one job a week to close out an approval argument is losing roughly AED 15,000 a year on a process problem, not a pricing problem.
Set an approval tolerance, and write it down
Going back to the customer for every small addition is its own problem: the job stops, the bay sits, and the customer starts to feel nickel-and-dimed. The usual answer is a stated tolerance — a band within which the workshop proceeds, above which it stops and asks again.
How a tolerance behaves in practice
Approved figure: AED 1,450 · tolerance 10% = AED 145
Revision to AED 1,540 (+90) → proceed, note the addition on the job card
Revision to AED 2,780 (+1,330) → stop, re-approve
What makes this work is that the tolerance is written on the estimate the customer approves, so the band itself is part of what was agreed. A tolerance decided privately, job by job, gives the workshop discretion it will struggle to defend.
Approval on WhatsApp, and what makes it a record
WhatsApp is how most UAE customers prefer to deal with a workshop, and a tapped approval is faster than any portal login. The weakness is rarely the channel — it is where the conversation lives.
- On a service advisor's personal phone, the record belongs to the advisor. When they leave, it leaves. When they are on leave and a customer disputes a job, nobody can produce it.
- In a shared workshop number with no job linkage, the message exists but has to be found by scrolling a thread that mixes bookings, approvals and status chatter across many vehicles.
- Logged against the job card, the approval sits with the estimate it responded to, and anyone at the counter can open it in seconds.
That last arrangement is what Avance GMSdoes: the estimate goes out from the system, the customer's reply is written back to the job card with its timestamp, and the approval history stays with the vehicle rather than with whoever handled it. It also removes the per-message API fee that makes some workshops ration their customer messaging.
Insurance and LPO jobs have a different approver
On an ordinary retail job the person who brings the vehicle usually decides. On insurance and fleet work that assumption breaks, and treating them the same way is how workshops end up holding unbilled repairs.
| Job type | Who approves | What the workshop needs on file |
|---|---|---|
| Retail | Owner or authorised driver | Approved estimate version and timestamp |
| Insurance claim | Insurer or surveyor for the covered scope; customer for the excess | Claim number, surveyor approval, separate customer agreement to the excess |
| Fleet / corporate | The named authoriser on the account, not the driver | LPO number and the approved scope it covers |
| Warranty or contract | The principal or contract holder | Authorisation reference and what falls outside cover |
The recurring failure is a fleet driver who says "go ahead" on work the LPO does not cover. The workshop does the job in good faith, and the account holder declines the line at invoicing because nobody with spending authority agreed to it. A job card that names the authoriser separately from the person who dropped off the vehicle prevents most of this.
Insurance work adds a second complication: the split between what the insurer settles and what the customer owes as excess. Those are two approvals against one job, and billing them cleanly depends on having recorded them as two things from the start.
Waiting for approval is a bay state
A job sitting unapproved still occupies a lift, a parking space and a technician's attention. Workshops that track approval as a job state — rather than as an absence of progress — tend to notice two things quickly.
- Approval turnaround is measurable. If estimates routinely sit for four hours, the bottleneck is often the estimate going out late in the day rather than customers being slow.
- Unanswered approvals need a follow-up rule. Without one, a job can sit for two days because the advisor assumed the customer would reply and the customer assumed the work had started.
Both are visible on a job board that shows how long each vehicle has been in its current state. Neither is visible in a system where the only statuses are open and closed.
Language and VAT on the estimate
An estimate a customer cannot read is not really an estimate. In the UAE that routinely means Arabic alongside English, and for many workshops Urdu as well — particularly for fleet drivers and trade customers. The approval is only as good as the customer's understanding of what they approved.
The same applies to tax treatment. A customer who approved AED 1,450 and is handed an invoice for AED 1,522.50 has a fair question if the estimate never mentioned the 5% VAT. Showing net, VAT and gross on the estimate itself costs nothing and removes a routine argument at the counter. Approved estimates that carry through cleanly into a VAT invoice also save the re-keying that introduces its own errors.
What this guide does not cover
- Consumer protection procedure and where disputes escalate in each emirate, which varies by authority and is worth checking locally.
- Warranty claim handling with manufacturers and principals.
- Labour rate setting and how to price diagnostic time.
- Parts sourcing and the stock side of a workshop job — covered in our auto parts inventory guide.
- How to evaluate workshop software as a buyer, including what to test in a demo.
See how Avance GMS handles this → Digital job cards, signed check-in inspections, estimates and approval requests on WhatsApp with the response logged against the job, insurance and LPO workflow, and one-step VAT invoicing from the approved job.
Frequently asked questions
What is customer estimate approval in a garage?
It is the point at which the customer agrees to a priced scope of work before that work starts. A useful approval records four things: which version of the estimate was agreed, by whom, through which channel, and at what date and time. Without those four, the workshop has an agreement it cannot evidence later.
Does a WhatsApp approval count as a record?
It depends where the message lives. A reply on a service advisor's personal phone is difficult to produce months later and leaves with the advisor. The same reply logged against the job card, with the estimate version it responded to, is a record the workshop owns. The channel matters less than whether the exchange is attached to the job.
What should happen when extra work is found after the customer has approved?
The revised scope needs its own approval. Stripping a job down often reveals work the inspection could not see, and the original approval covered a different figure. Treating the revision as a second approval — with its own estimate version and timestamp — is what keeps the final invoice defensible.
Should a garage set an approval tolerance?
Most workshops benefit from one. A stated tolerance — for example, proceeding without re-approval where the revision stays within a small percentage of the approved figure — avoids stopping a job over a consumable while still forcing a fresh approval on anything material. The tolerance works when it is written down and applied consistently, not decided per job.
Who approves an insurance or LPO job?
Usually not the person who dropped off the vehicle. On an insurance job the insurer or surveyor approves the covered portion, while the customer approves their own excess and any work outside the claim. On a fleet or corporate job the LPO is the authorisation, and the driver who brings the vehicle typically has no authority to approve spend at all.
Should the estimate show VAT?
It should be unambiguous. A customer who approves AED 1,450 and is invoiced AED 1,522.50 has a reasonable question if the estimate did not make the 5% VAT treatment clear. Showing the net, the VAT and the gross on the estimate removes a common source of dispute at collection.
What should a workshop do when a customer disputes work they say they did not approve?
Produce the record: the estimate version, the approval, the timestamp and the channel. Where that exists the conversation is usually short. Where it does not, the workshop is arguing recollection against recollection, which is why the record is worth building at the time rather than reconstructing afterwards.
Written by the Avance Technologies team in Dubai, from work implementing workshop systems for UAE garages. It describes operating practice rather than regulation, so the judgements here are ours — your own customer mix, insurance panel and fleet agreements may point somewhere different, and specific consumer protection obligations are worth confirming with the relevant authority in your emirate. Figures in the examples are illustrative. Reviewed August 2026.
How much are approval arguments costing you?
Most workshops discount their way out of them without ever counting the total. Tell us how many jobs you run a week and how approvals reach your customers today, and we will show you what the estimate and approval trail looks like on a real job card.