<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Newfoundland and Labrador Construction Law &#187; Contract Terms</title>
	<atom:link href="http://www.adambaker.net/category/terms/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adambaker.net</link>
	<description>Case comments by Adam Baker.</description>
	<lastBuildDate>Wed, 09 Nov 2011 03:39:07 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Case Brief: R. v Ron Engineering</title>
		<link>http://www.adambaker.net/case-brief-r-v-ron-engineering/</link>
		<comments>http://www.adambaker.net/case-brief-r-v-ron-engineering/#comments</comments>
		<pubDate>Tue, 07 Dec 2010 01:31:58 +0000</pubDate>
		<dc:creator>Adam Baker</dc:creator>
				<category><![CDATA[Bid Bonds]]></category>
		<category><![CDATA[Compliance with Tender Terms]]></category>
		<category><![CDATA[Contract Terms]]></category>
		<category><![CDATA[Bidding Process]]></category>
		<category><![CDATA[Breach of Tender]]></category>
		<category><![CDATA[Invitation to tender or bid]]></category>
		<category><![CDATA[Tender Compliance]]></category>
		<category><![CDATA[Tenders]]></category>

		<guid isPermaLink="false">http://www.adambaker.net/?p=363</guid>
		<description><![CDATA[R. (Ont.) v Ron Engineering &#038; Construction (Eastern) Ltd., [1979] 24 OR (2d) 332 (ONCA), revd [1981] 1 SCR 111, online: LexUM http://scc.lexum.umontreal.ca/en/1981/1981scr1-111/1981scr1-111.html This case is understood to be the leading case on the law of bidding and tendering in Canada. Facts The province of Ontario (the “owner”) retained an engineering consulting firm to prepare [...]]]></description>
			<content:encoded><![CDATA[<p></p><p><em>R. (Ont.)</em> v <em>Ron Engineering &#038; Construction (Eastern) Ltd.</em>, [1979] 24 OR (2d) 332 (ONCA), revd [1981] 1 SCR 111, online: LexUM <a href="http://scc.lexum.umontreal.ca/en/1981/1981scr1-111/1981scr1-111.html">http://scc.lexum.umontreal.ca/en/1981/1981scr1-111/1981scr1-111.html</a></p>
<p>This case is understood to be the leading case on the law of bidding and tendering in Canada.</p>
<h2>Facts</h2>
<p>The province of Ontario (the “owner”) retained an engineering consulting firm to prepare an estimated budget for the construction of a new water and sewage treatment plant.  The consultants returned a budget estimate of $2,744,700. The owner then issued a call for tenders for the construction of the plant.  The tender documents required a tender deposit to be submitted with the bids, and included the following statement:</p>
<blockquote><p>
. . . the tenderer guarantees that if his tender is withdrawn before the Commission shall have considered the tenders or before or after he has been notified that his tender has been recommended to the Commission for acceptance . . . the Commission may retain the tender deposit for the use of the Commission and may accept any tender, advertise for new tenders, negotiate a contract or not accept any tender as the Commission may deem advisable.
</p></blockquote>
<p>Ron Engineering (the “contractor”), submitted a bid on time and with the required $150,000 deposit in the form of a certified cheque.  An employee of the contractor was present for the opening of all the bids.  At $2,748,000, the contractor came in over $600,000 lower than the next bidder.  The employee immediately called the president of the contractor company about the possibility of a mistake in the bid.  Before she could tell him about the tender opening, he told her that he found he had made a mistake in the bid.  It was held as a fact at trial that there was nothing on the face of the bid which would indicate any error.  At 4:12 pm, an hour after the submission deadline of 3:00 pm, the contractor sent a telex to the owner saying they had made a mistake of $750,058 in their submission, and that their total bid price should have been $3,498,058.  The message went on to offer a submission of other documents to show the error and requested to withdraw from the bid process without being “penalized”.</p>
<p><span id="more-363"></span></p>
<p>After receiving this message from the contractor the owner went on to seek the contractor’s signature on the contract documents as provided for in the tender documents.  The contractor refused to sign the contract document for the reason that it had mistakenly sent a tender bid at a price far lower than it actually intended.  The owner then took the position that, per the tender documents, it was entitled to keep the tender deposit and awarded the contract to the second-lowest bidder.</p>
<p>The contractor sued for recovery of the deposit, and the owner counter-claimed for damages resulting from the contractor’s refusal to carry out the tender and at having to accept the next-lowest bidder.</p>
<h2>Procedural history</h2>
<p>The trial judge held that the owner was entitled to keep the deposit and dismissed the counter-claim.  The Ontario Court of Appeal reversed the trial judgment and directed the owner to return the deposit.  The Ontario Commission appealed to the Supreme Court.</p>
<h2>Issues to be determined</h2>
<p>Can a bidder rely on the contract doctrine of mistake to revoke a tender, notwithstanding any provisions in the tender documents to the contrary, as long as the bidder gives notice of the mistake to the owner prior to formal acceptance of the bid?</p>
<h2>Holding</h2>
<p>No.</p>
<h2>Rule of law</h2>
<p>A call for tenders is not an invitation to treat and a bid is not an offer.  Rather, a call for tenders is an offer, and a properly submitted bid constitutes an acceptance of that offer resulting in a unilateral contract. The tendering process involves two contracts, not one.  The second is the actual contract being competed for.  The first is the bidding contract.  Consideration for the bidder is the chance to compete for the second contract and the consideration for the owner is the promise that, if selected, the bidder will enter that contract on the terms provided in the documents.  The terms of the bidding contract are also contained in the tender documents.  If the terms stipulate it then the bidder’s acceptance of the owner’s offer is irrevocable.  If no error is apparent “on the face of the tender” then the bidding contract forms when the bid is submitted.</p>
<h2>Reasoning</h2>
<p>Justice Estey delivered the unanimous judgment of the court (Justices Martland, Dickson, Estey, McIntyre and Lamer sat for the appeal).</p>
<p>Estey J. noted at the beginning of his reasons that the facts before the court did not concern either “a case where the mistake committed by the tendering contractor is apparent on the face of the tender” or a case of “impropriety” where a contractor was attempting to recall a “legitimate bid” after discovering that they were the low bidder by a wide margin. Instead, Estey J. said that “the mistake here is one which requires an explanation outside of the tender documents themselves” ([1981] 1 SCR 111, p 117).</p>
<p>The Ontario Court of Appeal had relied on its decision in <em>Belle River Community Arena Inc.</em> v <em>W.J.C. Kaufmann Co. Ltd.</em> (1978), 20 OR (2d) 447 in finding that the contractor could recover the bid deposit.  In <em>Belle River</em>, a contractor had similarly wanted to withdraw its bid after finding a mistake in its pricing and argued that it could do so as long as there had been no formal acceptance of the bid by the owner.  The tenderer was identified as the offeror, the owner as the offeree, and the Court of Appeal held that where the offeree was informed of the mistake – <em>i.e.</em> that the original offer was not the one intended by the offeror – then the offeree could not accept it.  The <em>Belle River</em> facts were very close to the facts in <em>Ron Engineering</em>.</p>
<p>Estey J. disagreed with the Court of Appeal’s ‘mistake’ analysis.  In his analysis, the respondent contractor’s tender did not constitute an offer.  Instead, he found that the terms and conditions contained in the tender documents governing the submission of tenders caused a unilateral contract to be formed between owner and bidder on submission of a tender.  This contract – the tender contact – is distinct from the actual construction contract for which the owner is soliciting bids.  For convenience Estey J. labelled these contracts contract A and contract B (p 119).</p>
<p>Under this model, Estey J. stated: “[T]he principal term of contract A is the irrevocability of the bid, and the corollary term is the obligation of both parties to enter into a contract (contract B) upon the acceptance of the tender. Other terms include the qualified obligations of the owner to accept the lowest tender, and the degree of this obligation is controlled by the terms and conditions established in the call for tenders” (p 122-123).  In the case at hand Estey J. found that there was no controversy about the form and procedure followed and that all the terms and conditions required by the call for tenders had been complied with, and thus that contract A had crystallized between the parties (p 122).</p>
<p>Once Estey J. made the core finding that a tender contract – contract A – existed between the parties, all that remained was to determine the terms and conditions of the contract and whether they had been properly observed.  The terms and conditions in the tender at issue did in fact provide for recovery of the deposit under certain conditions, none of which were met by the respondent contractor, and so Estey J. found simply that, per the terms of the agreement, the owner was entitled to keep the deposit.  Estey J. noted in passing that the purpose of the deposit “was clear and simple . . . . [It] was required in order to ensure the performance by the contractor-tenderer of its obligations under contract A.”</p>
<p>On the vexing issue of the doctrine of mistake as it might apply in the circumstances, Estey J. dispensed with it simply by saying that it did not affect the contract A analysis because the issue of mistake was not raised by the parties until after contract A had validly formed.  He wrote that the mistake in question would certainly be pertinent to a consideration of whether “a shared <em>animus contrahendi</em>” existed for the purposes of the formation of a contract B.  But, whether contract B could have formed was never actually at issue.  Instead, “the rights of the parties [for the purposes of the matter at hand] fall to be decided [solely] by the tender arrangements” (p. 123).</p>
<p>This is not to say that the doctrine of mistake might not operate to prevent the formation of contract A in the right circumstances.  On this Estey J. referred to the case of <em>McMaster University</em> v <em>Wilchar Construction Ltd.</em>, [1971] 3 OR 801, where a tender was missing a page.  The trial judge in Wilchar described the case as one where “the offeree, for its own advantage, snapped at the offeror’s offer well knowing that the offer was made by mistake.”  On this, however, Estey J. wrote, again, that the issue was not so much one of mistake as of the failure to comply with the terms and conditions of the tender call (by submitting a proper set of documents) (p 124).</p>
<p>One issue that Estey J. declined to address at length was where, for example, a tender offer came in at a price so low as to be obviously made in error: “. . . as where the offeror intended to say $200 . . . but wrote $20 dollars by mistake.”  He hinted, though, that “it may well be that such a form of tender could not be ‘snapped up’ by the owner” (p 125).</p>
<p>All said, a call for tenders like the one in <em>Ron Engineering</em> &#8211; sometimes called a “classic” tender call today because of continually evolving procurement models – involves two contracts, the first being a tender contract, or contract A.  This contract according to its terms entails rights and obligations on the part of the parties under the same fundamental rules as any other contract.  These terms will generally include irrevocability and the right to the formation of the contemplated construction contract on acceptance of the tender.</p>
<p>A final point of note is an often quoted statement made by Estey J. in his reasons for decision which sheds some light on the rationale for his insistence on strict enforcement of the terms of a call for tenders: “[The] integrity of the bidding system must be protected where under the law of contracts it is possible to do so” (p 121).</p>
<h2>Nota Bene</h2>
<p>It is critical to understand that Estey J.’s creation of the two-contract analysis in Ron Engineering does not represent an attempt to turn the law of contracts on its head.  Instead, Estey J. simply applied the principles of contract law to the documents that passed between the parties to arrive at the conclusion that the parties had agreed to be bound by the terms of a process contract in anticipation of a construction contract.  As a result, Estey J.’s two-contract model of bidding and tendering only applies to situations where the underlying documents and surrounding circumstances support the creation of a process contract.</p>
<p>Some contemporary procurement models, such as some Request-for-Proposal models, are not understood in law to be a call for tenders and thus are not subject to the application of the rule in Ron Engineering.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adambaker.net/case-brief-r-v-ron-engineering/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Privilege Clauses and Dalcon Enterprises</title>
		<link>http://www.adambaker.net/privilege-clauses-and-dalcon-enterprises/</link>
		<comments>http://www.adambaker.net/privilege-clauses-and-dalcon-enterprises/#comments</comments>
		<pubDate>Thu, 13 Aug 2009 02:43:00 +0000</pubDate>
		<dc:creator>Adam Baker</dc:creator>
				<category><![CDATA[Contract Terms]]></category>
		<category><![CDATA[Privilege Clauses]]></category>

		<guid isPermaLink="false">http://www.adambaker.net/?p=117</guid>
		<description><![CDATA[I recently commented on Russell (Township) v. Dalcon Enterprises Inc., [2009] O.J. No. 2560 (Ont. S.C.J.) (&#8220;Dalcon&#8220;), and I indicated that the owner township had every right to exercise a contractual provision giving it &#8220;discretion&#8221; to award the contract to a bidder other than the lowest bidder. And it did. But I should mention that [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>I <a href="http://www.adambaker.net/?p=79">recently commented</a> on <em>Russell (Township)</em> v. <em>Dalcon Enterprises Inc.</em>, [2009] O.J. No. 2560 (Ont. S.C.J.) (&#8220;<em>Dalcon</em>&#8220;), and I indicated that the <a href="http://www.adambaker.net/?page_id=20#owner">owner</a> township had every right to exercise a contractual provision giving it &#8220;discretion&#8221; to award the contract to a bidder other than the lowest bidder.  And it did.  But I should mention that although they&#8217;ve been around for awhile, those types of provisions are controversial.  And understandably so.  After spending time and money preparing and submitting tender documents, a bidder is generally disappointed to lose the bidding competition.  And if the <em>low</em> bidder is snubbed in favour of one of their higher-priced competitors, you&#8217;ve got great potential for a great big row.</p>
<p>That&#8217;s what happened in <em>Dalcon</em>, except the contract was not actually awarded prior to the submission of an application to court.  Again, <a href="http://www.adambaker.net/?p=79">see my post</a> if you&#8217;re interested.</p>
<h2>Can They Do That?</h2>
<p>The question always asked when an owner passes over a low bidder by relying on a provision purporting to give them the power to do so is: Can they do that?  The answer is: Maybe.</p>
<p><span id="more-117"></span><br />
These clauses are called &#8220;privilege clauses.&#8221; Some pratitioners are of the opinion that privilege clauses are as enforceable as any other contract term.  And while they are generally enforceable, I personally would be a little more cautious before relying on one.</p>
<p>In <a href="http://www.canlii.org/en/ca/scc/doc/1999/1999canlii677/1999canlii677.html" target="_blank"><em>M.J.B. Enterprises</em> v. <em>Defence Construction (1951)</em></a>, [1999] 1 S.C.R. 619 (&#8220;<em>M.J.B.</em>&#8220;), which is a leading case in Canadian law on privilege clauses, the tender documents at issue stated: &#8220;The lowest or any tender shall not necessarily be accepted.&#8221;  This type of wording is fairly standard, although privilege clauses have gotten a little more sophisticated in response to developing case law.</p>
<p>But the catch is that the case law, arguably, is not entirely consistent.  For example, Iacobucci J&#8217;s discussion in <em>M.J.B.</em> indicates that in deciding which bidder to award a contract to, an owner should not make the decision based on &#8220;undisclosed&#8221; criteria.  But some subsequent decisions of lower courts have upheld owners&#8217; decisions made rejecting low bidders based on such critertia.</p>
<p>What <em>is</em> generally agreed on is that inclusion of a privilege clause does not eliminate owners&#8217; duty to deal with all bidders fairly and in good faith.  For example, see <a href="http://www.canlii.org/en/ca/scc/doc/2000/2000scc60/2000scc60.html" target="_blank"><em>Martel Building Ltd.</em> v. <em>Canada</em>, 2000 SCC 60</a>.</p>
<p>In any event, privilege clauses are not an overly complex subject, but an in-depth discussion is probably better saved for a subsequent post.  What I did want to correct was any impression I might have left that the owner township in <em>Dalcon</em> would be absolutely immune from any liability should they choose to exercise their &#8220;discretion&#8221; not to accept a bid.  In <em>Dalcon</em>, the owner township&#8217;s tender documents contained what were essentially privilege clauses.  And they did have the right to exercise their discretion under those clauses without seeking a court order stating so.  What they <em>couldn&#8217;t</em> do was exercise that discretion <em>improperly</em>, for example, in bad faith.  That is, a privilege clause may not be available for use if there are no circumstances which could justify its fair use.</p>
<h2><em>Nota Bene</em></h2>
<p>Public Tenders in Newfoundland and Labrador are governed by the <a href="http://assembly.nl.ca/Legislation/sr/statutes/p45.htm" target="_blank"><em>Public Tender Act</em></a>, R.S.N.L. 1990, c. P-45, section 8(1) of which is effectively a statutory privilege clause.<br />
See also the <a href="http://assembly.nl.ca/Legislation/sr/regulations/rc980103.htm" target="_blank"><em>Public Tender Regulations</em></a>, N.L.Reg. 103/98.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-7895084756998765";
/* 468x60, created 8/13/09 */
google_ad_slot = "5541566416";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script><br />
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
]]></content:encoded>
			<wfw:commentRss>http://www.adambaker.net/privilege-clauses-and-dalcon-enterprises/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Russell (Township) v. Dalcon Enterprises Inc.</title>
		<link>http://www.adambaker.net/russell-township-v-dalcon-enterprises-inc/</link>
		<comments>http://www.adambaker.net/russell-township-v-dalcon-enterprises-inc/#comments</comments>
		<pubDate>Fri, 31 Jul 2009 03:20:52 +0000</pubDate>
		<dc:creator>Adam Baker</dc:creator>
				<category><![CDATA[Breach by Owner]]></category>
		<category><![CDATA[Compliance with Tender Terms]]></category>
		<category><![CDATA[Contract Terms]]></category>
		<category><![CDATA[Bidding Process]]></category>
		<category><![CDATA[Invitation to tender or bid]]></category>

		<guid isPermaLink="false">http://www.adambaker.net/?p=79</guid>
		<description><![CDATA[Public sector owners like federal and provincial departments and large municpalities often have no qualms about throwing their weight around in the event of a contractual dispute. For that matter even smaller municipalities often have no reservations about getting into a racket with a contractor depending on the collective personality of their public officials. But, [...]]]></description>
			<content:encoded><![CDATA[<p></p><p>Public sector owners like federal and provincial departments and large municpalities often have no qualms about throwing their weight around in the event of a contractual dispute.  For that matter even smaller municipalities often have no reservations about getting into a racket with a contractor depending on the collective personality of their public officials.  But, sometimes, smaller public owners with less commercial expertise and fewer resources at their disposal might approach contracting companies with more trepidation.</p>
<p>Not to say that this was exactly the case with the Township of Russell, ON.  But, this past spring, the Township issued an invitation to tender for an expansion to its Lagoon.  The tender closed on May, 21, 2009, and of six bids received the two lowest were by Dalcon and Robert.  An engineering consultant hired by the Township reviewed the bids and recommended that Dalcon&#8217;s be rejected because of some issues with the bid documents, and that the contract be awarded to Robert.  In early June, both low bidders having gotten wind of the potential to gain or lose the project, Dalcon and Robert each threatned to sue the Township for damages if they were not found to be the successful bidder.</p>
<p>Rather than make the call and deal with one or the other threatened actions, the Township decided to head both actions off at the pass and brought an application to court to seeking a judicial order confirming the Township&#8217;s contractual ability to select a bidder without incurring liability to the unsucessful bidders.</p>
<p>But, the tender documents themselves provided at three points for the owner to exercise discretion in the final selection of a successful bidder.  Justice Ray dismissed the application, saying that where the Township&#8217;s own contract documents gave it discretionary power, there was no room for the court to &#8220;make the decision for Russell Township.&#8221;  That is, make your decision, and if there&#8217;s a legal dispute subsequently, <em>that&#8217;s</em> when you come to court.</p>
<p>See <a href="http://www.canlii.org/en/on/onsc/doc/2009/2009canlii31597/2009canlii31597.html" target="_blank"><em>Russell (Township)</em> v. <em>Dalcon Enterprises Inc.</em></a>, [2009] O.J. No. 2560 (Ont. S.C.J.).</p>
<p>This is an interesting little case, although it doesn&#8217;t really set out any ground-breaking <em>ratio</em>.  The moral of the story is that it doesn&#8217;t matter who&#8217;s threatening what in the way of a legal action, or how bad and mad they are, a contractual right pursuant to an agreed-to provision &#8211; assuming that the provision is enforceable &#8211; is what it is: a contractual right.</p>
<p>So, for smaller public owners everwhere, the general rules of engagement for tender contracts equally apply, including: (i) Make sure your tender contract documents are well-drafted, (ii) make sure you know what you can and can&#8217;t do under the contract, and (iii) if you can do it, and you need to do it, don&#8217;t be afraid put a provision into action.</p>
<p><script type="text/javascript"><!--
google_ad_client = "pub-7895084756998765";
/* 468x60, created 8/13/09 */
google_ad_slot = "5541566416";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script><br />
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></p>
]]></content:encoded>
			<wfw:commentRss>http://www.adambaker.net/russell-township-v-dalcon-enterprises-inc/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

