Specifications

Assumptions

Theme
Assumption

Filing a case

There is no requirement to make changes to the e-file once submitted until sent back for error correction/additional details

Users will find it easier to file a case using a web interface. Hence, the file a case functionality is not made available in the mobile app.

Scrutiny

It is assumed that there will be one FSO in the pilot court. In the case of multiple FSOs, the FSOs can decide the cases for scrutiny and will not be assigned cases specifically.

E-sign

E-signing of a case is only done by the person filing the case (complainant/complainant’s advocate). If additional complainants are present in the case, no signing will be required from their end.

File a case

  1. A petitioner or their advocate may file a case

  2. A case may have one or multiple petitioners and one or multiple respondents, depending on the case type.

  3. Features of this module include:

    • Info Box: Provides a checklist of required documents and the average time taken to file a case. This document list may also be downloaded as a PDF.

    • Generic Details: These are details to be filled for all case types, categories and sub-categories

    • Case-Specific Details: These are details that will be specific to the case type, category and sub-category

    • Pre-Filled Templates: Along with intuitive drop-down menus, supplementary templates in the form of word documents will be available to the petitioners/their advocates to use as a reference to facilitate speedy filing of cases

  4. As part of case details, users will be expected to enter values and upload documents

  5. Each petitioner and respondent may choose to appoint an advocate or represent the case party in person. In case the petitioner or respondent is opting for the party in person, they should have access to all actions that are to be performed by the advocate

  6. The technical process working in the backend to file a case has been detailed here.

Organisation Creation

  1. Users can add organization names using a fuzzy search box.

  2. Matching organization details will be auto-populated.

Case Name Generation

  1. The name of the case will be auto-generated based on the name of the petitioner and respondent.

  2. The case name will follow the format given below:

    • Primary petitioner name vs primary respondent name.

    • The first petitioner entered into the system can identify the primary petitioner.

    • The first respondent entered into the system can identify the primary respondent.

Appointment of advocates

  1. One or multiple advocates may be appointed by a litigant for representation in a case.

  2. Multiple petitioners/respondents may be represented by the same advocate.

  3. In case an advocate is selected by the Litigant, the search will be done using the name and BAR Council ID. Only exact matches will be provided by the system.

  4. The advocates are divided into two categories:

    • Primary Advocates

    • Other Advocates

  5. There needs to be a “Vakalathnama” to be uploaded as part of the process to declare the appointment of a “Primary advocate”. Each litigant and advocate will share one pre-existing Vakalathnama.

  6. Only primary advocates can perform actions in a case. Other advocates can only view case details.

E-signing

E-signing functionality has been provided as part of Case Filing. The user filing the case will be able to e-sign the case. The following methodologies for e-signing a case have been made available:

  • Aadhar OTP-based verification - The user may enter his/her registered Aadhar ID and confirm his identity by entering the OTP received by him/her on the registered mobile number.

Automated Scrutiny (Constituent element-based validation)

  1. To reduce the effort of the Scrutiny officer, validations will be applied to the form to prevent incorrect entries. The list of validations (constituent element-based validations) is available in the functional specifications. Any violations of these validations will be flagged to the user while filing the case.

  2. Users can choose to file a case despite the presence of constituent element-based validations).

  3. The validations of the fields may differ by case type. For example in NIA 138 cases, only one petitioner is allowed, and hence other petitioners cannot be added. However, in other case types, multiple petitioners may be added to a case.

  4. The FSO will be able to see errors/alerts based on certain rules for a case type. For example, as per law, a case cannot be filed post 6 months of the cheque bounce.

Save as Draft

  1. Users can save the case file as a draft.

  2. Values are retained even if the user logs out and logs in again.

  3. A temporary case ID is generated for drafts.

  4. The technical process for editing a case has been detailed here.

View as PDF (Document Indexing)

Users are currently used to view the Case in PDF format to ensure all details are provided and edit/add details. To ensure the ease of usage of the system, we will provide the ability to view the case file as a document in PDF format alternatively.

  1. The Case file in pdf format will be generated based on the civil and criminal code.

  1. Once the case is submitted, a PDF of the submission formatted as per court rules and requirements and bearing the appropriate signatures and authentications is created as an official / verifiable record of the filing.

Payments

The application fee is standardized and defined by the court. The current payment options are:

  1. Make an online payment: With the ability to integrate with the e-treasury services of respective states, online payment to facilitate the e-filing process is possible, enabling the entire process of filing to happen without needing to be physically present at the court.

  2. Pay at the counter in court: Offline payment is enabled for the 'Collector' role in the system. The collector will mark it as completed in the system.

