In private parking cases, one of the most important things to understand is that the law treats the Driver, the Keeper, and the Hirer as separate and distinct legal persons. This is true even where, in everyday life, they may all be the same individual.
Most confusion, and many costly mistakes, arise because people assume these roles are interchangeable. They are not.
The Driver is the person who was driving and parked the vehicle at the time of the alleged event. Only the Driver can personally see and accept the terms on a parking sign and only the Driver can directly enter into a parking contract.
The Registered Keeper (usually shortened to Keeper) is the person or organisation recorded by the DVLA as responsible for taxing the vehicle. The Keeper may have had no involvement in the parking event at all.
The Hirer is the person who had possession of the vehicle under a hire or lease agreement. In these cases, the Registered Keeper is usually a leasing or hire company, not the person who was driving.
In private parking enforcement, liability does not automatically move between these roles.
As a starting point, only the Driver can ever be liable for a parking charge under ordinary contract law. Parking companies usually do not know who the Driver was. They do not witness the parking event and they have no automatic way of identifying the person behind the wheel.
Instead, operators obtain vehicle details from the DVLA. That information identifies only the Registered Keeper, not the Driver. In hire or lease situations, it identifies the hire company, not the Hirer. At the point a parking notice is issued, the operator is therefore dealing with an unknown driver.
This is why the distinction between Driver, Keeper, and Hirer matters so much.
There is no general legal obligation on a Keeper or Hirer to identify the Driver to n unregulated private parking company. Private parking operators are not public authorities, and their requests for information do not carry compulsory powers. Any suggestion that a Keeper or Hirer must name the Driver is incorrect unless a specific statutory duty applies, which is rare and tightly defined.
The identity of the Driver is significant because once the Driver is identified, the legal landscape changes. The parking operator is no longer reliant on statutory mechanisms to pursue someone else and may instead pursue the Driver directly under contract law. For this reason, the way information is disclosed, and the capacity in which a person responds to a parking notice, can materially affect who may lawfully be pursued.
Where the Driver remains unidentified, a parking operator can only attempt to transfer liability away from the Driver if strict statutory conditions are met. Those conditions are set out in the Protection of Freedoms Act 2012 and apply only in defined circumstances. They do not apply to all land, they do not apply to all types of notice, and they do not apply unless the operator has complied precisely with the statutory scheme. How that statutory mechanism operates, and when it fails entirely, is explained in the article dealing specifically with PoFA and keeper or hirer liability.
Crucially, the law does not presume that the Registered Keeper or Hirer was the Driver. There is no general rule allowing a parking company to make that assumption. The separation of these roles exists precisely because Parliament recognised that they are not the same thing.
Many misunderstandings about private parking charges stem from confusion between these legal roles. Common claims such as “the registered keeper is automatically responsible” or “you must name the driver” are examples of this confusion. These and other widespread misconceptions are addressed separately in the myths and misconceptions section.
The purpose of this article is to establish the correct concepts and terminology. Understanding who the law is referring to at each stage, and why those distinctions matter, is essential before considering parking notices, liability, appeals, or enforcement. How statutory liability may (or may not) be transferred is addressed in later articles.