AI inspections for Zonar

Overview

EVIR proves that the walkaround happened. It does not tell you what was in the frame. Zonar's tags, zones and forced scan order make a driver stand at each part of the vehicle and say something about every component, and the result lands in the EVIR dashboard the moment the inspection uploads. The photos ride along on the defect line, one expander click away from the mechanic. RapidEye reads those photos instead of filing them: every attached image on every inspection, matched to the asset and the zone it came from, compared with the same zone on the same asset last week, and returned as a plain finding with the picture that proves it.

How it works with Zonar

An EVIR configuration is already a map of the vehicle, so the checks follow it. Zonar publishes configurations for tractor trailers, motorcoaches, school buses, forklifts, ready mix, front loaders, utility and law enforcement vehicles, white fleet vans and fixed locations, and every one of them is a numbered set of zones with a component list underneath. That numbering is what makes a photo readable by anything other than a person: the frame is not just "a truck", it is Zone 4 of asset 118 on a Tuesday morning.

• The defect photo. A driver marks a cracked lens, taps Add a Photo, and moves on. RapidEye reads the whole frame, not the part the driver was pointing at, and comes back with what else is in it: the scrape below the light, the missing fastener at the edge, the pooled fluid on the ground.
• The photo with no defect attached. An inspection can request a picture where nothing is wrong, and those are the most valuable frames you own, because they are the only record of a part in its normal state. RapidEye keeps them as the baseline for that zone and tells you the week the normal state stops being normal.
• Slow damage across inspections. A strap that has been fraying for a month never crosses the line into a defect on any single morning. Compared against the same zone four inspections back, it is obvious. That is the class of finding a walkaround structurally cannot produce.
• The inspection that was not really done. A black frame, a photo of the shop floor, the same picture submitted for two assets an hour apart. Zonar can prove the tag was scanned; the photo is where you find out whether anybody looked.
• Damage that arrived between the post-trip and the pre-trip. Two inspections, one night, the same asset and zone. Post-trip clean and pre-trip not, with both pictures and both inspector names, is the difference between a conversation and an argument.
• Assets that are not vehicles. Zonar's own configuration list includes buildings, access tunnels and classrooms. A room photographed on a route is the same problem as a trailer photographed on a route, and RapidEye reads it the same way.

A finding names the asset, the zone and the component, what kind of issue it is, how serious it looks, the frame it came from and the matching frame from last time, and a suggested next step. It lands in the RapidEye dashboard, and in a Slack channel or an inbox for the shop if you want it there. What happens next in Zonar is your shop lead's call: RapidEye never opens, closes or certifies a defect. And the six shapes above are examples, not a menu. If your drivers shoot short video walkarounds, if you have scans of an asset, if your standard is something local that no configuration in the world ships with, that is a setup conversation, not a limitation.

How to connect Zonar to RapidEye

1. Your Ground Traffic Control account, with the configurations you already run. The assets, the tag placements, the zone numbers and the component lists stay exactly as your team built them. Nobody moves a tag.
2. Photos on the inspection. EVIR already lets a driver attach photos to a defect, and Inspection Builder lets you request a photo where there is no defect at all, which is where the baseline comes from. Ask for one at the zones that cost you money: tyres, coupling, cargo area, load securement. If some part of the operation runs outside Zonar, a rental unit or a yard asset, RapidEye can send a capture link that opens on any phone with no app to install.
3. Add RapidEye as a user. Ground Traffic Control's user form is the whole of it, and the modal on this page has the exact path and the details to paste in.

How an EVIR inspection is built

Checked against Zonar's help centre and product documentation, September 2026.

EVIR stands for Electronic Verified Inspection Reporting, and the verified is the part that matters. RFID tags are fixed to the vehicle at each inspection zone, and the driver has to physically be at that tag, with the device against it, before the app will let them report on the components there. According to Zonar's help centre documentation (zonarsystems.net), the EVIR Mobile app runs both tagged EVIR inspections and tagless DVIR inspections, shows the zones in a list view and a map view of the asset, and offers a Report Tag Issue path when a tag is damaged or missing so the walkaround can continue honestly rather than silently.

Inside a zone the app is a tight five-step loop, repeated at every tag on the vehicle.

1. Step 1Scan the tagHold the device to the RFID tag for that zone. This is the step that turns a claim into a record.
2. Step 2Read the componentsThe app lists what belongs in this zone, so the same parts get checked in the same order every morning.
3. Step 3Pick the conditionTap a component and choose from the defect conditions the configuration allows.
4. Step 4Set the severityMinor means it needs repair. Major means the vehicle should not be operated.
5. Step 5Add a photoOptional. Up to three per component, twenty-one across the inspection. The step this page is about.

At the end the driver taps Certify and Submit, reviews the asset and zone information, and the inspection uploads. Zonar's product pages add the operational bookends: the app associates the driver with the asset from the time and date of that first scan, and drivers can clock in on the pre-trip and out on the post-trip.

Where a photo actually goes

Onto the defect line, and Zonar has built the plumbing for it properly. The Inspection Defects report and the Asset Inspection and Repair History screen both carry a Photos column, and the documentation is explicit about the interaction: if any photos are attached, you click the down arrow on the defect line to expand it and view them. That is a sensible design. The mechanic filtering to open Major defects on the assets at their location is one click from the picture. This is what a single defect line hands them.

Read that list again and notice what every field except the last one has in common: it is text, so a report can sort it, filter it, count it and trend it. The photo is the only field on the line that a computer never looked at, so the only way it turns into knowledge is a person clicking the arrow. On a fleet closing a few dozen defects a week, they do. At two hundred assets running pre-trip and post-trip inspections, that is upward of eighty thousand inspections a year, and the arrow gets clicked when something has already gone wrong. The gap is not in Zonar's report. It is that photo volume grew faster than the hours available to look at photos, which is the same thing that happened to every other industry that started documenting with a camera.

Can EVIR photos be required rather than optional?

Yes, and it changes what the integration can do. Zonar's documentation describes a second kind of photo entirely: an inspection can request photos where there is no defect at all. Those entries appear on the Inspection Details screen with a camera symbol, can be marked required with an asterisk so the driver cannot submit without one, and hold up to three images each. Inspection Builder is where they get added, alongside editing, moving, renaming and renumbering zones and components, and building inspection types beyond the pre-trip and post-trip pair.

Those no-defect photos are the ones RapidEye wants most. A defect photo shows you a problem someone had already noticed. A required photo of a healthy fifth wheel, taken every morning for six months, is a record of what healthy looks like on that specific asset, and it is the only way anything can tell you the week it stops looking that way. If your configurations already request them, the baseline exists in your account today.

Zonar integration FAQ