Assisted File Scrutiny

  1. Once the case is submitted by the user, it is forwarded to the file scrutiny officer. The file scrutiny officer can either validate the case or send it back with Feedback. The FSO is assisted by an optical character recognition (OCR) tool, built in to ensure that the correct document is uploaded by keyword matching and critical information matching with the metadata like amount on cheque

  2. Providing Feedback: Through a two-way communication portal, feedback by the FSO can be provided at the field level or section level. They can mark a field as an error and provide comments. The feedback will be shared with the petitioner/petitioner’s advocate for further updates. Notifications and SMS will be sent to notify users of pending tasks.

  3. Updating Case Details: Case details may be updated based on the feedback. Provision of feedback and update of case details can be done an infinite number of times.

  4. When the case is resubmitted after the FSO has sent back the case for correction, the comments added by the FSO during previous scrutiny will be visible so the FSO can easily check if they’ve been corrected

  5. Validate Case: Once the FSO is confident, on the details of the case, he/she may choose to move the case forward to the Judge for Admission.

    • Case type-wise checklist: A case type-wise checklist will be made available to the File Scrutiny officer to confirm whether a case has been scrutinized based on a certain set of rules. Question types to be supported as part of the checklist include

      • Yes/No answers

      • Short answer type

      • Long answer type

      • Multiple answers type

      • Checkbox answer type

      • Date answer type

      • Time answer type

  6. If there is more than one judge in the court establishment, the FSO will select which judge the file has to be assigned to.

Case Admission

  1. Once the FSO has validated the case, the case is moved to the Judge. The judge has the following options:

  • Send back for additional information.

  • Quick admit without additional information.

  • Schedule an admission hearing.

  1. Case ID Generation:

  • Follows the CIS system format.

  • A unique 6-digit code is generated for the case.

  1. Conduct Admission Hearing:

  • Conducted as per the process laid out in the Hearings section.

SMS Notifications

Parties should be notified via SMS at various points. A list of SMS at various points is mentioned here.

Case Withdrawal

Users can withdraw the case at any point in time before admission without the Judge's approval.

Ideas for Future Development

  1. E-Signing using a third party software such as emudhra

  2. Refund for case application fee

  3. Availability of indexed case files in PDF format will not be available in a localized language

  4. Automated generation of Video Conferencing link for Admission hearing

  5. SLA-based escalation matrix for scrutiny and admission

  6. Access of Drafted case filed by any user other than the one filing the case file

  7. Mask Fields and Documents: Certain documents are uploaded by Litigant/Advocate that are for the judge's eyes only and need to be masked

  8. Verification that the same advocate cannot be assigned to a litigant and a respondent

  9. While the case file is under scrutiny, the FSO marks certain fields as errors. Enabling advocate to only update fields with errors marked

  10. Case names can be updated during admission by the File scrutiny officer and the judge. Once a case is admitted, it cannot be edited.

  11. Chat between advocate and file scrutiny officer

  12. Police filing a charge sheet

  13. Assignment of cases to FSO

  14. Police filing a case

  15. Multiple petitioners signing a case. This may be required for other case types

  16. Defining SLA for FSO to complete scrutiny or SLA for advocates/litigants to make corrections

  17. Transfer of case across jurisdictions

  18. Suo Moto Cognizance - The Court needs to have the ability to initiate a case against someone on its own accord. An example where this is used - contempt of court.

  19. Advocate appointed by person and the person later wanting to become party in person. In V1, an application can be filed for this and then a change made by the CMO/Court Staff

  20. Download the case file and upload it with your signature for case filing

  21. Other litigants/lawyers added to the same case can view/edit drafts. A log of timestamp-user-edit is maintained by the portal for users to see if they want.

  22. In case multiple petitioners are filing the case, the signature of only the primary petitioner will be taken. To accommodate other case types it would be necessary to be able to handle multiple litigant signatures on a single document. e.g. in a case where several applicants are being represented by a common advocate, and they have all not given a POA in favour of a single person, they may all file a single pleading collectively but each person would be signing it individually.

Functional Specifications

#
Description
Mandatory/Optional
Field Type
Validation

1

Case Category

Mandatory

Boolean (Civil/Criminal)

If Civil is selected, give an error message with the following " Civil Cases are not supported, please use the XXXX link to continue filing)

2

Case Type

Mandatory

Boolean (Original/Appellate)

If Appeal is selected, give an error message with the following " Appeal Cases are not supported, please use the XXXX link to continue filing)

3

Statute

Mandatory

Dropdown

If anything other than IPC is selected, give an error message with the following " Statute Cases are not supported, please use the XXXX link to continue filing)

4

Section

Mandatory

Dropdown

If anything other IPC is selected, give an error message with the following " Statute Cases are not supported, please use the XXXX link to continue filing)

5

Filing Number

System Generated

Temp number to identify casee before case is admitted

6

CNR Number

System Generated

Final number to identify case after case is admitted

7

CaseID

System Generated

8

Tenant ID

System Generated

9

Court ID

System Generated

10

Bench ID

Based on Judge/Bench Assigned

11

Judge ID

Based on Judge/Bench Assigned

12

Filing No.

System Generated

13

Filing Date

System Generated

14

Case Description

15

Case Name

System Generated, with Ability for FSO to edit

Last updated