ADR

Mizan ADR · Online arbitration

Multiple parties.
One tribunal.
An award that stands.

From the request to the award, on one confidential file — filing, tribunal, terms of reference, instruction, hearings, award.

9
Stages, request to award
5
Roles on one file
3
Languages · FR EN AR
1
Record of every act

Who it is for

One file, three sides of the table

The same case, seen from each seat — and nobody sees past theirs.

The procedure

From the request to the award, in nine stages

Nine states, as the platform runs them. Each one is a gate. Point at a stage.

  1. Files the parties, the agreement, the request and the fees.

    Nothing advances until the file is complete.

  2. Admits the file, or sends it back with a notice.

    Admission opens the case to the other side.

  3. Are notified, join, and complete their own file.

    Every respondent seated before the next check.

  4. Confirms the complete file, both sides included.

    A verified file, or no tribunal.

  5. Nominations, votes, challenges — conflicts declared against the IBA guidelines.

    A seated tribunal, accepted by both sides.

  6. Drafted by the tribunal, approved by the parties on the file.

    They frame everything that follows.

  7. Fees settled and validated.

    Proceedings open once validated.

  8. Rounds of submissions and exhibits; hearings by video, recorded and transcribed.

    Closed when the record is complete.

  9. Renders the award. The record stays where it was made.

    Final.

The walk-through

Every feature, shown three ways

Each feature on its own page: the screen, the steps, the mechanism.

01Systems01 / 11

Pattern 01 · Facts

Every change to a case reaches AIOL, in order, exactly once

A transactional outbox announces each case change the moment it is committed — no button, no export, no nightly job.

ONE TRANSACTIONa document is filedits event is writtenOUTBOXseq 1 · dispute.createdseq 2 · document.filedseq 3 · …ONE WORKERsigns · sends in orderretries with backoffpauses on a defectAIOLdedups on event_idA change that rolls back leaves noevent. An event exists exactlywhen the fact does.
01Systems
02AIOL on the litige

Confidentiality

Built to be trusted with a dispute

A dispute file is what the parties least want read. That is the design constraint.

See it on a case

The platform as it is — screen, steps, mechanism.

Start with the systems, then follow the procedure chapter by chapter.