MOT quality control
What quality control means in MOT station operation — tester monitoring, QC checks, record keeping, follow-up actions and how to build an effective QC system.
Last reviewed: 2026-08-19
What is MOT quality control?
Quality control in the context of an MOT testing station means the ongoing monitoring and checking of MOT testing to ensure it is carried out to the required standard. It encompasses:
- Observing testers at work
- Re-examining vehicles that have been tested
- Reviewing test records and patterns
- Taking action where standards are not met
- Recording what was checked and what was found
QC is part of the AE's broader quality management responsibility.
Who carries out QC?
QC checks must be carried out by a competent person — someone with appropriate knowledge, skills, and experience to assess whether testing has been conducted correctly.
This could be:
- The AEDM
- A Site Manager with appropriate MOT knowledge
- Another competent nominated person
For single-tester sites where there is no second qualified person on-site, alternative arrangements are needed:
- A third-party assessor
- A reciprocal arrangement with another VTS
- Use of TQI data and test-log review as supporting evidence
- Periodic external observation
Minimum frequency
DVSA guidance specifies that QC checks should be carried out on each tester at a minimum of every 2 months.
This is a minimum — more frequent checks are appropriate for:
- Newly qualified testers
- Testers returning from extended absence
- Testers where previous concerns have been identified
- Periods of high testing volume
The frequency is not mandated in primary legislation with a specific number, but the MOT Testing Guide's "at least every 2 months" is the standard DVSA expects to see evidence of.
What a QC check involves
A QC check typically includes:
1. Re-examination of a tested vehicle
- Select a vehicle that has recently been tested
- Conduct your own assessment of the vehicle against the inspection manual
- Compare your findings with the tester's recorded result
2. Recording the outcome
- Were the tester's findings consistent with yours?
- Were any defects missed or incorrectly categorised?
- Was the correct inspection manual applied?
- Was the test duration appropriate?
3. Discussion and resolution
If there is a discrepancy between the QC check and the tester's result:
- Discuss with the tester
- Understand their reasoning
- Resolve the difference before the result is entered on MTS (if caught before submission)
- Record the agreed corrective action
4. Follow-up action
Where issues are identified:
- Additional training or coaching
- Closer monitoring for a period
- Adjustment to QC frequency for that tester
- Formal review if issues are persistent or serious
Building a QC system
An effective QC system for an MOT station covers:
| Element | Purpose | |---------|---------| | QC schedule | Ensures each tester is checked regularly (minimum every 2 months) | | Check records | Evidence of what was checked, when, and by whom | | Outcome records | What was found — including "satisfactory" results | | Action records | What was done when issues were identified | | Review cycle | Periodic check that the QC system itself is working | | TQI integration | Using TQI patterns to inform where QC attention should focus |
What DVSA expects to see
During a site review, DVSA will look for evidence that:
- A QC system exists and is being followed
- Checks are happening at appropriate frequency
- Results are being recorded (not just "in my head")
- Action is taken when issues are found
- The system is reviewed for effectiveness
They do not prescribe an exact format for records. However, records should clearly show who, when, what was checked, what was found, and what (if anything) was done.
Common QC pitfalls
| Pitfall | Problem | |---------|---------| | No written records | Cannot demonstrate to DVSA that QC is happening | | Only checking when problems arise | Reactive rather than systematic | | Same vehicle type always checked | May miss issues with specific test classes | | No action recorded | Even "no issues found" should be documented | | QC by someone without MOT knowledge | Checks may not identify genuine testing problems | | Single-tester site assumes QC is impossible | Alternative arrangements exist and are expected |
QC for single-tester sites
If your site has only one MOT tester:
- You cannot observe yourself testing — external arrangements are needed
- Options include: reciprocal observation with another VTS, periodic third-party assessment, peer review arrangements
- TQI review provides additional (though different) oversight
- Test-log review by the AE/Site Manager is complementary evidence
Being a single-tester site does not exempt the AE from QC responsibility.
How MOT Lens supports QC
MOT Lens helps stations plan, record, and retain QC activity:
- Quality work queue — see tests that may benefit from review, informed by attention signals
- QC records — record checks, findings, and outcomes linked to the relevant tester
- Follow-up tracking — actions from QC checks remain visible until resolved
- Tester context — QC records sit alongside training, TQI, and test history for each tester
- Evidence history — past QC records are retained and accessible
MOT Lens does not determine QC frequency for your station or decide whether a check passed or failed. Those decisions remain with the competent person conducting the review.
FAQ
How often should I do QC checks?
DVSA guidance specifies a minimum of every 2 months per tester. More frequent checks are appropriate where risk is higher (new testers, previous concerns, etc.).
What format should QC records be in?
There is no mandated format. Records should clearly capture: who was checked, when, what was examined, what was found, and what action (if any) was taken. Digital records are acceptable.
What if QC finds a problem after the test result was submitted?
If a result has already been submitted to MTS, the tester cannot retrospectively change it. Record the finding, discuss with the tester, plan corrective action, and adjust future QC intensity as appropriate.
Can I use TQI instead of QC checks?
TQI review is complementary to — not a replacement for — physical QC checks. TQI shows patterns; QC checks assess actual testing practice.
What training does the QC person need?
There is no specific "QC qualification," but the person must be competent to assess MOT testing quality. Typically this means they have appropriate MOT knowledge and experience with the inspection manual.
What happens if DVSA find no QC evidence?
Absence of QC evidence during a site review may result in advice, conditions on the AE's authorisation, or more serious consequences depending on the broader assessment findings.
See how MOT Lens supports this workflow
MOT Lens organises your station’s MOT data so you can review what matters and keep the evidence connected.