MOT test logs

What are MOT test logs?

MOT test logs are records of MOT tests carried out at your station, available through the MOT Testing Service (MTS). They provide a chronological record of every test conducted — including the date, time, tester, vehicle, result and other details.

For AEs and Site Managers, test logs are the primary source of evidence about day-to-day testing activity at the station.

What information test logs contain

Each test record in the log typically includes:

| Data | What it shows | |------|--------------| | Date and time | When the test was started/completed | | Vehicle registration (VRM) | Which vehicle was tested | | Make and model | Vehicle identification | | VIN | Vehicle Identification Number | | Vehicle class | Class 4, 5, 7, etc. | | Test result | Pass, fail, or abort | | Tester user ID | Who conducted the test | | Site ID | Which VTS the test was carried out at | | Test duration | How long the test took | | IP address | Which device/location the test was conducted from | | Test number | Unique identifier for the test | | Contingency information | Whether the test used contingency arrangements |

Who uses test logs and why

Authorised Examiners

AEs have a legal responsibility for the quality of testing at their stations. Test logs allow them to:

• Monitor daily testing activity
• Check whether tests are being conducted within expected parameters
• Identify patterns that may require investigation (e.g., very short tests, unusual hours, high abort rates)
• Verify testing against appointment records
• Provide evidence during DVSA site visits

Site Managers

Day-to-day operational oversight:

• Reviewing the previous day's tests
• Checking test volumes and tester activity
• Identifying operational issues (equipment problems evidenced by aborts, contingency use)

DVSA

Vehicle examiners review test logs as part of their site assessment preparation and during visits.

How to review test logs effectively

A useful review process:

1. Choose a period — daily, weekly, or monthly depending on your station's volume
2. Scan for patterns — test times, durations, results distribution
3. Check context — contingency use, unusual hours, abort patterns
4. Cross-reference — compare against appointment records where relevant
5. Investigate anomalies — if something looks unusual, gather more context before concluding
6. Record your review — even a brief note that you checked and found nothing unusual

What to look for

• Very short test durations — may indicate insufficient inspection time, or may be legitimate for simple vehicles
• Tests at unusual hours — might be fine (shift patterns) or might warrant checking
• High abort rate — could indicate equipment issues or process problems
• Contingency testing — understand why it was needed and whether it was appropriate
• Clustering — many tests in rapid succession from one tester

Important: none of these patterns automatically indicate wrongdoing. They are reasons for human review, not automatic conclusions.

Test logs vs TQI

| Test logs | TQI | |-----------|-----| | Individual test records | Statistical summaries | | Shows specific tests/vehicles/times | Shows percentages and averages | | Useful for investigating specific concerns | Useful for identifying broad patterns | | Daily/weekly operational review | Monthly/quarterly strategic review |

Both are useful — they answer different questions. TQI helps you identify where to look; test logs help you understand what happened.

How MOT Lens helps with test logs

MOT Lens imports test log data and structures it for operational review:

• Chronological station view — see all tests organised by date, tester and vehicle
• Attention signals — MOT Lens highlights patterns that may be worth reviewing (short tests, contingency, unusual sequences)
• Vehicle context — see test history alongside booking and DVSA history for the same vehicle
• Tester context — view a tester's test activity alongside their TQI, training and QC records
• Quality handoff — if something warrants further investigation, hand it to the Quality work queue
• Historical access — imported logs remain accessible for future reference

MOT Lens works with the CSV export from MTS. There is no live API connection — you import the files your station already has access to.

FAQ

How far back can I access MOT test logs?

Through MTS directly, test logs are available for download for a limited period. If you need longer-term records, you should retain your own copies (or use a tool like MOT Lens to keep imported history).

Are test logs the same as MOT history?

No. Test logs are your station's own records from MTS. MOT history (via the DVSA MOT History service) shows a vehicle's national MOT record across all stations. They contain different information and serve different purposes.

Do I need to review test logs regularly?

DVSA expects AEs to have quality management systems. Reviewing test logs is one part of active station oversight. The frequency depends on station volume and risk, but some form of regular review is expected.

What should I do if I find something concerning in the logs?

Investigate in context before drawing conclusions. Discuss with the tester, observe their work, conduct a QC check, or cross-reference against other evidence. Record your findings and any actions taken.

Can test logs prove DVSA compliance?

Test logs are evidence, not proof of compliance. They show what testing occurred. Whether that testing was compliant depends on how it was conducted — which requires additional evidence (observation, QC checks, vehicle condition).