Show Summary Details
Page of

(p. 17) 2. Agreement: Objective or Subjective? 

(p. 17) 2. Agreement: Objective or Subjective?
(p. 17) 2. Agreement: Objective or Subjective?

Ewan McKendrick

Page of

PRINTED FROM OXFORD LAW TROVE ( © Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a title in Oxford Law Trove for personal use (for details see Privacy Policy and Legal Notice).

date: 24 June 2021

This chapter discusses the approach adopted by the courts when seeking to ascertain the intention of the parties to a contract. The general rule is that the existence and content of an agreement are questions that must be answered by reference to the intention of the parties, objectively ascertained. Two leading cases are presented that consider the scope of the objective test, namely Smith v. Hughes (1871) LR 6 QB 597 and Centrovincial Estates plc v. Merchant Investors Assurance Company Ltd [1983] Com LR 158. The discussion then turns to the case where one party attempts to ‘snap up’ an offer which he knew that the offeror did not intend, and the case where one party was at fault in failing to notice that the other party’s offer contained a mistake, or he was himself responsible for inducing that mistake in the other party. The chapter concludes that it is not necessary to resort to a subjective approach in order to explain these cases; they can be analysed in terms consistent with the objective test which is generally applied by the courts.

Access to the complete content on Law Trove requires a subscription or purchase. Public users are able to search the site and view the abstracts and keywords for each book and chapter without a subscription.

Please subscribe or login to access full text content.

If you have purchased a print title that contains an access code, please see the information provided with the code or instructions printed within the title for information about how to register your code.

For questions on access or troubleshooting, please check our FAQs, and if you can't find the answer there, please contact us.