Every vehicle, forklift and trailer in one register

No, and we would rather say so on the page than in the first demo. We do not sell a box for the dashboard, we do not track where a vehicle is, and we do not score how it is driven. Gfacility is the administrative record: the register, the documents, the dates, the jobs and the costs. If you need live positions, route optimisation or driver-behaviour analysis, pair us with a telematics platform and keep Gfacility as the record. Because there is no hardware and no per-vehicle device subscription, the register also covers the trailers, forklifts and e-bikes nobody fits a device to.

It makes the conversation a lot shorter. In the Netherlands and Germany a system capable of monitoring employees needs works-council consent and a privacy assessment before it goes live, and a register that holds no location or driving-behaviour data simply does not carry that weight. Driver names, licence data and penalty notices are still personal data, so they get the same access control, retention rules and EU hosting as everything else in the platform.

Yes. A vehicle or a pool booking is an orderable item in the service catalogue, with its own intake questions and its own approval step. The request that gets approved is the same record that creates the asset, the driver assignment and the order to the leasing company, so the request and the vehicle never drift apart.

That is the timeline view: one lane per vehicle or machine, showing who holds it and until when, with lease end, hand-back windows and planned maintenance drawn on the same axis. It is how you spot that a van is promised to a project during the week it is booked into the garage.

Yes. Cards are registered against the vehicle and the driver, blocked as part of offboarding and of the end-of-lease return, and their transactions can be imported and matched to the vehicle and the reading. That gives consumption per vehicle in litres or kWh per 100 km, cost per kilometre, and the outliers worth asking about.

Yes, and it is the reason the module exists in a facility platform. Equipment is measured in running hours rather than kilometres and carries its own statutory inspection certificates, so those are first-class fields rather than a workaround in a vehicle record.

The portal shows one lessor's leased vehicles and ends when the contract does. It has nothing on your owned vans, your equipment, a second leasing company, your fines or your damage history. This register is lessor-neutral, covers the whole estate and keeps the history after the lease ends.

Yes. Keep it for location and driving behaviour, and use Gfacility for the register, the expiry dates, the work orders and the costs. Odometer readings can be imported so service intervals stay accurate without anyone mailing round for readings.

The spreadsheet is usually the import. Columns become fields, one row becomes one asset, and the dates you were tracking by eye become watched dates with an owner. Most customers are live in a week, and the first thing they see is how many deadlines were already inside 30 days.

Three ways, and you can mix them: entered by the driver or technician on the record, imported from a fuel or telematics export, or captured when a work order is closed. Service intervals and contracted mileage are then measured against the real reading.

Yes. Inspection intervals differ per country, APK in the Netherlands, MOT in the UK and HU in Germany among them, so the inspection date is held per asset with its own rule and reminder rather than assuming one national schedule for the whole fleet.