Kanana v. Misgav Local Planning Committee — Supreme Court dismisses untimely appeal where attorney’s electronic viewing of judgment started the appeal clock

Case
Ali Muhammad Kanana and Huriya Kanana v. Local Planning and Building Committee of Misgav, Misgav Regional Council, and Ministry of Interior
Court
Supreme Court of Israel, Civil Appeals Division (Registrar) (Israel)
Date Decided
June 18, 2026
Citation
C.A. 22169-11-25
Topics
Civil procedure; appellate deadlines; electronic service of process; extension of time

Background

The appellants, Ali and Huriya Kanana, sued the Local Planning and Building Committee of Misgav, the Misgav Regional Council, and the Ministry of Interior in the Haifa District Court. On June 29, 2025, Judge A. Alon dismissed the lawsuit at the threshold on limitations grounds pursuant to Rule 43 of the Civil Procedure Regulations, 5779-2018. The appellants sought to challenge that dismissal in the Supreme Court.

On December 10, 2025, the Ministry of Interior (Respondent 3) moved to strike the appeal as untimely. Records in Israel’s electronic case-management system, Net HaMishpat, showed that the appellants’ then-counsel, Adv. Khalid Faisal, had proactively accessed and viewed the judgment on the very day it was issued — June 29, 2025 at 10:50 a.m. via the system’s mobile application — and again on July 1, 2025. The statutory deadline to file a civil appeal therefore ran from June 29, 2025 and expired on October 26, 2025. The appeal was not filed until November 9, 2025 — roughly two weeks late — and no contemporaneous motion for an extension of time accompanied it.

The appellants’ response, ultimately filed June 3, 2026 after multiple extensions of time to respond, denied any delay and argued in the alternative for a retroactive extension. They contended that a mismatch between the attorney listed in the judgment header (Adv. Husam Sabit) and the attorney who actually represented them at trial (Adv. Khalid Faisal) constituted a defect in service, and that both attorneys had told Appellant 1 they never received the judgment — which he claimed to have discovered only through his own Net HaMishpat search on October 29, 2025. No affidavit from either attorney was submitted to support these assertions.

The Court’s Holding

Registrar Moran Yahav held that the appeal was filed out of time and declined to grant a retroactive extension, ordering it struck under Rule 147(b)(1) of the Civil Procedure Regulations. Applying the “service rule” (כלל ההמצאה), the court found that service is effected when a “website notification” is transmitted to counsel’s registered email address under Rule 161 of the Regulations, and that the Net HaMishpat logs conclusively showed Adv. Faisal had viewed — and thereby received — the judgment on June 29, 2025. Even assuming a formal defect in service, the court held that the alternative “knowledge rule” (כלל הידיעה) yielded the same result: a party’s documented, proactive viewing of a judgment in the system constitutes actual knowledge and starts the appeal clock regardless of any notification irregularity.

The appellants’ unsworn claim that neither attorney received or read the judgment was fatal to their position. The court stressed that contesting service through the Net HaMishpat system requires a proper affidavit from the attorney in question; bare assertions by counsel in a written submission do not suffice. Because Adv. Faisal had viewed the judgment on the day it was issued and no affidavit contradicted that record, the court found the appeal was due by October 26, 2025 and was filed approximately two weeks late.

Turning to the alternative request for a retroactive extension under Rule 176(b), the court found no “special reasons” to justify one. Established Supreme Court authority holds that confusion or breakdowns in the attorney-client relationship — including mid-litigation changes of representation — do not ordinarily constitute special reasons for a late filing. Here, Adv. Sabit had originally represented the appellants, was released from representation by court order in January 2025, and only filed a new power of attorney to re-enter the case in November 2025, four months after judgment. The application lacked essential details such as when the appellants first contacted substitute counsel and when the prior counsel was formally discharged, and it was unsupported by any affidavit. Absent special reasons, no extension could be granted.

Key Takeaways

  • An attorney’s proactive, logged viewing of a judgment in the Net HaMishpat system constitutes effective service and triggers the appeal clock, even if the attorney later asserts non-receipt.
  • Challenging service via the electronic court system requires a sworn affidavit from the attorney allegedly not served; unsworn assertions in a brief are insufficient and will be rejected.
  • Under both the statutory “service rule” and the judge-made “knowledge rule,” documented actual knowledge of a judgment cures any formal notification defect — the knowledge clock and the service clock converge.
  • A mid-litigation change of representation, and any resulting administrative confusion between outgoing and incoming counsel, is not a “special reason” under Rule 176(b) to extend the time to file an appeal.

Why It Matters

This decision reinforces the strict approach Israeli courts take to appellate filing deadlines. Attorneys who access judgments through Net HaMishpat acquire professional responsibility for acting on what they view; they cannot later disavow knowledge of the decision. The ruling makes clear that the electronic record is treated as near-conclusive evidence of knowledge, shifting a heavy burden onto any litigant who claims otherwise.

For practitioners, the case is a sharp reminder that changes of representation demand meticulous attention to pending deadlines. When outgoing and incoming counsel overlap, neither can assume the other is monitoring the docket. Courts will not absorb the cost of that coordination failure by granting extensions, and the absence of supporting affidavits from the attorneys involved will doom any attempt to explain the delay after the fact.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top