Australia: Generally protected: a government’s capacity to regulate enterprise bargaining via procurement policy

Last Updated: 10 August 2013
Article by Leigh Howard and Graham Smith

Key Points:

All commercial contract negotiations (both public and private) must carefully consider the impact of industrial laws if the contract involves a labour supply.

The extent to which a government can pursue industrial relations objectives through procurement has come into question following two recent judgments of the Federal Court: Construction, Forestry, Mining and Energy Union (CFMEU) v Victoria1 and Construction, Forestry, Mining and Energy Union (CFMEU) v McCorkell Constructions Pty Ltd (No 2).2

In both cases, Bromberg J found that the State of Victoria contravened the general protections provisions of the Fair Work Act 2009 (Cth) (FW Act) when it attempted to enforce its industrial relations policy with respect to its own procurement, contained in the Implementation Guidelines to the Victorian Code of Practice for the Building and Construction Industry.

The decisions not only impair a government's capacity to influence enterprise bargaining through its commercial leverage, they also confirm the expansive operation of the FW Act's general protections provisions.

Industrial regulation through government procurement: a brief background

The notion that governments can pursue industrial relations objectives when contracting is not a new or surprising phenomenon.3 Governments are significant purchasers of labour, and their purchasing power places them in a position to "set an example by acting as model employers".4 In Australia, this opportunity has been particularly explored in building and construction procurement, first commencing in 1992 when the NSW Government's Code of Practice for the Construction Industry was introduced on the recommendation of the Gyles Royal Commission.

Since then, separate procurement policies for the building and construction industry have been developed by all Australian States and Territories (except the ACT). In general terms, the majority of the jurisdictions have a "code" containing motherhood statements that express the intended design of industrial relationships on publicly funded building and construction work. These codes are given content through "guidelines" promulgated by the relevant government departments. A national federal code (originally negotiated by the Commonwealth and all States and Territories) sits at the apex,5 and most State and Territory codes and guidelines are expressed to be in conformity with the national federal code.

The "model employer" that governments have sought to uphold through these codes and guidelines has waxed and waned according to government policy of the day.

The Victorian Code and Guidelines

In July 2012, the recently elected Victorian Government introduced a new iteration of the guidelines to sit under the Victorian Code of Practice for the Building and Construction Industry (Code).

Revised guidelines

Compliance evidence

The revised Victorian guidelines require those submitting a tender or expression of interest (EOI) for publicly funded building and construction work in Victoria to provide documentation evidencing their compliance with the terms of the guidelines. Compliance is not just required for the work subject to the tender or EOI, but must also be demonstrated with respect to their business more generally (including their privately funded work). Importantly, bidders are required to ensure that their subcontractors and related entities are also Code-compliant.

Content of enterprise agreements, Construction Code Compliance Unit and its powers

Among other things, the July revisions to the Victorian guidelines:

  • sought to regulate the content of enterprise agreements by identifying certain types of clauses to be considered noncompliant;
  • established the Construction Code Compliance Unit (CCCU) to review the content of enterprise agreements and investigate compliance with the Code more generally; and
  • commissioned the CCCU with a number of sanction powers, including the power to exclude noncompliant entities from bidding for Victorian Government projects for a specified time.

Enterprise agreements entered into prior to 1 July 2012 were deemed compliant by the CCCU, irrespective of their content. However, enterprise agreements entered into by bidders, their related entities, and subcontractors after 1 July 2012 were liable to inquiry.

The Guidelines in practice: the Bendigo Hospital and Circus Oz projects

In late 2012, the CCCU was asked to scrutinise enterprise agreements relevant to the Victorian Government's Bendigo Hospital and Circus Oz projects. The following occurred in relation to the Bendigo Hospital project:

  • The Victorian Government initiated a tender process for the construction, facility management and maintenance of the Bendigo Hospital. It had shortlisted two consortia for the project. Lend Lease was a member of the consortium that was later earmarked as the preferred bidder.
  • In the concluding stages of the tender process, Lend Lease negotiated an enterprise agreement with its employees and the Construction, Forestry, Mining and Energy Union (CFMEU), which was approved by (then) Fair Work Australia to commence on 20 September 2012. This agreement was brought to the attention of the CCCU as part of the evaluation phase of each consortium.

