How to Automate MOT Expiry Alerts for a Fleet

Manual MOT tracking is one of the most common compliance failures in fleet management. Someone is supposed to check which vehicles are due, add reminders to a calendar, follow up with drivers. In practice, it gets missed — especially across larger fleets where the workload is spread across multiple people and spreadsheets. An automated MOT expiry monitoring system using the DVSA API eliminates that failure point. Every vehicle in the fleet is checked on a schedule, expiry dates are compared against thresholds, and alerts fire automatically before any vehicle expires.

What the automated system does

At its simplest, the system does four things on a daily schedule: fetch the current MOT expiry date for every registration in the fleet from the DVSA API, compare each expiry date against configurable thresholds (30 days, 14 days, 7 days is common), generate an alert for any vehicle within a threshold, and deliver that alert by email, Slack message or webhook. The result is a daily digest of vehicles approaching MOT expiry, delivered automatically. A vehicle that expires in 28 days appears in the 30-day alert. If it still hasn’t been booked in, the 7-day alert has fired three times and there is a documented record that the alert was sent.

The compliance value beyond convenience

For regulated fleet operators — hire and reward, haulage, coach operators — an auditable record of MOT monitoring is a compliance requirement. The Health and Safety Executive and the Traffic Commissioner both expect operators to demonstrate systems are in place to ensure vehicles are roadworthy. A documented automated monitoring system with log files showing when checks were run, what the results were, and when alerts were sent is a stronger compliance record than a spreadsheet.

How the DVSA API handles fleet lookups

The DVSA MOT History API supports bulk lookups as well as individual registration lookups. The API returns the current MOT expiry date as a top-level field on the vehicle record — so the monitoring system doesn’t need to iterate through the full test history. Results are stored with a timestamp after each check run, creating the audit log.

What the build involves

The fleet monitoring build adds three components on top of a standard MOT lookup integration: a scheduler (typically a cron job) that runs checks on a defined cadence, a threshold comparison and alert generation layer, and a notification delivery mechanism. The full fleet is stored as a list of registrations in a database table. Adding a vehicle to monitoring is adding its registration to the table.

What this doesn’t cover

MOT expiry monitoring covers one compliance obligation. Tax status and SORN are available via the DVLA Vehicle Enquiry Service — a separate API that can be added alongside if needed.

For complete build details and pricing, see the DVSA MOT API integration service. The Fleet Monitoring tier starts at £2,295. See what the underlying data looks like in the live MOT History demo. For the full pricing breakdown, see the integration cost post.

What the alerts look like

The most useful format is a single daily summary rather than a flood of separate messages. Each morning, the fleet manager gets one email listing every vehicle inside a threshold, grouped by urgency: expired, due within 7 days, within 14 days and within 30 days. Each line shows the registration, the vehicle, the expiry date and the depot or driver it belongs to. Once a vehicle's MOT is booked, it can be marked as booked so it stops nagging, and once it passes, the next check picks up the new expiry date automatically.

For larger operations, alerts can go to a different person per depot, post into a team channel, or create a job in your maintenance system through a webhook.

Adding vehicles

Vehicles are added by registration, either one at a time or by importing a spreadsheet. When a vehicle is added, it's checked straight away, so the dashboard is complete from day one. Removing a vehicle when it leaves the fleet stops its checks but keeps its history for the audit trail.

Tax as well as MOT

MOT expiry is only one date to watch. Road tax status comes from the DVLA rather than the DVSA, so adding the DVLA Vehicle Enquiry API to the same daily run lets one system watch both, with the same thresholds and the same daily summary. See automating vehicle tax and MOT checks.

New vehicles

Vehicles under three years old don't need an MOT yet, so they have no MOT expiry date. The system works out when the first MOT is due from the date of first registration, and starts alerting ahead of it like any other vehicle.