Selected cases

Federal Court of Australia · [2025] FCA 616

Watchlist

BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd (Review of Registrar’s Decision)

BCI Media Group Pty Ltd v CoreLogic Australia Pty Ltd (Review of Registrar's Decision) [2025] FCA 616 is a Federal Court procedural decision in a larger dispute about alleged access to and use of competitor data, comparative documents and customer loss. The immediate question was whether BCI had to give more particulars of allegations that comparative documents were presented to customers and caused them to leave, seek discounts or not subscribe. Needham J dismissed the review application, found no unpleaded inferential case on the material before the court, and ordered the respondents to pay costs.

Federal Court of AustraliaNot recorded

These are plain-English explainers, not legal advice. They are a good starting point, but check the linked official source before you rely on a specific section, and get advice for your situation.

Talk to a lawyer

Decision snapshot

Facts

The dispute

BCI Media Group and the CoreLogic parties were competitors in the market for subscription products giving customers access to information about building projects across Australia. BCI’s product was LeadManager. The competing product on the CoreLogic side was Cordell Connect. In the broader proceeding, BCI alleges that between 2016 and 2019 the CoreLogic parties surreptitiously accessed LeadManager through subscriptions obtained in third-party names, then used those logins to access and scrape content from LeadManager. BCI alleges that the scraped material was used to create comparative documents, improve Cordell Connect and procure customers. The pleaded causes of action in the main case include breach of contract, copyright infringement, breach of confidence and misleading or deceptive conduct under section 18 of the Australian Consumer Law. The decision at [2025] FCA 616 was not the final trial. It was a review of a registrar’s interlocutory decision. The CoreLogic parties had asked for further and better particulars of parts of BCI’s amended statement of claim, especially paragraphs 43(v) and 43(vi). Those paragraphs alleged, in substance, that by presenting information in comparative documents to customers and prospective customers, RP Data and Cordell induced them to believe Cordell Connect was more comprehensive and accurate than LeadManager, and that this caused customers to stop subscribing, require discounts, or not subscribe. BCI had confidential annexures listing customers said to fall into those categories. The registrar had already ordered BCI to add dates to those annexures, and that had been done. The remaining fight was about whether BCI also had to identify, for each customer or prospect, the date and method of inducement and the facts and matters relied on to support the alleged inference that comparative documents were presented and caused the pleaded outcomes. The CoreLogic parties argued BCI was really running an inferential case without properly pleading the foundational facts and inferences. They pointed to affidavit material, discovery and the absence of documents directly recording presentations to the named customers. BCI resisted that characterisation. It argued the relevant facts were already pleaded, especially when paragraph 43 was read with earlier allegations and admissions in the defence, and that the respondents were seeking evidence rather than proper particulars. Needham J heard the review de novo and dismissed it, with costs against the respondents.

Issue

The legal question

The main issue was whether paragraphs 43(v) and 43(vi) of BCI's amended statement of claim failed to give the respondents fair notice because they allegedly depended on an unpleaded inferential case. The respondents argued BCI needed to identify the foundational facts and inferences said to connect the presentation of comparative documents with customer belief and resulting customer loss, discounts or non-subscription. The court therefore had to decide whether further and better particulars were required under rule 16.45 of the Federal Court Rules, or whether the respondents were really seeking evidence rather than proper particulars of the pleaded case.

Outcome

Decision

The Federal Court dismissed the respondents' application to review the registrar's decision. Needham J held that the review was a hearing de novo, but the respondents still bore the onus of showing that the current particulars were inadequate and that they could not conduct their case without further particulars. On the reasons available, the court was not persuaded that BCI was running an unpleaded inferential case in paragraphs 43(v) and 43(vi). The formal orders included dismissal of the review application and an order that the respondents pay BCI's costs of that application. The orders also left open a possible special costs application and raised confidentiality issues about publication of the reasons.

Practical impact

Commercial note

If your business is in a court dispute, this case is a reminder to get the pleading right early. You need to state the material facts clearly enough to give fair notice, but you do not usually have to set out every piece of proof. If you want further particulars from the other side, you need to show more than curiosity or tactical advantage. You need to show the existing pleading is inadequate and that you cannot properly conduct your case without more detail. The decision also shows the value of good records. In a dispute about customer loss, discounts, sales presentations or competitor comparisons, your CRM records, internal emails, sales instructions and access logs may become central. Businesses using comparative sales material or competitor-derived information should get legal advice early, because those practices can lead to claims well beyond simple marketing disputes.

The story

This case sits inside a larger commercial dispute between competing providers of building-project information services. BCI Media Group sold LeadManager. The CoreLogic side sold Cordell Connect. The broader allegations are commercially serious. BCI says the CoreLogic parties accessed LeadManager through subscriptions obtained in third-party names, scraped information from it, used that material to create comparative documents, improved their own product and used the material to win customers.

The causes of action in the main proceeding include breach of contract, copyright infringement, breach of confidence and misleading or deceptive conduct under the Australian Consumer Law. But this judgment did not decide any of those claims. It dealt with a narrower procedural fight about pleadings and particulars before trial.

The immediate issue was paragraph 43 of BCI's amended statement of claim. BCI alleged that information in comparative documents was presented to customers and prospective customers, that this induced them to believe Cordell Connect was more comprehensive and accurate than LeadManager, and that this caused commercial harm to BCI. The alleged harm included customers ceasing subscriptions, requiring discounts, or prospective customers not subscribing at all.

BCI had confidential annexures listing the customers and prospects said to fall into those categories. The CoreLogic parties wanted more detail. They said BCI should identify, customer by customer, the date and method of inducement and the facts and matters relied on to support the alleged inference that comparative documents were presented and caused the pleaded outcomes.

What the parties were fighting about

The respondents relied on rule 16.45 of the Federal Court Rules. That rule allows a party to seek particulars if a pleading does not give fair notice of the case and the party may be prejudiced in conducting its case. But the rule also sets limits. The party seeking particulars must show that the existing particulars are inadequate and that it could not conduct its case without further particulars.

Here, the registrar had already ordered BCI to amend the confidential annexures to provide dates for the alleged conduct. According to the judgment, that had been done. The remaining requests were broader. The respondents wanted the date and method by which each customer was induced to believe the matters pleaded in paragraph 43(v). They also wanted particulars identifying the facts and matters relied on to support an inference that comparative documents were presented to each listed customer or prospect, that those presentations induced the pleaded belief, and that this caused the listed commercial outcomes.

The CoreLogic parties said BCI was really running an inferential case. Their argument was that the pleaded allegations in paragraphs 43(v) and 43(vi) could not stand on their own unless BCI also pleaded the foundational facts and the inferences it wanted the court to draw from those facts. They pointed to affidavit material from BCI's solicitor and to the absence of documents directly recording presentations to the named customers. In substance, they said they were being left in the dark about the real case they had to meet.

BCI's answer was that the respondents were trying to obtain evidence, not proper particulars. BCI said the relevant facts were already pleaded when paragraph 43 was read as a whole and in the context of earlier allegations. It also relied on the respondents' admissions in the defence about some aspects of the creation and use of comparative documents and the use of robotic process automation on LeadManager.

What the court decided

The court dismissed the review application. The formal orders were that the respondents' application to review the registrar's decision be dismissed and that the respondents pay BCI's costs of that application. The orders also allowed BCI to seek any special costs order by a later date and required the parties to notify the court about any confidentiality issues affecting publication of the reasons.

On the substance, the judgment expressly records that no unpleaded inferential case was found. Needham J agreed with the registrar's review of the principles applying to pleadings and particulars and emphasised that the respondents bore the onus of showing inadequacy and practical inability to conduct their case without more detail.

The reasons available show the court closely examining the structure of BCI's pleading, the admissions and non-admissions in the defence, and the respondents' argument that affidavit material and discovery showed BCI must be relying on inference. The respondents pointed in particular to affidavit passages saying BCI would rely on documentary evidence and authorised representations circulated among sales staff as evidence from which an inference would be drawn that the information and representations were deployed when dealing with customers and prospective customers.

BCI's position, as recorded in the reasons, was that the opening words of paragraph 43(v), referring to presenting information in the comparative documents, linked back to earlier pleaded factual allegations about the deployment of that information, much of which was admitted in some form. On the material available, the court was not persuaded that paragraphs 43(v) and 43(vi) amounted to an unpleaded inferential case requiring the further particulars sought.

Quick checklist

0/4

Practical limits of particulars under the Federal Court Rules

This decision is useful because it shows both what particulars can do and what they cannot do. A party can seek particulars where a pleading does not give fair notice and that deficiency would prejudice the conduct of the case. But particulars are not a general right to force the other side to reveal all of its proof, all of its reasoning, or every evidentiary step it may rely on at trial.

The judgment repeatedly returns to the distinction between material facts and evidence. That distinction matters in practice. A claimant must plead enough to identify the case it is making. A defendant is entitled to know the case it has to meet. But the court will not necessarily require a claimant to provide customer-by-customer evidentiary detail if the pleading already gives fair notice of the material allegations and the defendant can still conduct its case.

That is especially important in commercial disputes involving customer behaviour, sales conduct and causation. Businesses often want the other side to identify exactly which communication changed which customer's mind and on what date. Sometimes that level of detail may be necessary. Sometimes it may not. The rule asks a practical question: can the party seeking particulars conduct its case without them? If yes, the court may refuse the request.

The case also shows that a blanket non-admission does not automatically create an entitlement to more particulars. The court looked at the whole pleading and the defence, including admissions to some earlier allegations, rather than treating the non-admissions as decisive.

How businesses should read it

For business owners, the immediate lesson is about litigation discipline. If your business is suing, your pleading needs to set out the material facts clearly and coherently. If your business is defending, a request for particulars should be targeted and tied to actual prejudice, not just a desire to test the other side's evidence early.

The broader commercial story also matters. The underlying allegations concern competitor access to a subscription platform, scraping of information, creation of comparative documents, internal product improvement and customer acquisition. Those are all familiar risk areas for data-driven businesses. If your team accesses competitor systems, uses third-party logins, builds comparison sheets, or trains sales staff to use competitor-derived information, you should assume those practices may later be examined in detail in court.

Good records can make a major difference. In disputes about customer churn, discounts and lost prospects, businesses should be able to identify when a customer left, what discount was offered, what sales material was used, who approved it and what the source of the underlying information was. CRM notes, access logs, internal instructions and approval workflows can become central evidence.

Finally, this judgment should be read cautiously. It is a procedural decision and the available reasons do not run to the end of the judgment. So the safe takeaway is narrow: the court refused to order the extra particulars sought on this application. It did not decide who was right in the broader dispute.

Quick checklist

0/5

Dates and status

The judgment is dated 12 June 2025. It records that the review application was heard on 4 June 2025. It also notes that the matter was due back before the court for case management on 13 June 2025 and that the proceeding was listed for a 16 day hearing in September 2025. The orders further allowed BCI to make any application for a special costs order by 26 June 2025 and required the parties to notify the court by 10:30 am on 13 June 2025 of any confidentiality issues affecting publication of the reasons.

Those dates help explain the short-form nature of the reasons. Needham J said a prompt judgment was necessary given the upcoming case management and hearing timetable. That context reinforces that this was an interlocutory procedural ruling made in the lead-up to trial.

How Sprintlaw can help