Justice Lord Angus Glennie grants the Claimant’s application to formalize the Defendant’s name change and mandates immediate access to critical ePMS software to facilitate expert reporting.
Why did Muzoon Holding LLCB seek to amend the Defendant’s name in CFI 020/2023 under RDC r.18.2?
The dispute centers on the operational relationship between Muzoon Holding LLCB and the entity previously known as Elinx Infotech LLC. The Claimant initiated proceedings to address issues arising from a Cooperation Agreement dated 30 June 2024, specifically concerning access to the ePMS software. As the corporate identity of the respondent evolved during the litigation, the Claimant found it necessary to ensure that all court records, including those in the associated enforcement proceedings ENF-139-2024 and ENF-304-2023, accurately reflected the respondent’s current legal status.
The application was grounded in the necessity for procedural clarity and the enforcement of obligations under the Cooperation Agreement. By invoking RDC r.18.2, the Claimant sought to ensure that the Defendant, now identified as Belsons Innovations Technologies LLC, remained bound by all past and future statements of case. This amendment was not merely administrative; it was a prerequisite for the Court to issue enforceable orders regarding the software access that the Claimant contends is essential to the underlying merits of the dispute.
Which judge presided over the application for software access in CFI 020/2023?
Justice Lord Angus Glennie presided over this matter in the DIFC Court of First Instance. The order was issued on 16 August 2024, following the Claimant’s application dated 30 July 2024 and the consideration of the witness statement provided by Mr. Amr Bajamal.
What were the specific arguments advanced by Muzoon Holding LLCB regarding the ePMS software access?
The Claimant argued that the Defendant’s failure to provide access to the ePMS software hindered the progression of the case and the ability of experts to perform their duties. Relying on RDC r.4.2(14), the Claimant requested a mandatory order to compel the Defendant to restore the access that was previously established under the Cooperation Agreement. The Claimant maintained that without this access, the expert reporting process—a critical component of the litigation—could not proceed in accordance with the established Case Management Order.
The Defendant, by virtue of the Court’s order, is now required to facilitate this access by 26 August 2024. The Claimant’s position emphasized that the software is the central subject of the proceedings, and continued denial of access constituted a significant procedural obstacle that necessitated judicial intervention to prevent further delays in the expert evidence phase.
What was the precise jurisdictional and procedural question before Justice Lord Angus Glennie regarding the amendment of the Defendant’s name?
The Court was tasked with determining whether it had the authority under the Rules of the DIFC Courts (RDC) to permit a retrospective and prospective amendment of the Defendant’s name across multiple active files, including the primary claim and two associated enforcement actions. The doctrinal issue involved the court’s power to ensure that the correct legal entity is held accountable for obligations arising from a Cooperation Agreement, despite a change in the respondent’s corporate branding or registration status.
Furthermore, the Court had to address the intersection of procedural amendment and the management of expert evidence. The jurisdictional question was whether the Court could condition the revision of the Case Management Order timeline upon the Defendant’s compliance with the software access mandate, thereby linking procedural relief to the substantive performance of the parties.
How did Justice Lord Angus Glennie apply the RDC to resolve the expert report timeline dispute?
Justice Lord Angus Glennie utilized the Court’s case management powers to synchronize the deadlines for expert reports with the restoration of software access. By tying the filing deadlines to the "Grant of Access," the Court ensured that the parties would have the necessary data to finalize their reports. The reasoning followed a logical progression: first, confirming the identity of the Defendant; second, mandating the restoration of the status quo regarding software access; and third, adjusting the procedural calendar to reflect these realities.
The Court’s approach ensures that the expert reporting phase is not prejudiced by the Defendant’s previous non-compliance. The specific directives regarding the timeline are as follows:
The time for the Parties to file and serve any Expert Reports shall be extended to within 14 days of the Grant of Access (the “Deadline to file Expert Reports”).
The time for the Parties to file and serve any Supplemental Expert Reports shall be extended to within 14 days of the Deadline to file Expert Reports.
Which specific RDC rules and statutory provisions were applied in this order?
The Court relied primarily on RDC r.18.2, which governs the amendment of statements of case. This rule provided the legal basis for the Claimant to update the Defendant’s name from Elinx Infotech LLC to Belsons Innovations Technologies LLC across all relevant documentation. Additionally, the Court invoked RDC r.4.2(14), which grants the Court the power to make orders for the management of proceedings, specifically used here to mandate the restoration of access to the ePMS software. These rules collectively provided the procedural framework for the Court to maintain control over the litigation timeline and ensure the accuracy of the court record.
How did the Court utilize the Case Management Order dated 10 May 2024 in its reasoning?
The Court treated the Case Management Order of 10 May 2024 as the baseline for the litigation schedule, which had been disrupted by the software access issues. Rather than setting arbitrary new dates, Justice Lord Angus Glennie ordered that the Registry adjust the existing timeline once the Defendant complies with the software access mandate. This approach preserves the integrity of the original case management plan while providing the necessary flexibility to account for the delay. The Court’s instruction regarding the Registry’s role is clear:
The Registry shall, upon the Defendant’s compliance with paragraph 3 above, revise the timeline set out in the Case Management Order, dated 10 May 2024, accordingly.
What was the final disposition and the specific relief granted to Muzoon Holding LLCB?
The Court granted the Claimant’s application in its entirety. The relief included:
1. Formal permission to amend the Defendant’s name to Belsons Innovations Technologies LLC across all statements of case and associated enforcement files (ENF-139-2024 and ENF-304-2023).
2. A mandatory order requiring the Defendant to provide the Claimant with access to the ePMS software by 4:00 PM on 26 August 2024.
3. An extension of time for the filing and service of Expert Reports and Supplemental Expert Reports, linked to the date of software access.
4. An order that the Defendant pay the Claimant’s costs of the application, to be assessed by the Registrar if the parties fail to reach an agreement.
What are the practical takeaways for practitioners regarding corporate name changes and software access in DIFC litigation?
This case serves as a reminder that practitioners must be proactive in updating the court record when a respondent undergoes a name change, particularly when multiple enforcement actions are running in parallel. The use of RDC r.18.2 to amend multiple files simultaneously is an efficient mechanism to avoid procedural fragmentation. Furthermore, the case demonstrates that the DIFC Court is willing to utilize its case management powers under RDC r.4.2(14) to compel the production of digital evidence or access to software when such access is fundamental to the expert evidence phase. Practitioners should anticipate that the Court will link procedural extensions to the resolution of these types of discovery or access disputes to ensure that expert reports are based on complete information.
Where can I read the full judgment in Muzoon Holding LLCB v Belsons Innovations Technologies LLC [2024] DIFC CFI 020?
The full order can be accessed via the DIFC Courts website: https://www.difccourts.ae/rules-decisions/judgments-orders/court-first-instance/cfi-0202023-muzoon-holding-llcb-v-belsons-innovations-technologies-llc-formerly-known-elinx-infotech-llc
CDN link: https://littdb.sfo2.cdn.digitaloceanspaces.com/litt/AE/DIFC/judgments/court-first-instance/DIFC_CFI-020-2023_20240816.txt
Legislation referenced:
- RDC r.18.2 (Amendment of statement of case)
- RDC r.4.2(14) (Court’s power to make orders for the management of proceedings)