FEDERAL COURT OF AUSTRALIA

BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd (Review of Registrar’s Decision) [2025] FCA 616

File number(s):

NSD 285 of 2021

  

Judgment of:

NEEDHAM J

  

Date of judgment:

12 June 2025

  

Catchwords:

PRACTICE AND PROCEDURE -  Review of a Registrar’s Decision – hearing de novo – whether the respondent requires the provision of further particulars by way of a further amended statement of claim – where it is submitted that the applicant is running an unpleaded inferential case – where a blanket non-admission puts the applicant to proof on its case – where the applicant has steadfastly rejected the view that the way to proof lies in proving an inference – whether such an unpleaded inferential case arises – authorities considered – no unpleaded inferential case found – review application dismissed. 

  

Legislation:

Competition and Consumer Act 2010 (Cth) Sch 2 s 18

Federal Court Rules 2011 (Cth) rr 16.02, 16.03, 16.45

Queensland Uniform Civil Procedure Rules 1999 (Qld) r 149

  

Cases cited:

Ancient Order of Foresters in Victoria Friendly Society Ltd v Lifeplan Australia Friendly Society Ltd (2018) 265 CLR 1

ASIC v Pattenden [2024] FCA 1331

BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd (No 2) [2023] FCA 664

BCI Media Pty Ltd v CoreLogic Australia Pty Ltd [2022] FCA 1128

Bechara v Bates (2021) FCR 166; [2021] FCAFC 34

Cessnock City Council v 13259932 Pty Ltd [2024] HCA 17; 98 ALJR 719

Kingsgrove RSL v Sasevski [2002] NSWCA 342

Qualify Me Pty Ltd v Get Qualified Australia Pty Ltd [2016] FCA 192

Quinlan v Erm Power Ltd (No 1) (2021) 7 QR 377

Vaughan v Becton Property Group [2014] FCA 581

Yee v Wellington [2025] QSC 121

Yuanda Australia Pty Ltd v Dawson [2023] FCA 551

  

Division:

General Division

 

Registry:

New South Wales

 

National Practice Area:

Commercial and Corporations

 

Sub-area:

Commercial Contracts, Banking, Finance and Insurance

  

Number of paragraphs:

54

  

Date of hearing:

4 June 2025

  

Counsel for the Applicant:

Mr J Hennessy SC with Mr C McMeniman

  

Solicitor for the Applicant:

Gilbert + Tobin

  

Counsel for the Respondents:

Mr J Hastie

  

Solicitor for the Respondents:

Mills Oakley

ORDERS

 

NSD 285 of 2021

BETWEEN:

BCI MEDIA GROUP PTY LTD ACN 098 928 959

Applicant

AND:

CORELOGIC AUSTRALIA PTY LTD ACN 149 251 267

First Respondent

RP DATA PTY LTD ACN 087 759 171

Second Respondent

CORDELL INFORMATION PTY LTD ACN 159 137 274 (and another named in the Schedule)

Third Respondent

order made by:

NEEDHAM J

DATE OF ORDER:

12 June 2025

THE COURT ORDERS THAT:

1.    The application to review a Registrar’s decision filed by the respondents on 26 March 2025 (the RIA) be dismissed.

2.    The respondents to pay the applicant’s costs of the RIA.

3.    Any application by the applicant for any special costs order may be made by email to the Associate to Needham J by 26 June 2025.

4.    The parties are to notify the Court whether there are any issues of disclosure of confidential information in these reasons which would prevent its publication, by email to the Associate to Needham J by 10:30am on 13 June 2025.

Note:    Entry of orders is dealt with in Rule 39.32 of the Federal Court Rules 2011.

REASONS FOR JUDGMENT

NEEDHAM J:

The Registrar’s decision

1 The respondents, known in this litigation as the CoreLogic parties, seek a review of a decision of Senior National Judicial Registrar Farrell by way of Interlocutory Application (RIA). That decision, given on 14 March 2025, relevantly dismissed the respondents’ Second Further Amended Interlocutory Application (2FAIA) dated 12 February 2025. The RIA seeks orders in accordance with paragraphs 3B(b)(i), 3B(c)(ii), 3B(d)(ii) and 3C of the 2FAIA. Those orders read:

3B. In accordance with r 16.45 of the Rules, the Applicant provide further and better particulars by delivering to the Respondents amended versions of Confidential Annexures A, B and C which:

(b) in respect of each of (sic) customers mentioned in Confidential Annexure A, identifies:

(i) the date and method by which that customer was induced to believe the matters pleaded in paragraph 43(v) of the Amended Statement of Claim;

(c) in respect of each of the customers mentioned in Confidential Annexure B identifies:

(ii) the date on which the Applicant provided a discount to the customer; and

(d) in respect of each of the customers mentioned in confidential Annexure C identifies:

(i) the date and method by which that customer was induced to believe the matters pleaded in paragraph 43(v) of the Amended statement of Claim;

3C. In accordance with r 16.45 of the Rules, the Applicant provide further and better particulars of paragraphs 43(v) and 43(vi) of the Amended Statement of Claim which identify the facts and matters relied upon to support an inference that:

(a) RP Data and Cordell presented the information in the Comparative Documents to each of the customers, or prospective customers, mentioned in Confidential Annexures A, B and C;

(b) RP Data and Cordell, by presenting the information in the Comparative Documents to each of the customers, or prospective customers mentioned in Confidential Annexures A, B and C, induced those customers to believe that the information in Cordell Connect was more comprehensive and accurate than the information in LeadManager;

(c) In respect of each of the customers, or prospective customers, mentioned in Confidential Annexures A, B and C, by reason of the conduct pleaded in paragraph 43(v) of the Amended Statement of Claim, that customer:

(i) ceased subscribing to LeadManager;

(ii) required a discount in order to continuing (sic) subscribing to LeadManager; or

(iii) did not subscribe to LeadManager.

2 Confidential Annexures A, B, and C are, respectively, lists of:

(a)    customers who ceased subscribing to the applicant’s service LeadManager referred to in paragraph 43(vi)(a)(i);

(b)    customers who obtained a discount on their subscription referred to in paragraph 43(vi)(a)(ii); and

(c)    prospective customers, but did not subscribe to LeadManager referred to in paragraph 43(vi)(a)(ii);

of the Amended Statement of Claim (ASOC).

3 On 14 March 2025, the Registrar made orders that the applicant provide further and better particulars by amending the Confidential Annexures A, B and C to provide the dates on which it is alleged the conduct took place. That has been done.

4 Otherwise, the SFAIA was dismissed.

5 The applicant, BCI Media Group Pty Ltd, has filed an interlocutory application (AIA) seeking leave to amend the Confidential Annexures. The AIA has been stood over to 13 June 2025 (along with a further interlocutory application by the respondent filed on 3 June 2025, for access to a different set of Confidential Particulars) but I am assured that I can determine the RIA without impact on the determination of those applications.

6 At the hearing of the RIA on 4 June 2025, I was invited by the applicant to make a ruling without giving reasons. However, given the close argument on the RIA by both parties, taking most of a day, it seemed to me preferable to give at least short-form reasons for the orders I have made. The parties did not object to this course when proposed. The matter is back before me for case management on 13 June 2025, and the matter is listed for hearing for 16 days in September 2025. In those circumstances a prompt judgment is necessary, even if it does not adequately reflect the complexity of the arguments put before me.

The dispute

7 The dispute between the parties was summarised, albeit in relation to the dispute as pleaded in the original statement of claim, by Yates J in BCI Media Pty Ltd v CoreLogic Australia Pty Ltd [2022] FCA 1128 as (at [9]-[11]):

9 The general nature of BCI’s allegations can be summarised as follows. BCI, on the one hand, and CoreLogic Australia, RP Data and Cordell (who BCI calls the CoreLogic Parties) on the other, are competitors. They offer competing products that provide customers with access to information in relation to building projects throughout Australia. The information is accessed through a secure Internet site or a phone application by subscribing (for a fee) to the respective products and accessing the information they provide using individualised login details. BCI’s product is called LeadManager. The CoreLogic Parties’ competing product is called Cordell Connect.

10 BCI alleges that, between 2016 and 2019, the CoreLogic respondents surreptitiously accessed LeadManager. BCI alleges that the access was surreptitious because the CoreLogic Parties paid third parties (namely, the Forum Group, Skill Tech, and Gingold Investments) to obtain subscriptions to LeadManager in their own names. The third parties then provided their login details to the CoreLogic Parties, after which the CoreLogic Parties accessed LeadManager and “scraped” content from it, including by using the services of Telus International and Artis.

