What specific procedural dispute necessitated the involvement of Mr. Sami Caracand in the ongoing litigation between Smartpaper Computer Software and Keross?
The litigation, registered under CFI 012/2010, involves a dispute between the Claimant, Smartpaper Computer Software, and the Defendants, Keross and Farouk Said. While the substantive merits of the underlying claim remain the primary focus of the proceedings, the immediate procedural hurdle addressed in this application concerns the potential liability for costs. The Second Defendant, Farouk Said, initiated Application CFI 012/2010/09 with the specific objective of bringing Mr. Sami Caracand into the fold of the litigation.
The core of this dispute is the Second Defendant's attempt to join Mr. Caracand as a party to the proceedings, not for the purpose of the primary claim, but exclusively for the purpose of costs. This maneuver suggests that the Second Defendant believes Mr. Caracand bears a degree of responsibility or control over the Claimant’s litigation strategy or funding, thereby justifying his inclusion to ensure that any potential costs orders can be effectively enforced against him. The court’s intervention was required to manage the service of this application upon a non-party, ensuring that the principles of natural justice and procedural fairness were upheld before any such joinder could be considered.
How did H.E. Justice Omar Al Muhairi manage the court calendar regarding the pending applications in CFI 012/2010?
The hearing took place before H.E. Justice Omar Al Muhairi in the DIFC Court of First Instance on 17 April 2013. Following the review of the Claimant’s Application Notice CFI 012/2010/08 and the Second Defendant’s Application Notice CFI 012/2010/09, the Court determined that it was not in a position to finalize the matters on that date. Consequently, Justice Al Muhairi exercised his judicial discretion to adjourn the hearing of both applications to 6 May 2013, effectively reserving all costs associated with these applications until that future date.
What arguments did the Second Defendant, Farouk Said, advance regarding the joinder of Mr. Sami Caracand for costs?
Counsel for the Second Defendant, Farouk Said, argued that the inclusion of Mr. Sami Caracand was a necessary procedural step to ensure the integrity of the costs regime within the DIFC Courts. By filing Application CFI 012/2010/09, the Second Defendant sought to establish a legal nexus between Mr. Caracand and the Claimant, Smartpaper Computer Software, sufficient to warrant his joinder as a party for the limited purpose of costs. This argument rests on the premise that the court possesses the inherent power to join parties who may be the "real" litigants or those exerting control over the litigation, thereby preventing the Claimant from potentially shielding itself from adverse costs orders.
Conversely, the Claimant’s counsel participated in the hearing to address the procedural validity of this joinder attempt. While the specific oral submissions are not detailed in the order, the Claimant’s presence indicates a contest regarding the threshold requirements for joining a non-party to existing proceedings. The court’s decision to grant permission for service suggests that the Second Defendant met the initial evidentiary burden required to justify the court’s oversight of this joinder application, moving the matter toward a substantive hearing on the merits of the joinder itself.
What was the precise doctrinal issue regarding the service of process on a non-party that the Court had to resolve?
The primary legal question before the Court was whether it could, under the Rules of the DIFC Courts (RDC), authorize alternative service of an application for joinder upon a non-party who is not currently within the jurisdiction of the court or who may be difficult to serve through conventional means. The court had to determine if the proposed methods of service—specifically at the offices of the Claimant and via designated email addresses—satisfied the requirements of procedural fairness and effective notice. The doctrinal issue centers on the court's power to facilitate the joinder of a third party for costs under the RDC, ensuring that the individual sought to be joined is properly notified of the application and given a fair opportunity to respond before the court makes a determination on his liability.
How did Justice Al Muhairi apply the RDC 9.31 test to authorize the service of Application CFI 012/2010/9?
Justice Al Muhairi utilized the discretionary powers granted under the Rules of the DIFC Courts to ensure that the Second Defendant could effectively serve the application on Mr. Sami Caracand. By invoking RDC 9.31, the Court provided a clear, court-sanctioned pathway for service, bypassing potential obstacles that might arise from traditional service methods. The reasoning focused on the necessity of ensuring that Mr. Caracand was fully apprised of the application, thereby satisfying the requirements of due process.
The Court’s reasoning is explicitly captured in the following directive:
The Second Defendant shall have permission under RDC 9.31 to serve the Application CFI 012/2010/9 on Mr Sami Caracand: a. at the offices of Smartpaper Computer Software LLC, and b. at Mr. Sami Caracand's email addresses,( scaracand@smartpaperbpm.com ) ( sami@cloudconceptgroup.com ).
By specifying the exact email addresses and the physical location (the Claimant’s offices), the Court removed ambiguity, ensuring that the service would be deemed valid upon the completion of the specified electronic transmission. This approach demonstrates a pragmatic application of the RDC to prevent procedural delays in complex multi-party litigation.
Which specific provisions of the Rules of the DIFC Courts (RDC) were essential to the Court’s order?
The Court relied heavily on RDC 9.31, which governs the court's power to permit service by alternative means. This rule is the cornerstone of the order, as it allows the Court to authorize service in a manner that is not strictly prescribed by the standard rules of service, provided the court is satisfied that the method is likely to bring the document to the attention of the person to be served. By utilizing this rule, Justice Al Muhairi ensured that the Second Defendant’s application for joinder would not be frustrated by technical service issues.
How did the Court structure the timeline for the response to the joinder application?
The Court established a rigid procedural timetable to ensure that the matter could be resolved at the adjourned hearing on 6 May 2013. The order specified that service would be deemed effective on the same business day if sent before 4:00 PM, or the following business day if sent thereafter. Furthermore, the Court set a deadline of 24 April 2013 for Mr. Caracand to file and serve his response, and a deadline of 1 May 2013 for the Second Defendant to file a reply. This structured approach ensures that the Court is fully briefed on the arguments for and against the joinder before the hearing, minimizing the risk of further adjournments.
What was the final disposition of the application hearing held on 17 April 2013?
The Court adjourned the hearing of both Application CFI 012/2010/08 and Application CFI 012/2010/09 to 6 May 2013. No final decision was reached on the merits of the joinder or the underlying applications. The Court also reserved all costs associated with these applications until the hearing on 6 May 2013. This disposition reflects the Court's commitment to ensuring that all parties, including the potential third party Mr. Caracand, have the opportunity to present their positions before a final order is issued.
What does this order imply for future litigants seeking to join third parties for costs in the DIFC?
This order serves as a practical guide for litigants who intend to pursue non-parties for costs. It highlights the importance of utilizing RDC 9.31 to secure court permission for alternative service when the standard methods are insufficient or when the individual to be joined is closely linked to the existing Claimant. Litigants must be prepared to provide the court with specific, verifiable contact details for the non-party and must adhere to the strict timelines set by the court to maintain the momentum of the proceedings. The case underscores that the DIFC Court is willing to facilitate the joinder of third parties for costs, provided the procedural requirements are met with precision.
Where can I read the full judgment in Smartpaper Computer Software v Keross [2013] DIFC CFI 012?
The full text of the Application Order can be accessed via the official DIFC Courts website at: https://www.difccourts.ae/rules-decisions/judgments-orders/court-first-instance/cfi-0122010-application-order. A copy is also available via the CDN link: https://littdb.sfo2.cdn.digitaloceanspaces.com/litt/AE/DIFC/judgments/court-first-instance/DIFC_CFI-012-2010_20130417.txt.
Cases referred to in this judgment:
| Case | Citation | How used |
|---|---|---|
| N/A | N/A | No cases cited in this specific application order. |
Legislation referenced:
- Rules of the DIFC Courts (RDC) 9.31