Upload the driver card download and aiLogistic tells you what hours were exceeded, by how much, and which article of Regulation (EC) 561/2006 applies. Deterministic calculation, no AI.
A driving time report cannot be left to intuition: either the minutes add up, or they don't.
The aiLogistic violation engine reads the activities contained within the driver card .ddd files and checks them minute by minute against the six limits of Regulation (EC) 561/2006: continuous driving, daily driving, daily rest, weekly rest, weekly driving, and fortnightly driving. For each violation, it returns the date, type, applicable article, actual value, limit, and excess in minutes, with severity calculated by percentage of excess (minor, serious, or very serious).
There is no language model making the decision. It is pure and deterministic logic: the same data always yields the same result, and the rules are written with the detail required by the regulation. Continuous driving allows for a 45-minute break and also the 15+30 split, recognizing the correct order and rejecting the reverse. Daily driving is 9 hours extendable to 10 twice a week, and the app tracks the extensions already used before flagging a violation. Daily rest is 11 hours reducible to 9 up to three times between weekly rests. Weekly rest is 45 hours, or 24 reduced, with a maximum of one reduced week in a row. And the week runs from Monday to Sunday in local time, not a rolling seven-day window.
What sets this engine apart is what it does NOT say. If the file does not cover the complete week from Monday to Sunday, weekly driving, fortnightly driving, and weekly rest are not assessed: they are marked as “not assessable” with the reason stated. If a working period is on the edge of the data, nothing is asserted about it either. If it detects double crew driving, that day is excluded due to having a different regime. No violation is declared with half a week's data because an exaggerated report is useless in an inspection.
The analysis is saved alongside the file that originated it, and re-uploading the same download does not duplicate anything: re-analysis is idempotent, it deletes the previous result of that file and redoes it, preserving the periods you had already justified manually. The entire system is backed by a battery of fixed test cases that cover each limit, including edge cases, and must remain green before any change in the engine.
The six limits, not just the two easy ones
continuous driving (art. 7), daily (art. 6.1), daily rest (art. 8.2), weekly rest (art. 8.6), weekly driving (art. 6.2), and fortnightly (art. 6.3).
Exact minutes and cited article
each finding provides the real value, the limit, the excess in minutes, and the regulation reference, not a generic notice.
Calculated severity, not invented
minor, serious, or very serious based on the percentage of excess over the limit, with the same criteria in all cases.
No AI in the decision
deterministic and reproducible logic. The same .ddd files always produce the same report, whether you run it today or in a year.
"Not assessable" when applicable
if the entire week is missing or the working day is on the edge of the file, it marks it and explains why instead of asserting an infringement with partial data.
Well-made fine rules
break 15+30 only in the correct order, counting both weekly extensions to 10 hours, up to three reduced daily rests, and only one reduced week in a row.
Ventaja 7
Natural week Monday-Sunday in local time, as calculated by an inspection, not a rolling seven-day window.
Idempotent and exportable reanalysis
re-uploading the file does not duplicate findings, and the report is generated in PDF along with the unknown activity periods pending justification.

Create your account, upload a driver card download, and view the infringement report for Regulation (EC) 561/2006 as quickly as the file can be read.