UK: OCG Publish New Guidance On Land Development Agreements

Last Updated: 4 May 2010
Article by Jonathan Branton

The OGC has just published a long awaited commentary on the inter-play between the public procurement rules and land development agreements. This subject has been in the spotlight since the notorious Auroux v Roanne case of 2007, which highlighted that land transfers from public authorities which impose associated specified works obligations on developers are "public works contracts" and therefore subject to mandatory application of the public procurement rules if the relevant value thresholds are crossed. The OGC paper offers some further thoughts in relation to this. It seeks to clarify what are the "specified works obligations" necessary to place a land development agreement within the ambit of the public procurement rules, and in particular what sort of conditions in a land development will fall short of this test and thereby escape the rules.

The relevant law on public works contracts

Article 2(1) of the Public Contracts Regulations 2006 (PCR) defines a public works contract as "a contract in writing for consideration (in cash or in kind): (a) for the carrying out of a work or works on behalf of a contracting authority; or (b) under which a contracting authority engages a person to procure by any means the carrying out for the contracting authority of a work corresponding to particular specified requirements". In its paper the OGC has broken this down further into asking the following questions for the purposes of determining if a development agreement includes a public works contract, namely:

  • Is there a work or works required or specified by a contracting authority?
  • Is there an enforceable obligation (in writing) on a contractor to carry out that work or works?
  • Is there some pecuniary interest for carrying out this work (not necessarily a cash payment)?

If the above elements are all met then it is likely that the development agreement involves a public works contract subject to the procurement rules.

The Roanne case

This European Court of Justice (ECJ) case addressed these issues. It involved a French municipality (Roanne) engaging a third party developer (SEDL) to acquire land, build a leisure complex including a cinema and commercial premises (to be sold on to a third party) and a car park to be transferred back to the municipality together with various other outputs such as access roads and public spaces. The municipality of Roanne was the instigator and author of the project. The ECJ was asked to determine whether the agreement did in fact involve a public works contract subject to the procurement rules. The ECJ found that as the main purpose was to carry out works corresponding to specified requirements, it was a works contract that needed to be advertised and tendered under the OJEU rules. The construction of the leisure centre was to be regarded as corresponding to the requirements of the municipality because taken as a whole the project was intended to reposition and regenerate the local area. This was seen as a warning to local authorities everywhere that if a contract results in the provision of works to (public) order (in excess of the works value threshold of approximately Ł3.5m), then even if other aims are pursued through the project as well, there is a public works contract subject to the procurement rules which must be advertised accordingly. However, it is important to note (and the OGC stresses this) that the Roanne case did not change the law in any way, it merely brought it to wider attention.

Definition of "a work corresponding to specified requirements"

The OGC observes that the ECJ has yet to give explicit guidance on how exhaustively detailed a specification needs to be. The OGC offers a view that the specifications set by the contracting authority should be sufficiently detailed and be expressly referred to in the contract such that they may be legally enforceable. In a development agreement context there is a difference between that and a broad invitation to develop in accordance with applicable national or local land-use planning policies, and where the developer is free to put forward its own intentions, proposals and specifications within those parameters. Thus, the OGC has stated that in its view "where a contracting authority invites a developer or developers to submit their own proposals for the use or development of land or buildings, (competitively or otherwise) but without itself specifying the requirement, the public procurement rules may not apply, even if the contracting authority selects the winning proposal according to broad criteria pre-determined by the authority". This offers considerable flexibility set against the most conservative interpretations of the Roanne case and what is a public works contract, albeit it does not make crystal clear the point at which broad criteria for selection become sufficiently detailed specifications to be legally enforceable. This means that the correct interpretation of what is a public works contract in such cases will continue to warrant a very subjective assessment of fact and degree on a case by case basis.

Land deals and avoiding the procurement rules by expressing desirable outcomes rather than works obligations (Flensburg case)

The EU public procurement regime does not apply to straightforward land transfers with "no strings attached". A land transaction includes a transfer of a right or interest in land. The procurement regime applies to public works, and indeed services and supplies contracts. Roanne addressed how one characterises a "mixed contract", ie. a transaction that has elements of land acquisition and/or disposal, and elements of works and/or services. Such contracts are sometimes in the form of a joint venture between the contracting authority and an economic operator, and they often involve the contracting authority imposing requirements on what should be done with land contributed to the venture.

In particular the OGC notes a recent European Commission investigation concerning the German city of Flensburg. The Flensburg case involved the sale of land to a developer for the possible construction of a building that would correspond to certain urban development needs. However, apart from a simple statement of intent, that contract did not contain any legally binding obligation for the developer to construct the building envisaged. Rather, the contract only stipulated a right of buy back of the land in case the building was not constructed. The Commission has publicly stated in its press release noting the termination of the investigation that this was not a public works contract (nor a concession) because the contract in question did not contain a legally binding obligation to execute works on behalf of a contracting authority. The Commission further specifically confirmed that the buy-back right was not a sufficient sanction to create a positive and legally binding obligation to undertake the works.


The OGC states that the Flensburg case is a sound precedent to follow in land development situations and where a contracting authority only sets out general intentions that are not laid out in binding obligations, then the public procurement rules should not apply. The OGC adds that if a developer remained able to change the scope altogether without breaching the contract then again there would be a strong indication that the procurement rules did not apply.

Legal status of the OGC paper and the Flensburg case

