Skip to content
Automation & interfaces

Fleet compliance: licence checks and annual inspections

Vehicle inspections at least once a year, licence checks with no statutory interval: how one deadline record per vehicle and driver reminds and escalates.

24 min read FuhrparkUVV-PrüfungFristenFührerscheinkontrolle

In short and in plain language

Company cars must be checked. An expert checks each car at least once a year. The result is written down.

The firm must also know if each person has a driving licence. The law does not say how often to look. The firm sets this itself.

Some old licences must be swapped. For cards from 2002 to 2004, the last day is 19 January 2027.

A program can keep all dates for cars and people. It sends a reminder first. It reports when a date has passed.

We help you set up such a program.

A van whose inspection date slipped by unnoticed, a driving licence currently held in official custody, an inspection report sitting in the workshop inbox: in the fleets of small and mid-sized businesses, deadline problems rarely come from carelessness. They arise because the dates live in too many places. The accident prevention regulation requires every vehicle to be inspected by a competent person at least once a year (DGUV Regulation 70, Sec. 57(1)), the statutory general inspection follows its own intervals, and the registered keeper is answerable for the driving entitlement of every employee behind the wheel without any law setting an interval for checking it (StVG, Sec. 21). This article sorts out the duties, shows which fields a deadline record per vehicle and per driver needs, and describes how reminders, escalation and filed evidence work together, right up to the day someone leaves the business.

Key takeaways

  • Every company vehicle needs an inspection by a competent person at least once a year; the result is recorded in writing and kept at least until the next inspection (DGUV Regulation 70, Sec. 57).
  • A defect-free general inspection only covers roadworthiness. Warning clothing and load securing need a separate check; for cars, a defect-free manufacturer-specified service counts if its report covers both (DGUV Regulation 70, Sec. 57).
  • No law sets an interval for licence checks. But a registered keeper who orders or allows driving without a valid entitlement commits an offence (StVG, Sec. 21); the business sets the interval and documents it.
  • Card licences issued from 2002 to 2004 must be exchanged by 19 January 2027; cards issued since 2013 are valid for 15 years, categories C1 and C for five years at most (FeV, Annex 8e, Secs. 23 and 24a).
  • One deadline record per vehicle and per person calculates due dates, sends reminders with a fixed lead time, escalates overdue items to the responsible person and stops releasing a vehicle without evidence.
  • Joining and leaving control driving rights: nobody drives before the licence check, the briefing and the employer's designation (StVG, Sec. 21; DGUV Regulation 70, Sec. 35), and assignments end on the last working day.

Who carries which duty in the fleet

Two bodies of law overlap in a fleet. Road traffic law addresses the registered keeper: the keeper must not order or allow a vehicle to be used if they know, or ought to know, that the driver is not fit to drive independently or that the vehicle does not comply with the rules (StVZO, Sec. 31(2)). Occupational safety law addresses the employer: the accident prevention regulation for vehicles sets out whom the employer may entrust with driving and how often the vehicles must be inspected (DGUV Regulation 70, Secs. 35 and 57). With company vehicles both roles usually sit with the company, but the responsibilities inside it do not: the workshop or purchasing looks after the vehicles, HR or the team lead knows the licences, and the inspection reports end up wherever someone had time to file them.

Section 21 of the Road Traffic Act shows how seriously the keeper's role is taken. Anyone who, as keeper, orders or allows a person to drive who lacks the required entitlement or is banned from driving faces up to one year in prison or a fine (StVG, Sec. 21(1) no. 2). Even negligence is an offence, punishable by up to six months in prison or a fine of up to 180 daily rates (StVG, Sec. 21(2) no. 1). Where the offence is intentional, the vehicle itself can be confiscated if the driver's entitlement had been revoked or a driving ban was in force (StVG, Sec. 21(3)). The provision does not ask about a check interval; it asks whether the keeper allowed it. A business that can show it checks regularly and acts on information stands on different ground from one that relies on the documents from the hiring interview.

