Operator Licence Compliance: AI Tracks Checks, Audits and Renewals

To keep an operator licence in good standing, track four things: planned safety inspections inside your notified intervals, driver daily checks and defect reports, maintenance and driver-hours records kept for their required periods, and any change you must report to the regulator within 28 days. AI can read your sheets and flag what is due or missing.

The rules below come from the government's goods vehicle operator licensing guide on gov.uk, which applies mainly to goods vehicles over 3.5 tonnes gross plated weight used for hire or reward or in connection with a business (some lighter vans need a licence too). Your own licence conditions and the undertakings you gave when you applied are what count, and AI cannot tell you whether you meet them. It can make the dates impossible to miss.

Follow me on Instagram@sagnikteaches

What the regulator expects you to be able to show

An operator licence is granted on the strength of undertakings: promises about how you will keep vehicles safe, how drivers' hours will be controlled, and how records will be kept. The guide states that the traffic commissioner is entitled to expect compliance with those undertakings during the life of the licence, and that failure can lead to the licence being revoked, suspended or curtailed. So the question for your diary is not "what do we hope to do" but "what could we show if asked on Tuesday".

Connect on LinkedInSagnik Bhattacharya

From the guide's section on safety checks, the operator is responsible for making sure that:

Subscribe on YouTube@sagnikteaches

• safety inspections, including brake tests and other statutory testing, take place within the notified maintenance intervals, counted in ISO weeks, on vehicles and trailers;
• a maintenance planner is completed and displayed, setting preventative maintenance dates at least six months ahead, including test and calibration dates;
• drivers complete and return defect reporting sheets, defects are recorded and repaired promptly, and vehicles that are not roadworthy come out of service;
• vehicle maintenance records are kept for at least 15 months and can be produced on request;
• tachograph calibrations are current, vehicle unit data is downloaded at least every 90 days and driver card data at least every 28 days, drivers' hours records are kept for at least 12 months and working time records for at least 24 months;
• drivers hold the right licence for the vehicle, with regular licence checks (the guide says usually every three months);
• vehicle details on the licence are kept up to date, and relevant changes are notified within 28 days.

Check each period against the current guide before building it into a sheet, because a guide can be revised. The point of listing them here is to show how many separate clocks run at once on even a small fleet. A diary built from this list turns each clock into a row.

The sheet: six tabs that mirror the obligations

Resist the urge to buy software first. A spreadsheet that mirrors the obligations, with dates and one reminder formula, covers a fleet of up to a few dozen vehicles. Software can come later, and the structure you build now is what you will specify.

Two columns do most of the compliance work. Next due is a date, always a real date and not text such as "March". Status is a formula that reads the date and returns a word. For a date in column G:

=IF(G2="","NO DATE",IF(G2<TODAY(),"OVERDUE",IF(G2-TODAY()<=14,"DUE SOON",IF(G2-TODAY()<=42,"PLAN","OK"))))

Colour OVERDUE red and DUE SOON amber with conditional formatting, and add a summary block at the top of the sheet that counts each status. The first time you build it, expect to see several amber and red cells, and treat those as the useful result, not an embarrassment.

For inspections counted in ISO weeks, a week number is easy to get wrong by one around the New Year. Store the actual date of the last inspection, work out the due week from it with a formula, and show both. If you build the formulas with an assistant, using ChatGPT with Excel shows how to ask for them and check them.

A fleet walked through it: four trucks and two trailers

Take an illustrative small haulage firm with four rigid trucks and two trailers on one licence, a six-week inspection interval for the trucks and a ten-week interval for the trailers. The owner has a paper planner and a folder of inspection reports, and wants the diary in a sheet.

1. Load the data. One row per vehicle, with the date of the last inspection from the most recent report. That is twenty minutes with the folder open.
2. Calculate the next due date. Last inspection plus the interval in weeks, =D2+7*E2, shown beside the ISO week number =ISOWEEKNUM(F2).
3. Lay out six months. Ask the AI to turn the Vehicles tab into a rolling schedule (below). Print it for the workshop wall, since the guide expects the planner to be displayed.
4. Add the tachograph cycle. Vehicle unit downloads every 90 days and driver cards every 28 days become two date columns with the same status formula.
5. Set the weekly review. Fifteen minutes each Monday: sort Status so OVERDUE and DUE SOON are on top, assign a name and a date to each, and record that the review happened.

The result for this firm is a one-page view: six vehicles, each with a next inspection week, next annual test, next tachograph download and a status. It does not replace the maintenance contractor's own records, but it shows the owner whether anything is about to go wrong.

A planner prompt and what it returns

Give the assistant the vehicle table and ask for a plan, not a verdict. A prompt that works (paste only the columns it needs):

Below is a table of vehicles with their last inspection date and inspection interval in weeks.

For each vehicle, produce the next 26 weeks of planned preventative maintenance inspection dates, one every [interval] weeks from the last inspection date. Show the ISO week number and the date of the Monday of that week.