11 BCI alleges that this was done by the CoreLogic Parties themselves or through agents or subcontractors they engaged. The “scraping” was undertaken using manual processes (humans logging in and performing the “scraping”) and automated processes (in the form of programs known as “bots”). BCI alleges that the CoreLogic Parties used what they “scraped” from LeadManager to make comparisons between the contents of LeadManager and the contents of Cordell Connect. BCI alleges that these comparisons were used by the CoreLogic Parties for internal purposes, to improve Cordell Connect, and to procure customers

8 The causes of action pleaded by BCI against the CoreLogic parties in the ASOC are, in summary:

(a)    breach of contract;

(b)    copyright infringement;

(c)    breach of confidence; and

(d)    misleading and deceptive conduct in contravention of s 18 of the Australian Consumer Law (Schedule 2 to the Competition and Consumer Act 2010 (Cth)).

9 The Defence, in broad terms, admits some of the conduct alleged (for example, the creation of Comparative Documents comparing the data of both sides, and the use of robotic process automation on LeadManager to gain that information) but denies some specifics of various allegations, and denies wrongdoing as alleged.

10 The dispute at the heart of the RIA concerns the pleadings in paragraph 43 of the ASOC. That paragraph is quite lengthy. It can be found in the document entitled Parallel Pleadings at Attachment A to these reasons, which was handed up by the applicant during the hearing and sets out the relevant paragraphs of the pleading, that is, the section of the ASOC headed RP Data and Telus International and Artis Group accessed and copied information from LeadManager (paragraphs 41A-43C). The document has had long portions of particulars irrelevant to the RIA, mainly consisting of names of people alleged to have sent emails on particular dates, removed by my chambers in the interests of clarity and privacy.

11 Attachment A, while it sets out the ASOC paragraphs verbatim, from time to time paraphrases the Defence (see for example the defence to paragraph 41E). Where the specific terms of the pleading in the Defence are important, I have set them out below.

The questions to be determined

12 Although the RIA seeks a review of the Registrar’s decision, this is a hearing de novo and does not hinge on an error in the Registrar’s decision being shown (see Bechara v Bates (2021) FCR 166; [2021] FCAFC 34 at [17]).

13 The question as posed was, should BCI provide:

(a)    further particulars to paragraphs 43(v) and 43(vi) of the ASOC by way of further amendment to the Confidential Annexures A, B and C, and

(b)    further and better particulars “which identify the facts and matters relied upon to support an inference” that some of the CoreLogic parties “presented” the information in the Comparative Documents to the customers mentioned in the Confidential Annexures, and that they by doing so induced those customers to have a particular view of the two competitors’ services, and that by reason of that conduct and inducement, the customers took the actions that are listed in each of those Confidential Annexures.

14 The Confidential Annexures currently relied upon by the applicant provide only a row number, a company name, and a date when it is alleged that the named entity ceased to be a customer, had a discount applied, or would have become a customer. The date was ordered to be included by the Registrar in his decision. The additional facts sought to be included in the Confidential Annexures relate to the method by which customers were induced in the respective way alleged in each case.

15 The RIA calls on Rule 16.45 of the Federal Court Rules 2011 (Cth) (FC Rules). I set out the relevant rules as discussed in the Registrar’s reasons at [15]-[17].

15. Rule 16.02 relevantly provides:

Content of pleadings—general

(1) A pleading must:

(a) be divided into consecutively numbered paragraphs, each, as far as practicable, dealing with a separate matter; and

(b) be as brief as the nature of the case permits; and

(c) identify the issues that the party wants the Court to resolve; and

(d) state the material facts on which a party relies that are necessary to give the opposing party fair notice of the case to be made against that party at trial, but not the evidence by which the material facts are to be proved; and

(e) state the provisions of any statute relied on; and

(f) state the specific relief sought or claimed.

16. Rule 16.03 provides:

Pleading of facts

(1) A party must plead a fact if:

(a) it is necessary to plead it to meet an express denial of the fact pleaded by another party; or

(b) failure to plead the fact may take another party by surprise.

(2) However, a party need not plead a fact if the burden of proving the fact does not lie on that party.

17. Rule 16.45 provides:

Application for order for particulars

(1) If a pleading does not give a party fair notice of the case to be made against that party at trial and, as a result, the party may be prejudiced in the conduct of the party’s case, the party may apply to the Court for an order that the party who filed the pleading serve on the party:

(a) particulars of the claim, defence or other matter stated in the pleading; or

(b) a statement of the nature of the case relied on; or

(c) if there is a claim for damages—particulars of the damages claimed.

(2) An application under subrule (1) may be made only if:

(a) the particulars in the pleading are inadequate; and

(b) the party seeking the order could not conduct the party’s case without further particulars.

(3) A respondent who applies to the Court for an order under subrule (1) before filing the respondent’s defence must satisfy the Court that an order is necessary or desirable to enable the respondent to plead.

16 I agree with the Registrar’s review of the principles applying under the above Rules to the effect that the purpose of pleadings is to set out the material facts to be relied upon in the proceedings, so that the issues are sufficiently defined so that the parties understand them (at [18]), and that the purpose of particulars is to prevent parties from being taken by surprise, and to facilitate the collection of relevant evidence (see [18] and [19]).

17 The onus is on the CoreLogic parties to show that, pursuant to r 16.45(2), the current particulars are inadequate, and that they “could not conduct [their] case without further particulars”.

The dispute about an inferential case

18 The focus of the argument before me was the contention that the CoreLogic parties are not able to conduct their case in relation to the allegations in paragraphs 43(v) and 43(vi) without the primary facts relied upon to establish what they say is an inferential case pleaded in those paragraphs. They say that it became clear in January of this year that the pleading in those paragraphs relied on inferences being drawn, and that without knowledge of the primary facts which need to be proved to establish the inference, and without pleading of the inference sought to be drawn from those facts, they cannot meet that unpleaded inferential case.

19 As can be seen from Attachment A, the relevant paragraphs are as follows:

43(v) By presenting the information in the Comparative Documents to customers and prospective customers, RP Data and Cordell induced customers and prospective customers of BCI Media Group to believe that the information in Cordell Connect was more comprehensive and accurate than the information in LeadManager.

Particulars

(i) Customers and prospective customers of BCI Media Group presently known to BCI Media Group who were induced are set out in Confidential Annexures A, B and C.

43(vi) The conduct pleaded in paragraph 43(v) above caused:

(a) customers of BCI Media Group to:

(i) cease subscribing to LeadManager;

(ii) require BCI Media Group to apply a discount to their subscription fee; and

(b) prospective customers of BCI Media Group to not subscribe to LeadManager.

Particulars

(i) The customers of BCI Media Group who ceased subscribing to LeadManager as presently known to BCI Media Group are set out in Confidential Annexure A.

(ii) The customers of BCI Media Group where a discount was applied to their subscription as presently known to BCI Media Group are set out in Confidential Annexure B.

(iii) The prospective customers of BCI Media Group who did not subscribe to LeadManager as presently known to BCI Media Group are set out in Confidential Annexure C.

20 The defence pleaded to each of these paragraphs was that “the Respondents do not know, and cannot admit, allegation” (as filed). This blanket non-admission is in contrast to the pleadings to paragraphs (i) to (iv) of paragraph 43, which single out allegations which are admitted, sometimes confined to conduct of RP Data, one of the CoreLogic parties (paragraphs (i) and (ii)), or restricted to the emails “expressly particularized in that paragraph” (paragraph (iv)).

21 The ASOC does contain a pleading of an inference, in paragraph 43(iv). The particulars to that paragraph set out the conduct from which the pleaded inference could be inferred, including “what is pleaded in paragraphs 42(i) to 42(iii) above.” (It is accepted that the references to paragraph 42 in these particulars is an error and should read “43(i) to 43(iii) above”).

22 The respondents say that they pleaded to paragraphs 43(v) and (vi) in the way they did because they were unable to do otherwise. They did not take the view that the pleadings required the making of an inferential case against them until January of this year. No objection was taken to the amended pleading but, the respondents say, that is because they did not understand that the pleading was based on inferences.

23 The respondents say that there must be “something more” to link the pleadings in 43(v) and (vi) to the pleaded facts and particulars in paragraphs 43(i) to (iv). They say that the “something more” became crystallised by the terms of paragraphs [35] and [36] of an affidavit filed 31 January 2025 by the applicant’s solicitor, Mr Williams, who said:

35 I understand paragraph 22 of the 13 December Cliff Affidavit to suggest that because the Respondents have not identified in the Applicant's CRM on its review to date any written examples of Relevant Customers explicitly saying that their decision to cease subscribing to LeadManager is due to Cordell Connect's conduct, that conduct therefore cannot be proven. If that suggestion is being made, it is incorrect. BCI does not need to prove by reference to a record held by either party what was said to each customer or potential customer. The Court may reach that conclusion based on the facts that the comparative data was consistently provided to CoreLogic salespeople during the Period, along with instructions on how to impart that information to customers and potential customers of CoreLogic for the financial benefit of CoreLogic, and that such salespeople did so, when following those instructions.