For occupational safety, Section 35 of the accident prevention regulation defines who may drive independently: insured persons who have reached the age of 18, are physically and mentally fit, have been briefed on driving the vehicle, have demonstrated their ability and can be expected to carry out their tasks reliably (DGUV Regulation 70, Sec. 35(1)). They must also be designated by the employer to drive the vehicle; the implementation guidance considers it advisable to give this instruction in writing. Driving rights within a business are therefore more than a valid licence. They are a decision by the company that depends on conditions and can be recorded.

DutyWhoLegal basisInterval
Inspection by a competent person (UVV inspection)EmployerDGUV Regulation 70, Sec. 57(1)as needed, at least once a year
Record the inspection result in writingEmployerDGUV Regulation 70, Sec. 57(2)keep at least until the next inspection
Statutory general inspection (HU)Registered keeperStVZO, Sec. 29 with Annex VIII12, 24 or 36 months depending on vehicle type
Condition check by the driverDriverDGUV Regulation 70, Sec. 36(1)before each shift
Ensure a valid driving entitlementRegistered keeperStVG, Sec. 21; StVZO, Sec. 31(2)no statutory interval, set by the business
Designate and brief driversEmployerDGUV Regulation 70, Sec. 35(1)before the first independent drive

The statistics of the German statutory accident insurance for employees and business owners in 2024 show that driving for work is not a side issue in occupational safety. The share of new accident pensions among reportable occupational accidents is 1.3 percent for accidents on company premises without road traffic involvement and rises to 2.0 percent for occupational accidents on the road (DGUV). In the same year, 48 occupational accidents on the road and 39 accidents on business trips on the road were fatal (DGUV). Road accidents are rarer than accidents on company premises, but more severe on average. That is exactly why it pays to manage the two levers a business controls: the condition of its vehicles and the entitlement of the people behind the wheel.

The annual inspection under Section 57

The core fits in one sentence: the employer must have vehicles inspected for their operational safety by a competent person as needed, but at least once a year (DGUV Regulation 70, Sec. 57(1)). “As needed” means that the annual date is the floor, not the plan. An accident, a conversion of the load area or a defect report that goes beyond a trifle can make an inspection necessary before the next regular date. The record therefore needs more than the annual date; it needs a way to bring it forward.

The implementation guidance to Section 57 explains what “operationally safe” means: the inspection covers both the roadworthy and the work-safe condition of the vehicle (DGUV Regulation 70, Sec. 57). Roadworthiness concerns what a general inspection also looks at, such as brakes, steering, lights and tyres. Work safety concerns what working with the vehicle involves. The guidance gives warning clothing and load securing equipment as examples; in vans, bulkheads to the load area, shelving systems and bodywork usually belong to it as well. For bodywork such as loading cranes or aerial work platforms, the guidance also refers to inspections under separate rules, for example the Ordinance on Industrial Safety and Health.

For roadworthiness, the implementation guidance allows a shortcut: it counts as inspected if there is a defect-free result from an expert inspection under the StVZO. For cars and motorcycles it goes further: if an authorised specialist workshop has issued a defect-free result for a manufacturer-specified and properly performed service, and that result also covers the work-safe condition, for example the presence and condition of warning clothing and load securing equipment, the competent-person inspection counts as done (DGUV Regulation 70, Sec. 57). For a business with a car fleet this is the practical route: service and safety inspection fall on one date if the workshop explicitly confirms the work-safe condition in its report.

Two conditions that get lost in day-to-day work

The service only counts if the result is defect-free, and the report must mention the work-safe condition. A service record that lists only oil, filters and brake fluid does not prove it. For vans, trucks and vehicles with bodywork, the implementation guidance does not provide this equivalence; there, the competent-person inspection remains a separate check, of which a defect-free general inspection only covers the roadworthiness part.

According to the implementation guidance, a competent person is someone who, through professional training and experience, has sufficient knowledge of vehicle engineering and is familiar enough with the relevant rules to assess whether a vehicle is operationally safe. That can be the in-house workshop, a garage or an inspection organisation. What matters for the record is that the name or unit of the inspector is filed together with the report, so that it is clear later who assessed the condition.

