One camera pass, three fine cases: why multi-offence detection changes the workload

The new generation of enforcement cameras does not look for one thing. It reviews a passing vehicle for several offences at the same time, and each offence it records becomes a separate document with its own authority, deadline and route. A fleet that treats one camera pass as one case will be out of step with the paperwork within a month.

The operational issue

The AI cameras now in use in Greece are built to identify phone use, seatbelts, speed, red-light running and driving in reserved lanes, all without anyone reviewing the footage live. Greek data shows how much that produces: eight cameras registered 28,973 violations between 15 December and 8 January, more than 1,100 a day. A single unit on Syngrou Avenue flagged over 8,000 drivers for phone use or seatbelt offences and recorded 1,028 speeding violations in a 90 km/h zone.

Those are counts of offences, not counts of letters. When one vehicle passes one camera at one moment and the system records two offences, the fleet receives two files. They may arrive on different days, from different departments, with different deadlines and different rules about who can be held responsible.

What changes in the process

Volume is the visible part. The harder part is that the unit of work stops matching the event. A case file built around one moment no longer works when that moment produces three files. Fleet teams run into this in driver matching first, because the same driver has to be linked to several documents instead of one, and then in deadlines, because the files do not expire together.

Recharging follows the same pattern. If one offence is transferred to the driver and another is not, a fleet that groups them loses money on one and contacts the wrong person on the other. The rule per offence type decides the route, not the rule per camera.

What to review

Start with how cases are created. Does the intake split a single detection into separate files, or does it merge everything the authority sent? Check whether the deadline is stored per document or per vehicle, and whether the driver match is stored per offence. Then check the recharging step: which offence types are transferable in each country, and which stay with the fleet.

A practical next step

Take one week of fines from one country and count documents, not incidents. Group them by detection moment and see how many files share a moment. That number tells you how much of the current workload is invisible in an incident-based overview, and it is usually the most useful input for a capacity discussion.

Your fine management, fine-tuned.