36 BCI will be relying on the extensive documentary evidence of comparative information and specific authorised representations circulated amongst their sales staff during the relevant Period as reflecting evidence from which an inference will be drawn that the information and the representations were deployed when dealing with customers and prospective customers of CoreLogic. BCl's position is that it is not an answer to that evidence for CoreLogic to seek to rely on the absence of references to that information and the representations in the Applicant's CRM as it does not purport to be a verbatim record of the communications with the relevant customers any more than the Respondents' CRM purports to be a verbatim record.

(emphasis taken from respondents’ submissions on the RIA)

24 The affidavit of Mr Cliff, solicitor for the respondents, referred to by Mr Williams was not originally read on this application, and so the extracted paragraphs of Mr Williams’ affidavit were not put in context. At the  Court’s suggestion that it be read on the limited basis of providing context to what was an important part of the respondents’ case, it has now become part of the material on this application.

25 The respondents contend that the first sentence of paragraph 36 means that BCI, not having pleaded an inference by which it linked the presentation of the material (paragraph 43(iv)) and the inducement alleged in paragraph 43(v), intends to rely on unpleaded inferences to establish that link.

26 The respondents also referred to submissions made by BCI’s junior counsel before the Registrar (as set out in paragraphs 31 and 33 of the respondents’ submissions) where there was discussion of how the evidence as to an “overlap” between customers who were provided with the comparative documents who took up subscriptions for LeadManager, and the fact that communications between the salespeople for the relevant respondents, and the customers listed in the Confidential Annexures, lined up in particular ways. The CoreLogic parties say that such an approach is necessarily inferential, and is underlined by the approach now taken by the applicant in the AIA, which seeks to add to the names in the Confidential Annexures.

27 The heart of the CoreLogic parties’ submission is that “The fact that BCI is, in truth, running an (unpleaded) inferential case emerges from discovery” because “… neither party has discovered any document recording or referring to any presentation of Comparative Documents (or other approach) to [then current, and prospective] customers”. They say that the evidence filed by the applicant (which is complete as to lay evidence) does not demonstrate a link between any “presentations” and the named customers in the Confidential Annexures, and, so, “CoreLogic … remains wholly in the dark about the case that BCI seeks to advance against it”.

28 They relied in their argument on this point on the requirements of pleading an inferential case, pointing to a number of authorities which it is said supports their position.

29 The decision of Kennett J in ASIC v Pattenden [2024] FCA 1331 involved a similar factual backdrop in which an application was made following discovery and following the applicant having put on its evidence in chief, and allegations of which the particulars were sought were the subject of pleaded non-admissions. At [36] of Pattenden, it was submitted by the respondents that Kennett J expressly regarded the pleading of a non-admission as not being something which stood in the way of an application for the provision of particulars. His Honour went on to observe at [45] that the response of the applicant in those proceedings that the details of the allegations would be made by the evidence could not be seen as a full response, and that fairness required those matters to be provided by way of particulars, rather than having to await further steps.

30 The Court’s attention was then brought to the decision of Pagone J in Vaughan v Becton Property Group [2014] FCA 581. At [15] of Vaughan v Becton, Pagone J observed that the defence of the pleading in question offered up by Counsel, namely that the amended statement of claim, which alleged facts from which relevant inferences could be drawn with various specific allegations identified, was insufficient. Pagone J observed that a litigant should be told with precision which facts are alleged against them including which inferences a Court will be asked to draw as the basis for liability and which facts are said to justify those inferences. In that case, his Honour found that the amended statement of claim did not link the inferences which were said to base the actionable allegations, nor did it identify the facts which were said to warrant the inferences which needed to be drawn, with this conclusion founding his Honour’s decision to strike out the pleading.

31 Counsel for the respondent also noted two cases which cite the above principles expounded by Pagone J, namely those of Markovic J in Qualify Me Pty Ltd v Get Qualified Australia Pty Ltd [2016] FCA 192 and Cheeseman J in Yuanda Australia Pty Ltd v Dawson [2023] FCA 551.

32 The respondents further relied on the decision of Henry J in Yee v Wellington [2025] QSC 121, which, much like the circumstances in these proceedings, involved both copyright and breach of contract claims, although those claims arose from the perhaps subjectively more interesting world of music. At [22] of Yee, Henry J helpfully sets out what the requirements are for pleading an inferential case, which his Honour conceptualises as a three-step process requiring:

(1)    the adducing of direct evidence of what are cast as “foundational facts”;

(2)    identification of how those facts invite inferences of “intermediate fact”; and in turn

(3)    alleging a cause of action to be inferred from those foundational and intermediate facts.

33 While counsel for the respondents acknowledged that these conclusions were drawn in relation to the requirements of the Queensland Uniform Civil Procedure Rules 1999 (Qld), he observed that the relevant rule, being r 149, is substantially in the same terms as r 16.02 of the Rules. On the facts in Yee, his Honour concluded that the allegations pleaded in that statement of claim satisfied steps 1 and 3 above, but failed to satisfy the pleading requirements in relation to step 2. I am invited to draw the same conclusion in this application.

34 In the same vein of Queensland Supreme Court decisions, the respondents pointed to the decision of Bowskill J in Quinlan v Erm Power Ltd (No 1) (2021) 7 QR 377, in which her Honour noted at [65] the requirement in the rules for an explicit linking of facts to inferences, with that requirement necessitating that the relevant pleading spell out the precise manner in which the underlaying facts are to be deployed. The applicant resists, as it did before the Registrar, the conclusion that the pleading in 43(v) and (vi) is inferential, saying that the facts relied upon are pleaded and particularised in paragraphs 43 to 43(iv). They say that the push by the CoreLogic parties is an attempt to obtain, not particulars of a pleaded case, but evidence.

35 In support of this contention, they point to the fact that, on BCI’s case, the CoreLogic parties have sought to conceal their conduct relating to the creation and presentation of the Comparative Documents to customers and prospective customers, leading to lacunae in the evidence and in the CoreLogic parties’ disclosure. In particular, the applicant relies on the principle that where the CoreLogic parties have, they submit, created difficulties or impossibilities of proof by their wrongdoing, they bear the evidential onus; see Cessnock City Council v 13259932 Pty Ltd [2024] HCA 17; 98 ALJR 719 at [127]-[132]; Kingsgrove RSL v Sasevski [2002] NSWCA 342 at [42].

36 The applicant also points to the equitable nature of the relief sought in the breach of confidence and copyright causes of action. BCI says that their evidence will demonstrate that the CoreLogic parties, not BCI, will have the onus to prove that the Leadmanager profits in the relevant period should not be attributed to the wrongful conduct (see Ancient Order of Foresters in Victoria Friendly Society Ltd v Lifeplan Australia Friendly Society Ltd (2018) 265 CLR 1 at [13]-[21]).They say that their evidence will demonstrate that the CoreLogic parties, not BCI, will have the onus to prove that the Leadmanager profits in the relevant period should not be attributed to the wrongful conduct (see Ancient Order of Foresters at [13]-[21]).

Is there an unpleaded inferential case?

37 In discussion between the Bench and Mr Hastie, counsel for the CoreLogic parties, the question was asked whether the applicant sought, in fact, particulars of an inferential case in 43(v) and (vi), or whether they sought to tie the applicant to the pleadings as they stand; in which case, the applicant would not be able to assert, later in the conduct of this litigation, that they relied on inferences to make out the facts pleaded in 43(v) and (vi). Mr Hastie submitted that the CoreLogic parties’ position was that:

…[BCI is] running an inferential case. Their solicitor has sworn to it. It has been confirmed in exchanges before the registrar previously. The way in which the confidential annexures – and the correspondence has confirmed it as well. It has never been disavowed, including in the written submissions that have been progressively filed over the last couple of weeks on this application. It is evident that they must be running an inferential case.

38 Referring to this exchange, Mr Hennessy SC, for BCI, took the Court through the pleadings as set out in Annexure A, starting at paragraph 42 of the ASOC, and submitted (in very broad summary) that, in the pleadings leading up to paragraphs 43(v) and (vi):

(a)    the respondents admit that some of the CoreLogic parties used data obtained from BCI to create comparative documents;

(b)    the respondents admit that a process was created by which customers of one of the CoreLogic parties could request documents for the purpose of presentation to customers (noting that the applicant’s pleading is wider, but the defence restricts the admission to only one of the respondents);