The statistics of general inspections show how often vehicles develop defects between two dates. In 2025 the defect rate across all vehicles presented was 33.2 percent (KBA). For cars, one or more defects were found on around 8.0 million vehicles (KBA), so roughly one in three cars inspected was affected (KBA). The figures say nothing about company vehicles in particular. But they show why an inspection with a date, a result and a report is worth more than assuming a vehicle is fine because it is on the road every day.

Between the annual dates lies the condition check by the driver. Before each shift, the driver must check that the controls and safety devices work, report any defects found to the supervisor in charge and stop using the vehicle if defects endanger its operational safety (DGUV Regulation 70, Sec. 36). For a digital workflow this is the second input: a defect report captured with a form at the vehicle belongs to the same record as the inspection report. It can bring the next inspection forward or take the vehicle out of assignment until it is repaired.

General inspection: the second date on every vehicle

Alongside the annual safety inspection comes the statutory general inspection (Hauptuntersuchung, HU). Keepers of vehicles subject to registration must have them examined at regular intervals as set out in Annex VIII (StVZO, Sec. 29(1)). The intervals depend on vehicle type and permissible total weight. For the vehicles typically used in trades, services and delivery work, these values apply (StVZO, Annex VIII):

Vehicle typeGeneral inspectionSafety check
Car, first general inspection after first registrationafter 36 monthsnone
Car, every further general inspectionevery 24 monthsnone
Goods vehicle up to 3.5 t permissible total weightevery 24 monthsnone
Goods vehicle over 3.5 t up to 7.5 tevery 12 monthsnone
Goods vehicle over 7.5 t, after the initial periodevery 12 months6 months after each general inspection

The month of the next general inspection is shown on the inspection sticker on the rear number plate (StVZO, Sec. 29(2)). For the deadline record this is a month, not a day, and that is exactly what sets it apart from the annual safety inspection, which is tied to an inspection date. Both dates therefore belong in separate fields. If you want to combine them, deliberately schedule the safety inspection in the month of the general inspection or the service and have both done in one visit, provided the inspecting body also assesses the work-safe condition and notes it in the report.

The permissible total weight decides not only the inspection interval but also the licence category needed. Category B covers motor vehicles with a permissible total weight of no more than 3,500 kg (FeV, Sec. 6(1)). A van above that requires category C1 and thus an entitlement that is granted for a limited period. Each vehicle record therefore needs the permissible total weight and the required category, so that the assignment can check whether person and vehicle match. A spreadsheet with vehicles and drivers on separate tabs cannot perform this check.

Licence checks without a statutory interval

There is no comparable deadline rule for the driving entitlement. Section 21 of the Road Traffic Act penalises the keeper who orders or allows driving without an entitlement, but it does not say how often the keeper must check. The accident prevention regulation also sets conditions for drivers but no check interval (DGUV Regulation 70, Sec. 35). That is not a free pass but a task: the business sets the interval itself, justifies it and can show that it keeps to it. A one-off check at hiring hardly carries that justification, because a driving entitlement can be lost at any time.

The driving aptitude register shows how often that happens: in 2025, 85,864 driving entitlements were revoked (KBA). On top of that come driving bans, which an administrative authority or a court can impose for one to three months (StVG, Sec. 25(1)). For the duration of the ban, a licence issued by a German authority is held in official custody (StVG, Sec. 25(2a)). A visual check therefore only confirms the state on that day: a ban that takes effect afterwards, or a revocation in the weeks after the check, remains invisible to it.

The gap between two checks is closed not by software but by an agreement. Anyone who drives a company vehicle reports a revocation, driving ban or restriction of their entitlement without delay. This reporting duty belongs in the vehicle use agreement or the work instruction, and the record notes that it was communicated and acknowledged. The regular visual check then confirms that the details are still correct, and the reporting duty covers the time in between.

For the check itself, the original document is usually enough. The driving entitlement must be proven by a valid official certificate, and a valid licence must be carried when driving a motor vehicle (FeV, Sec. 4(2)). Every visual check covers the same points and records them:

  • Name and photo match the person who is to drive the vehicle.
  • The categories shown cover the assigned vehicle groups, for example C1 for vans over 3.5 t.
  • The expiry date of the card and the validity of time-limited categories lie in the future.
  • Conditions and restrictions shown as code numbers on the card are known and complied with.
  • Date, checking person and the result for each point are stored in the person's record.