The following occurred in relation to the Circus Oz project:

  • The Victorian Government concluded a tender process and appointed McCorkell Constructions to build and refurbish a premises to be the permanent site of a circus. McCorkell then initiated its own tender process for the demolition works to be undertaken on the site. Eco Recycling (Eco) responded to McCorkell's request for tender. During McCorkell's tender process, Eco concluded an enterprise agreement that commenced on 2 November 2012.
  • McCorkell advised Eco of the requirement that subcontractors for the project must demonstrate Code compliance, and that this meant that Eco's recently concluded agreement had to meet certain requirements. As Eco did not understand what this meant, McCorkell referred it to the CCCU.

In both instances, the CCCU judged the enterprise agreements to be noncompliant with the Code. The CCCU advised both Lend Lease and Eco that variation of their enterprise agreements was necessary to achieve Code compliance. In Lend Lease's case, attempts were made to negotiate with the CCCU, in the course of which Lend Lease offered to provide a number of undertakings to the Victorian Government about the operation of the enterprise agreement. Eco was advised by McCorkell that it could no longer tender, which resulted in Eco taking steps to vary its enterprise agreement to remove the offending provisions.

Matters came to a head when the CFMEU (the union covered by each enterprise agreement) commenced proceedings against the State and McCorkell pursuant to the FW Act's general protections provisions.

CFMEU intervention

The CFMEU's case was that the State, through the conduct of the CCCU, took adverse action by declaring Lend Lease's and Eco's enterprise agreements to be noncompliant with the Code.

Arguments of the CFMEU

Specifically, the CFMEU argued as follows:

  • Lend Lease and Eco were "independent contractors" within the meaning of section 342(1) item 4 of the FW Act.
  • Lend Lease's and Eco's employees had a "workplace right", as they were "entitled to the benefit" of a "workplace instrument" (their newly concluded enterprise agreements) within the meaning of section 341(1).
  • In the case of Lend Lease, the State was "proposing to enter into a contract for services", but had threatened to refuse "to make use of, or agree to make use of, services offered" by Lend Lease because of its employees' "workplace right" in contravention of sections 340(1), 342(1) item 4, and 342(2). A similar allegation was also made against McCorkell.
  • In the case of Eco, the State acted "with intent to coerce" Eco to vary its enterprise agreement to make it Code-compliant, in contravention of section 343(1). McCorkell was also alleged to have committed the same contravention.

CFMEU was initially granted injunctive relief.6 Much of the contest at substantive hearing centred around the precise legal meaning to be given to many of the terms quoted above.

Meaning of "independent contractor"

Much of the CFMEU's case was predicated on a finding that Lend Lease and Eco Recyclers were "independent contractors" — a finding to the contrary would have taken the State's conduct outside the scope of section 342(1) item 4.

The State's argument

The State submitted that "independent contractor" referred to the type of (usually individual) worker that is not an employee, and that the legal meaning to be given to the phrase should accord with the meaning that is commonly invoked by the employee/independent contractor dichotomy.7

The CFMEU's argument

The CFMEU argued that the meaning was not limited by this notion and extended to any legal entity carrying on the business of a contractor that provides services that include labour services, irrespective of scale.

Ruling of Bromberg J: Lend Lease and Eco Recyclers are independent contractors

Justice Bromberg adopted a beneficial approach to construction.8 In doing so, his Honour:

  • looked to context, and noted that other parts of section 342(1) referred to an "independent contractor" employing employees and engaging other independent contractors — this did not sit well with the State's assertion that the term was limited to the notion invoked by the employee/independent contractor dichotomy;9
  • looked to the phrase's ordinary meaning, which his Honour said "connotes an entity that furnishes supplies or performs work under a contract that does not create a relationship of principal and agent as between the contractor and the person who contracts for the benefit of the services supplied";10 and
  • traced the legislative history, and found support for the meaning advanced by the CFMEU in prior iterations of federal industrial law, most notably within the freedom of association and provisions introduced by the Workplace Relations and Other Legislation Amendment Act 1996 (Cth).11

All of this inextricably led to the conclusion that Lend Lease and Eco Recyclers were "independent contractors" for the purposes of the FW Act's general protections provisions.

As a consequence, it followed that the allegations of adverse action extended to Lend Lease's and Eco Recycler's employees, as the protection in section 342(1) item 4 extends to "persons employed or engaged by the independent contractor".