(c)    the respondents admit that one of the CoreLogic parties were in fact provided with comparative documents for that purpose; and

(d)    in relation to paragraph 43(iv), the particularised inference, the respondents admit the allegation 43(iv)(b) “as it concerns the emails expressly particularised in that paragraph”.

39 The result of the respondents’ admissions in relation to paragraph 43(iv)(b) then, reads as follows:

From at least 11 May 2017, employees of RP Data and Cordell … sent the expressly particularised emails containing information from the Comparative Documents to customers or proposed customers of BCI Media Group.

40 The particulars to 43(v) link the pleading in 43(iv) to requests for comparative documents as particularised in paragraph 43(ii), which lists a number of specific emails and dates.

41 The particulars to paragraph 43(v) provide:

Customers and prospective customers of BCI Media Group presently known to BCI Media Group who were induced are set out in Confidential Annexures A, B and C.

42 Mr Hennessy set out the applicant’s position as follows by drawing my attention to 43(v) and saying:

… the opening words [of 43(v) are] “by presenting the information in the comparative documents.” That is language that, self-evidently, refers back to previous sub-paragraphs that make a series of factual allegations about the deployment of information in the comparative documents by presentation, much of which is admitted in some form or another.

And that point addresses argument 1 by my friend immediately before lunch, because his point was that we have not identified the inferential case in paragraphs 43(v) and (vi). My point, with respect, is, of course we have, because 43(v), acknowledged by my learned friend both in writing and in oral submissions to be a pleading about the consequences of the conduct pleaded earlier, is referring to that earlier conduct, and that conduct is not to be mischaracterised as simply allegations about a general practice. They are specific allegations about the use of my client’s information in documents that were presented to customers and potential customers.

43 The applicant characterised the respondents’ case of “there must be something more” as ignoring the pleaded case of connections between 43(i)-(iv) on the one hand, and 43(v)-(vi) on the other, and criticises the blanket pleading of “do not know and cannot admit” in relation to the actions taken by staff of the CoreLogic parties to present the comparative documents to customers and prospective customers.

44 Mr Hennessy SC took me to part of the evidence, which included various directives to employees not to leave the comparative documents with customers, as indicating an attempt on the part of the CoreLogic parties to conceal the comparative documents. He submitted that “everything that goes before paragraph 43(v) constitutes the facts and then an inference as to presentation, that has the effect pleaded or the consequence pleaded in 43(v).” Additionally, the particulars to paragraph 43(vii) provide:

Particulars

It is to be inferred from the conduct pleaded in paragraphs 43(iv) to 43(vi) that some customers listed in Confidential Annexures A and C entered into subscription agreements with RP Data.

The customers and prospective customers who entered into subscription agreements with RP Data is solely within the knowledge of RP Data and will be provided after evidence and discovery.

Should the applicant be required to plead an inferential case in lieu of paragraphs 43(v) and (vi)?

45 It seems to me that the CoreLogic parties have not made out their contention that there is a necessarily unpleaded case underlying the pleadings in paragraphs 43(v) and (vi). Where BCI has expressly disavowed that position, and has pointed to the way in which it intends to run its case by proving the process and the directions to staff from which, it says, it can prove the inducement to customers and potential customers, it does not seem to me that the CoreLogic parties are unable to run their case on the pleadings and particulars currently provided.

46 I do not regard the affidavit of Mr Williams as being a definitive contention that the inferential case is restricted to paragraphs 43(v) and (vi). The Registrar dealt with this issue at [54] of his reasons, and I agree that the passage in Mr Williams’ affidavit is a summary, not a thoughtful analysis of the pleaded basis of his client’s case. In any event, there is a specific particularisation of an interference in 43(iv), and I accept the applicant’s submission that the whole of paragraph 43 needs to be read together, particularly as to the process by which the presentation of the comparative documents came about. Nor do I regard the different ways in which the parties have regarded their cases as resulting in the respondents’ position being “unanswered”. The complaint appears to be rather that the applicant does not agree with the respondents that there is an unpleaded inferential case for which particulars should be given.

47 For these reasons, I am not satisfied that there is an unpleaded inferential case. I am accordingly not minded to order the further particularisation of the claims in 43(v) and (vi), noting that the current pleading appears to accord with the requirements as to pleading articulated by Yates J in BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd (No 2) [2023] FCA 664 at [96].

48 I am not persuaded that the respondents cannot meet the case as pleaded. While there has been a careful pleading to paragraphs (i) to (iv), the blanket non-admission does not mean that the respondents are unable to plead to paragraphs (v) to (vi). The non-admission puts the applicant to proof of its case, and as the applicant has steadfastly rejected the view that the way to proof lies in proving an inference, it is on notice as to how it needs to prove its case.

Should BCI be required to amend the Confidential Annexures as sought in the RIA?

49 The above reasoning also applies to the amendments to the Confidential Annexures sought by the respondent. Where the applicant maintains that it is not pleading a case based on inferences, and where reading paragraph 43 as a connected whole, it appears that that claim may be able to be sustained, it is in fact a request for evidence to require that the “date and method by which … customer[s] were induced to believe the matters pleaded in paragraph 43(v) of the Statement of Claim”.

50 I am not persuaded that the particulars sought in the Confidential Annexures are “necessary” for the respondents to run their case. As noted by Yates J in BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd (No 2) at [97]:

BCI should also provide particulars of the identities of the various actual customers of BCI, the actual customers of RP Data, the prospective customers of BCI, and the prospective customers of RP Data, known to it, who acted in the ways alleged.

51 The Confidential Annexures comply with this requirement.

52 Accordingly, for the above reasons, I am not satisfied that the Confidential Annexures should be ordered to be amended to include the method by which it is alleged that the relevant customers were relevantly induced to a particular state of belief, as the basis for this is contained in the ASOC in paragraph 43.

Orders

53 Accordingly, the RIA should be dismissed with costs.

54 If there is any application by the applicant for any special costs order, any such application may be provided to my Associate within 14 days of today’s date, and will be determined at the substantive hearing of this matter.

I certify that the preceding fifty-four (54) numbered paragraphs are a true copy of the Reasons for Judgment of the Honourable Justice Needham.

Associate:

Dated:    12 June 2025

SCHEDULE OF PARTIES

 

NSD 285 of 2021

Respondents

 

Fourth Respondent:

CORELOGIC INC

Attachment A

BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd - NSD 285 of 2021 Parallel pleadings

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

RP Data and Telus International and Artis Group accessed and copied information from LeadManager

Access to LeadManager by RP Data

41A

Between July 2016 and 27 March 2020, RP Data used the User Details RP Data was provided by the Forum Group (in and after July 2016), SkillTech (after 3 October 2017) and Gingold (after 12 September 2018) to access LeadManager.

Particulars

i. The employees of RP Data who accessed LeadManager as currently known to BCI Media Group were [employees].

As to paragraph 41A, the Respondents:

(a) admit that RP Data, from time to time, used those User Details to access LeadManager; and

(b) otherwise do not know, and cannot admit the allegation.

41AA

RP Data also engaged in the conduct pleaded in paragraph 41A using software:

(a) that was licensed by RP Data on or around 21 December 2018, 6 February 2019, 5 March 2019, 20 August 2019, 20 September 2019;

(b) that is known as ‘UiPath Orchestrator Server’, ‘UiPath Unattended Robot’ and ‘UiPath Studio Development’ from a company named UiPath SRL;

(c) that is a type of “web crawling” software;

As to paragraph 41AA, the Respondents:

(a) admit the allegations in (a) and (b);

(b) deny the allegations in (c) and (d) they say further that:

i. the Robotics Program (as that term is used in the SOC) or, alternatively, robotic process automation was used to automate a number of different processes and tasks carried out by RP Data; and

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(d) to access and copy BCI Works and BCI Confidential Information from LeadManager,

(the Robotics Program).

ii. the use of the Robotics Program in connection with LeadManager was just one of the processes and tasks for which the Robotics Program or, alternatively, robotic process automation was used.

Access to LeadManager by Telus International

41B

From at least 4 October 2017, Telus International was contracted by RP Data, through and along with another subsidiary of CoreLogic, Inc named CoreLogic Solutions, to:

(a) access LeadManager using the User Details it was provided by RP Data;

(b) copy information from LeadManager; and

(c) provide the copied information from LeadManager to RP Data.

Particulars

i. The terms of the contract are in writing, recorded in a written agreement dated 1 November 2014 and associated Statement of Work dated 1 March 2018.

ii. The terms of the contract are also implied by the conduct pleaded in paragraphs 41C and 42A below.

As to paragraph 41B, the Respondents:

(a) say that:

i. on or about 1 November 2014, Telus International (U.S.) Corp (Telus) and Corelogic Solutions LLC (Solutions) entered into an agreement styled as a Master Professional Services Agreement (MPSA);