Which interval is appropriate depends on the business: on the number of trips, the type of vehicles and whether someone drives every day or occasionally takes a pool car. In the deadline record the interval is therefore a value per person or group, not a hard-coded one. If the business changes its rule, it changes a parameter and all due dates are recalculated. The decision itself and its reasoning belong in writing in the fleet policy.

Expiry dates on the card: exchange and time limits

Besides the question of whether the entitlement exists, there is a second one that a visual check easily misses: is the document still valid? Licences issued on or after 19 January 2013 are valid for 15 years (FeV, Sec. 24a(1)). Older licences must be exchanged according to a staggered schedule; once the relevant deadline has passed, the licence loses its validity (FeV, Sec. 24a(2)). The stages are set out in Annex 8e of the Driving Licence Regulation (FeV, Annex 8e):

LicenceExchange byBasis
Paper licence up to 1998, holder born 1953 or laterexpired, at the latest on 19 January 2025FeV, Annex 8e
Card licence issued 1999 to 2001expired on 19 January 2026FeV, Annex 8e
Card licence issued 2002 to 200419 January 2027FeV, Annex 8e
Card licence issued 2005 to 200719 January 2028FeV, Annex 8e
Card licence issued 2008 to 18 January 2013by year of issue, 19 January 2029 to 19 January 2033FeV, Annex 8e
Holder born before 1953, regardless of year of issue19 January 2033FeV, Annex 8e
Card licence issued on or after 19 January 2013valid for 15 years, date shown on the cardFeV, Sec. 24a(1)

The next stage affects many workforces directly: card licences issued from 2002 to 2004 must be exchanged by 19 January 2027 (FeV, Annex 8e). The driving entitlement itself does not lapse if the exchange is missed; what becomes invalid is the document used to prove it (FeV, Sec. 4(2) and Sec. 24a(2)). For the business it is still a case for the deadline list, because someone driving with an invalid licence cannot prove their entitlement as required at a roadside check. The record therefore needs the year of issue for older cards and, for newer cards, the printed expiry date.

A third deadline is tied to the categories. Entitlements for categories AM, A1, A2, A, B, BE, L and T are granted without a time limit, those for categories C1, C1E, C, CE, D1, D1E, D and DE for five years at most (FeV, Sec. 23(1)). Anyone driving vans over 3.5 t or trucks therefore needs a renewal every five years, with whatever evidence the licensing authority requires. If category C1 expires, category B remains: the person may still drive cars but no longer the heavy van. The assignment has to know exactly this distinction, otherwise it blocks too much or too little.

One deadline record per vehicle and per person

The record follows from the duties. It has two halves linked by the assignment: for each vehicle the inspection dates and evidence, for each person the entitlement, the checks and the briefing. A spreadsheet can hold this as long as one person maintains it and nobody else writes at the same time. As soon as the workshop, HR and dispatch look at the same dates, a shared data set with role-based rights is the more stable route. When moving away from the spreadsheet pays off is covered in the article Replacing spreadsheet workarounds.

Vehicle: master data

Internal number, number plate, vehicle type, permissible total weight and the licence category derived from it, plus location and responsible unit.

Vehicle: inspection dates

Date of the last safety inspection, interval and calculated due date, month of the next general inspection, the safety check for heavy vehicles, dates for bodywork.

Vehicle: evidence

Inspection report for each date with inspecting body and result, open defects with a deadline for repair and the defect reports from the pre-shift check.

Person: driving rights

Personnel number, area of work, driving rights with date and designating unit, and the vehicle groups they apply to.

Person: entitlement

Categories, expiry of time-limited categories, expiry date or year of issue of the card, code numbers, last visual check and the business check interval.

Person: briefing

Date of the briefing on driving the vehicle, acknowledged duty to report revocations or bans, and the vehicle use agreement.

Due dates are calculated from these fields, not typed in by hand. For the safety inspection the due date is the last inspection date plus the interval, where the interval is one year at most and can be shorter if the use or condition of the vehicle requires it. For a time-limited category the expiry date is the due date; for the visual check it is the date of the last check plus the business interval. Once the logic is defined this way, no calendar follow-up is needed; the overview emerges from the data, just as the article on tracking inspection deadlines without paper describes for work equipment.

