Case Conference — Superior Court: Jurisdiction and Initiating Rule 2.1
The most direct application of Rule 2.1 on jurisdictional grounds within the Divisional Court occurs during case conferences and related case-management processes. A case conference is ordinarily an administrative step used to set timetables, order transcripts, or settle the contents of an appeal record. In some matters it has also become the point at which a single judge initiates a Rule 2.1 inquiry into whether a proceeding is frivolous, vexatious, or an abuse of process, including where the concern is lack of jurisdiction or prematurity.
The decision in Montford v. Canadian College of Naturopathic Medicine et al., 2026 ONSC 4273, records one instance of this sequence. The reasons state that the Rule 2.1 notice followed a case conference:
[5] Following a case conference with the parties, I asked the Registrar of the Divisional Court to issue a notice under r. 2.1. I also issued directions advising the parties I was concerned the application in this court was frivolous, vexatious, or an abuse of process for the following reasons:
- Although the Tribunal initially dismissed Mr. Montford’s application, it subsequently allowed a request to reconsider that decision. As a result, the Tribunal process is ongoing.
- Absent exceptional circumstances, the court will not interfere in tribunal processes until they are complete.
- Allegations of bias or other procedural unfairness do not usually on their own demonstrate exceptional circumstances that would justify the court’s intervention.
- If Mr. Montford is unsuccessful when the Tribunal issues its final order, he would have the opportunity to seek judicial review of that decision, including the interim decisions and procedures.
The reasons given for the summary dismissal—that the tribunal process was ongoing and that exceptional circumstances justifying intervention were not shown—address prematurity and the exhaustion of administrative remedies. Prematurity is ordinarily raised by a formal motion to quash. In Montford, the case-management process led directly to a Rule 2.1 notice rather than a direction that the respondent bring a motion. The result was a summary disposition on jurisdictional grounds without a full motion record or factum from the respondent.
A similar sequence appears in Agha v. Fatima, 2025 ONSC 5675:
[3] During the case management process, the court issued directions raising the concern that the court did not have jurisdiction over the appeal and, therefore, that the appeal was frivolous, vexatious, or an abuse of process of the court. The court asked the Registrar to issue a notice under r. 2.1. The case management directions, which were provided to the parties with the r. 2.1 notice, asked the appellant to address the following concerns in his r. 2.1 submissions:
a. The Divisional Court does not appear to have jurisdiction to hear the appeal.
b. The proposed appellant relies on s. 19(1)(b) of the Courts of Justice Act, R.S.O. 1990, c. C. 43 (CJA). That provision addresses interlocutory orders. This is an appeal from a final order. 2025 ONSC 5675 (CanLII)
c. Paragraph 19(1)(a.1) of the CJA addresses appeals to the Divisional Court from a final order of a judge of the Family Court made only under a provision of an Act or regulation in Ontario. Kraft J. is not a judge of the Family Court. In addition, the order was made pursuant to an application under the Divorce Act and includes relief only available in the context of a divorce proceeding, such as for the equalization of property.
d. Although the proposed appellant cites s. 110 of the CJA, he does so saying that jurisdiction lies in the Divisional Court pursuant to s. 110. He does not seek a transfer to a different court under that provision. Section 110 does not provide a source of jurisdiction to this court.
In both cases the case-management judge identified a jurisdictional concern during an administrative step and converted that concern into a Rule 2.1 inquiry. This shifts the immediate burden onto the appellant to respond to a notice that the proceeding may be an abuse of process, rather than requiring the respondent to bring and support a formal motion to quash.
The underlying facts of the individual proceedings are not the focus of this note. The procedural point is that Rule 2.1 was used in place of the ordinary motion process for a pure jurisdictional or prematurity issue. When that occurs, the responding party is not required to prepare a notice of motion or factum, and the matter is resolved on the materials already before the case-management judge. Whether that approach is consistent with Collins v. Ontario, 2017 ONCA 317, and Simpson, 2016 ONCA 806, remains a question of the proper scope of Rule 2.1.
By using the case conference as the trigger for a Rule 2.1 notice, the court can reach a final dismissal on jurisdictional grounds through an informal administrative step. The appellant is then required to address, in written submissions, why the proceeding should not be dismissed as frivolous, vexatious, or an abuse of process. In these examples the case conference functioned as the occasion for initiating that summary process rather than solely as a scheduling event.
Case Management — Superior Court: Scheduling as Adjudication via Rule 2.1
Historically, case management was an administrative function used to set schedules, ensure timely filing, and move matters toward a hearing. Substantive questions—whether the court has jurisdiction, whether a pleading discloses a tenable cause of action, or whether a proceeding should be struck—were ordinarily determined on formal motions under Rule 21 or by motions to quash.
In recent years the Divisional Court has used active case management more frequently for docket control. A formal motion to strike requires a notice of motion, a factum, and satisfaction of the “plain and obvious” standard while taking the opposing party’s facts as true. A case-management conference does not impose those requirements. It typically proceeds by written direction or brief teleconference. If the case-management judge concludes that a proceeding is procedurally flawed or lacks a tenable basis, the judge may issue a Rule 2.1 notice rather than directing the respondent to bring a formal motion. Administrative non-compliance or a clear jurisdictional defect can be addressed under the Rule 2.1 standard of frivolous, vexatious, or abusive proceedings.
Rajaghatta v. Niranjan, 2025 ONSC 6032, illustrates one application of this approach. The reasons record that procedural issues were handled through case-management directions. The decision also notes s. 21(5) of the Courts of Justice Act, which permits a panel to review a single judge’s order. In the course of case management of the s. 21(5) motion, directions were given requiring the moving party to limit the factum to specified procedural issues. When those directions were not followed, the court did not proceed to a panel hearing of the review motion. Instead it dismissed the motion under Rule 2.1. No Rule 21 motion was brought.
The reasons in Rajaghatta confirm that a party is entitled to seek panel review under s. 21(5):
[9] Mr Rajaghatta now moves to review the orders of Labrosse J. before a panel of three judges of the Divisional Court. This he is entitled to do pursuant to s. 21(5) of the Courts of Justice Act.
The subsequent Rule 2.1 dismissal meant that the review motion did not reach a panel. In this instance, non-compliance with case-management directions formed part of the basis for the Rule 2.1 finding. The effect was that a single judge’s directions, combined with the Rule 2.1 disposition, prevented the s. 21(5) review from proceeding to a panel.
Because applications for leave to the Supreme Court of Canada are uncommon on purely procedural questions, further appellate review of these dispositions is limited. In Rajaghatta, case-management directions were followed by a Rule 2.1 dismissal of the s. 21(5) review motion, so the matter did not proceed to a panel. The decision records one instance in which non-compliance with those directions formed part of the basis for summary dismissal under Rule 2.1 rather than a formal motion or a panel hearing. The proper scope of Rule 2.1 in relation to jurisdictional or prematurity issues, and its consistency with Simpson and Collins, remains a question of how the rule is applied.
Directory of Records
Access the consolidated public records, dockets, and procedural analyses associated with this matter below.
Supreme Court of Canada (SCC)
1. Case Overviews & Timelines
- Case Overview: Supreme Court of Canada Docket 42381, 2026 ONCA 246 and 2.1B (2025 ONCA 90)
- History of the Jurisdictional Defect in Chowdhury (2025 ONCA 90): Rule 2.1 Applied Twice
- Wrong-Forum and “Abuse of Process”: Amstar (2025 ONCA 493) and Bernard Property (2019 ONCA 830)
- “Or” vs. “Or Otherwise”: Scaduto (2015 ONCA 733), Raji (2015 ONSC 801), and the Language of Rule 2.1.01
2. Constitutional Limits & Delegated Authority
- Jurisprudence of the Administrative Reverse Onus: Rule 2.1 vs. Established Precedent
- Rule 2.1, Section 137.1 of the Courts of Justice Act, and the Administrative Reverse Onus
- Rule 2.1 and the Automatic Stay: A Procedural Tension with Rule 2.01
- O. Reg. 322/24: Form 2.1A and the 2024 Amendments to Rule 2.1
- The Reverse Onus of Rule 2.1: The Practical Effect of the Automatic Stay in O. Reg. 322/24
- Form 2.1B and the Reverse Onus: Colourability and the Limits of Delegated Authority
4. Jurisdiction, Forum & Procedural Mechanics
- Rule 2.1.01 and Jurisdiction: Simpson (2016 ONCA 806), Collins (2017 ONCA 317) vs. Chowdhury
- Jurisdiction and the Initiation of Rule 2.1 Dismissals
- Rule 21.01 vs. Rule 2.1.01: "A Judge" vs. "The Court"
- Jurisdictional Contrast: Alberta, Quebec, and British Columbia
- Amstar (2025 ONCA 493) and Ingarra (2026 ONCA 139): When Jurisdiction Becomes "Frivolous"
5. Family Rule 1.4 & Rule 2.1
- Rule 1.4, Rule 2.1 and the Rules of Procedure: Can Ontario's Rules Committees Override the Common Law?
- O. Reg. 310/26 and Family Rule 1.4: The Shifting Framework of Summary Dismissals
Statutory References