1. Introduction: Meaning and scope

A Digital Case Resolution Optimization Engine is a technology system designed to improve how civil disputes are registered, classified, scheduled, processed, settled, and resolved. It may use workflow automation, legal databases, predictive analytics, artificial intelligence (AI), and online dispute-resolution tools.

In Morocco, such a system could support:

Civil claims involving contracts, property, compensation, and debt recovery.

Commercial disputes between companies.

Family and consumer disputes, subject to applicable procedural safeguards.

Electronic filing, case-status tracking, and procedural notifications.

Mediation, conciliation, and settlement management.

Judicial workload analysis and identification of avoidable delays.

Morocco already provides online judicial services through its Ministry of Justice, allowing citizens and legal professionals to access certain services remotely.

MRE+1

The crucial distinction is that optimizing the resolution of a case does not mean allowing an algorithm to replace a judge. A properly governed system helps organize proceedings, identify relevant information, and facilitate settlement while preserving the parties' right to be heard and the independence of the judiciary.

2. Legal framework in Morocco

A. Constitutional principles

The Moroccan Constitution provides the foundation for judicial independence, equality before the law, access to justice, and the protection of fundamental rights.

A digital case-resolution system should therefore ensure:

Equal access to judicial services, including for people with disabilities and those with limited digital access.

Fair opportunities for both parties to submit evidence and arguments.

Independent judicial decision-making.

Confidentiality and appropriate protection of personal information.

The availability of meaningful review when an automated system makes a procedural error.

B. Civil procedure legislation

Morocco's civil procedure framework governs jurisdiction, filing, notification, evidence, hearings, judgments, appeals, and enforcement.

A significant recent development is Law No. 58-25 on Civil Procedure, reported as entering into force on 24 August 2026 and replacing the former 1974 Code, subject to applicable transitional rules. The current procedural requirements should therefore be checked against the new law rather than assuming the former Code remains the governing framework for every proceeding.

Yassine Krari et Associés

The 2024–2025 reform process expressly addressed electronic litigation, digital judicial procedures, judicial efficiency, and the use of modern technology in court proceedings.

Ministère de la Justice+1

C. Personal-data protection

Law No. 09-08 governs the processing of personal data. A case-optimization platform may process names, addresses, identification records, financial information, pleadings, evidence, and sensitive information about litigants.

The platform's operator must assess the applicable legal basis, information duties, security requirements, data-retention rules, and CNDP procedures. Personal information gathered for one purpose should not automatically be reused for unrelated profiling or predictions.

D. Electronic transactions and records

Law No. 53-05 provides a framework for certain electronic data exchanges of a legal nature. Other applicable legislation may govern electronic signatures, trust services, digital evidence, and particular procedural acts.

An optimization engine must distinguish between a document that is technically uploaded and one that satisfies the legal requirements for filing, authenticity, admissibility, and service.

E. Mediation and settlement

A case-resolution engine may facilitate negotiation, conciliation, or mediation, where permitted by the applicable law. It can identify common issues, organize offers, calculate proposed payment schedules, and track settlement compliance.

However, a system should not treat a suggested settlement as binding merely because its algorithm predicts that one party is likely to accept it. Any agreement must satisfy the applicable requirements for consent, capacity, form, and enforceability.

3. How a digital case-resolution optimization engine works

Stage 1 — Electronic filing

Receive the claim, supporting documents, party information, and requested remedy.

Stage 2 — Validation and classification

Check document completeness, identify the dispute category, and flag possible jurisdictional or procedural issues.

Stage 3 — Scheduling and case management

Track deadlines, organize hearings, monitor service of notices, and help allocate administrative resources.

Stage 4 — Settlement or judicial determination

Offer mediation where legally appropriate, or support the court's handling of the contested case.

Stage 5 — Judgment, appeal, and enforcement

Record the outcome, monitor applicable appeal periods, and track enforcement steps.

The system should support each stage without independently deciding disputed facts, depriving a party of a hearing, or overriding a judge's legal authority.

4. Six relevant Moroccan judicial decisions

The following decisions illustrate legal principles that a digital case-resolution engine must respect. They are not six judgments specifically about AI optimization software; they concern constitutional review, notification, and procedural deadlines. Their relevance is the legal foundation they provide for designing reliable digital procedures.

Case 1: Moroccan Constitutional Court — Decision No. 255/25

Date: 4 August 2025 · File No. 303/25

Subject: Constitutional review of Bill No. 02.23 on Civil Procedure.

Background: The Constitutional Court reviewed the proposed civil-procedure reform, including provisions relating to electronic judicial processes, notification, and the administration of judicial proceedings.

Decision and principle: The Court declared a number of provisions unconstitutional. The decision is particularly significant for the limits it places on procedural arrangements that conflict with constitutional safeguards, including judicial independence and procedural fairness.

المحكمة الدستورية+1

Relevance to optimization engines: A system designed to allocate cases, manage judicial workloads, or automate procedural tasks must respect the constitutional division of responsibilities. Efficiency cannot justify transferring judicial decision-making powers to an inappropriate authority.

Practical lesson: The architecture and administration of digital court systems must preserve judicial independence and the parties' procedural rights.

Case 2: Court of Cassation — Decision No. 487

Date: 23 February 2000

Subject: Notification of a judgment and the commencement of an appeal period.

Legal principle: The reported decision explains that, under the former Code of Civil Procedure, the appeal period ran against a party from the notification made at that party's request, in accordance with the applicable procedural rule.

Jurisprudence+1

