DRISTI
  • 👋Welcome to DRISTI
    • Why DRISTI?
  • ⚖️About DRISTI
    • Overview
    • Design Principles
    • Value Proposition
    • Architecture Overview
    • System Users
    • Key Modules
      • Async Applications & Submissions
        • Key Features
        • Process & Workflows
        • Specifications
      • Case Management
        • Key Features
        • Process & Workflows
        • Specifications
      • E-Filling, Scrutiny and Admission
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Evidence
        • Key Features
        • Process & Workflows
        • Specifications
      • Listing & Scheduling
        • Key Features
        • Process & Workflows
        • Specifications
      • Hearings
        • Key Features
        • Process & Workflows
        • Specifications
      • Orders & Tasks
        • Key Features
        • Process & Workflows
        • Specifications
      • Summons, Bails, Warrants
        • Key Features
        • Process & Workflows
        • Specifications
      • User Benefits
      • User Registration
        • Key Features
        • Process & Workflows
        • Specifications
        • Sequence Diagrams
      • Roles per Module
    • API Specifications
    • Security
    • Privacy
  • 🧰DRISTI Platform
    • Architecture
      • Overview
      • Principles
      • High Level Design
        • Technology Stack
        • Access Control & Roles
        • Data & Analytics
        • Non Functional Requirements
          • Performance
          • Security
          • Data Retention
        • Logging Guidelines
      • Low Level Design
        • Advocate
          • Advocate - API Specifications
          • Sequence Diagram
        • Application
          • Application - API Specifications
          • Sequence Diagram
        • Case
          • Case - API Specifications
          • Sequence Diagram
        • Case Management
          • Case Management - API Specifications
          • Sequence Diagram
        • Evidence
          • Evidence - API Specifications
          • Sequence Diagram
        • Hearing
          • Hearing - API Specifications
          • Sequence Diagram
        • Order
          • Order - API Specifications
          • Sequence Diagram
        • Task
          • Task - API Specifications
          • Sequence Diagram
          • Summons
          • Warrant
      • Architectural and Design Decisions
        • Data Visibility
        • Detailed Case Access
        • Case Numbering
          • Filing Number
          • Court Case Number
          • CNR Number
          • Case Stages, Numbers & Dates
    • Interoperability
    • Release Notes
      • Release 1.1.0
      • Release 1.2.0
      • Release 1.3.0
      • Release 1.4.0
      • Release 1.5.0
      • Release 1.6.0
    • Hotfixes
      • Hotfix Release 17.3
      • Hotfix Release 18.1
      • Hotfix Release 18.2
      • Hotfix Release 18.3
      • Hotfix Release 18.4
      • Hotfix Release 19.1
  • 🪝Setup
    • Planning DRISTI Implementation
    • Establish Project & Team
    • Gather Requirements
    • Installation
      • Infrastructure Setup
        • Azure Setup
        • SDC - OpenShift Setup
      • Code Deployment
      • Configuration
        • Functional Configuration
        • Service Configuration
          • Court
            • Court UI
          • Case
            • Case UI
          • Advocate
            • Advocate UI
          • Application
            • Application UI
          • Task
            • Task UI
          • Order
            • Order UI
          • Hearing
            • Hearing UI
          • Evidence
            • Evidence UI
    • Quality Assurance Testing
    • Go Live
    • Operational Support
    • Monitoring
  • 🛣️Roadmap & Updates
    • Roadmap
  • 🌾Resources
    • Source Code
    • Technology Stack
    • Licensing
    • Legal Taxonomy
  • 🌐COMMUNITY
    • Interested in Contributing?
    • Github Discussion
    • Code of Conduct
  • 🪝Setup
    • Coming soon...
    • 🟢ABOUT US
Powered by GitBook
On this page
  • Usage
  • Format and Example
  • ID Gen Format
  • Reset Logic
  • Master Data Dependency
  1. DRISTI Platform
  2. Architecture
  3. Architectural and Design Decisions
  4. Case Numbering

CNR Number

Case Number Record

PreviousCourt Case NumberNextCase Stages, Numbers & Dates

Last updated 10 months ago

Usage

After a case has been admitted for trial i.e. it has been accepted during an Admission hearing or has been directly approved to get into trial, it is assigned a CNR Number and the date is marked as the registration date. This CNR number is aligned with the number format used by the (CIS) managed by the (NIC).

A case rejected at time of admission hearing, i.e. doesn't goes to trail, will not have a CNR number.

Format and Example

It has the following format and the table below also shows different examples.

The number is unique to a court establishment within a district within a state.

ID Gen Format

[STATE_ID][DISTRICT_ID][ESTABLISHMENT_ID]-[CNR_SQUENCENUMBER]-[cy:YYYY] 

This service will be enhanced to pull data from multiple masters to create the CNR number.

Reset Logic

The 6-digit case filing number part of the CNR Number is reset to start with 1, every calendar year. The first case logged at an establishment on 1st January will start with 1. For example, for Punjab, District Jalandhar and District and Sessions Court Establishment, this will be

PBJL01-000001-2025  // 1st Case on 1st January 2025
PBJL01-000002-2025  // 2nd Case (the sequence number will keep incrementing)

Master Data Dependency

CNR number uses the following masters

  1. State master to get STATE_ID

  2. District master to get DISTRICT_ID

  3. Establishment master to get ESTABLISHMENT_ID

  4. ID Gen master table to get CNR_SQUENCENUMBER

DIGIT's will be used to help generate this number. The format for filing number will be as below

🧰
ID Generation Service
Case Information System
National Informatics Center
CNR Number