Bilal v Ampol Australia Petroleum Pty Ltd (Discovery) [2026] FCA 591

Bilal v Ampol Australia Petroleum Pty Ltd (Discovery) [2026] FCA 591 is a Federal Court interlocutory decision about discovery in an employment and workers compensation related dispute. The court was not deciding whether Ampol had contravened the Fair Work Act. It was deciding whether Ampol had failed to comply with earlier discovery orders and whether the court should order fresh discovery and impose procedural consequences.

The application was dismissed. The orders show that the court did not grant declarations of non-compliance, did not order the broad fresh discovery sought, and did not stop Ampol from relying on documents or defence contentions in the way the applicant requested. At the same time, the court still made targeted case-management directions about an unredacted Excel schedule, reply evidence timing and trial tender dates.

The commercial story starts with a workers compensation claim. Mr Bilal had made a workers compensation claim against Ampol, and the judgment says that claim was apparently being managed by EML NSW Limited. The present Federal Court proceeding focused on a letter dated 11 November 2024 that appears to have been sent by EML on Ampol's behalf. The letter informed Mr Bilal that his weekly compensation payments would be suspended.

Mr Bilal alleged that the letter contained false or misleading representations about his workplace rights, and that those representations were made knowingly or recklessly in contravention of section 345 of the Fair Work Act 2009 (Cth). The court summarised three pleaded allegations. First, that the suspension of weekly payments on the basis of an alleged failure to attend a medical examination was false or misleading. Second, that the statement that weekly payments were being suspended was false or misleading because he was not actually receiving weekly payments at the time. Third, that the representation that the suspension was based on an independent medical examination said to have been made in accordance with the Workers Compensation Guidelines was also false or misleading.

Those substantive allegations were not decided in this judgment. They were listed for hearing on liability on 22 and 23 July 2026. Instead, the immediate dispute was about documents. Earlier in the case, Ampol had consented to give discovery by categories. On 27 November 2025, the court made discovery orders reflecting that position.

After the orders were made, Ampol searched for documents relating to Mr Bilal's workers compensation claim and also searched across its Microsoft 365 environment, including email accounts, shared drives and other document repositories, using a date range from 2 November 2023 to 17 December 2025. Ampol also asked EML's solicitors whether EML held documents within the discovery categories and whether EML would provide copies to Ampol so they could be discovered. EML's solicitors responded that EML was not willing to release documents to Ampol.

On 23 December 2025, Ampol filed and served its first list of documents and a verifying affidavit, and produced 83 documents. The judgment records that the documents were produced in native format with metadata preserved, except where redactions to privileged information required conversion to PDF. Mr Bilal then wrote to Ampol raising complaints and requests about the adequacy of discovery.

Ampol responded on 7 January 2026, addressing multiple issues, confirming that it would comply with its ongoing discovery obligation under the Federal Court Rules, and indicating that a new discovery list would be prepared to address some of the complaints. Further correspondence followed. Around 15 January 2026, Ampol became aware that additional potentially responsive documents might be stored in a separate database called SolvInjury. It then carried out further searches. On 23 January 2026, Ampol provided a more detailed updated discovery list identifying each discovery category, the number of documents within each category, reasons for redactions, and the categories into which privileged documents fell. On 12 February 2026, Ampol served a supplementary list and produced another 166 documents located on the SolvInjury database.

Despite those steps, Mr Bilal pressed an interlocutory application seeking declarations that Ampol had failed to comply with the discovery orders, an order for fresh discovery verified in accordance with the Rules, an order preventing Ampol from relying at trial on documents not discovered in accordance with the proposed new order, and an order preventing Ampol from relying on certain defence contentions about EML being its insurer.

The legal issue was not whether the suspension letter was lawful. The issue was whether Ampol had complied with the discovery orders made on 27 November 2025 and, if not, what the court should do about it. The catchwords and introductory parts of the reasons show that the dispute covered several procedural points at once.

Mr Bilal argued that the court had ordered non-standard discovery by categories and that this required more than ordinary relevance-based production. He contended, in substance, that Ampol had to discover all documents answering the categories, not merely conduct reasonable searches. He also challenged the adequacy of Ampol's searches, including the way Ampol searched its systems and the steps it took in relation to documents held by EML. He said Ampol had not properly complied with orders requiring discovery in native format with metadata preserved and had not properly complied with an order concerning documents recording or evidencing the appointment of EML as insurer and related workers compensation policy documents.

The catchwords show the court also had to consider the overarching purpose in section 37M of the Federal Court of Australia Act 1976 (Cth), whether compliance with the Technology and the Court Practice Note was required, whether any particular form of searches was required, the effect of the deponent of the discovery affidavit not being an officer of the respondent, the form of the discovery list, redaction of a discovered document containing sensitive employee information, and a claim of legal professional privilege.

For a business reader, that means this was a broad attack on the mechanics of discovery. It was not just a complaint that some documents were missing. It was a challenge to the search process, the listing process, the verification process, the production format, the handling of sensitive information, and the treatment of documents said to be within the company's control through another entity.

The available reasons do not include the full detailed analysis of each point. What is clear is that the court had to decide whether the complaints established real non-compliance serious enough to justify declarations, fresh discovery and trial-related sanctions, or whether the better course was to treat the matter as one of practical case management in light of the searches already undertaken and the supplementary discovery already given.

