Custom app for permit certificates and vehicle documents
At a roadside inspection, what counts is not what is filed in the office, but what is available in the cab. A driver who has to search through folders or a full inbox at that moment is kept waiting longer than necessary. And anyone who swaps vehicles overnight may, in the worst case, be driving with the copy belonging to a different registration.
What must be right in the cab
For road haulage of goods, the NIWO issues the European licence. That licence comes with licence certificates: certified copies, one for each vehicle you deploy. The licence and the certificates are valid for five years. The certificate belongs to the vehicle being driven, not to the driver and not to the company in general.
That is the practical problem. Vehicle fleets change. A tractor goes to the workshop, a driver takes another one, and the link between person, vehicle and document is least well recorded at exactly that moment. The office administration is correct; in the cab lies last week's copy.
Alongside the licence certificate, there is more that travels with the vehicle: the vehicle registration document, inspection records, insurance documents and, for international transport, additional papers. They share one thing: they belong to a registration and they carry an expiry date.
An app does not solve permit administration. That belongs in the office, in the NIWO software where the fleet and capacity requirements are kept. What the app does solve is that the driver has the correct document for the correct registration plate at the moment of inspection, even when the connection drops.
How we build this
The app revolves around one action: showing what belongs to this vehicle, right now. Anything that takes more than a few taps is, in practice, skipped.
The driver selects or scans the registration plate at the start of the journey. From that moment, the app knows which documents belong to it and which do not.
What belongs to the vehicle is put on the phone as soon as there is a connection, so it is available at the moment when there isn't one.
If a driver switches to another vehicle, the app records it with a timestamp. That way, you can see afterwards who drove which registration plate and when.
An expiring inspection or a document due for renewal should be visible before the driver pulls away, not only at the checkpoint.
What the app does in practice
Showing the right document for the right registration plate is the core of it. The rest depends on your fleet and on whether you operate internationally.
Documents per registration plate
The driver sees what belongs to this vehicle. No folder structure and no list of every vehicle in the company.
Available without coverage
Documents are stored locally on the device. Under a viaduct, in a depot or at the port, the app works the same as on the motorway.
Vehicle changeover
A change of vehicle is recorded with time and person, so the link between driver and registration plate is correct afterwards.
Validity shown on the map
Each document shows until when it is valid. What is expiring appears at the top instead of disappearing into a folder.
Reporting what is missing
If a document is missing, the driver reports it from the app, with the registration plate attached. The report reaches whoever can resolve it.
Connection to the administration
New or replaced documents come from the licensing register at the office, so no second version of the truth appears on the phones.
Who we build for
Who uses the app differs by company. Four situations.
Drivers on changing equipment
Those who are not in the same vehicle every day benefit most from a link that is confirmed per trip.
Fleet managers
They see which documents are expiring and on which vehicle something is missing, without having to call the drivers.
Companies with international transport
Cross-border journeys carry more documents. They should be ready per journey, not per company in a shared folder.
Businesses working with charter operators
For hired-in transport, you record who you work with and which documents you have checked. That belongs in the same overview as your own vehicles.
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Technology and integrations
Document types are added and validity rules change. Which papers belong to a vehicle and when a signal should be raised should be configurable, not hard-coded into the app.
Why Appfront
The document belongs to the registration plate
Not with the driver and not with the company. We build the integration so that a change of vehicle automatically brings the correct documents with it.
No signal is the norm here
Loading bays, car parks and border crossings are exactly where the document is needed. The app works there without a connection.
One source for the documents
The papers come from the administration at the office. A PDF someone once forwarded is not a source.
We don't control what happens next
We don't decide what an enforcement officer asks for or accepts. We make sure the driver has what they need within a few taps.
Security and privacy
A phone in a cab holds company documents and data that can be linked to an individual: who drove when, and in which vehicle. We set access by role, give a driver only the vehicles they are assigned to, and log every view. Anything stored locally on the device is encrypted and can be remotely wiped if a phone is lost.
For this subject, the reliability of the moment is what matters. An integration between driver and number plate added after the fact tells you nothing reliable about yesterday's journey. We record the confirmation with a timestamp and the person responsible, even when the synchronisation happens later, and any correction appears as a visible correction. How we handle security ourselves is set out in our information security policy.
Frequently asked questions about documents in the cab
That is not for us to decide. What an enforcement officer accepts depends on the rules in force at the time and on the country you are driving in. What an app does do is make sure the driver has the right document for the right registration plate immediately to hand.
Yes. Documents are loaded onto the device in advance and remain available without coverage. Changes synchronise as soon as a connection is restored.
The driver selects or scans the registration plate at the start of the journey. That confirmation is recorded, so it is clear afterwards who drove which vehicle.
The driver reports this from within the app, with the registration plate included. The report reaches the fleet manager, so it does not end up as a remark in the canteen.
We build that side separately. Fleet, power requirement and re-test are covered on our page about NIWO software.
Often, yes. If you already use an app for trips or hours, we build the document side into it rather than placing a second app alongside it. See our approach to building an app.
Does your driver know right now which document belongs with their vehicle?
Call a driver who is in a different vehicle today than yesterday and ask how they get to the licence document. If that takes longer than half a minute, a check costs you time you do not need to lose. We build this as a standalone app and as part of a broader app development project.