In Canada&#39;s famous &quot;Ron Engineering&quot; case, what really is protected by Contract A?
<p>In Ron Engineering, the supreme court ruled that a "Contract A" is formed when a bidder submits a bid.  This seems to imply that Contract A is formed <strong>by</strong> the bidder, not the receiver of that bid, unilaterally.  As I understand Ron Engineering, Ron Engineering made a mistake and could not retract their bid.  In effect, Ron Engineering was not let out of Contract A.</p>

<p>However, as Contract A is usually explained, it protects bidders from poor practice from people receiving bids.  For instance, if the receiver does not go with the lowest bid due to other bids having additional terms not spelled out in the original tender, the lowest bidder can sue.  This appears to be the complete opposite of the decision in Ron Engineering.</p>

<p>So what does Contract A really do, and who is bound by it?</p>

<p>The issuer of contract A would be legally bound if the contract was accepted is what it means.</p>

<p>The Canadian Supreme Court established that the bid is a contract (A) and the actual contract for construction (B) are both separate contracts.</p>

<p>The company sued in order to get it's deposit back, but was not successful, because the bid was considered a legal contract that the company was bound to.</p>

<p>The court was saying that a company is, generally, bound to what it's bid was.</p>

<p><a href="https://en.wikipedia.org/wiki/R_v_Ron_Engineering_and_Construction_(Eastern)_Ltd" rel="nofollow noreferrer">https://en.wikipedia.org/wiki/R_v_Ron_Engineering_and_Construction_(Eastern)_Ltd</a></p>

<h2><a href="https://en.wikipedia.org/wiki/R_v_Ron_Engineering_and_Construction_(Eastern)_Ltd" rel="nofollow noreferrer">R v Ron Engineering and Construction (Eastern) Ltd</a></h2>

<p>Established that, in certain circumstances (see 
<a href="https://law.stackexchange.com/questions/6263/what-is-a-contract-and-what-is-required-for-them-to-be-valid">What is a contract and what is required for them to be valid?</a>), submitting a tender could create a binding contract on the tenderer <strong>and</strong> the caller of the tender. </p>

<p>In Tercon Contractors Ltd. v British Columbia (Transportation and Highways), the trial judge summarized the factors to be considered in deciding whether a matter constitutes a call for tenders or a non-binding request for proposals:</p>

<ul>
<li>the irrevocability of the bid,</li>
<li>the formality of the procurement process,</li>
<li>whether tenders are solicited from selected parties,</li>
<li>whether there was anonymity of tenders,</li>
<li>whether there is a deadline for submissions and for the performance of the work,</li>
<li>whether there is a requirement for a security deposit,</li>
<li>whether evaluation criteria are specified,</li>
<li>whether there was a right to reject proposals,</li>
<li>whether there was a statement that this was not a tender call,</li>
<li>whether there was a commitment to build,</li>
<li>whether compliance with specifications was a condition of the tender bid,</li>
<li>whether there is a duty to award contract B, and</li>
<li>whether contract B had specific conditions not open to negotiation</li>
</ul>

<p>If the tender creates a Contract A, then what the obligations on each party will be under such a contract will depend on the particular terms of that contract. In the case of Ron Engineering, one of the terms was that if the tender was withdrawn the security deposit would be forfeit. In other cases, if the principal does not comply with their obligations the bidder can sue - those obligations <em>might</em> include one to assess tenders and award Contract B in a certain way. Most principals will spell out their assessment method with sufficient wiggle room so that any decision can be reasonable - a statement to the effect that "assessment of tenders is not based solely on price" would suffice.</p>

contract-law