Rules:
- Do not move dates for holidays or availability; instead list any date from 24 December to 1 January in a "Check manually" section.
- If two vehicles fall in the same week, say so in a "Clashes" section.
- Do not add vehicles or dates I did not give you.
- Output a table, with vehicles as rows and weeks as columns, then the two sections.

Vehicles:
T1 | last inspection 2026-09-14 | 6 weeks
T2 | last inspection 2026-09-21 | 6 weeks
T3 | last inspection 2026-10-05 | 6 weeks
T4 | last inspection 2026-10-12 | 6 weeks
TR1 | last inspection 2026-09-28 | 10 weeks
TR2 | last inspection 2026-10-19 | 10 weeks

A fragment of the answer (illustrative), showing the next three inspections for three of the six vehicles:

Under the table, a good answer lists two "Check manually" dates (T3 and TR2 are both due on 28 December, in the holiday period) and four clashes: T1 and TR1 in week 50 (7 December), T3 and TR2 in week 53 (28 December), T4 and TR1 in week 7 (15 February) and T2 and TR2 in week 10 (8 March). If the model reports only one clash, it has not checked every pair, which is exactly the slip to look for. It should also show that T1 and T2 were due on 26 October and 2 November, before the date you ran it, so those two need a logged inspection or they are already overdue. Read the arithmetic yourself against the sheet, because dates and week numbers are exactly where a model can slip by one week, and ISO week 53 exists only in some years (2026 has one). A formula in the sheet is the stronger source of truth; the AI's table is a draft for the wall and a second opinion on clashes.

Driver checks and defect reports: turning paper into a log

Most small operators have the paper trail and no overview. Daily check sheets and defect forms pile up in a folder, and the one defect that mattered is somewhere in week 31. An assistant can help you turn a batch into a defect log, and flag anything that was reported but never closed.

Before and after

Before: a scanned or typed batch of notes, as the drivers wrote them.

12/10 T3 nearside rear light out, told Sam
14/10 T3 light fixed? not sure
15/10 TR1 brake pipe chafing on axle 2 - need looking at
16/10 T2 windscreen washer empty, topped up

After (illustrative, asked for a table with the categories Lights, Brakes, Tyres, Fluids, Body, Other and a Status of Open, Closed or Unclear):

The 14 October line is the telling one. "Light fixed? not sure" is not a repair record, so the model should mark the status Unclear and you should chase it. The brake pipe defect matters more: it must not stay Open and the trailer must come out of service until it is dealt with, which is a decision for a person, not a formula. Add a rule to the sheet that any Brakes defect still Open after 24 hours turns red.

Insist on this prompt line: "Do not mark a defect Closed unless the note says it was repaired, by whom or when." Models like to be helpful and will round "fixed?" up to "fixed" unless told not to.

Tachograph and records dates, filled in for one vehicle

The retention and download periods are easiest to keep when they sit on the vehicle's own row. Here is how one truck's line might read on a given day, with the status formula applied (all dates illustrative, today taken as 5 November).

Driver B's overdue card download is the sort of item that the paper planner never showed, because nobody was assigned the 28-day clock. The sheet gives it a name and a date. The records retention periods then sit in a small table on the Licence tab, so that nobody clears out the filing cabinet too early: 15 months for vehicle maintenance records, 12 months for drivers' hours, 24 months for working time. A reminder to check them against the government guide twice a year is enough.

Reporting changes within the time limit

The guide says licence holders must tell the traffic commissioner of relevant changes within 28 days, and names examples such as a change in legal entity (for instance, a sole trader becoming a limited company), changes of directors, or the death of a person named on the licence. It also notes that licences are not transferable, so operating as a new entity without a new licence is not permitted. Treat the guide's full list as the authority.

A Changes tab turns this into a clock. Whenever something happens that could be reportable, the person who spots it adds a row. The notify-by date is the event date plus 28 days, with the same status formula. Examples of what goes on the tab:

• a director leaves, or a new one is appointed;
• a vehicle is hired in, or sold, and the licence's vehicle list no longer matches the yard;
• the transport manager changes;
• you, your transport manager, an officer or an employee receives a relevant conviction or accepts a fixed penalty;
• the business changes name or structure;
• an operating centre arrangement changes.

Keep vehicle details on the licence in step with reality. The guide warns that failing to make changes promptly, such as removing vehicles that were hired, can affect repute. A quarterly check that compares the yard with the licence's vehicle list takes ten minutes and costs nothing. A prompt for the check, using the fleet list and the licence list pasted side by side:

List A is the vehicles in my yard. List B is the vehicles on my operator licence record. Show vehicles in A but not in B, vehicles in B but not in A, and any where the registration differs by one character. Do not guess; if a row is ambiguous, say so.

An audit-readiness check you can run on yourself

Once a quarter, pick an inspection at random and trace it end to end, as an auditor would. A prompt can run the questioning, with you supplying the evidence:

