This post in 30 seconds.
- The problem: a reach truck is down at a customer site 70 km away and the ticket says "fault light, won't lift". Somebody at the service desk now has to decide whether that sentence is worth a technician's afternoon.
- The number: Aquant's 2025 field service benchmark puts one in seven onsite visits down as unnecessary. Top performers run a 3% avoidable dispatch rate, the bottom fifth 24%.
- The model: the operator standing next to the machine records six things (the machine and its plate, the display error, the hour meter, the affected component, the sound, and what happened) before anyone chooses between a remote fix, a planned visit with the right part, or an emergency call-out.
- Who this is for: service managers, planners and dispatchers at construction equipment dealers, forklift and material handling dealers, and plant rental branches.
The call comes in at 07:50. A reach truck at a distribution centre has a fault light on and won't lift, the shift starts in ten minutes, and the caller is the warehouse supervisor, not the operator.
He doesn't know the model. He thinks it "beeped and stopped".
If you run the service desk at a forklift dealer, an equipment dealer or a plant hire branch, you know what happens next. Somebody picks the nearest engineer with a gap in the diary, guesses at the brand from the account history, and sends a van. The diagnosis starts when the van arrives, an hour and a bit later, and about one time in seven it turns out the trip wasn't needed at all.
This post is about the ten minutes before that decision. What the person on site should record, how the desk reads it, and what changes in the three outcomes that follow: fix it remotely, plan a visit with the right part, or send someone now. The rental version of the same problem (what the machine looked like at handover and at return) gets its own section, because it uses the same flow.
We build Venta Capture, a product of VentaVid, so the operator who is already standing next to the machine can show your desk the plate, the code and the sound before a van moves. Start for free and send a test flow to your own phone from the yard.
In this post:
Why "it's throwing a fault" is not enough for mobile plant
A boiler sits in a plant room and a fixed machine sits in a factory. Mobile plant and machinery sits wherever the job is this week: a muddy compound, a customer's warehouse, a quarry with no signal at the bottom. The distance is what makes the dispatch decision expensive, and the person you send is usually the most experienced technician you have.
Three things make the phone description worse for this kind of equipment than for almost anything else.
- Mixed fleets, proprietary codes. A dealer with a full-line agency still services trucks from five other brands. Each has its own display, its own code list and its own diagnostic connector, so "it says E-something" on the phone tells the desk very little until someone knows which truck it is.
- The caller isn't the operator. The supervisor rings; the operator who heard the noise has been moved to another truck. The one person who could describe the fault is no longer in the conversation.
- Telematics stops at the code. Fleet telematics will show error codes as service alerts and the key hour meter on the trucks that carry a box. It won't show the hydraulic weep under the mast, the bent fork carriage, or the sound the pump made just before it stopped.
The result is a dispatch made from one sentence, and the numbers on that are not kind. Aquant's 2025 benchmark counts 14% of truck rolls, one in seven onsite service visits, as unnecessary, with top performers holding avoidable dispatch to 3% and the bottom fifth sitting at 24%. And a field call is the dear kind of labour: Clue's heavy equipment repair cost guide puts on-site repairs 20 to 30% above in-shop work because of travel and setup time.
What a truck roll costs in full, and why routing software doesn't fix the blind dispatch, is covered in our post on reducing truck rolls. This post assumes you've read it and gets specific about plant.
The six things to ask the site operator to record
Every forklift operator already walks round the truck before the shift for the forklift daily check. Every excavator operator does a walkaround too, if only to check the tracks. A fault capture is the same walk with a phone in hand and a list on the screen, and it takes about as long.
Six items, in this order, give the desk enough to choose an outcome without anyone having to diagnose over the phone. They take the operator about two minutes, and the order matters because the plate decides how the rest is read.
A few notes on why those particular six.
The plate first, always. A serial number is the difference between a parts pick and a parts guess. The same fault code on two series of the same brand can point at different controllers, and generic code readers don't work on forklifts at all, which is why every fault-code guide starts with "know your model".
Active or stored matters more than the code itself. Herculift's forklift troubleshooting guide puts it plainly: a fault code is a symptom flag, and the technician needs the exact code, when it appears (start-up, under load, after an hour), and whether it's constant or intermittent. A ten-second video of the display after a key cycle answers three of those four questions without a phone call.
The hour meter is the item everyone forgets. Rental checklists tell customers to note the hour meter reading at delivery; nobody tells them to note it at breakdown. For the desk it decides whether the job is warranty, whether the service was overdue, and whether the branch should have seen this one coming.
The sound is the item nobody thinks to ask for. When I sit with a service desk for a morning, the tech's first question on the phone is usually "what does it sound like?", and the answer is always a description of a description. A clip with the machine keyed on ends that conversation.
The generic version of this list, and how to guide an untrained person through capturing it, is in our post on guided photo capture. The point of guided capture is that the six items above are built into the flow, so the operator doesn't have to remember them and the desk doesn't have to ask twice.
Three outcomes: remote fix, planned visit with the part, emergency call-out
Nobody at the desk has to diagnose from the video. The job is to pick one of three actions, and the six items make that pick defensible.
The second and third rows carry most of the cost, because they are the visits that either should not happen or should not happen twice. Comparesoft's round-up of first-time fix benchmarks puts the industry average near 75 to 80% with best-in-class at 88 to 90%, and lists missing parts, the wrong skill and inaccurate diagnostics as three of the five reasons a first visit fails. All three are decided before the van leaves.
Aquant adds the cost of getting it wrong: a failed first visit adds two more visits on average and 14 days to resolution. For a customer whose only reach truck is down, 14 days is a hire truck on your account.
So the first-time fix rate for plant is mostly a planning number. Did the engineer with the right training go, and was the right part in the van stock? Both come straight from the plate and the code.
The pre-visit assessment mechanics that apply to any field service operation are in our pre-visit assessment post; for mobile plant the twist is that the assessment doubles as remote triage for safety. A leaking lift cylinder is a stop-use call before it's a parts call.
How it runs with Venta Capture
Nothing in this post needs the customer to install anything, and nothing needs a technician on a video call. That's deliberate. A dealer with 400 trucks under contract can't staff 400 video appointments, and the operator's time and your engineer's time don't need to line up.
Send the link. When the call comes in, the desk sends a secure, personal capture link by WhatsApp or SMS to whoever is standing next to the machine. Branches that want to skip the phone call put a QR code on the truck's service sticker or in the customer portal, so the operator scans it the moment the fault light comes on. No app, no account; it opens in the phone's browser in the operator's own language.
Guided capture. The flow walks the operator through the six items with an example photo per step: the plate with a frame to line up, the display, the hour meter, then a video step with an instruction on screen ("walk around the machine and say out loud what you hear"). A yes/no question ("is anything leaking?") sends them to a close-up step only when it matters. The recording happens on the phone in the session, and a retake asks why.
Review when ready. The submission lands in your service desk inbox as a case with its own reference number and the job number from your own system alongside it. The spoken explanation is transcribed and searchable, so "grinding from the mast on lift" is a line of text a workshop dispatcher can filter on. Assign it to the brand specialist, add a note, request a retake in one click, or copy the case into the DMS or ERP that holds the job.
Teams using Venta Capture for support and field service report 23% of customer problems solved without dispatching a technician, and 4 out of 5 issues handled and closed the same day. For an equipment dealer that translates directly into the first two rows of the outcome table: the seat switch and the stored code never become a van.
A note on what the product does and doesn't do. It doesn't diagnose the truck; your technician does that from better evidence. It records the server receipt time and location of the submission, which proves when the case arrived, not when the machine failed. And it flags signals for a human to look at rather than deciding anything on its own.
See how the field service flows are set up on the Venta Capture field service page, and the mechanics of the flow itself on the guided video capture page.
Want to see it on a truck from your own fleet? Book a demo and bring the three fault codes that came in most often last month.
Once the engineer has been, the same link works the other way round: a completion capture of the repaired component and the cleared display, which is the proof of work that ends the "was it actually fixed" call a week later. The broader picture of remote diagnostics in field service lives in its own post; this one stays on the machine.
The rental angle: the same flow at on-hire and off-hire
A rental branch has the fault problem and a second one on top of it: what did the machine look like when it went out, and what does it look like now it's back?
The paper answer is a handover form. Maptrack's template, updated May 2026, records the current hour meter reading, the fuel level and existing damage, tells you to photograph all four sides plus close-ups of damage, the hour meter display and the safety labels, and has both parties sign. That's the right list.
The trouble is who holds the camera, whether the photos are findable three weeks later, and whether the off-hire set is comparable with the on-hire set.
Run the six-step fault flow twice with a different heading and you have a condition capture that the driver, the site manager or the yard can complete without a branch inspector. At on-hire the delivery driver captures the four sides, the plate, the hour meter and the fuel gauge, and hands over. At off-hire the customer's site manager runs the same flow before collection, and the yard runs it again at check-in. Three records, same steps, same order, each sealed with a receipt time and location.
- Linked cases. The pre-hire inspection and the post-hire inspection sit in one file, so a reviewer compares two sealed records side by side rather than hunting through a shared drive. The comparison is a person's job; the product puts the two records next to each other.
- Both parties hold the same file. The flow can send the submitter their own copy on submission. When a scratch on the counterweight comes up at return, customer and branch are looking at the same handover record, not at each other.
- Hours and fuel become evidence. The meter display and the gauge are photographed in the session, timestamped on receipt, and tied to the hire agreement number.
The reason this matters commercially sits in the branch's own numbers. Gary Stansberry's composite of top-performing independents in RER found damage waiver charged on 28.4% of tickets, averaging 13.7% of the base rental. A damage waiver is the branch pricing in disputes it can't document; the fewer undocumented returns, the less that line has to carry.
InTempo's advice on damaged returns says the same in one sentence: photographic evidence with a time stamp and geolocation tag leaves little room for debate.
If you're comparing tools for this, our post on remote inspection software covers what to look for. The short version for rental: the person already at the machine captures, the branch reviews, and both records live in one case.
Run the numbers for one branch
Illustrative figures, so redo them with your own.
Take a branch that runs 60 field calls a week. At Aquant's one in seven, about eight of those shouldn't have rolled. Say each one is two hours of an engineer and a van at a field rate; Clue's guide puts US heavy equipment labour at roughly $75 to $150 an hour, and your field rate sits above your shop rate.
That's somewhere between 16 and 24 engineer hours a week on trips a two-minute capture would have settled, before you count the fuel and the customer who paid a call-out for a seat switch.
Then add the repeat visits. If your first-time fix sits at the 75 to 80% industry average, 12 to 15 of those 60 calls come back, and the plate and the code would have prevented the share caused by wrong part and wrong skill.
You won't win all of them. The ones you win are the trivial faults and the wrong-part trips, and those are the ones that annoy customers most.
The flow costs the operator two minutes while the truck is stopped anyway. Start for free, build the six-step flow, and put the link on next week's "fault light" tickets before you change anything else.
Fixed production equipment has its own post: industrial equipment service video. The parts-and-skills problem it solves is in why technicians arrive without the right parts.
Frequently asked questions
What should a site operator record when a forklift or excavator throws a fault?
Six things: the whole machine and its type plate, the display error as it shows now, the hour meter, the affected component, ten seconds of sound with the machine keyed on, and a short clip explaining what happened just before. In that order, with the plate first, because the plate decides which engineer and which parts.
We have telematics on the fleet. Why do we need a video as well?
Telematics tells you which code the controller logged and how many hours the truck has, on the trucks that carry a box. It doesn't show the leak, the bent carriage, the noise, or what the operator was doing, and it doesn't cover the other brands in the fleet. The two together give the desk a code and a picture; either alone leaves a guess.
Will site operators film the machine?
They will if it's two minutes, opens from a link or a QR code, and needs nothing installed. The truck is stopped anyway and the operator wants it back. Keep the flow to six steps with an example photo for each and completion is rarely the problem; asking for "some photos" with no guidance is.
Does this replace the technician's diagnosis?
No. The desk uses the capture to choose between a remote fix, a planned visit with the right part, and an emergency call-out; the technician still diagnoses the machine, now with the plate, the code, the hours and the sound in front of them before they leave. Venta Capture provides the evidence, not the verdict.
Can the same flow be used for rental handovers?
Yes, with a different heading. Run it at on-hire (driver), at off-hire (customer) and at check-in (yard), and the records sit as linked cases in one file for a reviewer to compare. The submitter can receive their own copy, so both parties hold the same record if a damage charge is raised.
Who can see the recordings, and how long are they kept?
Cases live in your own inbox with visibility set per form, so a rental condition flow can be limited to the branch that owns the machine. Retention and auto-purge are configurable, data is encrypted in transit and at rest, and every case carries an audit log of who opened, claimed and changed it.
See the machine before the van moves
One sentence on a ticket is not a reason to send your best engineer 70 km. Six things recorded by the person already standing at the machine are, and they also tell you when not to send anyone. The rest of the dispatch decision doesn't get easier; it gets made with the plate, the code, the hours and the sound in front of the desk instead of a description of a description.
What it takes to start.
- Free plan, no credit card. Build the six-step fault flow from a standard template and send it to your own phone from the yard.
- Live in 10 minutes for a first standard flow. Stuck? Book a free setup call and we build it together.
- Nothing for the operator to install. The link or QR code opens in the phone's browser, in their language, with your branding on it.
Venta Capture is built by the VentaVid team; the setup call is with a person who has built equipment flows before.
Start for free and put the link on next week's fault tickets. Or book a demo and bring one truck, one code and one off-hire dispute; we'll build the flow for all three on the call.