Meaning of "proposing to enter into a contract for services"

The CFMEU's case also relied upon the finding that the State and McCorkell were "proposing to enter into a contract for services" when committing the impugned adverse action.

In Lend Lease's case


In Lend Lease's case, the State contended that there was no "proposal" to contract with Lend Lease. The tender process was still in progress, and section 324(1) item 4 required some certainty as to counterparty.

This was rejected, with his Honour noting that the State had effectively equated the meaning of "proposing" to connote "intending". This interpretation could not be sustained because other parts of section 342(1) prohibited adverse action against "prospective employees". The protection for "prospective employees" went beyond circumstances where there is an intention to employ them, and it would be anomalous to confine the protection afforded to prospective contractors vis-ŕ-vis prospective employees. His Honour concluded that the phrase speaks to a potential contractor whose engagement is merely "under consideration or in prospect".12

Contract for services

The State also argued that a "contract for services" with Lend Lease was not under consideration or in prospect. The State pointed to the substance of the tender documentation, being a contract for the construction, facility management and maintenance of a hospital. It was not a contract for labour services in itself, which is the type of contract to which section 342(1) item 4 is directed.

His Honour accepted this at one level, but ultimately found the tender documentation to envisage a contract with Lend Lease to build a hospital, and a contract of that kind "will inevitably require the provision of labour services to a material degree".13

No proposal to contract

The State also pointed to fact that neither the State nor Lend Lease was party to core contractual documentation under negotiation. A separate project company and one of the shortlisted consortia were in fact the proposed parties to the contract, and it followed that neither the State nor Lend Lease was proposing to contract.

However, a deed between the State and the builder had been drafted, which, his Honour found, contained obligations that would be enforceable by the State against the project builder from the inception of the proposed contract. This was enough for his Honour to find that a "contract for services" was in consideration between the State and Lend Lease, because the deed:

"... must be read and understood as part of a contractual scheme in which each of the [contract documents] are intended to be linked and in which each will contribute to ensuring the State obtains the works and services including those to be provided by the appointed builder."14

In McCorkell's case

The case against McCorkell was much less involved, owing to the simplicity of the negotiations with Eco. In conformity with his findings of law with respect to Lend Lease's case, his Honour found that:

  • a contract for services was "under consideration or in prospect" at the time Eco forwarded its quote to McCorkell;15
  • the fact that McCorkell later "narrowed in" on other tenderers on the basis of price did not derogate from the fact that, at a certain point, McCorkell was contemplating contracting with Eco, but excluded Eco for reasons that included its noncompliance;16and
  • notwithstanding that Eco would have obtained property in salvageable items following demolition, it was still predominantly a contract for labour services.17

The result

The consequence of finding that Lend Lease and Eco were "independent contractors" that were "proposing to enter into a contract for services" flowed as a matter of course. His Honour accepted that both the State and McCorkell "threatened" to take adverse action against Lend Lease and Eco within the settled meaning of that term.18 This was "because" of the rights conferred upon Lend Lease and Eco employees under the respective enterprise agreements, and noncompliance with the Code by both contractors was one motivating factor for taking the adverse action.19

As the State and McCorkell did not discharge the reverse onus of proof required to defeat an allegation of adverse action,20 the cases against them were upheld.

The State's coercion against Eco

Coercion and the State's attempt to discharge the reverse onus of proof

The CFMEU separately alleged that that the State coerced Eco. This was said to occur when the CCCU communicated to Eco (at least implicitly) that it needed to vary its enterprise agreement if it wanted to tender for government work.21 Noting that "intent to coerce" within section 343(1) has the accepted meaning of "intent to negate choice",22 his Honour characterised the State's task of overcoming the reverse onus of proof as follows:

"On the facts and allegations made in this case, it seems to me that section 361 imposed on the State an obligation to negate that a substantial and operative reason for the action it took was a desire to have Eco and its employees take steps to vary the Eco Agreement and that any such motivation was not pursued with an intent to negate the choice of Eco and its employees not to take those steps ... the State will need to establish that if it did negate choice, the exertion of the pressure involved was not unlawful, illegitimate or unconscionable."23

