Workshop estimates: agree the work before it expands

The workshop calls while dispatch is arranging the next departure. There is another fault. The van is already there. “Shall we do that as well?”

A useful fleet-side authorisation process records what work is proposed, what has been agreed, who can decide and what changes require another decision. Keep the estimate and the instruction distinct. When extra work appears, add a dated change record connected to the original scope. Do not rely on a workshop booking or an estimated-cost field to explain what someone actually authorised.

This is an operating routine for managing your own decisions. Contract terms and the circumstances of a repair govern legal questions. There is no universal percentage in this guide that makes every extra charge acceptable or unacceptable for a commercial fleet.

Cover: AI-generated editorial illustration made with Higgsfield; not a customer estimate, signed approval or documented repair.

Define the decision before sending the van

Start with the reason for the visit. Is the workshop being asked to diagnose a reported problem, quote for a specified repair, or carry out agreed work? If you need diagnosis first, describe that stage and ask what it costs. Avoid an instruction such as “sort it out” when the intended scope is narrower.

Give the request a vehicle reference and a job reference. Describe the symptom or requested task in plain language without inventing a technical diagnosis. Keep any relevant workshop advice with the request. The person coordinating the booking does not need to pretend to be the technician.

Ask the workshop to identify what the proposal includes, any exclusions and what remains uncertain. If further diagnosis could change the scope, record that uncertainty before somebody treats an estimate as the final job. Discuss the expected vehicle availability separately from the amount.

This early distinction also helps when different people share the work. The dispatcher may arrange delivery, while an owner decides expenditure. A colleague reading the job should know which stage has actually been authorised and which decision is still pending.

Read the estimate as a proposal

Check that the estimate belongs to the correct vehicle and concern. Look for the proposed tasks, parts and labour, the stated tax basis, and any assumptions. If the wording is too broad to understand, request clarification before issuing an instruction.

ADAC's workshop guidance recommends documenting the proposed work and agreeing contact when additional work or extra costs arise. That is useful practical advice. It does not make consumer membership services or every consumer-law interpretation applicable to a commercial fleet contract.

Ask whether the proposal includes diagnosis, parts ordering, subcontracted work or collection. Where an item is provisional, keep it visible. A single total can conceal different assumptions in otherwise similar quotes, so compare scope before comparing amounts.

Retain the original version. If a workshop revises the proposal, keep the new version with a clear relationship to the earlier one. A file called “latest estimate” becomes ambiguous once several colleagues have downloaded their own copy.

Write down the instruction you actually give

An internal spending limit and an external repair instruction serve different purposes. The first says who in your business can decide. The second tells the workshop what you are asking it to do. Keep the relevant record of both, using your existing purchasing rules.

Use your agreed channel: email, a purchase-order system or another controlled record. If a decision happens by phone, document the actual conversation promptly and send a clear confirmation of your understanding. Do not backdate a note or call an unanswered message an acceptance.

Avoid prewritten wording that grants more authority than intended. If you agree a cost ceiling, explain its scope and basis in the instruction, and keep the workshop's response. Have the appropriate adviser review contractual wording where needed. A blog template cannot decide how a particular agreement will be interpreted.

Give an extra-work request its own decision

When the workshop discovers another problem, ask what changed. Is the additional item necessary to complete the original task, a separate repair recommendation, or an uncertainty that needs more diagnosis? Obtain the technician's explanation rather than attempting to make the technical judgment from an abbreviated message.

Record the proposed additional scope, the stated additional cost or revised total, the tax basis and the effect on availability. Clarify whether the revision replaces the original estimate or adds to it. That distinction prevents a supplementary amount from being mistaken for the full job total.

Route the request to the person with authority to decide. If they are unavailable, use the agreed deputy or escalation route. Avoid silently converting “waiting for owner” into permission because the workshop has a slot today. Ask the provider how work and vehicle storage will be handled while a decision is pending.

A response can accept the proposal, decline it, request clarification or authorise only a defined stage. Preserve the actual response and communicate it to the workshop. Internal discussion alone does not establish that the provider received the instruction.

Keep safety and payment questions separate

A spending decision does not establish that a vehicle is safe to use. If the workshop raises a safety concern, obtain the relevant technical advice and involve the person responsible for vehicle operation. Declining a proposal is not permission to put the van back on a route.

Likewise, deciding to proceed does not establish that an insurer, lessor or warranty provider will reimburse the work. Check the applicable arrangements and preserve any required provider decisions separately. Keep “repair authorised by fleet” and “funding confirmed” as different statements when they are different facts.

If the parties disagree about what was instructed, preserve the records and seek appropriate advice. Do not rewrite the original instruction to make the history appear tidier. The aim is a faithful account, including uncertainty, rather than a file that merely supports one preferred explanation.

Follow one change from request to decision

An illustrative composite example, not a customer story: a fleet authorises diagnosis of a recurring starting problem. The workshop identifies a proposed repair and asks to replace an additional component during the same visit.

The dispatcher records the proposal against the job and asks for the scope and availability impact. The owner agrees the main repair but asks for clarification about the additional component. The workshop receives a confirmation that distinguishes the agreed work from the pending question.

Later, the clarification arrives and the owner makes a second decision. Both instructions remain attached to the same job. Another colleague can identify what was authorised at each stage without reconstructing it from memory.

Record the decision while the proposed work can still be discussed with the workshop. Keep the later invoice check and vehicle collection linked to the same job.

A change note for your next workshop call

Use this as an internal record alongside the actual correspondence. It is not contractual wording or a substitute for communicating the decision to the workshop.

• Vehicle and job reference:
• Original estimate reference and version:
• Additional work proposed and reason:
• Additional amount or revised total, with tax basis:
• Effect on expected vehicle availability:
• Decision, authorised person and date:
• Instruction sent to the workshop and response received:
• Open questions, next action and responsible person:

Mark a response as pending until it has actually arrived. Keep the request and the decision as separate records.

Establish the routine before the next call

1. Name the decision-maker and deputy. Follow your own purchasing authority and document who covers absence.
2. Separate diagnosis, estimate and instruction. Identify the authorised stage before the vehicle leaves.
3. Agree the contact route for changes. Give the workshop a working contact and escalation route.
4. Record the next supplement request. Include scope, cost basis, availability and the actual decision.
5. Test the record with a colleague. They should be able to explain what the workshop was told without calling the original authoriser.

Fleet by Elevera's vendor repair workflow records a vehicle, vendor, booking date, estimated and final costs, notes and repair status, with associated documents. This workflow is gated separately for Enterprise access. Those records can provide context for your manual authorisation process. They do not establish a built-in purchase-order approval, enforced spending ceiling or electronic signature. Keep the actual authorisation in your agreed controlled channel and link its reference to the job; do not treat a repair status as approval evidence.

Related reading on the Fleet journal:

• Maintenance and workshop records
• Recorded cost analysis
• Incident records linked to repairs

Book a Fleet by Elevera demo.