The OGC paper does not have the formal legal value of the EU public procurement Directives, the (UK) Public Contracts Regulations 2006, or related Court judgements in the UK and the ECJ. Similarly, the Flensburg case – which follows as it does a European Commission press release rather than an ECJ judgement – does not have ultimate legal force. However, the OGC is the governmental body entrusted with the monitoring and application of procurement law in the UK, and the European Commission is the body similarly charged with ensuring and enforcing respect for the procurement rules on an EU-wide basis. Neither body expresses a view on such significant issues without thinking very carefully and consulting the leading legal experts available. It may therefore be reasonably assumed that this is the best guidance for interested parties available at present.

Other situations identified by the OGC

The OGC also identifies some other typical situations in which questions arise as to whether or not a development agreement includes a public works contract subject to the procurement rules, namely:

  • Development contracts ancillary to a lease: the OGC notes that a contracting authority leasing property to a developer and charging a rent, while allowing the developer to build to its own requirements, should not constitute a public works contract. The payment of rent is not a pecuniary interest corresponding to specified works requirements in such a case, and this is so even if the development agreement sets out certain limitations to what the developer may do in order to protect the authority's interest as lessor.
  • Building licences: the OGC observes that on some occasions rather than development agreements involving transfers of (public) land, contracting authorities grant building licences to build subject to various conditions, thus allowing the authority to retain control of the freehold pending satisfactory completion of relevant works. If that licence imposes specified works obligations on the developer it will normally be covered by the procurement rules, but if the licence only contains negative obligations on the developer not to go back on its own pre-determined plans then this should fall short of the specified works obligations necessary to place it within the procurement rules.
  • Mixed developments: where only a small part of a much wider development situation includes specified works obligations that a contracting authority wishes to impose (eg. a major development which includes the relocation of council offices as one discreet part) then an authority may wish to ring fence and procure the discreet part without the whole development (and associated land transfers) becoming subject to the procurement rules. On the other hand if the specific circumstances make it practically impossible to make such a separation then the safe approach would be to procure the whole development.

Planning obligations

Since the Roanne judgement there has been a debate as to whether additional planning obligations under UK law flowing from (for example) s.106 or s.278 (highways) agreements might also be covered by the procurement rules. While such obligations may sometimes appear in the same light as pure planning conditions (for example as terms limiting use or specifying mitigation to be carried out by the developer) in some cases they may go much further and stipulate the carrying out of works (eg. highways or schools) that might otherwise be carried out by the authority. The OGC has declined to express a view on this and promises to revert with further guidance in due course.

Impact of the new Remedies Directive

A series of very recently adopted amendments to the Public Contracts Regulations 2006 will take effect on 20 December 2009. These follow the 2007 EC Directive on procurement remedies otherwise known as the new "Remedies Directive". This will be the subject of another detailed briefing shortly but the immediately obvious implication for current purposes is that the new remedy of a Court declaration of ineffectiveness will be available for situations where no OJEU advert has been published when it should have been. This is precisely the judgement that is often made in Roanne-type situations, ie. a determination is made that a given development agreement situation falls outside the procurement rules altogether – perhaps because of a "Flensburg" assessment or similar – and so a development proceeds with no OJEU advert at all.

Of course, if that judgement that the procurement rules did not apply is upheld, then no declaration of ineffectiveness will be given. However, the possibility of such a remedy being granted post award of the contract (NB. the existing regime allows for damages only as a remedy post award) will escalate the risk assessment of the original decision as to how safe is the conclusion that the procurement rules did not apply and no advert was required. In such situations further strategic considerations are likely to come into play, such as the publication of voluntary "transparency" or "award" notices" which may publicise the fact that contracts have been awarded without full OJEU process, and briefly set out why. The object of such voluntary publications will be to flush out any potential challenges there and then to limit the availability of potential declarations of ineffectiveness in the future.

A declaration of ineffectiveness will only have prospective effect, meaning that works entered into already will remain legal, just that further works will be required to stop. If no voluntary transparency or award notices have been published then proceedings to obtain a declaration of ineffectiveness must be commenced no later than six months from the date of entry into force of the contract concerned. In addition, even if a declaration of ineffectiveness is warranted a Court may decline to give it if there are overriding reasons in the general interest.

Conclusions

The OGC sums up noting the following points as indicative of a development agreement situation not being subject to the procurement rules:

  • the development is undertaken at the autonomous initiative and instigation of the developer;
  • the development agreement is incidental to a transfer or lease of land and only contains protections to the public authority's retained interest in the land;
  • the development is based on proposals put forward by the developer rather than specifications set by the authority, even if the proposals were sought by the authority and a winner chosen;
  • there is no pecuniary interest (ie. payment in cash or kind) passing from the authority to the developer; and/ or
  • the development agreement does not contain specified and enforceable obligations, even if the parties may agree some general intentions.

The OGC is at pains to stress that every situation must be assessed in the round and taking into account all relevant facts and agreements, and artificial arrangements with no purpose other than circumvention of the rules are likely to be viewed with suspicion. Given the sensitivity of the area the OGC paper is never a substitute for expert legal opinion applied to all the specific facts of each case.

All in all the OGC commentary offers very useful guidance for what has loong been a vexed issue, even after Roanne. This will be helpful in guiding contracting authorities and developers alike in judging when and where the procurement rules bite in future development agreements, and taking balanced risk judgements accordingly. The new Remedies Directive – particularly when taken together with the recent higher incidence of procurement challenges generally – serves merely to highlight further still the importance of getting this right.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.