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

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.

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.

Needham J identified the review as a hearing de novo. That meant the judge reconsidered the issue afresh rather than simply asking whether the registrar had made an error. Even so, the onus remained on the CoreLogic parties to satisfy rule 16.45(2). They had to show both that the current particulars were inadequate and that they could not conduct their case without further particulars.

The central legal question was whether paragraphs 43(v) and 43(vi) involved an unpleaded inferential case. If they did, the respondents argued BCI should have pleaded the foundational facts and the inferences to be drawn, rather than leaving those matters to emerge later through evidence or submissions.

The judgment sets out the relevant pleading rules. A pleading must identify the issues the party wants the court to resolve and state the material facts necessary to give fair notice of the case, but not the evidence by which those facts will be proved. The court also accepted the standard distinction between pleadings and particulars. Pleadings define the material facts and issues. Particulars help prevent surprise and facilitate the collection of relevant evidence.

The respondents relied on authorities about inferential pleading, including cases saying that if liability depends on an inference, the pleading should identify the facts said to justify that inference and the inference itself. BCI resisted the idea that its case in paragraphs 43(v) and 43(vi) was inferential in that sense. It said those paragraphs referred back to earlier pleaded conduct about the creation, circulation and presentation of comparative documents.

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.

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.

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.

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.