ii. on or about 2 March 2018, Telus and Solutions agreed on the terms of a document entitled Statement of Work (SOW);

iii. the SOW set out, inter alia, tasks which Telus was to perform under the MPSA including the:

review residential data quality and assess the data integrity against competitors in each state for both residential and commercial properties including Cordell data”;

iv. the tasks which Telus, in fact, performed were:

A. accessing LeadManager;

B. counting the number of construction projects recorded in LeadManager, whether by human labour or using the Robotics Program, by:

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

  

(1) the State or Territory in which the project was located;

(2) the stage at which the project was at;

(3) the category or type of the project;

(4) the number of companies and contacts listed in respect of each project;

C. recording the details pleaded in sub-paragraph (iv)(B) herein in spreadsheets and providing those spreadsheets RP Data;

D. alternatively to sub-paragraph (iv)(C) herein, providing the information pleaded in sub-paragraph (iv)(B) herein to RP Data;

E. on one occasion, accessing LeadManager and downloading a copy of the Fair Use Policy (as that term is defined in the SOC);

(together, Telus Tasks);

(b) admit paragraph (a);

(c) deny paragraphs (b) and (c) to the extent they are inconsistent with the matters pleaded in paragraphs (a) and (b); and

(d) otherwise admit paragraphs (b) and (c).

41C

From at least 4 October 2017 until on or around 29 March 2019, Telus International used User Details it was given by RP Data to access LeadManager pursuant to the contract pleaded in paragraph 41B above.

As to paragraph 41C, the Respondents:

(a) say that Telus performed the Telus Tasks between dates alleged;

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

Particulars

i. The employees or contractors of Telus International who engaged in that conduct on behalf of Telus International as currently known to BCI Media Group were [employees].

ii. The employees or contractors of Telus International were provided with email addresses with the suffix @corelogic.com.au for the purposes of carrying out the conduct above.

(b) deny the allegation to the extent it is consistent with the matters pleaded in

(a) herein; and

(c) otherwise, admit the allegations.

Access to LeadManager by Artis Group

41D

In or about September 2018, RP Data contracted the Artis Group to:

(a) assist RP Data in setting up the Robotics Programs to access LeadManager using the User Details it was provided by RP Data;

(b) access LeadManager using the User Details it was provided by RP Data;

(c) copy information from LeadManager;

(d) provide the copied information from LeadManager to RP Data.

Particulars