Relevance to optimization engines: A deadline-monitoring system must identify the correct party, the relevant notification event, and the applicable procedural rule. It cannot calculate every deadline using a single generic formula.

Practical lesson: Deadline automation must be rule-specific and preserve an auditable record of the notification event.

Current-law qualification: This decision arose under the former Code. Its present application must be assessed under Law No. 58-25 and any applicable transitional provisions.

Case 3: Court of Cassation — Decision No. 428

Date: 9 February 2005 · File No. 3882/2003

Subject: Notification at an address elected through a lawyer and the commencement of an appeal period.

Legal principle: The reported decision concerned notification at an elected address and its effect on the calculation of the appeal period under the former procedural framework.

Jurisprudence

Relevance to optimization engines: Digital systems must distinguish between a party's residential address, an elected address for service, and other contact information. An address recorded in a database is not necessarily the legally relevant address for every procedural act.

Practical lesson: Case-management software should preserve the legal status and history of addresses and flag disputed service instead of automatically treating every delivery as valid.

Case 4: Court of Cassation, Civil Chamber — Decision No. 3302

Date: 14 December 2005 · File No. 4421/1/6/2004

Subject: Refusal to receive a notification and the calculation of an appeal period.

Legal principle: The reported decision addressed the procedural consequences of refusing notification, including the applicable rule for calculating the appeal deadline under the former Code.

Jurisprudence

Relevance to optimization engines: A platform must differentiate between successful service, unsuccessful delivery, refusal, and disputed service. Each event may have a different legal consequence.

Practical lesson: The system should record the actual event and apply the relevant rule only after the event has been properly classified.

Case 5: Court of Cassation, Commercial Chamber — Decision No. 1343

Date: 8 December 2004 · File No. 1383/3/2/2003

Subject: Refusal of notification and the time limit for appeal.

Legal principle: The reported decision considered the effect of refusal to accept notification and the applicable calculation of the appeal period under the former procedural rules.

Jurisprudence

Relevance to optimization engines: Commercial litigation often involves strict procedural deadlines. A digital engine should distinguish the rules applicable to commercial proceedings from those applicable to other proceedings and should not assume that every notification failure has the same legal effect.

Practical lesson: Procedural rules should be maintained as a version-controlled legal ruleset, with the relevant date and type of proceeding recorded.

Case 6: Court of Cassation, Commercial Chamber — Decision No. 131/2

Date: 4 March 2021 · File No. 2019/2/3/1698

Subject: Notification where a party claimed to reside abroad.

Background: The reported dispute concerned notification made to a family member in Morocco despite submissions that the affected party lived abroad.

Legal principle: The Court of Cassation found that the lower court had failed to address relevant submissions and evidence concerning residence and notification.

Law Gratis

Relevance to optimization engines: A platform should not treat an address match or a delivery status as conclusive proof that legal service was valid. It must allow relevant evidence and objections to be considered by the competent judicial authority.

Practical lesson: Automated systems need exception handling and human review when parties dispute notification or jurisdictional facts.

Comparative summary of the six cases

These authorities are useful for the design of a legally compliant optimization engine, but the older decisions must be interpreted in the context of the law applicable to the proceedings concerned. None should be represented as approving algorithmic adjudication.

5. Alternative dispute resolution and settlement optimization

A digital engine can help parties resolve disputes without requiring a full contested hearing.

Morocco's Law No. 95-17 on arbitration and conventional mediation provides a statutory framework for arbitration and mediation. A digital platform can support these processes by organizing submissions, managing communications, scheduling sessions, and recording settlement proposals.

Global Guide to Alternative Dispute Resolution+1

Potential functions include:

Identifying cases that may be suitable for voluntary mediation.

Scheduling sessions and communicating proposals.

Helping parties organize the documents relevant to settlement.

Recording agreed payment schedules and other settlement terms.

Tracking compliance with a settlement agreement.

The platform must not pressure a party into settling, disclose confidential offers without authorization, or represent a proposed settlement as enforceable before the applicable legal requirements are met.

6. Risks and safeguards

An additional risk is that historical case data may reflect existing disparities or incomplete records. A model trained on such data may reproduce past patterns rather than identify what the law requires in an individual case.

7. Illustrative example

Suppose a company in Casablanca files a civil claim to recover an unpaid contractual debt.

A digital case-resolution engine could:

Register the claim and supporting contract.

Check whether required documents appear to be missing.

Flag possible questions concerning jurisdiction.

Track service of process and relevant procedural deadlines.

Offer mediation if the dispute and applicable rules make it appropriate.

Organize the evidence and submissions for the court.

Record the judgment and track the applicable appeal or enforcement procedure.

If the defendant disputes the notification, the system should flag the dispute for consideration rather than automatically declare the claim uncontested or the appeal time-barred.

The judge remains responsible for determining the legal consequences of contested facts and applying the governing law.

8. Conclusion

Digital Case Resolution Optimization Engines could improve civil justice in Morocco by reducing administrative delays, making procedural information easier to access, improving deadline monitoring, and supporting mediation.

Their legal legitimacy depends on more than speed. They must comply with current civil-procedure legislation, protect personal data, preserve the right to be heard, and remain subject to appropriate human and judicial oversight.

The six decisions discussed above provide examples of the constitutional and procedural safeguards that matter when designing such systems. They are supporting authorities on procedural fairness and notification, not direct precedents on AI-powered dispute resolution. For formal litigation or academic publication, the full judgments and the provisions of Law No. 58-25 should be checked before relying on any older procedural rule.