Jones v Padavatton

Jones v Padavatton [1968] EWCA Civ 4 is a leading English decision on contract law. The decision demonstrates how domestic agreements, such as in between a mother and daughter, are presumed not to be legally binding unless there is clear intention.

Jones v Padavatton
CourtCourt of Appeal
Decided29 November 1968
Citation(s)[1968] EWCA Civ 4, [1969] 1 WLR 328; All ER 616
Court membership
Judge(s) sittingLord Justice Danckwerts, Lord Justice Salmon, Lord Justice Fenton Atkinson
Keywords
Creating legal relations, enforceability

Facts

A mother, Mrs Violet Lalgee Jones, agreed with her daughter, Mrs Ruby Padavatton, that if she would give up her secretary job at the Indian embassy in Washington DC and study for the bar in England, the mother would pay maintenance (from Trinidad, East Indian descent). The mother gave monthly payments of 42 pounds and then bought a London house (the daughter moved out of a one-room flat in Acton to 181 Highbury Quadrant, Highbury) which she lived in and rented out. Then they had a quarrel while Mrs Padavatton was still completing her bar exams at Lincoln's Inn. The mother brought an action for possession of the house. The daughter argued there was a binding contract that she could stay.

Judgment

The Court held that there was no binding contract. Although there would have been a contract if it was not the domestic parties related, there was insufficient evidence to rebut the presumption against domestic arrangements. Also, the Court of Appeal stated that the agreement would last until the daughter had passed her Bar finals; yet 5 years had elapsed and she had still not passed them, therefore the contract had elapsed.

gollark: Lyricly is now permanently banned. How fun.
gollark: <@319753218592866315> Have you read Kevin Underhill's analysis of German beekeeping laws?
gollark: > Note: right now autofree is hidden behind the -autofree flag. It will be enabled by default in V 0.3. If autofree is not used, V programs will leak memory.
gollark: You can't use the accursed resultoptional hybrid they have in situations when you have a value which *can* actually be nonexistent for whatever reasons, and it's actually `Result<T, string>` constantly.
gollark: Because they aren't really doing "option" and "result" at that point as much as a bizarre special-cased thing which is basically just indirected exceptions.

See also

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.