i. The terms of the contract are in writing, recorded in a written Services Quotation dated 31 October 2018 (signed by an employee of RP Data, [employee] and a written Master Services Agreement and Statement of Work dated 1 August 2020.

ii. The terms of the contract are to be implied by the conduct pleaded in paragraphs 41E and 42B below.

As to paragraph 41D, the Respondents:

(a) say that:

i. Artis was contracted to set up Robotics Programs which were to be used to automate a number of different processes and tasks carried out by RP Data including, but not limited to, the use of Robotics Programs in respect of LeadManager;

ii. The tasks actually performed by Artis in connection with LeadManager were limited to:

A. calculating the time the Robotics Program took to count the number of projects recorded in LeadManager as set out in the document which is COR.001.002.0485;

B. extracting a Project Spreadsheet from LeadManager, which document is COR 001.002.0487

(together, Artis Tasks);

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

  

(b) deny the allegations to the extent they are inconsistent with the position pleaded in (a) herein.

41E

Between September 2018 and 27 March 2020, Artis Group used User Details it was provided by RP Data to access LeadManager in accordance with the contract pleaded in paragraph 41D above.

Particulars

i. The employees or contractors of Artis Group who engaged in that conduct on behalf of Artis Group, as currently known to BCI Media Group were [employees’.

ii. The employees or contractors of Artis Group were provided with email addresses with the suffix @corelogic.com.au for the purposes of carrying out the conduct above.

The Respondents deny the allegation they say that they repeat and rely on the matters pleaded in paragraph 41D above.

Copying information from LeadManager

42

When RP Data accessed LeadManager as pleaded in paragraph 41A, above, it downloaded, captured screenshots and copied information from LeadManager in respect of projects published on LeadManager into:

(a) documents saved onto a shared network drive controlled by RP Data and accessible to employees of RP Data and Cordell; and

(b) emails sent between RP Data and Cordell employees.

Particulars

i. The shared network drive referred to in (a) presently known to BCI Media Group had the address: \\bpvwin01-

As to paragraph 42, the Respondents:

(a) say that RP Data:

i. accessed LeadManager;

ii. captured screenshots of Projects Reports (as that term is defined in the SOC) in LeadManager:

A. on 2 September 2019 as referred to in document COR.001.002.0528; and

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

fs1.ad.corelogic.asia\Departments\Telus SharedFolder\Robotics\CordellConnectComparison.

ii. The RP Data employees who sent or received the emails referred to in (b) presently known to BCI Media Group are: [employees].

iii. The Cordell employees who sent or received the emails referred to in (b) presently known to BCI Media Group are: [employees].

iv. The emails referred to in subparagraph (b) as are presently known to BCI Media Group are as follows:

(A) Email from [employee] to [employee] dated 24 January 2018.

(B) Email from [employee] to [employees] on 2 September 2019.

(C) Email from [employees] on 9 August 2019.

B. in December 2019 as referred to in document COR.001.002.0113;

(b) say, further, that RP Data:

i. accessed LeadManager;

ii. exported a Project Spreadsheet (as that term is defined in the SOC) from LeadManager on or about 30 January 2018, being document COR.001.002.0610;

(c) say, further that RP Data:

i. received the spreadsheets produced by Telus as part of the Telus Tasks (as pleaded in paragraph 41B(a) above) which compared the number of projects recorded in LeadManager with the number of projects recorded in Cordell Connect; or

ii. alternatively, received the information provided to it by Telus as part of the Telus Tasks and created spreadsheets from that information (as pleaded in paragraph 41B(a) above) which compared the number of projects recorded in LeadManager with the number of projects recorded in Cordell Connect;

iii. circulated those spreadsheets between certain of its employees by email;

(d) deny the allegations in (a) and (b) to the extent they are in consistent [sic] with the matters pleaded in paragraphs (a) to (c); and

(e) otherwise admit paragraphs (a) and (b).

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(D) Email from [employee] [employees] dated 8 August 2019.

(E) Email from [employee] to [employee] dated 14 August 2019.

(F) Email from [employee] to [employee] dated 10 September 2019.

(G) Email from [employee] to [employees] on 12 September 2019.

(H) Email from [employee] to [employees] on 11 October 2019.

(I) Email from [employee] to [employees] on 6 December 2019.

(J) Email from [employee] to [employees] on 10 February 2020.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(K) Email from [employee] [employees] on 10 February 2020.

(L) Email from [employee] to [employee] on 1 March 2020.

(M) Email from [employee] to [employees] dated 3 March 2020.

(N) Email from [employee] to [employees] on 6 March 2020.

 

42A

When Telus International accessed LeadManager as pleaded in paragraph 41C above it downloaded and copied information from LeadManager in respect of projects published on LeadManager into:

(a) excel spreadsheets saved onto a shared network drive controlled by RP Data and accessible to employees of RP Data and Cordell; and

(b) emails sent to RP Data employees.

Particulars

(ai) The acts of Telus International were performed by employees or contractors of Telus International named [employees].

(i) Telus International provided the copied information to RP Data by email and through a shared drive at the address “R:\Telus Shared Folder” accessible by RP Data and Cordell.

The Respondents deny the allegation they say that the tasks which Telus performed were the Telus Tasks.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(ii) The following employees presently known to BCI Media Group received the emails referred to in (b) from Telus International: [employees].

(iii) The emails referred to in subparagraph (b) as presently known to BCI Media Group are as follows:

(A) Email from [employee] to [employee] dated 24 November 2017.

(B) Email from [employee] to [employees] dated 27 November 2017.

(C) Email from [employee] to [employees] dated 15 January 2019.

(D) Email from [employee] to [employee] dated 15 January 2019.

(E) Email from [employee] to [employees] dated 29 January 2019.

(F) Email from [employee] to [employees] dated 1 February 2019.

(G) Email from [employee] to [employees] dated 4 February 2019.

(H) Email from [employee] to [employees] dated 5 February 2019.

(I) Email from [employee] to [employees] dated 6 February 2019.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(J) Email from [employee] to [employees] dated 7 February 2019.

(K) Email from [employee] to [employees] dated 8 February 2019.

(L) Email from [employee] to [employees] dated 11 February 2019.

 

42B

When Artis Group accessed LeadManager as pleaded in paragraphs 41E above it downloaded and copied information from LeadManager in respect of projects published on LeadManager into:

(a) excel spreadsheets saved onto a shared network drive controlled by RP Data and accessible to employees of RP Data and Cordell; and

(b) emails sent to RP Data employees.

Particulars

(i) The acts of Artis Group were performed by employees or contractors of Artis Group ([employees]) and by the Robotics Program which Artis Group assisted RP Data in setting up.

(ii) Artis Group provided the copied information to RP Data by email and through a shared drive presently known to BCI Media Group at the address “R:\Telus Shared Folder” accessible by RP Data and Cordell.

(iii) The following employees presently known to BCI Media Group received Copied Information by email from Artis Group: [employees].

(iv) The emails referred to in (b) presently known to BCI Media Group are as

The Respondents deny the allegation they say that they repeat and rely on the matters pleaded in paragraph 41D above.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

follows:

(A) Email from [employee] to [employees] dated 4 March 2019.

(B) Email from [employee] to [employees] dated 23 May 2019.

(C) Email from [employee] to [employee] dated 23 May 2019.

(D) Email from [employee] to [employees] dated 28 May 2019.

(E) Email from [employee] to [employee] on 25 July 2019.

 

42C

RP Data used the information copied from LeadManager as pleaded in paragraphs 42 to 42B above to create documents which compared information from LeadManager to information from Cordell Connect (hereafter referred to as Comparative Documents).

Particulars

i. The Comparative documents presently known to BCI Media Group took the form of:

(A) spreadsheets given titles “Cordell vs BCI Comparison”, “Comparison Connect BCI” and “Project Spreadsheets”;

(B) documents given the titles “CoreLogic Data Supremacy Sheet”, “BCI Comparison”, “Cordell Comparison”, “Cordell Competitor Comparison Sheet”, “Value prop and comparison pack”, “Comparison Connect BCI”;

(C) a PowerPoint presentation titled “The Cordell Connect Advantage”;

As to paragraph 42C, the Respondents:

(a) say that the Comparative Documents:

i. were created between October 2017 and February 2020 by Telus and RP Data using, respectively, the data pleaded in paragraphs 41B(a)(iv)(B) and 42(c)(ii) of the Defence (Relevant Data);

ii. consisted of spreadsheets and presentations which compared the number of projects recorded in LeadManager with the number of projects recorded in Cordell Connect;

iii. did not contain any words or content taken from LeadManager;

(b) deny the allegations to the extent they are inconsistent with paragraph (a) herein; and

(c) otherwise admit the allegations.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(D) emails sent between employees and officers of RP Data and Cordell comparing information from LeadManager to information in Cordell Connect.

ii. The Comparative Documents were saved by RP Data on a shared network drive controlled by RP Data and accessible to employees of RP Data and Cordell at the following address presently known to BCI Media Group:

\\bpvwin01-fs1.ad.corelogic.asia\Departments\Telus SharedFolder\Robotics\CordellConnectComparison.

iii. The employees of RP Data who sent or received the emails referred to in

(D) above that are currently known to BCI Media Group are: [employees]

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

iv. The officers of RP Data and Cordell who sent or received the emails referred to in (D) above that are currently known to BCI Media Group are: [employees].

v. The employees of Cordell who sent or received the emails referred to in

(D) above that are currently known to BCI Media Group are: [employees].

vi. The emails referred to in referred to in (D) above presently known to BCI Media Group are as follows:

(A) Email from [employee] to [employees]dated 25 October 2017.

(B) Email from [employee] to [employees] 31 October 2017.

(C) Email from [employee] to [employees] dated 23 November 2017.

(D) Email from Irene Gardner to [employees] dated 5 December 2017.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(E) Email from [employee] to [employees] dated 22 December 2017.

(F) Email [employee] to [employees] dated 24 January 2018.

(G) Email from [employee] to [employees] dated 1 March 2018.

(H) Email from [employee] to [employees] dated 7 March 2018.

(I) Email from [employee] to employees and officers of RP Data and Cordell on the email list titled “DL-Exec 2017 CoreLogic International” dated 15 March 2018.

(J) Email from [employee] to [employees] dated 4 April 2018.

(K) Email from [employee] to [employees] dated 4 April 2018.

(L) Email from [employee] to [employees] dated 19 April 2018.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(M) Email from [employee] to [employees] dated 24 April 2018.

(N) Email from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL- APAC Sales”, “DL-MarketingGroup”, “DL-Sales Ops Team”, “DLProduct- DL”, “DL-Solutions” and “Legals Australia” dated 16 May 2018.

(O) Email from [employee] to employees and officers of RP Data and Cordell on the email list “DL-Exec 2017 Corelogic International” dated 16 May 2018.

(P) Email from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL- APAC Sales” and “DL-Exec 2017 Corelogic International” and Sandy Forster dated 23 May 2018.

(Q) [employee] to [employees] dated 25 May 2018.

(R) Email from [employee] to [employees] dated 30 May 2018.

(S) Email from [employee] to [employees]  dated 14 June 2018.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(T) Email from [employee] to [employees] dated 2 August 2018.

(U) Email from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL- APAC Sales”, “DL-MarketingGroup”, “Corporate Systems”, “DLSales Directors”, “DL-Sales Management Group”, “Staff Support” and “Sales Support” and Loren Wakeley dated 13 August 2018.

(V) Email from [employee] to [employee] dated 31 August 2018.

(W) Email from [employee] to [employees] dated 3 September 2018.

(X) Email from [employee] [employees] dated 18 September 2018.

(Y) Email from [employee] to [employees] dated 19 October 2018.

(Z) Email from [employee] to [employees] dated 3 December 2018.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(AA) Email from [employee] to [employees] dated 20 December.

(BB) Email from [employee] to [employees] dated 15 January 2019.

(CC) Email from [employee] to [employees] dated 30 January 2019.

(DD) Email from [employee] to [employees] dated 30 January 2019.

(EE) Email from [employee] [employees] dated 31 January 2019.

(FF) Email from [employee] to [employees] dated 30 January 2019.

(GG) Email from [employee] to [employees] dated 28 February 2019.

(HH) Email from [employee] to [employees]dated 28 May 2019.

(II) Email from [employee] to [employees] dated 14 June 2019.

(JJ) Email from [employee] to [employees] dated 2 July 2019.

(KK) Email from [employee] to [employee] dated 8 July 2019.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(LL) Email from [employee] to [employees] dated 8 August 2019.

(MM) Email from [employee] to [employees] on 9 August 2019.

(NN) Email from [employee] [employees] dated 9 August 2019.

(OO) Email from [employee] to [employees] dated 14 August 2019.

(PP) Email from [employee] to [employees] dated 9 September 2019.

(QQ) Email from [employee] to [employee] dated 10 September 2019.

(RR) Email from [employee] to [employee] dated 12 September 2019.

(SS) Email from [employee] to [employees] on 12 September 2019.

(TT) Email from [employee] to [employees] on 11 October 2019.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(UU) Email from [employee] to [employees] on 6 December 2019.

(VV) Email from [employee] to [employees] on 10 February 2020.

(WW) Email from [employee] to [employees] on 10 February 2020.

(XX) Email from [employee] to [employee] on 1 March 2020.

(YY) Email from [employee] to [employees] dated 3 March 2020.

(ZZ) Email from [employee] to [employees]  on 6 March 2020.

 

Use of Comparative Documents created from LeadManager Information

43

RP Data used the information copied from LeadManager (as pleaded in paragraphs above 42 to 42B above) and the Comparative Documents (as pleaded in paragraph 42C above) to improve Cordell Connect by:

(a) identifying gaps in the information on Cordell Connect; and

(b) using information copied from LeadManager to fill those gaps.

The Respondents deny paragraph 43.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

Particulars

i. The gaps that RP Data identified and filled using information copied from LeadManager and the Comparative Documents which are presently known to BCI Media Group are in respect of projects listed at paragraph A1 of the Applicant’s Confidential Particulars dated 12 September 2023 (Applicant’s Confidential Particulars).

ii. The conduct is to be inferred from emails sent between the following directors and employees of RP Data and Cordell in respect of identification and filling of gaps in Cordell Connect:

(A) RP Data employees: [employees]

(B) Cordell employees: [employees].

(C) Directors of RP Data and Cordell: [employees].

 

43(i)

From February 2018, RP Data created a process whereby employees of RP Data and Cordell could request Comparative Documents to be generated by employees of RP Data for presentation to customers or prospective customers of BCI Media Group.

Particulars

As to paragraph 43(i), the Respondents:

(a) admit the allegation insofar as it concerns RP Data; and

(b) otherwise deny the allegation.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

i. The process is outlined in documents produced by RP Data titled ““CBS data superiority sheet process.docx” and "Cordell Data Superiority report request HOW TO.docx”.

ii. The Comparative Documents created by this process was referred to within RP Data as “Cordell Connect Data Superiority Packs”.

 

43(ii)

From about February 2018, employees of RP Data and Cordell requested and were provided Comparative Documents pursuant to the process pleaded in paragraph 43(i) above.

Particulars

i. The employees who submitted the requests as presently known to BCI Media Group are:

(A) [employee] on 16 May 2018;

(B) [employee] on 21 May 2017, 31 May 2018;

(C) [employee] on 25 May 2018 and 7 November 2018;

(D) [employee] on 29 May 2018 and 4 June 2018;

(E) [employee] on 26 July 2018;

(F) [employee] on 21 August 2018 and 12 to 22 December 2018.

As to paragraph 43(ii), the Respondents:

(a) admit the allegation insofar as it concerns RP Data; and

(b) otherwise deny the allegation.

43(iii)

From April 2018, employees of RP Data and Cordell were provided Comparative Documents and directed by RP Data to present them to customers and prospective customers of BCI Media Group.

Particulars

As to paragraph 43(iii), the Respondents:

(a) admit that Comparative Documents, being documents of the type pleaded in paragraph 42C(a) above, were to provided to, or circulated between, employees of RP Data; and

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

i. Employees of RP Data, [employees], circulated the Comparative Documents on a monthly basis and instructed the following employees in the sales team presently known to BCI Media Group to use the Comparative Documents in discussions with customers and prospective customers of BCI Media Group:

(A) employees of RP Data: [employees].

ii. On or around 30 May 2018, an employee of RP Data, Sandy Forster, instructed the following employees in the sales team by email dated 30 May 2018 to use the Comparative Documents in discussions with customers and prospective customers of BCI Media Group:

(A) employees of RP Data: [employee]; and

(B) employees of Cordell: [employees].

iii. Between April 2018 and August 2018, emails were sent from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL-APAC Sales” and “DL- Exec 2017 Corelogic International” instructing them on how to present Comparative Documents to customers and prospective customers of BCI Media Group.

iv. The email lists comprised of the following employees and officers of RP Data and Cordell in the relevant period as far as these are known to BCI Media Group:

(A) employees of RP Data: [employees];

(b) otherwise deny the allegations:

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(B) employees of Cordell: [employees]; and

(C) officers of RP Data and Cordell: [employees].

Particulars

i. The emails referred to in (iii) above presently known to BCI Media Group are as follows:

(A) Email from [employee] to [employees] dated 4 April 2018.

(B) Email from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL- APAC Sales”, “DL-MarketingGroup”, “DL-Sales Ops Team”, “DLProduct- DL”, “DL-Solutions” and “Legals Australia” dated 16 May 2018.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(C) Email from [employee] to employees and officers of RP Data and Cordell on the email list “DL-Exec 2017 Corelogic International” dated 16 May 2018.

(D) Email from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL- APAC Sales” and “DL-Exec 2017 Corelogic International” and Sandy Forster dated 23 May 2018.

(E) Email from the email account sales.operations@corelogic.com.au to employees and officers of RP Data and Cordell on the email lists titled “DL- APAC Sales”, “DL-MarketingGroup”, “Corporate Systems”, “DLSales Directors”, “DL-Sales Management Group”, “Staff Support” and “Sales Support” and [employee] dated 13 August 2018.

 

43(iv)

From at least 11 May 2017, employees of RP Data and Cordell:

(a) presented the information in the Comparative Documents; and

(b) sent emails containing information from the Comparative Documents, to customers or prospective customers of BCI Media Group.

Particulars

i. The conduct can be inferred from what is pleaded in paragraphs 42(i) to 42(iii) above.

ii. Employees who issued requests for Comparative Documents known to BCI Media Group are particularised in paragraph 43(ii) above.

iii. The employee of RP Data presently known to BCI Media Group who sent the emails referred to in (b) was [employee].

As to paragraph 43(iv), the Respondents:

(a) do not know, and cannot admit paragraph (a);

(b) admit paragraph (b) insofar as it concerns the emails expressly particularised in that paragraph; and

(c) otherwise deny paragraph (b).

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

iv. The employee of Cordell presently known to BCI Media Group who sent the emails referred to in (b) was [employee].

v. Customers or prospective customers of BCI Media Group who received the emails referred to in (b) as presently known to BCI Media Group are listed at paragraph A2 of the Applicant’s Confidential Particulars.

vi. The emails referred to in (b) as presently known to BCI Media Group were sent by the following employees of RP Data and Cordell on the following dates:

A. [employee] on 11 May 2017;

B. [employee] on 13 July 2017.

C. [employee] on 13 October 2017;

D. [employee] on 16 November 2017;

E. [employee] on 6 December 2017;

F. [employee] on 18 December 2017;

G. [employee] on 22 February 2018;

H. [employee] on 29 May 2018;

I. [employee] on 16 July 2019;

J. [employee] on 23 July 2019;

K. [employee] on 27 September 2019;

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

L. [employee] on 8 October 2019;

M. [employee] on 22 October 2019;

N. [employee] on 23 October 2019;

O. [employee] on 24 and 29 October 2019;

P. [employee] on 31 October 2019;

Q. [employee] on 31 October 2019;

R. [employee] on 7 November 2019;

S. [employee] on 19 and 26 November 2019;

T. [employee] on 21 November 2019;

U. [employee] on 28 November 2019; and

V. [employee] on 10 February 2020.

vii. [employee] sent the emails referred to above using an email address with the suffix “@cordell.com.au” and a sign off “Cordell”.

 

43(v)

By presenting the information in the Comparative Documents to customers and prospective customers, RP Data and Cordell induced customers and prospective customers of BCI Media Group to believe that the information in Cordell Connect was more comprehensive and accurate than the information in LeadManager.

Particulars

The Respondents do not know and cannot admit paragraph 43(v).

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

i. Customers and prospective customers of BCI Media Group presently known to BCI Media Group who were induced are set out in Confidential Annexures A, B and C.

 

43(vi)

The conduct pleaded in paragraph 43(v) above caused:

(a) customers of BCI Media Group to:

i. cease subscribing to LeadManager;

ii. require BCI Media Group to apply a discount to their subscription fee; and

(b) prospective customers of BCI Media Group to not subscribe to LeadManager.

Particulars

i. The customers of BCI Media Group who ceased subscribing to LeadManager as presently known to BCI Media Group are set out in Confidential Annexure A.

ii. The customers of BCI Media Group where a discount was applied to their subscription as presently known to BCI Media Group are set out in Confidential Annexure B.

iii. The prospective customers of BCI Media Group who did not subscribe to LeadManager as presently known to BCI Media Group are set out in Confidential Annexure C.

The Respondents do not know and cannot admit paragraph 43(vi).

43(vii)

The conduct pleaded in paragraph 43(v) above caused:

(a) customers; and

The Respondents do not know and cannot admit paragraph 43(vii).

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(b) prospective customers,

to enter into subscription agreements with RP Data.

Particulars

i. It is to be inferred from the conduct pleaded in paragraphs 43(iv) to 43(vi) that some customers listed in Confidential Annexures A and C entered into subscription agreements with RP Data.

ii. The customers and prospective customers who entered into subscription agreements with RP Data is solely within the knowledge of RP Data and will be provided after evidence and discovery.

 

43A

The knowledge of RP Data in respect of the activities of RP Data and Cordell pleaded in paragraphs 24 to 43(vii) above:

(a) is to be inferred from the fact the acts were carried out by the employees and directors of RP Data as pleaded and particularised in paragraphs 24 to 43(vii) above; and further or alternatively,

(b) arises from:

i. emails, reports and presentations received and sent by directors of RP Data, being [employees], which gave them knowledge of the activities; and

ii. the communication of approval to RP Data, orally and in writing, to engage in the activities, by directors of RP Data, [employees].

Particulars

As to paragraph 43A, the Respondents:

(a) admit the allegation insofar as it is alleged that RP Data had knowledge of the activities admitted or pleaded in paragraphs 24 to 43(vii) above; and

(b) otherwise deny the allegation they say that Cordell did not engage in any of the alleged activities.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

i. In respect of the knowledge referred to in (b)(i) above, as presently known to BCI Media Group:

(A) [employees] (individually and as part of the “DL-Exec- 2017 CoreLogic International” email list) received the Comparative Documents particularised in paragraph 42C above and the emails particularised in paragraph 43(iii) above, in relation to the creation and use of Comparative Documents by RP Data and Cordell.

(B) On or around 12 March 2019, [employee] was provided a report in relation to the Robotics Program (by which RP Data was accessing and copying information from LeadManager using subscriptions obtained from third parties (the Forum Group, SkillTech and Gingold) without the knowledge or consent of BCI Media Group), as recorded in an email from [employees] dated 12 March 2019.

(C) On or around 20 August 2019, [employee] received an email from [employee], in relation to the costs of the procurement and reimbursement of Gingold for its subscription to LeadManager (by which, RP Data was accessing and copying information from LeadManager without the knowledge or consent of BCI Media Group and creating Comparative Documents) dated 20 August 2019.

(D) On or around 3 April 2020, [employee] received an instant message from [employee] which referred to obtaining a subscription to LeadManager from a third party without the knowledge or consent of BCI Media Group, as recorded in an email from [employee] to [employee] dated 3 April 2020.

(E) On or around 31 August 2018, [employee] received a report from employee] in relation to the creation and use of Comparative Documents by RP Data and Cordell, which took the form of an email from [employee] to [employee] dated 31 August 2018.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(F) On or around 28 August 2017, [employee] received and email from [employee] in relation to the reimbursement of SkillTech for its subscription to LeadManager dated 28 August 2018.

(G) On or around 19 September 2018, [employee] received an email from [employee] in relation to the procurement and reimbursement of Gingold for its subscription to LeadManager dated 19 September 2018.

(H) On or around 5 October 2018, [employee] received an email from [employee] in relation to the engagement of Artis Group to develop Robotics Programs for RP Data, dated 5 October 2019.

(I) On or around 5 June 2018, [employee] received a report in relation to the Robotics Program (by which RP Data was accessing and copying information from LeadManager using subscriptions obtained from third parties (the Forum Group, SkillTech and Gingold) without the knowledge or consent of BCI Media Group), by email from [employee] to [employees] dated 5 June 2018.

(J) On or around 5 June 2018, [employee] received a presentation in relation to the Robotics Program (by which RP Data was accessing and copying information from LeadManager using subscriptions obtained from third parties (the Forum Group, SkillTech and Gingold) without the knowledge or consent of BCI Media Group), which is to be inferred from an email [employees] dated 5 June 2018.

(K) On or around 17 August 2018, [employee] received a presentation in relation to the Robotics Program (by which RP Data was accessing and copying information from LeadManager using subscriptions obtained from third parties (the Forum Group, SkillTech and Gingold) without the knowledge or consent of BCI Media Group), which is to be inferred from an email [employee]

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

to [employees] dated 8 August 2018.

ii. In respect of the approval referred to in (b)(ii) above, as presently known to BCI Media Group:

(A) On or around 15 March 2018, [employee] gave oral approval to [employees] in relation to the creation and use of the Comparative Documents by RP Data and Cordell, as recorded in an email from Craig Mackenzie to employees and officers of RP Data and Cordell on the email list titled “DL-Exec 2017 CoreLogic International” dated 15 March 2018.

(B) On or around 20 August 2019, [employee] gave oral approval to [employee] for the procurement and reimbursement of Gingold for its subscription to LeadManager, which is to be inferred from an email from [employee] to [employee] dated 20 August 2019.

(C) On or around 28 March 2019, [employee] gave written approval to [employee] and [employee] for the invoices issued by Telus International for the conduct referred to in paragraph 41B, 41C and 42A above, as recorded in an email from [employee] to [employee] dated 28 March 2019.

(D) On or around 28 August 2017, [employee] gave oral approval to [employees] for the reimbursement of SkillTech for its subscription to LeadManager, which is to be inferred from an email from [employee] to “Accounts Payable”, [employees] dated 28 August 2018.

(E) On or around 24 September 2018, [employee] gave written approval to [employee] and [employee] for the reimbursement of Gingold for its subscription to LeadManager, as recorded in an email from [employee] to [employee] and [employee] dated 24 September 2018.

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(F) On or around 5 October 2018, [employee] gave oral approval to [employee] for the engagement of Artis Group to develop Robotics Programs for RP Data, which is to be inferred from an email from [employee] to [employee] dated 5 October 2019.

(G) On or around 19 October 2018, [employee] gave written approval to [employee] and [employee] for invoices issued by Telus International for the conduct referred to in paragraphs 41B, 41C and 42A above, as recorded in an email from [employee] to [employee] and [employee] dated 19 October 2018.

(H) On or around 19 November 2018, [employee] gave written approval to [employee] and [employee] for invoices issued by Telus International for the conduct referred to in paragraphs 41B, 41C and 42A above, as recorded in an email from [employee] to [employee] and [employee] dated 19 November 2018.

 

CoreLogic Australia and Cordell knew and were involved in the conduct of RP Data

43B

CoreLogic Australia had knowledge of, approved and encouraged RP Data in the activities pleaded in paragraphs 24 to 43(vii) above by reason of:

(a) emails, reports and presentations received by directors of CoreLogic Australia, being [employee], [employee], [employee] and [employee], which gave them knowledge of the activities:

(b) the communication of approval to RP Data, orally and in writing, to engage in the activities, by directors of CoreLogic Australia, being [employee], [employee] and [employees];

(c) reports and commercial justifications of the activities provided by a director of CoreLogic Australia, being [employee], which encouraged RP Data to engage in those actions; and

The Respondents deny paragraph 43B.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

(d) the emails and documents created by RP Data, and the Comparison Documents, in the course of its activities pleaded in paragraphs 24 to 43(vii) above which were stored in an information management system shared by RP Data, CoreLogic Australia and Cordell which was accessible to and used by directors common to them and employees whom they jointly controlled.

Particulars

i. In respect of the knowledge referred to in (a) above, BCI Media Group refers to and repeats the particulars of paragraph 43A(b)(i).

ii. In respect of the approval referred to in (b) above, BCI Media Group refers to and repeats the particulars of paragraph 43A(b)(ii),

iii. In respect of the encouragement referred to in (c) above, as presently known to BCI Media Group:

A. On or around 31 August 2018, [employee] sent [employee] a report in relation to the effectiveness and benefits of the process for the creation and use of Comparative Documents by RP Data, by email from [employee] to [employee] dated 31 August 2018.

B. On or around 8 March 2020, [employee] engaged in discussions with RP Data’s “PMO team” in relation to the financial benefits through costs savings of the Robotics Program (by which RP Data was accessing and copying information from LeadManager using subscriptions obtained from third parties (the Forum Group, SkillTech and Gingold), as recorded in an email from [employee] to [employee] dated 8 March 2020.

iv. In respect of the emails and documents referred to in (d), BCI Media Group refers to and repeats the particulars to paragraph 6(f) above and relies on

 

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

all of the specific emails and documents produced by RP Data and which are particularised in this pleading.

 

43C

The knowledge of Cordell in the activities of RP Data and Cordell pleaded in paragraphs 24 to 43(vii):

(a) is to be inferred from the fact the acts were carried out by the employees of Cordell ([employee] and [employee]) as pleaded and particularised in paragraphs 42C to 43(vii) above; and further or alternatively,

(b) emails, reports and presentations received by:

i. directors of Cordell, being [employee], [employee], [employee] and [employee]; and

ii. employees of Cordell, [employee] and [employee], which gave them knowledge of the activities;

(c) is to be inferred from the fact that all of the emails and documents created by RP Data, and the Comparison Documents, in the course of its activities pleaded in paragraphs 24 to 43(vii) above which were stored in an information management system shared by RP Data, CoreLogic Australia and Cordell which was accessible to and used by directors common to them and employees whom they jointly controlled.

Particulars

i. In respect of the knowledge referred to in (b)(i) above, insofar as it relates to the directors of Cordell, BCI Media Group refers to and repeats the particulars to paragraph 43A(a) above.

The Respondents deny paragraph 43C.

Para

BCI Media’s Amended Statement of Claim dated 27 February 2024, filed 29 February 2024

CoreLogic’s Defence 22 December 2023

 

ii. In respect of the knowledge referred to in (b)(ii) above, insofar as it relates to the employees of Cordell, as presently known to BCI Media Group:

A. [employee] (individually and as part of the “DL-APAC Sales” email list) received: emails containing copied information from LeadManager particularised in paragraph 42 above; the Comparative Documents particularised in paragraph 42C above; and emails containing reports in relation to the creation and use of Comparative Documents particularised in paragraph 43(iii) above.

B. [employee] (individually and as part of the “DL-APAC Sales” email list) received by email to an address with the suffix “@cordell.com.au”: emails containing copied information from LeadManager particularised in paragraph 42 above; the Comparative Documents particularised in paragraph 42C above; and emails containing reports in relation to the creation and use of Comparative Documents particularised in paragraph 43(iii) above.

iii. In respect of the emails and documents referred to in (d), BCI Media Group refers to and repeats the particulars to paragraph 43B(d) above.