The real gain lies in the link. When a vehicle is assigned to a person, permanently as a company car, by the day as a pool vehicle or through shift planning, the workflow checks three things: whether the vehicle has a valid safety inspection and general inspection, whether the person holds the required category, and whether their last check lies within the interval. If one of the three fails, the assignment does not fail silently but states the reason. How such checks are built into a plan is shown in the article on shift rosters that check rest periods and qualifications.

Remind, escalate, block

A record that only displays due dates is a better list. It becomes effective when it acts: it reminds in good time, it escalates when nobody responds, and it halts assignment when evidence is missing. The stages can be put into words and can therefore be automated. The time spans in the following sequence are example values that each business sets for itself.

A set time before the due date, for example 14 days for the visual check and four weeks for the safety inspection, a reminder goes to the person and to the fleet desk. For vehicles, the workflow proposes a slot with the workshop or inspection body.

Escalation needs a responsibility that does not hinge on a single person. Who is in charge of the fleet, who deputises and when a notice goes to management belong in a rule, just as with approvals, whose deputies and deadlines are covered in the article on digitising approval workflows. A reminder sent to an inbox nobody reads is not a reminder.

Halting assignment is the step that affects daily work the most. It therefore needs a clear way out for the case where the inspection took place but the report has not been filed yet: an authorised person confirms the appointment with a reason, the halt is lifted for a few days, and the log records who decided this. For the driving entitlement there is no such way out. There, only a new visual check lifts the halt, because Section 21 StVG and Section 31 StVZO apply precisely at this point.

Filing evidence without collecting more than needed

For the safety inspection, the regulation prescribes the evidence: the results must be recorded in writing and kept at least until the next inspection (DGUV Regulation 70, Sec. 57(2)). The implementation guidance names an inspection log, an inspection card index or an inspection report as examples. In a digital workflow this is the report from the workshop or competent person, filed with the vehicle, with inspection date, inspecting body, result and, where there were defects, confirmation that they have been fixed. Which form the responsible accident insurance institution expects in a given case can be clarified with it before the paper binder is retired.

So that reports do not end up as attachments in someone's inbox, filing needs a fixed entry point: a shared mailbox or an upload on the vehicle record, from which the report is matched via number plate or internal number. Text recognition can read the inspection date and number plate from the document and make a suggestion that a person confirms. How such capture is set up is described on the page on document digitisation.

For licence checks the opposite principle applies: file as little as possible. Personal data must be adequate, relevant and limited to what is necessary for the purpose (GDPR, Art. 5(1)(c)). To prove a check, date, checking person, categories seen, expiry dates and the result are usually enough. A full copy of the card with photo and licence number is mostly not needed for this; anyone who files one anyway records the reason and keeps access tight. Which other questions need answering when digitising processes involving personal data is collected in the article on data protection when digitising processes.

Access to and retention of driver data follow the rules of the personnel file, not those of the vehicle file. The workshop and dispatch can see whether a person is cleared for a vehicle group, but not the details of their entitlement. How rights and retention periods are handled in a digital personnel file is described in the article Digital personnel files: access, retention and evidence.

Besides inspection and check dates, a fleet carries contracts with their own deadlines: leasing, insurance, maintenance contracts and fuel cards. They do not belong in the inspection deadline record but in a contract register with notice and renewal dates. How to build such a register is shown in the article on contract registers, notice periods and renewals.

Joining, moving, leaving: HR data as the trigger

Many gaps in a fleet arise at the transitions. A new employee gets the keys on day one because a customer appointment is pressing, and the licence check is noted for later. An employee moves from a car to the heavy van, and nobody checks whether he holds category C1. A driver who has left still appears as authorised to drive weeks later. None of these cases is ill will; each happens because the information arises in one place and is needed in another.

The trigger for all three cases sits in the HR master data: joining, a change of role and leaving are created there anyway as a record with a date. If the fleet workflow is connected to it, joining creates an open task “check driving rights” with a visual licence check (StVG, Sec. 21), a briefing on driving the vehicle and designation by the employer (DGUV Regulation 70, Sec. 35(1)). Only when all three are done is the person cleared for driving. The briefing belongs in the same matrix as the other safety briefings; how these are planned and evidenced per person is covered in the article on safety briefings, scheduled and evidenced.

