Attachment_3_-_Functional_Requirements.xlsx
XLSX spreadsheet 70 KB Posted
- Solicitation number
- RFP 026-2630601-RA
- Issued by
- Orange County, San Diego City, California
About this file
This document is a Functional Requirements attachment for the County of Orange, Office of the District Attorney (OCDA) Request for Proposal (RFP) for a new Case Management System (CMS). The RFP seeks a comprehensive digital solution to replace the existing legacy system, with proposals due on September 18, 2024, and services expected to commence in February 2025. The project involves implementing a Commercial-off-the-Shelf (COTS) solution that supports complex prosecutorial workflows across case processing, evidence management, trial preparation, and case support services. A pre-proposal submission meeting is scheduled for August 14, 2024, with a question and answer deadline of August 21, 2024. Potential vendor interviews are planned for the week of November 4, 2024, with an anticipated 11-year contract term.
The procurement will evaluate proposals across five key criteria: Solution Offering + Requirements (300 points), Implementation Services (200 points), Experience and Qualifications (100 points), Corporate Sustainability (50 points), and Cost (100 points). The RFP includes provisions for local small businesses (OCLSB) and Disabled Veteran Business Enterprises (DVBE), offering a 5% bid price reduction or scoring advantage for qualified vendors, with an enhanced 8% preference for businesses certified in both categories. Vendors must be certified by the California Department of General Services and maintain a principal operation center in Orange County. At least 20% of the total bid amount must be allocated to certified OCLSB or DVBE subcontractors. The project requires integration with external systems including law enforcement, court, and victim services platforms, and will replace a current system characterized by multiple auxiliary applications and manual processes.
View the file
Other files
Show all 45
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Instructions
| County of Orange, Office of the District Attorney (OCDA) |
| Request for Proposal |
| Functional Requirements - Instructions |
| Instructions |
| This Attachment contains Functional Requirements requested for the OCDA CMS. |
Instructions: The Respondent shall use the response codes below to indicate whether the Solution meets the requirements or whether the Respondent recommends changes to the stated requirement.
Complete this Attachment and submit as an MS Excel file as part of the Respondent's Proposal Package.
| Field | Definition / Instructions |
| ReqID | Requirement Identification Number: This should be used to refer to requirements in correspondence |
DO NOT EDIT THIS FIELD
Level 0 and Level 1 Capabilities The description of the requirement
DO NOT EDIT THIS FIELD
Requirement The Respondent's response to whether and how the Functional Requirement will be met.
Indicate how the requirement, as currently written, will be met by the Respondent's proposal using the following codes:
Respondent Response Definitions:
O - Out of the Box - The requirement can be met out of the box N - No - The requirement cannot be met G - ConfiGuration - The requirement can be met with some configuration C - Customization - The requirement can be met with some customization 3 - 3rd Party - The requirement can be met with the help of a third-party Respondent F - Future Release - The requirement will be met in a planned future release
Only one response per requirement will be accepted.
An omitted response will be assumed to be the same as a response code of "No".
Respondent Response A Respondent comment is required when the response is either G, C, 3, or F.
When a comment is required, describe how the requirement will be met.
Additionally, Respondents may provide suggested changes to improve the requirement, or comments on the Respondent's response. (Optional).
Respondent Comment
Capability Definitions
| County of Orange, Office of the District Attorney (OCDA) |
| Request for Proposal |
| Functional Requirements - Capability Definitions |
| Level 0 Capability | Level 1 Capability | Definition |
| 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Receive and review Direction for Complaint (DFC) outlining details of the reported crime (e.g., individuals involved, reported crime(s) committed, charges requested), etc.), assign the case to appropriate OCDA staff (e.g., Attorneys, investigators, clerks, etc.), and determine if and what charges should be filed. |
| 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Based on the parameters outlined in the legislation, ensure that personal identification data related to a defendant’s race is not available to the attorney making a charging decision and that that process is auditable. |
| 1.0 Case Initiation Processing | 1.3 Generate Charging Instruments | Upon determination of charges related to the reported crime(s), develop the formal charging decision and assemble charging documents, outlining what charge(s), enhancement(s), allegation(s) and prior(s) are to be filed for the reported crime(s). |
| 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Prepare for and hold first formal appearances to inform the defendant of the charges file against them, convey information on the defendant’s rights, and schedule subsequent steps in the prosecution process. |
| 1.0 Case Initiation Processing | 1.5 Conduct Arraignments | Prepare for and conduct initial hearing on the case, where the defendant is officially charged with the crime, is notified whether they will be held on bail, and asked to enter a plea. Defendants may also be informed of other related details (e.g., issuance of protective orders). |
| 1.0 Case Initiation Processing | 1.6 Determine Bail Recommendation | Prior to the arraignment, determine whether bail should be recommended or if there is justification to keep a defendant in custody. If bail is recommended, submit the bail recommendation to the judge to determine if bail should be set and for how much. |
| 1.0 Case Initiation Processing | 1.7 Manage Defendants (In or Out of Custody) | Manage the status of in or out of custody defendants. Track arrest and detainment process for in-custody defendants as well as ensure that out-of-custody defendants are participating in prosecutorial process as required. |
| 2.0 Case Flow Processing | 2.1 Assign Case | Upon accepting the case from the filing agency, assign the case to appropriate OCDA staff including Attorneys, Clerks, Investigators, etc. |
| 2.0 Case Flow Processing | 2.2 Submit Charging Documents | File formal charging documents against a defendant with the court, indicating the initiation of an official criminal and/or civil case. |
| 2.0 Case Flow Processing | 2.3 Submit and Issue Protective Orders | Submit protective order requests and receive/manage court orders outlining scope of protections for victims and witnesses while the criminal case is active. These protective orders can include domestic violence protection orders, restraining orders, no contact orders, etc.) |
| 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Manage hearings for a case. This includes calendar management, filing ad responding to hearing reset requests. Hearing types include initial appearances, pre-trial hearings, preliminary hearings, etc. |
| 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Monitor and capture the final outcomes of a case. |
| 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Generate and offer a plea agreement which proposes to the defense and the court a resolution of a defendant’s case and modifies charges and/or other terms, if the defendant agrees to the terms of the agreement. This may include a guilty or no contest plea. |
| 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Prepare for and conduct hearings on a case where evidence is presented to the judge to determine if and how to move forward with the case. This includes preliminary hearings, pre-trial hearings, etc. |
| 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Prepare and file motions or responses (e.g., oppositions) with the court, requesting that the court provided decision or path forward on a specific aspect or activity on a case (e.g., oppose a motion to dismiss a charge at pretrial hearing). |
| 4.0 Evidence Management | 4.1 Manage Discovery Process | Identify and collect all materials that should be made discoverable on a case. Track the provision of discovery materials to the defense as required and any modifications to those materials including bates stamping and redactions. Propound and respond to discovery requests made pursuant to Civil Discovery Act. |
| 4.0 Evidence Management | 4.2 Manage Evidence | Collect, store, and track the inventory of paper, digital, and other forms of evidence related to a case. This may include the production of copies or providing direct access to the Defense as part of the Discovery Process. |
| 5.0 Trial Processing | 5.1 Manage Trial Preparation | Collect, organize, and prepare case materials (e.g., evidence) including tech services, transcriptions, graphics, IT, etc. and complete case actions (e.g., collect testimony, complete operational tasks, etc.) for a case to be presented in trial. |
| 5.0 Trial Processing | 5.2 Manage Jury Selection | Prepare for and interview prospective jurors, including preparation for Voir Dire and Voir Dire questionnaires. |
| 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Design, develop, and present a presentation which visually narrates the facts, evidence, and other related details of the case. |
| 5.0 Trial Processing | 5.4 Prepare Jury Instructions | Provide recommendations for instructions to the selected jurors that present and describe applicable laws and legal processes related to the duties and responsibilities of the jury. |
| 5.0 Trial Processing | 5.5 Prepare Sentencing Recommendation | Following the submission of charging documents, determine and document a sentencing recommendation to be shared with the court for consideration. |
| 5.0 Trial Processing | 5.6 Track 3rd Party Trial Involvement | Manage the involvement of third parties (i.e., a person, group, or entity independent of the prosecution and the defendant) on a case |
| 6.0 Case Support Service Management | 6.1 Manage Victim Services/Assistance | Provide and manage a variety of services to support the victims affected by a case. These services can include emergency assistance, counseling, court escort assignment, and crisis intervention. |
| 6.0 Case Support Service Management | 6.2 Manage Restitution and Compensation | Generate and submit motions for restitution to provide funds to the victims affected by a case. When appropriate, track restitution payments made prior to judgment and sentencing. Orange County Probation, California State Victim Compensation Board, and Waymakers are in charge of handling the restitution process for all criminal cases. The District Attorney’s office is in charge of handling restitution for civil cases. |
| 6.0 Case Support Service Management | 6.3 Manage Witnesses | Identify, interview, and collect testimony from witnesses on a case. Schedule witnesses for hearings and manage communications. |
| 6.0 Case Support Service Management | 6.4 Manage Warrants | Prepare and file probable cause affidavit and warrant requests. Review and manage warrants aka writs issued by the court that authorizes an action that would otherwise be considered unlawful (e.g., search and seizure, arrest, etc.). |
| 6.0 Case Support Service Management | 6.5 Manage Subpoenas | Issue, review, and manage subpoenas aka writs issued to compel testimony and/or produce evidence on a case. Subpoenas can be issued by the prosecution, defense, or the court. |
| 6.0 Case Support Service Management | 6.6 Conflict (Recusal) Management | Removal of a prosecutor or the entire OCDA office to prosecute a case due to a known or newly reported conflict of interest. |
| 6.0 Case Support Service Management | 6.7 Manage Confidential Informants | Identify and manage witnesses that can provide information on cases being investigated or prosecuted while maintaining their confidentiality. |
| 6.0 Case Support Service Management | 6.8 Manage DNA Program | Support the investigation and reporting of cases through the collection of DNA samples that are compared to DNA evidence collected within a crime scene. |
| 7.0 Investigation Management | 7.1 Provide Trial Support | Support prosecution during the trial to uncover facts, collect additional evidence, analyze case information / documentation, provide testimony. |
| 7.0 Investigation Management | 7.2 Investigate incoming arresting agency filings | Provide investigative support to prosecution and law enforcement agencies for select cases initiated by law enforcement agencies. Activities include additional evaluation of a case and its merits, developing leads for additional witnesses, witness interviews, evidence collection, etc. |
| 7.0 Investigation Management | 7.3 Investigate internal DA Investigations/cases | Provide investigative support to prosecution on select cases and investigations that may lead to the filing of charges, initiated internally by the District Attorney’s office. Activities include additional evaluation of a case and its merits, developing leads for additional witnesses, witness interviews, evidence collection, etc. |
| 8.0 Special Case Management | 8.1 Manage Grand Jury Cases | Investigate and complete subsequent case actions (e.g., collect testimony) for select serious state felony cases that will be presented to the Grand Jury. Prepare and present to the Grand Jury. |
| 8.0 Special Case Management | 8.2 Manage Juvenile Cases | Investigate, prosecute, and complete subsequent case actions for juvenile cases, cases involving defendants under the age of 18. |
| 8.0 Special Case Management | 8.3 Manage Extradition | Initiate and manage process of ensuring that an individual (defendant or witness) is delivered to Orange County for trial. |
| 8.0 Special Case Management | 8.4 Manage Special Filings and Cases | Investigate, prosecute, and complete subsequent case actions (e.g., collect testimony) for special filings and cases. |
| 8.0 Special Case Management | 8.5 Manage Public Integrity Unit | Oversee the initiation, investigation, and prosecution of cases where alleged criminal misconduct took place. |
| 8.0 Special Case Management | 8.6 Manage SVP / MDO Cases | Investigate, prosecute, and complete subsequent case actions (e.g., collect testimony) for SVP and MDO cases, cases involving alleged sexual violent predators (SVP) and Mentally Disordered Offenders. |
| 8.0 Special Case Management | 8.7 Manage Mental Health Cases | Investigate, prosecute, and complete subsequent case actions (e.g., collect testimony) for cases involving defendants with alleged mental health disorders / illnesses. |
| 8.0 Special Case Management | 8.8 Manage Public Records Act Requests | Receive and fulfill requests from the public through the Public Records Act. These requests can be sent via email, online on the OCDA website, or on paper. The requests must be responded to promptly within 14 days as required by law. |
| 9.0 Diversion Case Management | 9.1 Determine Diversion Eligibility | Determine if the defendant in a case is eligible to participate in a diversion program, deferring further proceedings while the qualifying defendant completes their court-ordered diversion program. |
| 9.0 Diversion Case Management | 9.2 Manage Diversion Programs | Track cases and defendants entering diversion programs and anticipated completion date. |
| 9.0 Diversion Case Management | 9.3 Monitor Diversion Compliance | Ensure qualifying defendants participating in a diversion program, are meeting the requirements / expectations of their assigned program. |
| 9.0 Diversion Case Management | 9.4 Manage Treatment Courts | Manage cases assigned to alternative treatment courts that provide supervision of judicial system and rehabilitation programs for specific qualifying cases. These cases include defendants dealing with drug addiction, mental illness, etc. |
| 10.0 Post-Disposition Processing | 10.1 Manage Post-Adjudication Compliance | Ensure that defendants are completing the actions and compliant to the terms of the judgement and sentence of a case. |
| 10.0 Post-Disposition Processing | 10.2 Manage Writs and Appeals | Review and revisit cases whose convictions are being appealed or challenged (aka by Writ) by one or more parties involved in the original case. |
| 10.0 Post-Disposition Processing | 10.3 Apply Re-Sentence Adjustments | Adjustment and re-application of a criminal sentence due to an issue / error with the original sentence and / or as a result of a change in statute. Re-sentencing adjustments can be initiated by the defendant, by statute, by the DA, or by the Court of Appeal. This also includes cases of clemency and / or pardons. |
| 10.0 Post-Disposition Processing | 10.4 Expunge Records | Receive expungement orders and manage the expunging of case records, cases where the arrest or conviction is erased from the defendant's criminal history. |
| 10.0 Post-Disposition Processing | 10.5 Seal Records | Receive and manage orders to seal case records, cases where the arrest or conviction are made private but remain on a defendant's criminal history. |
| 10.0 Post-Disposition Processing | 10.6 Manage Post Conviction Litigation | Review and manage actions taking place after the initial adjudication of a case. These actions include post-conviction petition and motions authorized by statute, post-conviction Brady compliance and post-conviction restitution issues. |
| 10.0 Post-Disposition Processing | 10.7 Manage Conviction Integrity | Prevent, identify, and remediate false or otherwise erroneous case convictions. |
| 10.0 Post-Disposition Processing | 10.8 Probation Management | Monitor probation activities and compliance to determine need to intercede (motion to revoke) or otherwise advise the court on subsequent actions. |
| 10.0 Post-Disposition Processing | 10.9 Parole Management | Monitor parole activities and compliance to determine need to intercede (motion to revoke) or otherwise advise the court on subsequent actions. |
| 11.0 Reporting and Analytics | 11.1 Manage Internal and Statutory Reporting | Collecting, compiling, and aggregating data reports to be submitted internally and externally to regulatory agencies. |
| 11.0 Reporting and Analytics | 11.2 Develop Custom Reports | Collecting, compiling, and aggregating data to fulfill one-off reporting requests based on user-defined criterion. |
| 11.0 Reporting and Analytics | 11.3 Manage KPIs (e.g., Grant, Performance etc.) | Establishing, measuring, and monitoring key performance indicators that support the District Attorney’s office in measuring the effectiveness of their business operations, programs, and prosecutorial process. |
| 12.0 Solution Management | 12.1 Manage Administrative Dashboard | Manage dashboards that enable managers, supervisors, and system administrators to manage their teams, processes, and workflows across the three divisions (Legal, Bureau of Investigations, Administration). This includes user authorizations, case assignments, workflow queue management, etc. |
| 12.0 Solution Management | 12.2 Track Assignments/ Workloads | Assign, track and monitor case assignments and workloads across the entire prosecutorial team to ensure efficient and effective distribution of case assignments to the appropriate teams / individuals. Cases can be assigned to individuals or teams of individuals (e.g., Mental Health Unit). |
| 12.0 Solution Management | 12.3 Manage Justice Partner Integrations | Manage and monitor the receipt, transmission, and transfer of data from justice partners. This includes law enforcement agencies, courts, etc. |
| 12.0 Solution Management | 12.4 Manage Public/Authorized User Portal Access | Manage public and authorized access to the the Public and Authorized User Portal that supplies data and information on prosecutorial cases to the public and a variety of authorized users including witnesses, victims, victim advocates, defense attorneys, etc. |
| 12.0 Solution Management | 12.5 Workflow Management | Organization and coordination of staff and their assigned activities that need to be completed as part of the prosecution process. |
| 12.0 Solution Management | 12.6 Data Analysis / Performance Management | Develop business cases and data views to provide data insights to better manage and achieve goals of OCDA. |
| 12.0 Solution Management | 12.7 Case Record Management | Update, maintain, manage overall case records to ensure most accurate, up-to-date, data, information, and documents are included. |
Functional Requirements
| County of Orange, Office of the District Attorney (OCDA) |
| Request for Proposal |
| Functional Requirements - Response Template |
Req ID Level 0 Capability Level 1 Capability Functional Requirements Vendor Response Comment Required Vendor Comment (Required when response is either G, C, 3, or F)
| FN1 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to manually create a new case or defendant record and enter details (e.g. defendant info, agency name, victim name, booking information, custody location, etc.) for an incoming case recommended for prosecution by external (e.g., law enforcement agencies) or internal parties (e.g. prosecutor) | |
| FN2 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to attach documents, images, audio, etc. to the case or defendant record for an incoming case (e.g. arrest report, initial evidence, Photos, Bond Receipts, Coroner's Report, Countywide Warrant, Financial Records, Gang Predicates, Lab Receipts, Medical Records, Misdemeanor Package, etc.) | |
| FN3 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to apply a set of consecutive numbers (bates stamps) to consecutive pages of each document submitted as part of the case record | |
| FN4 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to automatically present a new incoming case record as part of a user's work queue for cases transmitted from integrated law enforcement agency system(s) | |
| FN5 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to automatically transfer relevant data, details, and information (e.g. Court case number, crimes committed, etc.) from the integrated law enforcement agency system(s) as part of the newly created case or defendant record in the CMS | |
| FN6 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to assign a case review status (e.g. received, in-review, accepted/ denied, more information is required, etc.) to an incoming case | |
| FN7 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to assign statutory reporting codes (e.g. DOJ code) | |
| FN8 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to auto-generate and assign a case number to an incoming case based on configurable criteria (e.g. case type, courthouse, case nature, etc.) | |
| FN9 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to access and maintain all previous and active case records as part of a comprehensive case record for each defendant (e.g. warrants, arrest records, custody status, court dispositions, etc.) | |
| FN10 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to document the location where each offense supposedly took place for an incoming case | |
| FN11 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to reopen a previously closed or completed case for subsequent action (e.g. refile, appeal, refer for diversion, etc.) | |
| FN12 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to review and confirm acceptance of an incoming case automatically marking the case as an initiated case in the CMS | |
| FN13 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to manually and automatically (based on configurable rules) assign a case intake request to a particular unit for case processing | |
| FN14 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to re-submit/add new information including documentation for a previously submitted case | |
| FN15 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to select a case type for a new case which triggers a particular workflow | |
| FN16 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to reject a case and document justification for rejection (i.e. rejection code) | |
| FN17 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to flag a case to the submitting agency to signal that the case has been rejected | |
| FN18 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to flag cases that have been rejected and require further response / clarification | |
| FN19 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to share status of review (e.g., accepted, rejected, needs further investigation, etc.) for incoming arresting agency filings with the initiating agency | |
| FN20 | 1.0 Case Initiation Processing | 1.1 Conduct Case Intake | Ability to review and confirm acceptance of an incoming case automatically marking the case as an initiated case in the CMS | |
| FN21 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to automatically retain a copy of the case record at time of filing (aka what was sent over to the DA as part of the initial filing) | |
| FN22 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to configure case types where race blind charging will apply | |
| FN23 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to automatically redact and hide specified case data (e.g. race, ethnicity, etc.) from view after case intake request is received, for applicable case types | |
| FN24 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to document the charging decision with redacted case data | |
| FN25 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to make visible the case data after the initial charging decision is generated | |
| FN26 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to track changes made to the charging decision before and after the data is made visible | |
| FN27 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to require written justification when changes are made to the original charging decision after the data is made visible | |
| FN28 | 1.0 Case Initiation Processing | 1.2 Manage Race Blind Charging Compliance | Ability to exclude a case from race blind charging that otherwise would have been subjected to it and require written justification be provided for the exception | |
| FN29 | 1.0 Case Initiation Processing | 1.3 Generate Charging Instruments | ability to create and update a charging code table that outlines each charging code, the crimes they’re associated with, and other charge related details (e.g., enhancements, allegations, priors) | |
| FN30 | 1.0 Case Initiation Processing | 1.3 Generate Charging Instruments | Ability to assign initial charges to a case based on a listing of configurable offense codes that include both state and local charges, allegations, enhancements, etc. | |
| FN31 | 1.0 Case Initiation Processing | 1.3 Generate Charging Instruments | Ability to generate a charging document that outlines the initial charges (including assigned charging codes) to be filed with the Court | |
| FN32 | 1.0 Case Initiation Processing | 1.3 Generate Charging Instruments | Ability to document and track all allegations and subsequent charges throughout the life of a case | |
| FN33 | 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Ability to manually and automatically (based on configurable rules) document and track defendant and case information and appearance status as a result of the initial appearance | |
| FN34 | 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Ability to document and track defendants appearance at a hearing (appeared, failure to appear, etc.) | |
| FN35 | 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Ability to document and track bail options and other matters to be presented at the initial appearance | |
| FN36 | 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Ability to record the defendant's response to the charges by entering a plea (e.g. guilty, not guilty, or no contest to the charges) | |
| FN37 | 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Ability to enter the bail amount set at arraignment | |
| FN38 | 1.0 Case Initiation Processing | 1.4 Manage Initial Appearance | Ability to generate a request for warrant (e.g., for a defendant that failed to appear at a hearing) | |
| FN39 | 1.0 Case Initiation Processing | 1.5 Conduct Arraignments | Ability to capture and track indigency claim and ruling | |
| FN40 | 1.0 Case Initiation Processing | 1.5 Conduct Arraignments | Ability to search within the CMS and view past bail / release recommendations and conditions based on specified criterion (e.g., case types, defendant history, etc.) | |
| FN41 | 1.0 Case Initiation Processing | 1.5 Conduct Arraignments | Ability to track compliance with bail conditions, including uploading associated documents (e.g., responsive documents for PC 1275.1 compliance) | |
| FN42 | 1.0 Case Initiation Processing | 1.6 Determine Bail Recommendation | Ability to enter the bail amount set at arraignment, including whether a hold has been placed and/or other restrictions imposed (e.g., passport). | |
| FN43 | 1.0 Case Initiation Processing | 1.6 Determine Bail Recommendation | Ability to create and update bail schedule(s) to assist in determining and setting appropriate bail recommendations | |
| FN44 | 1.0 Case Initiation Processing | 1.6 Determine Bail Recommendation | Ability to automatically generate bail recommendations based on configurable business rules and case data | |
| FN45 | 1.0 Case Initiation Processing | 1.6 Determine Bail Recommendation | Ability to document and track identifying details and information for each defendant as part of a master person record (e.g. previous cases, aliases, DOB, SSN, language issues, developmental disabilities, immigration issues, housing status, mental health status, physical health, substance use, veteran, tattoos, physical address, etc.) | |
| FN46 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability for the solution to suggest the defendant name based on previously saved defendant records | |
| FN47 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to add and track co-defendants on the same case record | |
| FN48 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to add and track defendants on separate case records | |
| FN49 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to create a defendant 'group' profile and associate multiple defendants to it (e.g., XYZ gang profile) | |
| FN50 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to link the newly accepted case to a defendant's existing case record | |
| FN51 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to receive custody information (e.g., location) of a defendant electronically from a law enforcement agency | |
| FN52 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to manually create and update a defendant person record in the system | |
| FN53 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to merge multiple defendant person records into one person record | |
| FN54 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to enter and track defendant relationships (including but not limited to gang affiliation, family, romantic relationship, etc.) | |
| FN55 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to add unique identifiers to a defendants person record based on pre-determined criterion (e.g. CSEC, eSCARS, etc.) | |
| FN56 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to enter standard details (e.g., name, home address, gang affiliation, etc.) into the defendant's person record | |
| FN57 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to associate a person record with a case and make updates accordingly without updating the master person record | |
| FN58 | 1.0 Case Initiation Processing | 1.7 Manage Defendants (In- or Out-of Custody) | Ability to assign and re-assign multiple users to a case to one or multiple workflow steps and/or activities to take place during case life cycle (e.g. prosecution, investigator, defense counsel, hearing attendees, defense expert witness, etc.) | |
| FN59 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability to assign an entire team to a case | |
| FN60 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability for multiple individuals assigned to a team to have the same or different roles (flexible assignments) | |
| FN61 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability for users assigned to a case to add additional users to a case | |
| FN62 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability to assign and reassign cases in bulk | |
| FN63 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability to assign roles / responsibilities to each user on a case | |
| FN64 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability to automatically assign activities (e.g. charging document generation) to be completed based on the roles / responsibilities assigned to each user on a case and other configurable business rules | |
| FN65 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability to maintain history of staff assignments with the caseloads by individual, departments, and teams | |
| FN66 | 2.0 Case Flow Processing | 2.1 Assign Case | Ability to submit charging documents to the Courts | |
| FN67 | 2.0 Case Flow Processing | 2.2 Submit Charging Documents | Ability to apply an esignature to charging instruments | |
| FN68 | 2.0 Case Flow Processing | 2.2 Submit Charging Documents | Ability to e file charging documents with the Court | |
| FN69 | 2.0 Case Flow Processing | 2.2 Submit Charging Documents | Ability to generate a request to submit protective orders | |
| FN70 | 2.0 Case Flow Processing | 2.3 Submit and Issue Protective Orders | Ability to receive protective orders electronically from the Court | |
| FN71 | 2.0 Case Flow Processing | 2.3 Submit and Issue Protective Orders | Ability to manage and monitor the status of requests for protective orders | |
| FN72 | 2.0 Case Flow Processing | 2.3 Submit and Issue Protective Orders | Ability to enter and track details related to the protective order once it is issued (e.g., life span of order, description of order, parties involved, etc.) | |
| FN73 | 2.0 Case Flow Processing | 2.3 Submit and Issue Protective Orders | Ability to track issuance of and compliance with protective orders | |
| FN74 | 2.0 Case Flow Processing | 2.3 Submit and Issue Protective Orders | Ability to automatically notify a user of a conflict (e.g. via a conflict warning pop up) when hearing dates are selected and one or multiple selected participants are unavailable | |
| FN75 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to prompt designated users to request a continuance when the prosecutor and alternate prosecutor are not available to participate in the hearing | |
| FN76 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to view individual Court calendars displaying hearings and other event details | |
| FN77 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to view court and other resource availability (e.g. courtroom availability, bailiffs, etc.) on individual calendars | |
| FN78 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to subscribe to external calendars and share calendar externally | |
| FN79 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to generate and file reset requests based on conflicts | |
| FN80 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to automatically update the case record once hearings and other events are scheduled by the Court (e.g. case initiation, managing hearings, trial dates, child dependency, civil forfeiture, etc.) | |
| FN81 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to electronically receive and display available hearing dates for a particular case (or cases) on individual calendars | |
| FN82 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to update case record with updated hearing dates and associated details (case number, defendant name, etc.) | |
| FN83 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to flag case documents to be part of a calendar event for parties to access during hearings | |
| FN84 | 2.0 Case Flow Processing | 2.4 Set and Track Hearing Dates | Ability to keep record of case disposition received from the integrated Court system and any manual updates made thereafter | |
| FN85 | 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Ability for case disposition and associated details to be automatically updated based on data transmitted from the Court system (e.g. disposition at case/party record level as well as at charge level; disposition for special allegations, etc.) | |
| FN86 | 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Ability to access comprehensive view of all case dispositions within a case record | |
| FN87 | 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Ability to manually add case disposition and associated details (e.g. bail amount, hearing dates, orders, conditions, verdicts, minute orders, findings, etc.) | |
| FN88 | 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Ability to transmit case disposition and associated details from the integrated Court system (i.e. Vision) | |
| FN89 | 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Ability to capture sentencing conditions (e.g., whether each sentence on each charge/allegation is ordered consecutively or concurrently per charge/allegation, if the sentence is ordered for the overall case, credits for time served, etc.) | |
| FN90 | 2.0 Case Flow Processing | 2.5 Manage Case Dispositions | Ability to lock / unlock plea offer parameters | |
| FN91 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to generate a plea offer for a case and submit to the Court for review and approval | |
| FN92 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to generate a plea offer across multiple cases and submit to the Court for review and approval | |
| FN93 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to automatically send and receive final plea offer to the defense (e.g. via an integration with eDefender) | |
| FN94 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to track all activities, actions taken, and outcomes of the plea agreement negotiation process with the defense (e.g. plea agreement offer, counteroffers, dates of communication, evidence utilized to support plea) | |
| FN95 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to extend multiple plea offers on a case | |
| FN96 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to put an end date on a Plea Offer that would change the status to withdrawn or expired automatically, if not modified | |
| FN97 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to define parameters for plea offers based on the charge level and degree | |
| FN98 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to review and approve a proposed plea offer electronically | |
| FN99 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to review and approve proposed departures from office guidelines on certain / exceptional plea offers | |
| FN100 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to generate global plea offers that include multiple cases for the same defendant in more than one courthouse | |
| FN101 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to track changes made to the plea agreement (e.g. extension to plea agreement) | |
| FN102 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to select one or more cases involved with the plea agreement | |
| FN103 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to track the plea offer issued by the court | |
| FN104 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to track updates made to plea offers | |
| FN105 | 3.0 Manage Pre-Trial Events | 3.1 Manage Plea Offers | Ability to create a pre-trial checklist where users can mark progress of actions / activities | |
| FN106 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to create and maintain individual profiles for all Judges to track their case loads and overall trends (e.g., case disposition) | |
| FN107 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to select and assemble hearing packets with relevant details, information, and documentation (e.g. witness information, witness testimonials / transcripts, evidence, etc.) for a case to be made accessible offline and/or outside of the application | |
| FN108 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to record communications with the Judge and results of each hearing (e.g. further arraignment required, charges reduced, dismissed, etc.) and associate them with the relevant hearing (e.g. preliminary, pre-trial, trial, etc.) | |
| FN109 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to upload and link hearing transcripts and associate them with the relevant hearing within the case record | |
| FN110 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to record and link documents (e.g. motions, etc.) submitted and filed as part of each hearing to the case record | |
| FN111 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to flag evidence that cannot be used in the case, based on outcome of the hearing | |
| FN112 | 3.0 Manage Pre-Trial Events | 3.2 Conduct Hearings | Ability to generate and edit motions (e.g. suppression of evidence) and associate them with the relevant activity (e.g., hearing) within the case record | |
| FN113 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to search and select a standard template relevant to the motion at hand | |
| FN114 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability for the solution to automatically recommend motion templates to utilize based on pre-defined criteria | |
| FN115 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to file (manual or eFile) motions with the Courts | |
| FN116 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to document rulings resulting from the motions that are issued by Court | |
| FN117 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to receive motions from defense and create notification to attorney for review | |
| FN118 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to generate a response and to link that response to the original motion | |
| FN119 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to receive an order from the court, and link that order to the original motion | |
| FN120 | 3.0 Manage Pre-Trial Events | 3.3 Prepare and File Motions | Ability to automatically suggest relevant discovery based on case parameters (e.g., charges, agency, etc.) and generate a discovery request | |
| FN121 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to associate fees with discovery documents | |
| FN122 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to monitor fees charged and paid for discovery documents | |
| FN123 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to capture status of a discovery request (requested, provided, not provided, destroyed, etc.) | |
| FN124 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to propound and respond to discovery requests made pursuant to Civil Discovery Act (e.g., requests for admissions, requests for production) | |
| FN125 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to group evidence based on what step of the workflow it is relevant to (e.g., pre-trial, trial, etc.) | |
| FN126 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to upload multiple pieces of evidence or discovery files at once (e.g. uploading a zipped folder including multiple JPEG images) | |
| FN127 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to automatically send confirmation letters, outlining all evidence and discovery files associated with the case record | |
| FN128 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to notify users assigned to a case, that the witness or defendant on the case has a sealed file | |
| FN129 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Track modifications made to discovery materials, including bates stamping and redactions | |
| FN130 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to send and track notices sent to defense about availability of discovery | |
| FN131 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to override 'discoverable' classification based on configurable criteria. | |
| FN132 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to set a parameter to prevent other users from overriding the 'discoverable' classification | |
| FN133 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to store (if necessary), track, and maintain record of all discoverable files and / or case information (e.g. evidence, motions, etc.) as part of the case record | |
| FN134 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to link discoverable files and / or case information (e.g. evidence, motions, etc.) stored in external applications (e.g. evidence.com) as part of the case record | |
| FN135 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to conduct discovery on case files and / or case information (e.g. evidence, motions, etc.) | |
| FN136 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to mark which files and / or case information (e.g. evidence, motions, etc.) will be considered discoverable (aka be shared with the defense to be presented as part of the trial) | |
| FN137 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to provide justification for files and / or case information (e.g. evidence, motions, etc.) marked as 'not discoverable' | |
| FN138 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability for the system to gather all files marked as discoverable and share them with the defense | |
| FN139 | 4.0 Evidence Management | 4.1 Manage Discovery Process | Ability to track existence and location of physical evidence, sensitive evidence or evidence stored in offline locations | |
| FN140 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track information related to the submission, request and possession of physical evidence (e.g. submitter of evidence, last requested by, in possession of, date/time last requested, etc.) | |
| FN141 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track location of physical case records and identify which cases are scanned and available electronically or are stored physically in the warehouse | |
| FN142 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to generate and capture barcodes assigned to physical evidence | |
| FN143 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to enable password protection to limit access to specific evidence files | |
| FN144 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track all evidence submitted to the Court as part of a case (e.g., physical evidence, forensic evidence, witness testimony, etc.) | |
| FN145 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track the status of evidence submission to the Courts (e.g., submitted, admitted, suppressed, etc.) | |
| FN146 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to apply OCR to digital evidence files so that documents are searchable | |
| FN147 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to rename an evidence file while logging all previously assigned names, including the originating name | |
| FN148 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to view thumbnails of evidence files | |
| FN149 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability annotate evidence files | |
| FN150 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to retain a copy of the original unannotated version of the evidence file | |
| FN151 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to send a request to an internal team to convert copies of evidence files (that are otherwise not viewable or playable) | |
| FN152 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to upload and /or associate a case with converted evidence files | |
| FN153 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track return of original file and versioning of converted file | |
| FN154 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to mark whether an evidence file was converted | |
| FN155 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track an activity log for each piece of evidence (e.g., last opened, last shared, etc.) | |
| FN156 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to associate the same evidence file with multiple case records | |
| FN157 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to create evidence checklists based on configurable criteria that automatically apply based on the case type selected | |
| FN158 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to upload supplementary visuals to be used as part of the trial presentation workbook | |
| FN159 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to assign multiple attorneys to a case at trial team, designating role as 1st chair, 2nd chair, etc. | |
| FN160 | 4.0 Evidence Management | 4.2 Manage Evidence | Ability to track the disposition of evidence introduced as exhibits at hearings and/or trial and recommend actions for retention and disposition of evidence | |
| FN161 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to merge multiple case summary notes into a single unified note | |
| FN162 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to submit single or merged case summary notes to users for review | |
| FN163 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to document and track all activities completed and actions taken in preparation for trial | |
| FN164 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to select one or multiple discovery files (including evidence) to be excluded from use by the defense during trial | |
| FN165 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to select and assemble trial packets with relevant details, information, and documentation (e.g. witness information, witness testimonials / transcripts, evidence, etc.) for a case to be made accessible offline and/or outside of the application | |
| FN166 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to flag discovery files that are excluded from consideration during trial | |
| FN167 | 5.0 Trial Processing | 5.1 Manage Trial Preparation | Ability to capture configurable attributes of the final jurors selected | |
| FN168 | 5.0 Trial Processing | 5.2 Oversee Jury Selection | Ability to document if and when a prosecutor challenges or outright rejects the placement of one or multiple jurors on a case | |
| FN169 | 5.0 Trial Processing | 5.2 Oversee Jury Selection | Ability to document a reason for rejection for each juror challenged / rejected by a prosecutor | |
| FN170 | 5.0 Trial Processing | 5.2 Oversee Jury Selection | Ability to capture internal notes on each juror | |
| FN171 | 5.0 Trial Processing | 5.2 Oversee Jury Selection | Ability to view requests for alternate juror assignments | |
| FN172 | 5.0 Trial Processing | 5.2 Oversee Jury Selection | Ability to search for, organize, and compile data and information from the case record and copies of case files to be used as part of the trial presentation workbook on a case | |
| FN173 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability to select, structure, and organize evidence to be utilized as part of the trial presentation | |
| FN174 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability to annotate case files as part of the trial presentation workbook | |
| FN175 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability to access the trial presentation on a mobile device (e.g. Mobile tablet) | |
| FN176 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability for multiple users to collaboratively review and annotate documents simultaneously to be included as part of the trial presentation for a case | |
| FN177 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability to prepare, edit, and compile verdict information for the Court | |
| FN178 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability to capture all individuals appearance at or participating in a proceeding | |
| FN179 | 5.0 Trial Processing | 5.3 Conduct Trial Presentation | Ability to store jury instructions submitted by the Court | |
| FN180 | 5.0 Trial Processing | 5.4 Prepare Jury Instructions | Ability to edit and update Court submitted jury instructions |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .