Company Car Service

Lighting checks for a delivery fleet: how to plan inspections and repairs without unnecessary downtime

Check each vehicle’s lights functionally, record the result against its registration number, and arrange beam-setting measurements and repairs only where a problem has been found. Handle vehicles in batches according to fault urgency and operational availability.

26 October 2026 Redakcja FleetPoint

First, separate fleet-wide checks from workshop visits

Before the season when drivers are more likely to travel after dark, it is worth checking the lights on all company vehicles. However, this does not mean every van needs to be sent for a measurement straight away. A brief functional check helps identify vehicles that need further assessment, and workshop visits can be booked for those where something gives cause for concern.

This is a practical way to limit the number of vehicles off the road at the same time. There is no confirmed, universal repair time or number of vehicles a workshop can handle per day. Batch sizes therefore need to be set with the job schedule, replacement vehicle availability and the workshop’s actual capacity in mind.

Working lights are about more than visibility. Regulations require vehicles used on the road to be maintained in a condition that does not compromise safety and allows their lighting and signalling equipment to function properly. A detected fault should therefore not be treated merely as an entry in a fleet report.

Step 1. Decide who checks the vehicles and where the results are recorded

Assign someone to collect the check results, even if drivers carry out the checks themselves. Without a single place to record them, a report can easily be lost, vehicles can be confused, or a repair can remain unnoticed while waiting for an appointment. The form can be simple, but it should make it possible to track the process from the initial check through to the recheck.

Plan the checks to cover every active vehicle, including those not making a long journey that day. When drivers change or a vehicle is handed over, make sure the result is linked to the specific vehicle, not just to the person reporting it.

  • The vehicle’s registration number or another unique identifier, and the check date;
  • The result for each light, according to the equipment fitted to that vehicle;
  • A description of the fault and, if useful, a photo;
  • An urgency rating and an indication of whether further assessment at a workshop or a Polish vehicle inspection station (SKP) is needed;
  • The planned service date and confirmation that the vehicle was rechecked after the repair.

Step 2. Carry out a brief functional check

Include dipped and main beam headlights, sidelights, indicators, brake lights, reversing lights, fog lights and number plate lights on the form. Not every vehicle has the same set of lamps, so check the equipment fitted to each specific vehicle. The driver or coordinator can assess whether the available lights work, whether the lamps are clean and whether any damage is visible.

It is worth carrying out the check in a way that also allows the brake lights and reversing lights to be tested, for example with the help of another person. Do not assume that no report from a driver means the lights are working properly. The key is to record the result for every item, including when no issue has been found.

This check establishes whether a lamp comes on and whether any damage is visible. It does not, however, confirm that the headlights are correctly aligned or that the beam pattern and intensity are correct. These checks require specialist equipment, so arrange measurements and adjustments with an SKP or a workshop that has the appropriate equipment.

Step 3. Set the order of work according to the fault’s impact on safety

Once you have collected the forms, do not schedule visits solely by the date a fault was reported. First review faults that affect visibility or the signalling of manoeuvres. Then address the other issues identified. This is an operational order for handling faults, not a legal classification of an individual case.

Not every lighting fault automatically has the same legal consequences or means the vehicle must be taken off the road. What matters is the type of problem and its impact on safety. If you are unsure whether the vehicle can safely continue to be driven, refer it to a vehicle inspection diagnostician authorised in Poland or a workshop for assessment before further use. Do not decide this solely on the basis of your own category in a spreadsheet.

  • Urgent priority: a problem affecting visibility or the signalling of manoeuvres. Arrange an assessment and agree the next steps with the workshop as soon as possible.
  • Next in line: other detected faults that require a repair or measurement. Schedule them so that several vehicles are not off the road at the same time.
  • Uncertainty about safety: suspend the decision on whether the vehicle can continue to be driven and arrange an assessment by a Polish vehicle inspection diagnostician or workshop.

Step 4. Book vehicles in batches, not the whole fleet at once

Once you have a list of vehicles with faults, divide it into batches. Put the highest-priority vehicles in the first batch, then choose subsequent dates according to vehicle availability and the work schedule. Before confirming a visit, check which vehicles are needed for jobs and whether the company has a replacement vehicle available. Do not set a fixed number of vehicles per day as a standard in your plan: capacity depends on the workshop and the service required.

When reporting a fault, provide the vehicle identifier, check results, a description of the symptom and a photo, if one was taken. Ask the workshop to distinguish the agreed scope from any additional work that may be required. After the measurement or repair, collect details of the work carried out and update the status in your records. A fault is only closed once the record also includes a recheck.

One pitfall is booking visits for the whole fleet based only on the phrase ‘lighting check’. This may take vehicles that are working properly off the road unnecessarily. Another risk is assuming that every lamp that comes on is correctly aligned. A functional check and a beam measurement answer different questions.

Example: a delivery fleet before the season of driving after dark

A company checks the vehicles used for deliveries after dark. Drivers record the results on one form linked to the registration number. The coordinator can see which vehicles have a full set of working lights, which have a fault and where a headlight alignment measurement is needed.

The coordinator first books assessments for vehicles with issues affecting visibility or the signalling of manoeuvres. The remaining vehicles with detected problems are assigned to subsequent batches, scheduled around the job calendar and the workshop’s capacity. After the work, the coordinator records the result of the recheck. This means vehicles in good working order are not sent for measurements just because the check covered the whole fleet, and the fault list does not end with the initial report.

The results can later be assessed using simple measures: the percentage of vehicles checked, the number of faults found per 100 checks, the number of unresolved urgent faults, the time from detection to repair, and the hours vehicles are off the road. These are indicators for comparing your own results over time, not statutory or industry standards.

Summary

Operationally, three things matter most: check every vehicle, distinguish a lamp function test from a measurement of its alignment, and avoid having several vehicles in the workshop at the same time. FleetPoint can coordinate reports and appointments through a single account manager, oversee the service process and provide transparent accounting for the work. This gives the company an organised list of faults and control over repair priorities, instead of having to look for information separately from drivers and workshops.

Sources

Keep reading

More from the FleetPoint knowledge base

Browse the full knowledge base