March 12, 2025
With compliance checks evolving rapidly, your site’s test data is more critical than ever, and is fast becoming the frontline evidence used by the DVSA when identifying non-compliant sites.
VEs have often taken a look through your site’s test logs before they come to visit you, but since 2022, the DVSA has started conducting routine offsite reviews, meaning more compliance checks are happening over the phone. These calls focus on the data they already have about your site—most importantly, your test logs.
The DVSA aren’t slowing down. They’re planning to leverage data even more to pinpoint MOT sites that are either:
1. Seriously non-compliant – doing something majorly wrong.
2. Serially non-compliant – repeatedly failing to meet DVSA expectations.
So if you haven’t had one of these calls yet, chances are you will soon.
Using technology to identify non-compliance
We will be further refining the machine learning and data analysis we use to target MOT garages who choose not to do the right things and, where appropriate, prosecuting them.
This supports our strategy of engaging with customers, tackling non-compliant behaviour and ensuring our frontline teams are directed to any who are found to be seriously and serially non-compliant.
Source: Driver and Vehicle Standards Agency business plan, 2024 to 2025
Before they call you, the VE will comb through all your test logs looking for red flags. Then, in the phone call, they’ll grill you on what they find.
Will you be able to answer questions like:
• Why you should expect Tapley tests to take longer than normal tests?
• Why the time between tests is just as important as test duration, when assessing risk?
• Why a tester forgetting to log off a test could be classed as fraud by the DVSA?
If you don’t regularly review your test logs, record what actions you’ve taken to prevent re-occurrence, and store those records properly, you will not be able to answer the VE’s questions satisfactorily – especially if they’re asking about tests completed months (or even years!) ago.
But the DVSA say that a successful quality management system is evidenced if you can prove that:
1. You are already aware of the issue
2. You understand why it’s a risk
3. That you’ve taken steps to prevent it from happening again
In operating systems, AE’s should always remember that sometimes things will go wrong. A successful quality management system is one that identifies things going wrong in a timely way and helps the AE put things right.
A quality regime that never identifies things going wrong is unlikely to be working effectively. Where things are found to be going wrong, then it is key to record this and show what has been done to prevent reoccurrence.
Source: The MOT Testing Guide Section B (Authorised Examiners)
Understanding the risks hidden in your test log data is crucial for preventing issues from recurring. Many Site Managers mistakenly assume that as long as their testers know what to do, they don’t need to worry too much about their own knowledge of risk indicators.
But in reality, it’s your responsibility to monitor your site’s test data and pick up on areas of concern – from identifying potential compliance risks to spotting operational inefficiencies – so you can take action before problems escalate (and become evidence of ‘serial non-compliance’).
During offsite reviews, it won’t be your testers speaking to the VE; you’ll be the one who must confidently demonstrate that you’re on top of your data. If a manager can’t explain why a quick retest might be a red flag or why a test accidentally logged on overnight is a significant concern, then you’re left vulnerable when the DVSA calls.
That’s why MOT Juice is launching a new series in our Site Manager CPD modules. Each month, we’ll take a deep dive into a different key risk filter, breaking down:
• What the risk is – Uncover the specific issue the test log filter is designed to catch.
• Why it matters – Understand how this risk can impact your site’s compliance and operations.
• What to look for – Learn the key indicators in your test logs that signal potential trouble.
• What actions to take – Discover practical steps to prevent the issue from recurring.
Sign up now, and gain the insights you need to handle VE reviews with confidence—making each compliance check a breeze with MOT Juice!
Since studying IT and design in high school I have always had a passion for designing and building websites and systems. Working for MOT Juice has allowed me to design a lot of the user interface our users see and interact with on a day-to-day basis. My experience includes over 10 years with Photoshop designing websites and system User Interfaces, 12 years of HTML, PHP and CSS coding, 3 years of learning jQuery and 8 years working within the motor industry. In 2021, I started learning Python, Apache, C# and Ruby to add to my coding skillset.
MOTJUICE