The State sought to meet this by calling the relevant CCCU official who met with Eco. Her evidence was that:

  • her intention when communicating with Eco was to provide it with information about its compliance, and to respond to its queries as best she could within the scope of the CCCU's role; and
  • she did not act with an intention to coerce Eco into varying the enterprise agreement.

Justice Bromberg held that this evidence was not capable of satisfying the State's onus of disproving the coercion, for the following reasons:

  • It was not evidence establishing whether or not the CCCU was motivated to negate the choice of Eco. Rather, it was evidence of an intention to provide information. It should have been directly put to the witnesses whether or not she was motivated to coerce Eco into varying its enterprise agreement.
  • The official's intention, in her own words, was to respond to Eco "within the scope of the role" of the CCCU. As it was CCCU's role to procure Code compliance, it naturally followed that the CCCU would desire that enterprise agreements be compliant, and that parties should take steps to vary noncompliant agreements.24

Was the State's conduct unlawful, illegitimate or unconscionable?

What was then left to decide was whether or not the State's conduct involved pressure that was "unlawful, illegitimate or unconscionable". Justice Bromberg found that issuing the guidelines was in itself such conduct:

"The guidelines impose parameters for the allowable content of enterprise agreements different to those provided for by the FW Act. In many respects the differences are stark. The exertion of economic pressure upon industrial parties for the purpose of limiting or restricting their freedom to bargain within the parameters established by the FW Act is, in my view, illegitimate because it serves to defeat the scheme for agreement making prescribed by FW Act.

The impugned conduct of the State in this case involved the application of economic pressure on parties to an enterprise agreement and was driven by parameters for bargaining and agreement making contained in the Guidelines. It therefore involved a purpose and effect which served to undermine the scheme of the FW Act. For that reason, it seems to me that the conduct was illegitimate conduct and that the second element required to prove an "intent to coerce" is established."25

The CFMEU's allegation that McCorkell also coerced Eco failed. His Honour accepted evidence establishing that McCorkell held no intention to exert any pressure on Eco to vary its agreement.26

Leave to appeal sought and revised version of guidelines

The Victorian Government has sought leave to appeal both decisions, which a Full Court is due to hear in November. Unless overturned, Bromberg J's findings largely spell the end to a government's ability to dictate the content of enterprise agreements through its own commercial leverage. This has consequences for the whole eastern seaboard, as New South Wales and Queensland recently introduced revised guidelines primarily based upon Victoria's version.27

Shortly after the ruling, the Victorian Government reissued a revised version of the guidelines to clarify that they do not "require, encourage or promote conduct that would constitute a contravention of the FW Act" and issued a practice direction that effectively suspends any monitoring of enterprise agreement content. New South Wales and Queensland have taken similar measures.

Implications: breadth and potential of general protections

Government procurement aside, the rulings demonstrate the breadth and potential application of the FW Act's general protection provisions. By reason of the expansive meaning given to both "independent contractor" and "proposing to enter into a contract for services", it is abundantly clear that all commercial contract negotiations (both public and private) must carefully consider the impact of industrial laws if the contract involves a labour supply.


1Construction, Forestry, Mining and Energy Union (CFMEU) v Victoria [2013] FCA 445.

2Construction, Forestry, Mining and Energy Union (CFMEU) v McCorkell Constructions Pty Ltd (No 2) [2013] FCA 446.

3See generally B Creighton, "Government procurement as a vehicle for workplace relations reform: the case of the National Code of Practice for the Construction Industry" (2013) 40 Federal Law Review 349.

4International Labour Organization, General Survey Concerning the Labour Clauses (Public Contracts) Convention 1949 (No 94) and Recommendation (No 84), International Labour Conference, 97th Session, 2008, Report III (Pt 1B), [2].

5Now a legislative instrument (the Building Code 2013 (Cth)) made under the Fair Work (Building Industry) Act 2012 (Cth), section 27(1). However, unlike the former national federal code, the Building Code 2013 also incorporates major elements of the former Federal Government guidelines.

6Construction, Forestry, Mining and Energy Union (CFMEU) v Eco Recyclers Pty Ltd [2013] FCA 24. In the case of Lend Lease, Gray J accepted an undertaking by the State that it would not exclude Lend Lease from the Bendigo Hospital project until the matter was determined. His Honour's decision was not published.

7Relying upon the meaning given to "independent contractor" under the Independent Contractors Act 2006 (Cth), section 4.

