When a transport inspector stops a VTC (private-hire) vehicle on a Spanish highway, the first thing they ask for isn't the vehicle's license. It's proof that this specific ride was reported to the RVTC, the national VTC vehicle registry, before it started. If it wasn't, the fine doesn't care whether the reason was "I forgot" or "I didn't know": the vehicle can be taken off the road on the spot.
If you run or plan to run a VTC operation in Spain, this is worth understanding even if you're not based there yourself, because it's one of the more distinctive compliance regimes in the private transport industry: pre-trip reporting to a live registry, not after-the-fact record-keeping. This article isn't legal advice: it's an operational checklist of what a VTC fleet in Spain has to keep current, meant to be reviewed monthly, not read once and forgotten.
Legal notice
This content summarizes common obligations for the VTC sector in Spain as of publication. The rules vary by autonomous community and change over time (the LOTT transport law and its implementing regulation, plus the specific conditions attached to each authorization). Before making a decision that depends on this, consult a lawyer specialized in transport law or the sector association in your region.
The framework: the LOTT and the RVTC
Spain's Ley de Ordenación de los Transportes Terrestres (LOTT) and its implementing regulation govern VTC activity nationally, but the day-to-day operational detail runs through the RVTC, the registry where every operator has to log each ride before it's provided. It isn't an after-the-fact record: the pre-trip communication is what legitimizes the ride at the moment it happens.
What "before it's provided" means in practice
The communication to the RVTC has to happen with whatever minimum lead time the current regulation requires (typically minutes, not hours, and the margin is tight), and has to include the plate number, the driver and the time window of the ride. A dispatch system that assigns the job and reports it in the same flow avoids the most common failure mode: the ride itself went fine, but it was reported late, or not reported at all.
Documentation checklist: what has to stay current at all times
- Valid VTC authorization for the vehicle, matching the correct autonomous community if it operates under regional rules.
- Liability insurance with specific coverage for passenger transport, not a personal auto policy.
- Current roadworthiness inspection (ITV), on the schedule that applies to a professional-use vehicle, which is more frequent than a private car.
- Driver's license/certificate current and valid, and confirmation that the driver actually behind the wheel is the one reported to the RVTC for that ride.
- Vehicle identification decal, if the relevant autonomous community requires one to be visibly displayed.
- Record of every reported ride, kept for as long as the regulation requires, so you can answer a retroactive audit, not just a roadside stop.
- Driver-with-vehicle lease agreement, when the ride is provided under that arrangement, signed and dated before the ride takes place.
The three failures that generate the most fines
1. Reporting late, not reporting wrong
The content of the RVTC report is almost never the problem: the timing is. An operator dispatching over WhatsApp and reporting to the RVTC "whenever there's a gap" is operating with an open fine risk on every single ride, even if it works out fine 95% of the time.
2. The driver doesn't match what was reported
If the person actually driving isn't the one reported (a last-minute swap for a sick day or an emergency), the ride isn't covered even though the vehicle is. This is the most common failure in fleets where several drivers share a vehicle.
3. Expired paperwork with no advance warning
Insurance, the roadworthiness inspection and the authorization all have expiry dates. Without a system that warns weeks ahead, it's easy to discover a vehicle has been running for two weeks on an expired inspection only when an inspector stops it.
How to run this without depending on one person's memory
The approach that scales is treating compliance as data, not as a folder: every vehicle with its expiry dates, every driver with their license attached, and every ride reported in the same step it's dispatched, not as a separate task someone can forget on a busy day. The bigger the fleet, the more expensive it gets to depend on one person remembering to renew ten documents on time.
Summary table: document, typical expiry, consequence if it lapses
| Document | Typical expiry | Consequence if it lapses |
|---|---|---|
| VTC authorization | Tied to the grant | Vehicle taken off the road |
| Liability insurance | Annual | Ride runs uncovered, serious fine |
| Roadworthiness inspection | 6-12 months (professional use) | Vehicle can't carry passengers |
| Driver's license/certificate | Per certificate | Driver not qualified for the ride |
| RVTC report | Per ride, before it starts | Fine for an unreported ride |
What to do next
Run this exercise on your current fleet: for every vehicle, do you know the exact expiry date of its inspection, insurance and authorization without having to dig through a folder? If the answer takes more than a minute, that's the first gap to close, before an inspector finds it for you. Related: if your fleet's cancellation policy isn't written down either, the no-show policy is the next document worth putting on paper. TransfersManager stores each vehicle's and driver's documentation with expiry dates and advance alerts, so compliance doesn't depend on someone remembering.
