A transport inspection is a scheduled check of drivers, a vehicle, the load, and the loading or unloading site that flags deviations before they cause an accident, incident, or quality problem out on the road — or before they get picked up during a roadside check, customer audit, or SQAS Transport Service assessment. A working transport inspection programme stands or falls on three things transport companies often only partly get right: a risk-based rhythm for driver spot checks and vehicle checks, checklists that are genuinely usable at the loading or unloading site, and action follow-up that's airtight across borders. This article shows how to set up, run, and maintain all three — for ADR, SQAS, or your own fleet checks.
Structured transport inspections make a difference because they don't just flag deviations — they get them demonstrably resolved, before they're picked up during a roadside check, customer audit, or SQAS Transport Service assessment. Every transport company already checks something: drivers walk around their vehicle, planners check paperwork, ADR transport requires complete equipment on board. The difference isn't whether you check, but how.
Poorly structured transport inspections produce three symptoms we see time and again:
Good transport inspections close those gaps: they provide evidence for clients and assessments and keep drivers, vehicles, and loads in the condition you promise. The gap between "we check" and "we're in control" is extra wide in transport — the work happens outside the gate, where no one's watching.
Whatever requirement you operate under — ADR, SQAS Transport Services, ISO 28000, TAPA, ISO 39001, or your own fleet policy — the execution logic is essentially the same. You check the vehicle, equipment, documentation, and driver against a standard, capture evidence, and verify on a cycle. What differs by framework are the reporting and scope requirements; for the substantive interpretation of those, check with your DGSA, certifying body, or SQAS assessor. Here we focus on what's the same everywhere: how to carry out these checks effectively.
A workable transport inspection programme is built around six elements — scope, frequency, role division, time allocation, training, and action management — plus analysis afterward.
1. Scope — what do you check, and at what level? The biggest challenge is getting the checklist right: every inspection point needs to be sharp and clear to whoever carries out the check — the planner at the yard isn't an experienced auditor. The starting point is your own fleet and transport profile. Typical scope categories:
2. Check by risk, not by calendar. Different risk profiles call for different inspection frequency and intensity. Split your scope along two questions: how likely is it that something goes wrong here (probability of a deviation), and how severe is the consequence if it's not caught (criticality)? Together they determine how intensively you inspect:
3. Role division. Vehicle and equipment checks are done by the workshop or QHSE; behaviour and document checks by the planner or driver supervisor; out in the field, the driver is your first line of control. Build in independence: don't have a system audit carried out by whoever manages the fleet day to day.
4. Time allocation. Too many checkpoints at too high a freqeuncy means a spot check gets rushed, especially under time pressure at a loading site. Plan no more than can genuinely be assessed. The rule of thumb: better to get it right once than half-right twice.
5. Training and instruction. Handing a planner a checklist without explanation doesn't work. How would they know what "load securing compliant" means, or which ADR equipment belongs with this transport? That takes explanation — especially for dangerous goods or customer-specific requirements, and sometimes authorized, trained personnel.
6. Action management. A check without a system to fix deviations achieves little, and in transport the deviation is often far from the office. A good spot check is followed by a correct action: feedback, assignment, deadline, and follow-up. Assigning it to the right location is the real bottleneck here (see below).
Analysis. Improvement requires trend analysis: which shortcomings keep recurring, with which drivers, vehicles, or routes? Track a handful of hard indicators and adjust accordingly.
You run a transport inspection in seven steps: preparing, observing on site, capturing evidence, classifying, naming the action, closing out with the driver, and reporting immediately. This sequence works for every transport inspection, regardless of the framework:
During a driver spot check at an unloading site, the driver was well equipped and his paperwork was in order, but there wasn't a single emergency or fire-fighting facility nearby, and the grounding clamp wasn't connected either. In the sixteen-point checklist, every point was about the driver and vehicle; nothing was said about the unloading environment. The fix wasn't stricter driver checks, but an extra section, "loading and unloading site" — fire-fighting equipment, eyewash, grounding, wheel chock placement, fall protection — with a short explanation for each point.
A finding only becomes valuable once it's immediately followed by an assigned action with a deadline and verification. A spot check without action management is just busywork. This is exactly where most transport inspection programmes break down: the finding gets logged and only reaches someone's desk weeks later, by which point they no longer remember which trip it was about. Context gone, action half-hearted.
Three rules to prevent this:
Especially with a cross-border fleet, this stands or falls on assigning findings to the right place. Teams that let a finding automatically land at the location where the driver is based keep follow-up short — even remotely. That kind of automated assignment is something teams set up in Easy to Inspect.
The five most common pitfalls in transport inspections are a generic checklist, a calendar-driven frequency, missing photo evidence, the unloading site staying out of view, and actions without verification.
Set the frequency based on the risk profile per driver and route: drivers on ADR tank transport or new, high-risk routes deserve a higher frequency; experienced drivers on fixed, low-risk trips can be covered with spot checks. Factor in incident history and complaints when deciding.
In the field, the driver is the first line of control: they stop deviations at the source. Independent checks by a driver supervisor, planner, or QHSE staff member come on top of that. Checks involving dangerous goods call for authorized, trained personnel.
Probability of a deviation: how likely is it that something goes wrong here? Criticality: how severe is the consequence if it's not caught? A cosmetic vehicle defect has a high probability but low criticality; a leaking ADR tank is the reverse. Together they determine frequency and intensity.
Schedule fixed review moments (annually, for example) and build an "improvement opportunities" field into the checklist itself. Tie reviews to changes in the fleet, customer or SQAS requirements, and ADR regulations, as well as to incidents and roadside checks.
Yes. Photo evidence shows that the conclusion is based on an actual observation. Add the licence plate, date, and, where relevant, the shipment number; dated and traceable in a controlled system, they hold up.
Yes — and it's actually recommended. Work with separate checklists per type of check, but with one shared action module and trend analysis. That way you see in a single overview whether a recurring finding sits with the driver, the vehicle, or the location.
Yes — and it's actually recommended. The SQAS Tank Cleaning and SQAS Warehouse assessment questionnaires also include many topics that require checks or inspections. Think of Behaviour Based Safety assessments, condition monitoring of installations, daily inspections of internal transport equipment, inspections of assets (such as racking, fall protection, liquid-tight floors), storage checks, workplace inspections, and security inspections. These can all be built into Easy to Inspect very effectively.
The gain is in the administrative tail and remote follow-up: on paper, writing up a spot check typically takes 20–45 minutes afterward; digitally, the report is ready immediately and the action lands automatically. On the execution itself, you save little — observing properly still takes time.
With five indicators: the number of spot checks completed according to plan; the share of checks with findings (and whether that's falling); the share of deviations resolved within the deadline; the frequency of recurring shortcomings with the same driver, vehicle, or route; and the outcomes of external roadside checks, customer audits, and SQAS assessments over 2–3 years.
Mark Gijtenbeek — SQAS assessor and DGSA (Dangerous Goods Safety Adviser, ADR/RID/ADN), Lead Auditor ISO 9001/14001/27001/45001. More than 25 years of experience in transport, chemical distribution, and tank cleaning, with a focus on practically setting up inspection and assessment programmes. LinkedIn
Start your 30-day free trial with Easy to Inspect — with a checklist builder for your own spot-check, vehicle, equipment, and load lists, and automatic action assignment to the right location across Europe. Works for ADR, SQAS, and your own fleet checks. Your first spot check is up and running within an hour. Start your free trial.