The court dismissed the interlocutory application. That means Mr Bilal did not obtain declarations that Ampol had failed to comply with the discovery orders, did not obtain the broad fresh discovery order he sought, and did not obtain the requested orders preventing Ampol from relying on undiscovered documents or certain defence contentions.

The costs of the interlocutory application were reserved. So the court did not finally determine who should pay the costs of that application at that point.

The court also made further practical directions. By 20 May 2026, the parties were required to confer and provide proposed consent orders about three matters: discovery by Ampol of an unredacted version of an Excel schedule containing details of the applicant's alleged injuries, an appropriate extension to the time for the applicant to file reply evidence, and the date by which the parties had to file any documents they intended to tender at trial, no later than 1 July 2026.

Those orders matter because they show the court's approach was not simply to reject the application and move on. The court still dealt with specific document and timetable issues in a targeted way. That is often how discovery disputes are managed in practice. A court may refuse broad allegations of non-compliance or punitive sanctions, while still making narrower directions to deal with particular documents or procedural fairness concerns.

Based on the parts of the reasons that are available, the decision points to a practical approach to compliance. Ampol had conducted searches, produced documents in native format with metadata preserved except where privilege redactions required PDF conversion, responded to complaints, identified another database, and then supplemented discovery with a substantial further production. The dismissal of the application suggests that the court was not persuaded that the criticisms justified the more drastic relief sought.

Care is still needed in drawing narrow doctrinal conclusions. The published reasons available here are truncated before the full reasoning is reproduced. So while the result supports a practical compliance reading, any precise proposition about the exact legal standard for category discovery, the role of the technology practice note, or the treatment of control over third-party documents should be checked against the full reasons before being relied on in advice or litigation strategy.

For businesses, the main message is that discovery is judged by what you actually do. If your company is in litigation, you need a defensible process for identifying where relevant documents may sit, searching those systems, preserving the right file formats where required, and explaining any redactions or privilege claims. Courts are unlikely to be impressed by vague assurances that someone looked for documents. They want a process that can be described and, if necessary, verified.

This case also shows that practical compliance and ongoing efforts matter. Ampol did not stop with its first production. After complaints were raised, it responded, said it would continue to comply with its ongoing discovery obligations, identified another possible source of documents in the SolvInjury database, searched it, and then served supplementary discovery. The result suggests that a court may be more interested in whether a party is genuinely working to comply than in whether the first production was flawless.

That does not mean businesses can be casual. Discovery disputes can become expensive and distracting very quickly. Here, the argument expanded into questions about search methodology, metadata, the form of the list, the person swearing the affidavit, privilege, redactions and third-party records. If your records are spread across email, shared drives, HR systems, claims platforms and external providers, a court case can expose every weakness in your document management.

The involvement of EML is especially important for businesses that outsource functions. The judgment records that Ampol asked EML's solicitors whether EML held documents within the discovery categories and whether copies would be provided, and that EML was not willing to release documents to Ampol. That is a warning sign for any business using insurers, claims managers, payroll providers, HR consultants or software platforms. Before litigation escalates, you should understand what records they hold, whether those records are within your control for discovery purposes, and what contractual or practical rights of access you have.

The case also highlights the overlap between discovery and confidentiality. The catchwords refer to redaction of a discovered document containing sensitive employee information and to legal professional privilege. Businesses should not assume that every responsive document can simply be handed over in full. But they should also not assume that redactions or privilege claims will be accepted without scrutiny. The safer course is to document the basis for each redaction or privilege claim and to be consistent about production format.

Finally, the reference to the overarching purpose in section 37M is a reminder that Federal Court procedure is meant to facilitate the just resolution of disputes as quickly, inexpensively and efficiently as possible. In practical terms, that means discovery should be proportionate, organised and transparent. Courts may resist turning discovery into a satellite war if a party has taken real steps to comply and continues to correct the record. But businesses that approach discovery casually risk extra cost, delay and loss of credibility.

The judgment was delivered on 13 May 2026 by Shariff J in the Federal Court of Australia, New South Wales Registry, in the Employment and Industrial Relations National Practice Area. The applicant appeared in person. Ampol was represented by counsel and solicitors.

The underlying Fair Work claims were listed for hearing on liability on 22 and 23 July 2026. This decision did not resolve those claims. It resolved only the interlocutory application about discovery.

The court's orders required the parties to confer and provide proposed consent orders by 20 May 2026 about an unredacted Excel schedule, an extension for reply evidence, and the timetable for filing documents intended to be tendered at trial.

This page is based on the Federal Court judgment in Bilal v Ampol Australia Petroleum Pty Ltd (Discovery) [2026] FCA 591. The published text clearly states the orders, catchwords, procedural setting and key factual background to the discovery dispute.

The published reasons available here are truncated before the full detailed reasoning appears. Because of that, this explainer focuses on the procedural story, the issues clearly identified by the court, the orders made, and the practical reading for businesses. Any more exact proposition about the court's doctrinal reasoning on category discovery, search standards, third-party control, or the technology practice note should be checked against the complete reasons.