Act as a careful reviewer of my operator licence records. I will tell you what I have for one vehicle. Ask me up to 12 short questions, one at a time, that test whether I can show: the planned inspection date, the actual date, the report, defects found, who signed off, repairs and the date of the next inspection. After my answers, list any gap in the chain and what evidence I should locate. Do not give legal advice.

The value is the gaps it reveals: a report with no signature, a repair without an invoice, a planned date with no outcome. You are rehearsing the question "show me" before somebody else asks it. Pair it with the wider checklist in the small-fleet audit checklist, which is written for a different rulebook but uses the same idea of an evidence trail.

A missed week that the sheet caught

An illustrative case: a trailer's inspection was due in week 41. The maintenance contractor moved it by a week because of a staff shortage, and the owner agreed on the phone. In week 42 the inspection went ahead, so the gap since the last one was eleven weeks on a ten-week interval. Nothing in the paper planner showed it, because the planner still read "wk 41, done".

The sheet showed it. The Inspections tab holds the actual date, the Vehicles tab computes the gap from the previous inspection, and a column compares the gap with the notified interval. The owner saw "GAP 11 vs 10" and decided how to handle it: record why, tell the contractor that dates cannot move without a call to the transport manager, and note on the planner that the next inspection stays pinned to the original schedule, not the late one. The lesson is to measure the actual gap and not only whether a box was ticked. Whether a one-week slip is acceptable under your own licence conditions is not something a spreadsheet can say, so ask a transport adviser if you are unsure.

Who does what each week and each quarter

Compliance diaries fail because the owner is on holiday or the one person who understands the sheet is off sick. Write the routine as a short rota anyone can follow.

Keep the review log, even though it is dull. A line saying "reviewed 14 Oct by [name], 3 items assigned" is evidence that the system operates, which is what the undertakings are about. If you are choosing the people and tools, drafting a safety plan and toolbox talks with AI covers the written policies that sit behind the diary.

Keeping driver and vehicle data safe in the chat

The sheet holds personal data, and the chat does not need most of it. A habit that costs nothing: use staff codes, never names, in anything you paste, and keep the key in your own file. Keep dates and fleet numbers, because those are what the AI needs. Do not paste licence numbers, addresses or dates of birth at all. Use a business plan, or a personal plan with training switched off, and check the current privacy settings on the vendor's own page. If you want to see how cameras and telematics fit with consent, read AI dash cams for fleets: cost, privacy and driver consent.

One last control worth adding is a rule of ownership: the AI proposes, a named person disposes. Every flag the assistant raises is a prompt for a person to check the underlying record, never a decision in itself, and anything that touches a legal duty is confirmed against the government guide or an adviser. Set that as the standing rule on the front tab, and the diary stays an aid to your judgement and not a substitute for it.

Operator licence questions fleet owners ask

Can AI tell me whether I am compliant?

No. It can show you what is overdue, missing or inconsistent in your own records, which is valuable, but whether you meet your licence conditions is a legal judgement made by the regulator against the undertakings you gave. Use the sheet to prepare, and ask a transport adviser or solicitor if you are unsure.

How long should maintenance records be kept?

The government's goods vehicle operator guide says vehicle maintenance records should be kept for at least 15 months and shown to the traffic commissioner on request. Many operators keep them longer because they also support warranty and resale. Check the current guide, since retention periods can be revised.

Who should own the sheet?

Name one person, normally the transport manager on a standard licence or the owner on a small fleet, with a nominated deputy. A shared sheet that everybody can edit and nobody reviews is the usual way records go quiet. Put a weekly review in the diary and record who did it.

Is it safe to put vehicle and driver details into an AI chat?

Use a business plan or switch off training in a consumer account, and paste only what the task needs. Driver names, licence numbers and dates of birth are personal data, so use initials or staff codes in the chat and keep the key in your own sheet.

What if I find a gap in my records?

Do not back-fill or alter old entries. Record the gap honestly, note what has been done since, and fix the process that allowed it. If it affects an undertaking on your licence, take advice on whether and how to tell the regulator.

Further reads

• Fleet Admin for Small Businesses: Automate Services, Checks and Fuel — Automate service reminders and checks for any small fleet.
• Driver Qualification File: AI Tracks Expiring Documents — Track expiring driver documents the same way.
• Detention Pay: AI Tracks Wait Times and Invoices Brokers — Log waits and invoice for them with the same discipline.
• Owner-Operator Expenses: AI Sorts Receipts and Fuel Statements — Keep the money side of a small haulier as tidy.
• AI in Fleet Management: Auditing Yard Time and Tolls From Telematics — Use telematics data to check your own records.
• How to Add Human Approval Steps to AI Automations — Keep a named person signing off what the AI flags.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: the government's Goods vehicle operator licensing guide on gov.uk (licence weights, undertakings, transport manager, planner, driver licence checks, retention periods, tachograph download intervals, 28-day notifications), read through the gov.uk content API on 5 November 2026; Microsoft Excel and Google Sheets function lists (ISOWEEKNUM). Fleet, dates and defects are illustrative.