MTS test log CSV fields

Overview

When you download test logs from the MOT Testing Service Performance dashboard, you receive a CSV (comma-separated values) file. Each row represents a single MOT test conducted at your station.

This page explains the available fields and their operational relevance.

Field reference

| Field | What it contains | Why you might review it | |-------|-----------------|----------------------| | Test date | Date the test was conducted | Chronological review, checking activity patterns | | Test time | Time the test started or was recorded | Identifying out-of-hours testing, checking scheduling | | Vehicle registration (VRM) | Registration mark of the tested vehicle | Cross-referencing against appointment records | | Make | Vehicle manufacturer | Understanding vehicle mix | | Model | Vehicle model | Understanding vehicle mix | | VIN | Vehicle Identification Number | Unique vehicle identification, fraud detection in extreme cases | | Vehicle class | MOT test class (4, 5, 7, etc.) | Ensuring testers are authorised for the class tested | | Test result | Pass, fail, or abort | Monitoring pass/fail ratios, abort patterns | | Tester user ID | MTS user ID of the tester | Attributing tests to specific individuals | | Site ID (VTS number) | The testing station identifier | Multi-site management, confirming correct site | | Test duration | Time from start to submission | Identifying very short or very long tests | | IP address | Client IP address used during the test | Verifying tests were conducted on station equipment | | Test number | Unique MTS test identifier | Reference for specific test queries | | Contingency code | Whether contingency arrangements were used | Understanding when normal connectivity was unavailable | | Contingency date/time | When the contingency test was conducted | Matching contingency tests to actual testing periods |

Understanding each field in context

Test date and time

The primary sorting dimension. When reviewing logs:

• Tests outside normal operating hours may be legitimate (evening/weekend testing) or may warrant a question
• Clustering of many tests in short periods could indicate normal busy periods or might suggest process checks are worthwhile

Vehicle registration (VRM)

Useful for:

• Matching tests to appointment records
• Identifying whether the same vehicle has been tested multiple times in quick succession
• Cross-referencing with customer records

Test duration

Duration is the time between starting and completing the test on MTS. Context matters:

• Very short durations (e.g., under 15 minutes for a full Class 4 test) may warrant checking — though a straightforward newer vehicle may legitimately test faster
• Very long durations may indicate the tester paused mid-test or encountered issues
• Duration alone does not prove quality — a thorough tester might still be fast on simple vehicles

IP address

Shows which device/network connection was used to submit the test. Useful for:

• Confirming tests were submitted from station premises
• Identifying whether tests are being submitted from unexpected locations

Contingency information

Contingency testing is used when normal MTS connectivity is unavailable. Fields show:

• Whether contingency was invoked
• The date/time the contingency test was actually conducted

Occasional contingency use is normal (internet outages happen). Frequent or patterned contingency use may indicate infrastructure issues — or may warrant further investigation.

Working with the CSV

In a spreadsheet

You can open the CSV in Excel or Google Sheets to:

• Sort by date, tester, duration, or result
• Filter for specific testers or results
• Calculate basic statistics (average duration, pass rate per tester)
• Create charts for visual review

Limitations of spreadsheet review

• Manual and time-consuming for high-volume stations
• No easy way to connect tests to TQI, vehicle history, or quality records
• No audit trail of what you reviewed or concluded
• Historical analysis requires maintaining many separate files

In MOT Lens

MOT Lens imports the same CSV and provides:

• Structured views by tester, date, and vehicle
• Attention signals for patterns worth reviewing
• Connection to vehicle records, bookings, and TQI
• A record of your review activity
• Historical access across multiple imports

Practical tips

• Download promptly. MTS availability for historical logs is limited.
• Keep the raw CSV. Even if you import into another tool, retain the original file as a source record.
• Don't over-interpret single fields. A short test, an unusual time, or a different IP address is a reason to check context — not a conclusion.
• Combine with TQI. Test logs show individual events; TQI shows patterns. Use them together.

FAQ

Are all these fields always present?

The exact columns may vary slightly. Some fields may be blank for specific test types or circumstances (e.g., contingency fields are empty for normal tests).

Can I get more detail than the CSV provides?

The CSV export is the standard format from MTS. For specific individual test details, you can view them on-screen within MTS, but the CSV is what is available for bulk download.

Is the VRM in the CSV always the current registration?

The VRM recorded is the one present at the time of the test. Vehicles that have been re-registered since will show the registration they had when tested.

Does the CSV include failure reasons?

The basic test-log CSV shows the overall result (pass/fail/abort). Detailed failure reasons (specific defect items) are visible within MTS for individual tests but may not be included in the bulk CSV export.

How should I store downloaded CSV files?

Securely — the data includes vehicle registrations and could be considered operational business data. Follow your existing data protection practices.