03-03-2026, 07:34 PM
On initial review of the material provided, the company presently benefits from a solid Schedule 4 position.
The Notice to Keeper is vulnerable on PoFA grounds and, if tested in court, that defect would likely prevent the operator from transferring liability to the company. Legally, that is a strong footing.
The issue is not whether the PoFA argument is sound, but whether it will ever be permitted to do its work. If the company is inclined to settle once the tone escalates, the statutory protection becomes academic rather than operative.
Ordinarily, a defect of this nature places the operator in a binary position: identify the driver or abandon keeper liability. Because the point is rooted in statutory wording rather than factual dispute, it carries real weight before a judge.
The constraint in this case is therefore not the law, but the employer’s likely response to escalation.
If the employer has a pattern of capitulating as soon as debt recovery letters begin, then the practical value of a PoFA defence is limited. It will never reach the stage where the argument is tested. The operator will escalate to a debt collector, the tone of correspondence will change, and the employer will pay to make it go away. In that scenario, the statutory defence is legally sound but commercially irrelevant because it will not be allowed to operate.
You therefore have two paths.
The first is to maintain the PoFA position and keep the matter at keeper level. That preserves the strongest technical defence. But it leaves control in the hands of an employer who has demonstrated that they will likely fold once the matter escalates.
The second option is to identify the driver. If the driver is formally named with a full serviceable address, the operator must pursue the driver directly. That removes the employer from the liability chain and from the decision-making process.
However, that step has consequences.
Once the driver is identified, the Schedule 4 protection falls away. There is no longer any need for the operator to rely on keeper liability. The claim becomes a straightforward contractual claim against the driver. Any PoFA defect becomes irrelevant. The driver stands alone.
That does not mean the case becomes weak. It simply means the defence must move from statutory technicality to substantive liability.
As driver, the available defences would be as follows.
First, signage and contractual formation.
The sign states “NO PARKING” and then refers to liability for a parking charge of £100. There is an argument that a purely prohibitive sign does not offer a contractual licence to park on terms, but instead withdraws permission entirely. In that construction, no contract is formed and the only possible cause of action would be trespass, which only the landowner could pursue and only for actual loss.
That argument is not frivolous, but it is not a guaranteed winner. Courts increasingly treat signs that combine a prohibition with a stated charge as creating a contractual framework. The presence of the £100 charge and reference to driver liability strengthens the operator’s contractual argument.
A clearer photograph of the signage will assist in assessing the precise wording and structure of the terms, which is essential to determining whether the sign creates a contractual offer capable of acceptance or merely imposes a prohibition. The exact language used, particularly how the £100 charge is framed, is critical to analysing whether any enforceable contract arose.
Second, implied licence as a contractor.
The driver was not a random motorist. The vehicle was attending a legitimate business on that private road. There is a strong argument that a business operating from that site carries with it an implied right of access for customers and suppliers. That implied licence extends to reasonable use of the access road incidental to deliveries and collections.
The operator will say that any such licence does not extend to remaining stationary in breach of clearly displayed restrictions. The strength of this defence will depend on the precise terms of the leaseholder’s rights and the nature of access arrangements on that road.
Third, necessity due to mechanical defect.
This is the most factually persuasive defence. The vehicle developed a defect affecting its lighting system, rendering it unroadworthy and unsafe for continued operation. If the vehicle could not lawfully or safely continue, and arrangements were made promptly to attend a repair facility, then the stop was not discretionary parking. It was compelled by safety and regulatory necessity.
If compliance with the alleged contractual term (immediate departure) would have required the driver to commit a regulatory offence or create a road safety risk, that materially alters the analysis. Contract law does not require a party to commit illegality or expose themselves to danger in order to avoid a parking charge.
The key will be evidence. The nature of the defect, when it was discovered, why the vehicle could not be moved elsewhere immediately, and whether the duration of approximately 39 minutes was strictly necessary must all be capable of being explained coherently.
Fourth, proportionality and legitimate interest.
This is not a retail car park managing turnover. It is an industrial access road serving businesses. Penalising a contractor dealing with a safety defect does not obviously serve a legitimate commercial interest comparable to the Supreme Court reasoning in Beavis. That does not automatically defeat the claim, but it frames it differently.
If the driver is identified, the case is no longer technical. It becomes fact-sensitive and evidence-driven. It is defensible, but it carries litigation risk. You would need to be prepared to defend a small claim properly and calmly.
As for the IAS, you should approach it with realistic expectations.
An IAS appeal will need to be tightly structured and focused on legal points and evidential necessity. It should not read like a forum submission. It should identify the statutory and contractual defects, the absence of a defined parking period, the nature of the signage, the implied licence, and the safety-driven necessity.
However, the IAS is not a court. It is not a statutory tribunal. It is operated within the same corporate environment as the trade association and therein lies the inherent conflict of interest. Assessors are anonymous and most likely not even legally trained, even though they mendaciously claim they are. They are supposed to produce reasoned, legally rigorous decisions but, as experience shows, that is highly unlikely. Technical arguments, particularly on PoFA, are frequently dismissed with superficial reasoning. Fact-based arguments are usually brushed aside if the operator’s photographs show a vehicle stationary for a period of time.
In blunt terms, an IAS rejection is more likely than not, regardless of merit.
The IAS stage should therefore be treated as a procedural step, not as the arena in which you expect justice to be done. The real battleground, if it comes to it, is the small claims court, where statutory construction, contractual principles, and evidence are examined impartially by an actual judge.
The decision therefore comes down to control versus protection.
Keeping the matter at keeper level preserves the strongest statutory defence but leaves the employer as the weak link.
Identifying the driver removes the employer from the equation, removes the PoFA shield, and places the matter squarely in the hands of someone willing to defend it.
The legal case remains defensible if the driver is named. It simply changes character from a technical Schedule 4 challenge to a substantive contractual and necessity-based defence.
In your scenario, my advice is to appeal to IAS as Keeper. If rejected, immediately notify the operator of the driver’s full name and serviceable address and require all future correspondence to be directed to the driver. This approach preserves leverage for as long as possible without triggering the employer’s reflex payment behaviour.
As for the “Head of Legal & Compliance,” there is no strategic value in further informal contact. That avenue has been exhausted. The matter should now be treated as adversarial and procedural.
The defence, if the driver is later identified, remains viable on signage, implied licence, and necessity grounds. But control over who receives the pressure letters is a separate strategic decision, and the proposed timing is the rational one if employer behaviour is the dominant constraint.
Do you need assistance in putting together the IAS appeal at this stage?
The Notice to Keeper is vulnerable on PoFA grounds and, if tested in court, that defect would likely prevent the operator from transferring liability to the company. Legally, that is a strong footing.
The issue is not whether the PoFA argument is sound, but whether it will ever be permitted to do its work. If the company is inclined to settle once the tone escalates, the statutory protection becomes academic rather than operative.
Ordinarily, a defect of this nature places the operator in a binary position: identify the driver or abandon keeper liability. Because the point is rooted in statutory wording rather than factual dispute, it carries real weight before a judge.
The constraint in this case is therefore not the law, but the employer’s likely response to escalation.
If the employer has a pattern of capitulating as soon as debt recovery letters begin, then the practical value of a PoFA defence is limited. It will never reach the stage where the argument is tested. The operator will escalate to a debt collector, the tone of correspondence will change, and the employer will pay to make it go away. In that scenario, the statutory defence is legally sound but commercially irrelevant because it will not be allowed to operate.
You therefore have two paths.
The first is to maintain the PoFA position and keep the matter at keeper level. That preserves the strongest technical defence. But it leaves control in the hands of an employer who has demonstrated that they will likely fold once the matter escalates.
The second option is to identify the driver. If the driver is formally named with a full serviceable address, the operator must pursue the driver directly. That removes the employer from the liability chain and from the decision-making process.
However, that step has consequences.
Once the driver is identified, the Schedule 4 protection falls away. There is no longer any need for the operator to rely on keeper liability. The claim becomes a straightforward contractual claim against the driver. Any PoFA defect becomes irrelevant. The driver stands alone.
That does not mean the case becomes weak. It simply means the defence must move from statutory technicality to substantive liability.
As driver, the available defences would be as follows.
First, signage and contractual formation.
The sign states “NO PARKING” and then refers to liability for a parking charge of £100. There is an argument that a purely prohibitive sign does not offer a contractual licence to park on terms, but instead withdraws permission entirely. In that construction, no contract is formed and the only possible cause of action would be trespass, which only the landowner could pursue and only for actual loss.
That argument is not frivolous, but it is not a guaranteed winner. Courts increasingly treat signs that combine a prohibition with a stated charge as creating a contractual framework. The presence of the £100 charge and reference to driver liability strengthens the operator’s contractual argument.
A clearer photograph of the signage will assist in assessing the precise wording and structure of the terms, which is essential to determining whether the sign creates a contractual offer capable of acceptance or merely imposes a prohibition. The exact language used, particularly how the £100 charge is framed, is critical to analysing whether any enforceable contract arose.
Second, implied licence as a contractor.
The driver was not a random motorist. The vehicle was attending a legitimate business on that private road. There is a strong argument that a business operating from that site carries with it an implied right of access for customers and suppliers. That implied licence extends to reasonable use of the access road incidental to deliveries and collections.
The operator will say that any such licence does not extend to remaining stationary in breach of clearly displayed restrictions. The strength of this defence will depend on the precise terms of the leaseholder’s rights and the nature of access arrangements on that road.
Third, necessity due to mechanical defect.
This is the most factually persuasive defence. The vehicle developed a defect affecting its lighting system, rendering it unroadworthy and unsafe for continued operation. If the vehicle could not lawfully or safely continue, and arrangements were made promptly to attend a repair facility, then the stop was not discretionary parking. It was compelled by safety and regulatory necessity.
If compliance with the alleged contractual term (immediate departure) would have required the driver to commit a regulatory offence or create a road safety risk, that materially alters the analysis. Contract law does not require a party to commit illegality or expose themselves to danger in order to avoid a parking charge.
The key will be evidence. The nature of the defect, when it was discovered, why the vehicle could not be moved elsewhere immediately, and whether the duration of approximately 39 minutes was strictly necessary must all be capable of being explained coherently.
Fourth, proportionality and legitimate interest.
This is not a retail car park managing turnover. It is an industrial access road serving businesses. Penalising a contractor dealing with a safety defect does not obviously serve a legitimate commercial interest comparable to the Supreme Court reasoning in Beavis. That does not automatically defeat the claim, but it frames it differently.
If the driver is identified, the case is no longer technical. It becomes fact-sensitive and evidence-driven. It is defensible, but it carries litigation risk. You would need to be prepared to defend a small claim properly and calmly.
As for the IAS, you should approach it with realistic expectations.
An IAS appeal will need to be tightly structured and focused on legal points and evidential necessity. It should not read like a forum submission. It should identify the statutory and contractual defects, the absence of a defined parking period, the nature of the signage, the implied licence, and the safety-driven necessity.
However, the IAS is not a court. It is not a statutory tribunal. It is operated within the same corporate environment as the trade association and therein lies the inherent conflict of interest. Assessors are anonymous and most likely not even legally trained, even though they mendaciously claim they are. They are supposed to produce reasoned, legally rigorous decisions but, as experience shows, that is highly unlikely. Technical arguments, particularly on PoFA, are frequently dismissed with superficial reasoning. Fact-based arguments are usually brushed aside if the operator’s photographs show a vehicle stationary for a period of time.
In blunt terms, an IAS rejection is more likely than not, regardless of merit.
The IAS stage should therefore be treated as a procedural step, not as the arena in which you expect justice to be done. The real battleground, if it comes to it, is the small claims court, where statutory construction, contractual principles, and evidence are examined impartially by an actual judge.
The decision therefore comes down to control versus protection.
Keeping the matter at keeper level preserves the strongest statutory defence but leaves the employer as the weak link.
Identifying the driver removes the employer from the equation, removes the PoFA shield, and places the matter squarely in the hands of someone willing to defend it.
The legal case remains defensible if the driver is named. It simply changes character from a technical Schedule 4 challenge to a substantive contractual and necessity-based defence.
In your scenario, my advice is to appeal to IAS as Keeper. If rejected, immediately notify the operator of the driver’s full name and serviceable address and require all future correspondence to be directed to the driver. This approach preserves leverage for as long as possible without triggering the employer’s reflex payment behaviour.
As for the “Head of Legal & Compliance,” there is no strategic value in further informal contact. That avenue has been exhausted. The matter should now be treated as adversarial and procedural.
The defence, if the driver is later identified, remains viable on signage, implied licence, and necessity grounds. But control over who receives the pressure letters is a separate strategic decision, and the proposed timing is the rational one if employer behaviour is the dominant constraint.
Do you need assistance in putting together the IAS appeal at this stage?
Never argue with stupid people. They will drag you down to their level and then beat you with experience. - Mark Twain