8Citing Barclay v Board of Bendigo Regional Institute of Technical and Further Education (2011) 191 FCR 212; 274 ALR 570; [2011] FCAFC 14 at [14]–[17]; Kelly v Construction, Forestry, Mining & Energy Union (CFMEU) (No 3) (1995) 63 IR 119 at 130; Australian Municipal, Administrative, Clerical and Services Union v Greater Dandenong City Council (2000) 101 IR 143; [2000] FCA 1231 at [75]; National Union of Workers v Qenos Pty Ltd (2001) 108 FCR 90; 183 ALR 475; [2001] FCA 178 at [48]; Construction, Forestry, Mining and Energy Union (CFMEU) v Pilbara Iron Co (Services) Pty Ltd (No 3) [2012] FCA 697; BC201204747 at [35]; Waugh v Kippen (1986) 160 CLR 156 at 164–5; 64 ALR 195; 60 ALJR 250;.

9Above, n 1, at [122]–[126]; above, n 2, at [89]–[93].

10Above, n 1, at [128]–[131]; above, n 2, at [95]–[98].

11Above, n 1, at [132]–[163]; above, n 2, at [99]–[130].

12Above, n 1, at [132]–[163], relying upon Employment Advocate v Williamson (2001) 111 FCR 20; 185 ALR 590; [2001] FCA 1164 at [15].

13Above, n 1, at [184]–[187].

14Above, n 1, at [188]–[212].

15Above, n 2, at [135]–[142].

16Above, n 2, at [141], [162]–[166].

17Above, n 2, at [143]–[146].

18Above, n 1, at [213]–[251]; above, n 2, at [148]–[152], citing, inter alia, Gietzelt v Craig-Williams Pty Ltd (No 1) (1959) 1 FLR 456 at 459; Gietzelt v Craig-Williams Pty Ltd (No2) (1959) 1 FLR 465 at 466–8; Community and Public Sector Union (CPSU) v Telstra Corp Ltd (No 2) (2000) 101 FCR 45; [2000] FCA 872 at [15]–[16]; Construction, Forestry, Mining and Energy Union (CFMEU) v Bengalla Mining Co Pty Ltd (No 2) [2013] FCA 362 at [49].

19Above, n 1, at [252]–[255]; above, n 2, at [153]–[174]. See FW Act, section 360.

20Above, n 1, at [252]–[255]; above, n 2, at [153]–[174].

21That is, that the State coerced Eco into exercising a "workplace right" — namely, the right to vary an enterprise agreement conferred by sections 207–210 of the FW Act.

22Citing National Tertiary Education Industry Union v Commonwealth of Australia (2002) 117 FCR 114; 114 IR 20; [2002] FCA 441 at [103]–[104]; Seven Network (Operations) Ltd v Communications, Electrical, Electronic, Energy, Information, Postal, Plumbing and Allied Services Union of Australia (CEPU) (2001) 109 FCR 378 at 388; 184 ALR 65; [2001] FCA 456; Construction, Forestry, Mining and Energy Union (CFMEU) (NSW Branch) v Alfred (2011) 203 IR 78; [2011] FCAFC 13 at [12].

23Above, n 2, at [231].

24Above, n 2, at [234]–[246].

25Above, n 2, at [256]–[257]; relying upon Hanley v Automotive, Food, Metals, Engineering, Printing and Kindred Industries Union (2000) 100 FCR 530; 182 ALR 563; [2000] FCA 1188 at [44]; above, n 22, at [35], [41].

26Above, n 2, at [277]–[278].

27Implementation Guidelines to the New South Wales Code of Practice for Procurement: Building and Construction, July 2013; Implementation Guidelines to the Queensland Code of Practice for the Building and Construction Industry, July 2013.

Clayton Utz communications are intended to provide commentary and general information. They should not be relied upon as legal advice. Formal legal advice should be sought in particular transactions or on matters of interest arising from this bulletin. Persons listed may not be admitted in all states and territories.

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

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

Some comments from our readers…
“The articles are extremely timely and highly applicable”
“I often find critical information not available elsewhere”
“As in-house counsel, Mondaq’s service is of great value”

Mondaq Advice Centre (MACs)
Up-coming Events Search
Font Size:
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
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (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

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’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.


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.


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 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.


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.


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.


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.


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

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

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

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