When someone changes role, the workflow compares the vehicle groups of the new position with the person's categories. If a category is missing, assignment for that group is not released and HR receives a note. On leaving, driving rights end on the last working day; keys, fuel card and logbook are tracked as items to be returned, and the driver data is deleted once the defined retention period has passed. The same logic for accounts and access is described in the article on account access when staff join and leave.

The vehicle side is not affected by this. Inspection reports belong to the vehicle and must remain available at least until the next inspection, regardless of who last drove it. If a vehicle is sold or returned to the lessor, its record is closed and only deleted once the retention period set by the business has expired.

From binder to record in five steps

Moving from a binder to a deadline record is not a major project if it happens in the right order. Five steps keep it manageable, and each one on its own already leaves you in a better position than before:

  1. Take stock: all vehicles with internal number, number plate, type and permissible total weight, all people with driving rights, plus the last inspection report and the general inspection month for each vehicle.
  2. Set the rules: inspection interval per vehicle group, check interval per group of people, reminder lead times, responsibility and deputies. The business makes these decisions, not the software.
  3. Create and fill the record: transfer from the existing list and mark gaps instead of guessing. A missing inspection date is an open task, not an empty field.
  4. Connect the sources: HR master data for joining and leaving, shift planning or pool booking for assignment, a mailbox or upload for inspection reports.
  5. Review the first run: hold the overview of due dates against reality, clear overdue items and watch reminders and escalations for a few weeks before switching on the assignment halt.

Sectors differ mainly on the vehicle side. In the trades, vans with shelving and load securing often shape the picture; in logistics, heavy vehicles with safety checks and time-limited categories; at service providers, pool vehicles used occasionally by many people. The record is the same in all three cases; what differs is the inspection intervals, the check intervals and who does the assigning.

How we set up the fleet workflow

We build the fleet workflow with the systems the business already has: HR master data, shift planning, document storage and calendar. In a process analysis we record where vehicle data, licence checks and inspection reports live today and who maintains them. From this we create the deadline record with your business rules, and process automation takes over reminders, escalation, assignment checks and the log, including the cases where a system does not respond or a mandatory field is empty.

Where data from several programs comes together, such as the personnel number from payroll and the vehicle data from the workshop software, data integration defines the one place where each item is maintained. Which inspection and check intervals you set remains your decision; we set up the system so that it keeps to these rules and documents them. To get started, a short description via the contact page is enough: how many vehicles and drivers, where the lists live today and who maintains them. We do not need any personal driver lists for this.

This article is based on data from: Accident Prevention Regulation for Vehicles (DGUV Regulation 70, Secs. 35, 36 and 57 with implementation guidance, BG Verkehr edition), Road Traffic Act (StVG, Secs. 21 and 25), Road Vehicle Registration and Licensing Regulation (StVZO, Secs. 29 and 31, Annex VIII), Driving Licence Regulation (FeV, Secs. 4, 6, 23 and 24a, Annex 8e), General Data Protection Regulation (Art. 5), Federal Motor Transport Authority (KBA: vehicle inspection statistics for 2025 and key figures on drivers, annual review 2025) and DGUV (occupational accident statistics 2024). The information is general and does not replace legal advice in individual cases.

Related Articles

Data & documents

Storing e-invoices: what the GoBD require since 2025

Since the July 2025 GoBD amendment, keeping the XML part of e-invoices is enough. When the PDF part must stay and how to file incoming and outgoing invoices.

22 min read
Law, security & funding

Minimum wage 2027: updating master data and costing

From 1 January 2027 the German minimum wage is 14.60 euros. Where the rate hides outside payroll, how mini-job rosters fit and what belongs in your costing.

19 min read
Process analysis & assessment

Digitalisation plan 2027: from single projects to a roadmap

How small firms turn separate digital projects into a 2027 digitalisation plan: systems, fixed dates, dependencies, budget per quarter and clear ownership.

18 min read