Online Dispute Resolution (ODR)


ODR is a digital space where parties can convene to work out (or attempt to work out) a resolution to their dispute or case.

ODR can be used to address different business needs that include (but are not limited to): prevention and early resolution of disputes, reduction in judicial caseloads, reduction in resources, and increased access to justice for unserved or underserved segments of the community.

What it Includes

ODR includes:

  • Identification of parties and associated details
  • Identification of dispute/case and associated details
  • Identification of permissions, roles, and information sharing requirements
  • Direct communication between parties
  • Identification of roles and appropriate communication channels for third parties
  • Identification of preferred modes of communication for all participants
  • Escalation to include third-parties and/or computer-enabled interventions
  • ODR case routing and roster/panel management (when needed)
  • Resolution or attempted resolution of dispute or case
  • Date/time of resolution with appropriate documentation and audit trail
  • Facilitation capture and management of relevant information and artifacts
  • Generation of required documents for resolution
  • Education of parties on process
  • Reporting re. key performance metrics
  • Adherence to relevant timeliness standards/deadlines and standard ODR models
  • Security in/out and within ODR platform/system
  • Authentication in and within the ODR platform/system

What it Does not Include

The ODR component may employ many related components to provide a litigant, judicial officer, court staff, and other case participants important capabilities.   Table 1, below identifies capabilities that may be available through the ODR component but are optimally provided by another court enterprise component.  It lists those capabilities provided by the related component.  It notes whether the external capability is:

  • Required: Fundamental to the operation of this component.
  • Expected: Commonly provided by an external component to support a more robust solution.
  • Optional: May be provided by an external component but may often be provided internally.Alternatively, the capability may not be provided at all.

Table 1 - Externally Provided Capabilities



Required / Expected / Optional

View relevant court case information

01-Case Manager


View participant information

02-Case Participant Manager


View case calendar

04-Scheduling Calendaring


Update case schedule

04-Scheduling Calendaring


Generate notifications



Process payments (fees, fines, settlements)

17-Payment Processing


File documents

07- Electronic Filing Manager


Prepare judicial documents

Word processing software


Generation of standardized court documents

29-Court Form Document Generation


Authenticate the user and determine user authority to access application functions

23-Identity Management


View evidence and exhibits

11-Evidence and Exhibit Management


Applicable Standards and Documents

  • JTC Resource Bulletin: ODR for Courts:
  • JTC Resource Bulletin: Case Studies in ODR for Courts: A view from the front lines:
  • JTC Resource Bulletin: Introduction to the Next-Generation Court Technology Standards Application Component Model:
  • Efiling standards (ECF)
  • Leverage NIEM
  • Leverage GRA
  • ICODR - International Council for Online Dispute Resolution