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
      • Hotfix Release 19.2
      • Hotfix Release 19.3
      • Hotfix Release 20.1
      • Hotfix Release 20.2
      • Hotfixes Release 20.3
  • 🪝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
  • Prerequisites for the Module
  • Documentary Evidence + Affidavits
  • Witness Testimony
  • Functional Specifications
  • Assumptions
  • Ideas for Future Development
  1. About DRISTI
  2. Key Modules
  3. Evidence

Specifications

Key Product Outputs

Judge/Benchclerk will be able to tag certain submissions as evidence

Judge/Benchclerk and parties to a case will be able to easily view the evidence of a case

Judge/Stenographer will be able to record witness testimony during an evidence hearing

Witness testimony will be signed by Witnesses and the Judge

Witness testimony will be easily accessible as evidence of a case

Prerequisites for the Module

  • Case File to exist in the system

  • A registered user that has joined a case

Documentary Evidence + Affidavits

  1. Tagging and Untagging Submissions as Evidence: Certain submissions may be marked as evidence based on the discretion of the judge.

    1. The judge or bench clerk may tag these submissions as evidence from the UI

    2. On the discretion of the judge, submissions may be untagged as evidence during the case

  2. No tagging/untagging of submissions as evidence will be possible once the Judgement has been passed/case is in ‘Disposed’ stage.

  3. View and Download Evidence: Evidence will be visible to all parties of a case in the documents section. The parties can view and download evidence from the document section.

    1. Upload of Documentary Evidence

Witness Testimony

  1. Testimony Formats:

    1. Witness Deposition formats will be available - with placeholders for common attributes

    2. Based on the values of attributes, the deposition template will be populated

    3. Additional content will be added by the Judge/Stenographer while recording the witness deposition.

  2. Record Witness Testimony: There may be one or multiple witnesses presented as evidence.

    1. The typist will be able to select the witness the testimony is being recorded for from the complainants + respondents + witnesses added in the case file

    2. At one point, 1 witness deposition may be tagged to ‘Complainants’ or ‘Respondents’.

    3. We need to ensure that witness is added to the system before they are presented in court

    4. The typist will be able to record the Witness Testimony in writing during an Evidence Hearing

    5. The judge will be able to see in real time the witness testimony being recorded (similar to transcripts)

  3. Witness Testimony Workflow:

    1. Once a witness testimony is recorded, it is sent for Digital Signing to the Witness.

    2. Once signed by the Witness, it is sent for Signing by the Judge

    3. On successful signing, the Witness testimony will be published in PDF format and auto tagged as evidence

    4. The pdf will be available for view and download in the documents tab of the ‘View Case’ File screen

    5. Once witness testimony is published, it will automatically be tagged as evidence by the system.

Functional Specifications

Assumptions

Theme

Assumption

Evidence

Litigants/Advocates cannot tag a submission as evidence. Only bench clerk/judge will be able to tag documents as evidence

Recording of Physical evidence against cases is not required as part of NIA. If required, a copy of the same will be uploaded to the system.

No other transcripts/depositions apart from witness deposition are considered as evidence

Documents cannot be marked as evidence once a case is disposed

Witness

Witnesses can be added to a case by the Judge/benchclerk without an associated workflow.

Witness Testimony

Witness Testimony is only recorded in an evidence hearing.

Only a witness and the judge have to sign a witness testimony

For Witness testimony uploaded as evidence, the other party cannot file a response

No voice/video recordings of witness depositions will be stored.

Ideas for Future Development

  1. Recording/Tagging of Physical evidence against cases

  2. Maintaining chain of custody of physical evidence

  3. For witness depositions uploaded as affidavits, the format of the affidavit will not be provided

  4. Translation and transcription of witness deposition in regional languages

  5. Conversion of Physical Documents to Digital Formats via OCR

  6. Ability to let Police provide evidence in certain cases

  7. Tagging of physical and oral evidence separately. Within oral evidence, tagging chief examination and cross-examination separately

  8. If an issue with marking a document as evidence, the accused can add a comment on a document as objections

  9. The same evidence may be associated with multiple cases. E.g. a knife may be a piece of evidence in more than one murder case if two murders took place with it. Currently, in V1, we are tag evidence to a case

PreviousProcess & WorkflowsNextListing & Scheduling

Last updated 10 months ago

Functional specs are available

⚖️
here