Attachment A PD Case Management RFP Requirements.xlsx
XLSX spreadsheet 216 KB Posted
- Attached to
- CASE MANAGEMENT SYSTEM
- Solicitation number
- 215343
- Issued by
- Niobrara County, Wyoming
About this file
This is a functional requirements specification document for a Case Management System (CMS) procurement by the State of Wyoming, Office of the State Public Defender (OSPD). The solicitation requests proposals for a comprehensive case management solution to support public defender operations, with proposals due by 2:00 p.m. Mountain Time on October 2, 2026. Written questions must be submitted through the Public Purchase online bidding system by 2:00 p.m. Mountain Time on September 8, 2026. The specification document outlines 96 information technology requirements and 45 business requirements that the proposed system must address, covering core case management functionality, calendaring and scheduling, reporting and analytics, accessibility, system administration and security, data security and privacy, integration capabilities, and system maintenance and support. All submission materials must be uploaded completely through the Public Purchase system by the deadline, with incomplete uploads deemed non-responsive and subject to elimination from evaluation.
The requirements document employs a standardized response methodology requiring vendors to indicate how each specification is satisfied using six options: Y (yes—out-of-box functionality), R (reporting tools), T (third-party functionality), M (must include—custom modifications), F (future availability within one year), or N (not available). The IT requirements include mandatory compliance with 26 Wyoming Enterprise Technical Standards (WyIT) policies covering IT operations, data privacy, security, and information management, as well as two additional data destruction standards. Business requirements emphasize usability, data consistency with audit trail capabilities, support for existing case weighting systems, customizable reporting across multiple parameters, secure document management, and integration with Google Calendar and File and Serve Express electronic filing systems. The system must be cloud-based, fully accessible online without license charges for external users, support role-based access controls, provide end-to-end encryption, and comply with federal, state, and local data protection regulations including CJIS and HIPAA standards.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Attachment A PD Case Management RFP Requirements Revision 2.xlsx | XLSX spreadsheet | |
| RFP 0046-N.pdf | ||
| Sample IT Contract.pdf | ||
| Sample Closing Sheet.pdf | ||
| RFP 0046-N Addendum 1.pdf |
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
| Instructions | |
| The vendor must provide an answer for each numbered specification with 1 of the following 6 options. Additionally, on each tab, please provide the Company and Solution Name where indicated. | |
| Company Name: | |
| Product(s) Name: |
| Answer | Definition |
| Y | YES - Functionality is provided out of the box through the completion of a task associated with a routine configurable area that includes, but is not limited to, user-defined fields, delivered or configurable workflows, alerts or notifications, standard import/export, table driven setups and standard reports with no changes. These configuration areas will not be affected by a future upgrade. The proposed services include implementation and training on this functionality, unless specifically excluded in the Statement of Work, as part of the deployment of the solution. |
| R | REPORTING - Functionality is provided through reports generated using proposed Reporting Tools. |
| T | THIRD PARTY - Functionality is provided by proposed third party functionality (i.e., third party is defined as a separate software Vendor from the primary software Vendor). The pricing of all third-party products that provide this functionality MUST be included in the cost proposal. |
| M | MUST INCLUDE - Functionality is provided through customization to the application, including creation of a new workflow or development of a custom interface, that may have an impact on future upgradability. The pricing of all modifications identified in the functional requirements MUST be included in the cost proposal. |
| F | FUTURE AVAILABILITY - Functionality is provided through a future general availability (GA) release that is scheduled to occur within 1 year of the proposal response. |
| N | N/A - Functionality is not provided |
IT
| Company/Product Name: | ||||
| IT | ||||
| Line # | MoSCoW | Description | Vendor Response: Y,R,T,M,F,N | Notes/Comments/Reference to Location in RFP Response |
| Core Case Management | ||||
| IT-1 | Must Have | Ability to manage client information, case details, and legal documentation | ||
| IT-2 | Must Have | Tracking of case progress through various stages | ||
| IT-3 | Must Have | Secure storage of all case-related documents, including evidence, motions, court orders, and correspondence | ||
| IT-4 | Must Have | Ability to upload, download, and share files securely | ||
| IT-5 | Must Have | Version control for document edits and updates | ||
| IT-6 | Must Have | The CMS should allow the office to fully own the data stored within the system | ||
| IT-7 | Must Have | The office must retain full ownership of all case data | ||
| IT-8 | Must Have | Archiving function to store closed cases while mantaining historical data | ||
| IT-9 | Must Have | Clear procedures for exporting and backing up data in case of service terminiation or transfer to another platform | ||
| IT-10 | Must Have | Migrate old data into new system | ||
| Calendaring and Scheduling | ||||
| IT-10 | Must Have | Integrated calendaring system to track court dates, deadlines and important case events | ||
| IT-11 | Must Have | Automated system to notify users of upcoming deadlines or court apperances | ||
| IT-12 | Must Have | Synchonzation with attorney calendars (Google Calendar) if needed | ||
| IT-13 | Must Have | Integrate with File and Serve Express electronic filing for importing documents, dates, and deadlines | ||
| Reporting and Analytics | ||||
| IT-13 | Must Have | Automated and customizable reports on caseloads, case status, attorney performance, and other metrics | ||
| IT-14 | Must Have | Date-based reporting for open, closed, or pending cases by various criteria (e.g case type, specific crime case status, attorney, region) | ||
| IT-15 | Must Have | Ability to export reports in multiple formats (PDF, CSV etc) | ||
| IT-16 | Must Have | Ability to assign and track case weight (e.g. felony, misdemeanor, specific crime) for case load balancing | ||
| IT-17 | Must Have | Visualization of case distribution among attorneys, including caseload age, status, and case type | ||
| IT-18 | Must Have | Tracking of attorney caseloads, work distribution, and case outcomes to assit in managing workload and performance evaluations | ||
| IT-19 | Must Have | Provide functionality for users to configure and generate customizable dashboards and ad-hoc, scheduled and automated reports from real-time data | ||
| IT-20 | Must Have | A single, web-based access point for both attorneys and staff, with a powerful search function | ||
| IT-21 | Must Have | The ability to run ad hoc reports on a wide range of data points, including case types, subcases, attorney workloads, and procedural history. | ||
| IT-22 | Must Have | Generating end-of-year statistics requires manual manipulation of data, which is time-consuming and inefficient. | ||
| Accessibility and Usability | ||||
| IT-23 | Must Have | The CMS should be fully cloud- based to allow access from any location, facilitating remote work | ||
| IT-24 | Must Have | The CMS must be compatible with a variety of operating systems and web browsers, utilizing open standards to ensure accessibility | ||
| IT-25 | Must Have | Simple intuitive design to reduce the need for extensive training | ||
| IT-26 | Must Have | Configurable dashboards to allow quick access to relavant information such as upcoming court dates, case status | ||
| IT-27 | Should Have | Fully responsive design with mobile compatibility to allow access on smartphones and tablets | ||
| System Administration and Security | ||||
| IT-28 | Must Have | Centralized admin panel for managing users, permissions, and system settings | ||
| IT-29 | Must Have | User permission based on roles (RBAC) (attorneys, paralegals, databse assistants) to control access to sensitive case information | ||
| IT-30 | Must Have | Ability to assign "databse assistants" who manage day-to-day operations for each office, with backup access for all staff in case of absences | ||
| IT-31 | Must Have | Audit trails to track user activity and changes made in the system | ||
| IT-32 | Must Have | Support for multi-factor authentication to ensure secure access to the system | ||
| IT-33 | Must Have | Detailed user activity logs for accountability and tracking | ||
| Data Security and Privacy | ||||
| IT-34 | Must Have | End-to-end encryption for all data in transit and at rest | ||
| IT-35 | Must Have | Compliance with industry-standard security protocols | ||
| IT-36 | Must Have | Compliance with federal, state, and local laws governing data protection and privacy (e.g. CJIS compliance, HIPAA) | ||
| Integration and Automation | ||||
| IT-37 | Should Have | Intergation with email providers for sending and recieving case-related communication | ||
| IT-38 | Must Have | Intergation with document scanning tools for digitizing case files and discovery | ||
| IT-39 | Must Have | Support for importing data from legacy systems, including assistance with data migration | ||
| IT-40 | Must Have | Automatically generate standard documents (intake forms, case opening letters) upon case creation | ||
| IT-41 | Must Have | Ability to securely upload, store, and organize discovery files minimizing additional equipment costs | ||
| IT-42 | Must Have | System must integrate with File and Serve Express | ||
| IT-43 | Must Have | Seamless integration with other relevant systems used by the office | ||
| System Maintenance and Support | ||||
| IT-44 | Must Have | Scalability to grow with the office's needs without requiring significant upgrades or infrastructure changes | ||
| IT-45 | Must Have | Guaranteed high availability with service level agreements (SLAs) | ||
| IT-46 | Must Have | Redundancy and failover mechanisms to ensure system availability in case of failures | ||
| IT-47 | Must Have | Comprehensive training materials, onboarding assisstance, and customer support | ||
| IT-48 | Must Have | Frequent software updates to improve functionality, security, and performance, with minimal disruption to operation | ||
| Data Validation and Search | ||||
| IT-49 | Must Have | Prompt users for valid field entries, and to not accept invalid entries | ||
| IT-50 | Must Have | All fields in the system must be searchable | ||
| ETS IT Operation Policies | ||||
| IT-51 | Must Have | WyIT - 1001 Agency Controlled Information Technology (IT) Change Management and Maintenance 07/2024 | ||
| IT-52 | Must Have | WyIT - 1002 Electronic Communication Management 07/2024 | ||
| IT-53 | Must Have | WyIT - 1003 Contingency Planning 07/2024 | ||
| IT-54 | Must Have | WyIT - 1004 Web Standards & Compliance 07/2024 | ||
| ETS Data Privacy Policies | ||||
| IT-55 | Must Have | WyIT - 2001 Information Classification 6/2024 | ||
| IT-56 | Must Have | WyIT - 2001 - GL- Information Classification Guidelines 8/2024 | ||
| IT-57 | Must Have | WyIT - 2001 - S - Information Classification Standard 8/2024 | ||
| IT-58 | Must Have | WyIT - 2002 - Data Protection for Electronic Government Services 6/2024 | ||
| IT-59 | Must Have | WyIT - 2002 - GL - Data Loss Prevention Guideline 1/2025 | ||
| IT-60 | Must Have | WyIT - 2003 - Data Backup, Storage and Restoration 6/2024 | ||
| IT-61 | Must Have | WyIT - 2004 - Information Breach 6/2024 | ||
| IT-62 | Must Have | WyIT - 2004 - GL Information Breach Response Guidelines 8/2024 | ||
| IT-63 | Must Have | WyIT - 2005 - Information Residency and Transportation 6/2024 | ||
| IT-64 | Must Have | WyIT - 2006 - Agency Official for Privacy (AOP) 6/2024 | ||
| IT-65 | Must Have | WyIT - 2007 - Data and Privacy Exception Request 6/2024 | ||
| IT-66 | Must Have | WyIT - 2008 - Website Online Maps and Data Disclaimer Policy 6/2024 | ||
| IT-67 | Must Have | WyIT - 2009 - Clean Desk Confidential Information and Sensitive Materials Policy 8/2024 | ||
| IT-68 | Must Have | WyIT - 2010 - Agency Data Sharing Review Frequency Policy 8/2024 | ||
| IT-69 | Must Have | WyIT - 2013 - S - Standard for Electronic Data Destruction and Sanitization Standard 01/2025 | ||
| ETS Security and Privacy Policies | ||||
| IT-70 | Must Have | WyIT - 3023 - Generative Artificial Intelligence Acceptable Use 06/2024 | ||
| IT-71 | Must Have | WyIT - 3001 - General Security Acceptable Use 06/2024 | ||
| IT-72 | Must Have | WyIT - 3001 - S - Sending Encrypted Email Standard 06/2024 | ||
| IT-73 | Must Have | WyIT - 3002 - Security Exception Request 06/2024 | ||
| IT-74 | Must Have | WyIT - 3003 - Information Security 06/2024 | ||
| IT-75 | Must Have | WyIT - 3004 - Security Awareness Training and Education 8/2024 | ||
| IT-76 | Must Have | WyIT - 3005 - Access Controls 8/2024 | ||
| IT-77 | Must Have | WyIT - 3006 - Identification and Authentication 06/2024 | ||
| IT-78 | Must Have | WyIT - 3007 - System and Communication Protection 06/2024 | ||
| IT-79 | Must Have | WyIT - 3008 - Risk Assessment 8/2024 | ||
| IT-80 | Must Have | WyIT - 3009 - Computer Security Threat Response 06/2024 | ||
| IT-81 | Must Have | WyIT - 3010 - Incident Response 06/2024 | ||
| IT-82 | Must Have | WyIT - 3011 - Systems and Services Acquisition 06/2024 | ||
| IT-83 | Must Have | WyIT - 3012 - System and Information Integrity 8/2024 | ||
| IT-84 | Must Have | WyIT - 3013 - Physical and Environmental Protection 8/2024 | ||
| IT-85 | Must Have | WyIT - 3014 - Personnel Security 8/2024 | ||
| IT-86 | Must Have | WyIT - 3015 - Physical Media 06/2024 | ||
| IT-87 | Must Have | WyIT - 3016 - Mobile Device Security 06/2024 | ||
| IT-88 | Must Have | WyIT - 3017 - Remote Access 06/2024 | ||
| IT-89 | Must Have | WyIT - 3018 - Software Use 06/2024 | ||
| IT-90 | Must Have | WyIT - 3019 - Local Administrative Rights 06/2024 | ||
| IT-91 | Must Have | WyIT - 3020 Vulnerability Scanning 062024 | ||
| IT-92 | Must Have | WyIT - 3021 - Patch Management 06/2024 | ||
| IT-93 | Must Have | WyIT - 3022 - Mainframe Security 8/2024 | ||
| IT-94 | Must Have | WyIT - 3025 - Source Code Control Policy 06/2024 | ||
| IT-95 | Must Have | 09400-P221 Policy for Electronic Data Destruction and Sanitization 11/5/18 | ||
| IT-96 | Must Have | 09400-S221 Standard for Electronic Data Destruction and Sanitization 11/5/18 |
https://drive.google.com/file/d/1G3mEc-q2wkzi_O-0qBtUW96J96IRaVO-/view?usp=sharinghttps://drive.google.com/file/d/1VzH3IBcpPPEUadwsjr0880ysiKa4gm86/view?usp=sharinghttps://drive.google.com/file/d/1qLy4P0Uk2v1r5lAghJtDibRUhXCIkTEL/view?usp=sharinghttps://drive.google.com/file/d/1011qnwpHDQGZw1DMs_lbgJGg4d1mdxMk/view?usp=sharinghttps://drive.google.com/file/d/1v-I_YlA4Hr0eP3kEjHBhOiytFqle6ROG/view?usp=sharinghttps://drive.google.com/file/d/15dU5XFf7MbqNaHKnUd-2r6O2bc_2-tyj/view?usp=sharinghttps://drive.google.com/file/d/1_ld3C1LCVH1qpi5lAHhbU7vD9LpNaWmZ/view?usp=sharinghttps://drive.google.com/file/d/1fG2TwRU0LXhzQFNuSBF0k20m16xh8GTV/view?usp=sharinghttps://drive.google.com/file/d/1TLvf8gwIR9rsnCUDgnnAuw59e_kaZLq7/view?usp=sharinghttps://drive.google.com/file/d/1cadvi9uZD4yoOEgTzLGoA_7tm-WeYpsJ/view?usp=sharinghttps://drive.google.com/file/d/11UgBtHxJtdpeTJPSxWHt7AEU3ASGDfiH/view?usp=sharinghttps://drive.google.com/file/d/1jo_dl-n6t9ePALqELiXpXx6P5FVNPj4a/view?usp=sharinghttps://drive.google.com/file/d/10MTMx-S0JZm1ZNjEKEwqZJbk5bUhL8sN/view?usp=sharinghttps://drive.google.com/file/d/1cdjsUHd2caCf2F2A8ifU7eu79dRps-eK/view?usp=sharinghttps://drive.google.com/file/d/1KwWzy5sxaII4l21JY-0CnIZmyTbOtK1_/view?usp=sharinghttps://drive.google.com/file/d/1HsxqmkDJQDZyTM63BmCzZu6lTtD20lE3/view?usp=sharinghttps://drive.google.com/file/d/1kM2IL4kzY_IfSPb-2geMfWTVAIwkthPP/view?usp=sharinghttps://drive.google.com/file/d/1Gg28RMFj_Z1ak31NebLjS22VT9FMAyf4/view?usp=sharinghttps://drive.google.com/file/d/1V3vJ7TVNHB3P8RgvznArAnFx0xxIk_lV/view?usp=sharinghttps://drive.google.com/file/d/1xMK796PfD-84e25UlF3a7vSNmxBJs_lH/view?usp=sharinghttps://drive.google.com/file/d/16Y2ntfbIqbT92RSbnJXRdXbbLq2MI4kv/view?usp=sharinghttps://drive.google.com/file/d/1GRsMT93AjO4DHLN6fwDp_-YKhrvps2zh/view?usp=sharinghttps://drive.google.com/file/d/1io4GT8iCRGJarVaRMshQEhWSw-famRQl/view?usp=sharinghttps://drive.google.com/file/d/1twnEmtlUq9lpTw-1algC7M_S0wBFVHsv/view?usp=sharinghttps://drive.google.com/file/d/15RzOwKk_cEUlTqsoWODreilnO1iG2_ss/view?usp=sharinghttps://drive.google.com/file/d/1fW2JpWLlKpZDkKtnBz1P76Za2xxdNkiA/view?usp=sharinghttps://drive.google.com/file/d/1YdZ7H7GwZcluwZNgqmnzPoDxJ14Trmo4/view?usp=sharinghttps://drive.google.com/file/d/1fb-oV6aJq7n6vgl1_RmuDWJpF5aXAC36/view?usp=sharinghttps://drive.google.com/file/d/15CPyr173avK3jgoWI3nyCBzcq3BQo_1I/view?usp=sharinghttps://drive.google.com/file/d/1n75Q4K9h_JIcFqEe9wRjZvB-ysvBHm5w/view?usp=sharinghttps://drive.google.com/file/d/1pwyC5us2aXEUdQz2QiKKiNtHBFNWsD4Z/view?usp=sharinghttps://drive.google.com/file/d/1TmURvJIgxZ067DX3VWyiSQ19fhU4lj1R/view?usp=sharinghttps://drive.google.com/file/d/1rdf4kYH6amTDUAyYiO86dKglU3tCWu9W/view?usp=sharinghttps://drive.google.com/file/d/15Sw5dao9X2gDcgyashsqIByXPEROHPfl/view?usp=sharinghttps://drive.google.com/file/d/1whtEx6kAVpwN3w8dQZ7F1Fds0og0VK74/view?usp=sharinghttps://drive.google.com/file/d/1hTWBBHYL7p8ttltvwkZSo8T2A_-gOFzb/view?usp=sharinghttps://drive.google.com/file/d/15xsE4juTelZvxtLcSsUXVAzWfAP36q3y/view?usp=sharinghttps://drive.google.com/file/d/1bl7HoEt0CaZYL4OTEBK4_CXMevG5rQQ9/view?usp=sharinghttps://drive.google.com/file/d/1da5-9zGpDTO-GtoTQMtxOrYtQDl1k5mA/view?usp=sharinghttps://drive.google.com/file/d/1kTlWRqrGWSkKYX0GTuQV8rfI6zZWUUQt/view?usp=share_linkhttps://drive.google.com/file/d/1qfvUQHt10D2uHfJtYUz1wLoiFMuJQ-AY/view?usp=share_linkhttps://drive.google.com/file/d/1SMn0u1iMB5TzGrL8NWOgIytHs0e9hYdb/view?usp=sharinghttps://drive.google.com/file/d/1WtSU4FMCr5krwl22b9J6p_Yb8ezq_LBf/view?usp=sharinghttps://drive.google.com/file/d/1D3AsuPoaLtzDGSMHYNnD00ZBopOVmMC_/view?usp=sharinghttps://drive.google.com/file/d/1TCdKGM9EHTGLBWg_ByDwf1WmLZ3p90im/view?usp=sharinghttps://drive.google.com/file/d/1Qvwsehw7OtDYO3SLxBkEngoGWDg9pn5e/view?usp=sharing Business Requirements
| Company/Product Name: | ||||
| Business Requirements | ||||
| Line # | MoSCoW | Description | Vendor Response: Y,R,T,M,F,N | Notes/Comments/Reference to Location in RFP Response |
| Usability and Functionality | ||||
| BR-1 | Must Have | The system must be intuitive and easy to use, enabling the capture, storage, and seamless transfer of all current data to the new system (for conflict checks, etc.). | ||
| BR-2 | Must Have | It must be accessible online for free without any charges for licenses for external users | ||
| BR-3 | Must Have | The system should minimize the need for complex training | ||
| BR-4 | Must Have | A user-friendly interface with intuitive data entry and correction processes. | ||
| Data Consistency and Integrity | ||||
| BR-5 | Must Have | The system should maintain an audit trail to track actions taken by different users, which would be useful for accountability and improving training | ||
| BR-6 | Must Have | The CMS must be able to track who is inputting data at any point in the process. This will help in the monitoring training needs and reducing subjectivity | ||
| BR-7 | Must Have | The CMS should have defined and non-editable fields (e.g., felony vs misdemeanor) to avoid subjectivity and maintain data consistency | ||
| Case Weighting and Categorization | ||||
| BR-8 | Must Have | The system must support the existing case weighting system, or a variation thereof, allowing for case weight determination based on category and specific crimes | ||
| BR-9 | Must Have | The system should offer a list of common crime categories, with an "other" option for flexibility | ||
| BR-10 | Must Have | The system should offer more categories of crimes than are currently available, especially in felony and misdemeanor cases | ||
| BR-11 | Must Have | The CMS should be able to expand the type of data collected and offer ease of use beyond just data collection | ||
| Custom Reporting | ||||
| BR-12 | Must Have | Reports should be able to track case type by name of crime | ||
| BR-13 | Must Have | It should also allow for the creation of custom reports based on different fields like attorney, county, field office, and type of case | ||
| BR-14 | Must Have | The system must offer as much flexibility and creativity as possible in generating reports to meet different reporting needs | ||
| BR-15 | Must Have | The CMS must provide the ability to create custom reports based on various parameters, including case status, type of case, case wight, attorney assignment, time period (fiscal year), and specific charges (drug cases, DUI cases, violent cases) | ||
| BR-16 | Must Have | The CMS should allow reports to be run based on specific time periods, including assigned case dates, closed cases, and case progress over any specified time frame | ||
| BR-17 | Must Have | The system should allow reports to be generated on open and closed cases assigned to any attorney over a specific period or fiscal year | ||
| Navigation and Data Entry | ||||
| BR-19 | Must Have | The CMS must have a simple user interface with limited choices for data entry to reduce complexity and subjectivity | ||
| BR-20 | Must Have | The CMS should allow for seamless navigation between different county data entries while remaining in the same portal for the field office | ||
| BR-21 | Must Have | The system must support the fast pace of daily operations in a public deffenders office | ||
| Compliance and Security | ||||
| BR-22 | Must Have | The system solution must be compliant with State Statutes, rules, policies and standards | ||
| BR-23 | Must Have | The solution must include the collection and secure storage of detailed client and case information, along with performing clonflict checks and crifying eligibility services | ||
| Case Assignment and Tracking | ||||
| BR-24 | Must Have | The CMS must allow for tracking the procedural process of all cases (e.g. pending, sentencing, pending trial, pending closure) | ||
| BR-25 | Must Have | Efficient case assignment and tracking mechanisms are essential, ensuring balanced workloads and consistent monitoring of case status | ||
| BR-26 | Must Have | The system should provide the ability to check the status of any case at any given time | ||
| BR-27 | Must Have | The ability to track public defender fees accurately, including requested and ordered amounts | ||
| BR-28 | Must Have | Alignment between the closing sheet and database options for seamless case closure | ||
| BR-29 | Must Have | The ability to track the procedural progress of cases in detail | ||
| Performance Metrics and Reporting | ||||
| BR-30 | Must Have | Reporting and analytic functions provide insights into caseloads, performance metrics, and compliance with legal standards | ||
| BR-31 | Must Have | The system must be able to collect and display performance statistics related to public defenders and their cases | ||
| BR-32 | Should Have | The system should track PD performance mertics based on case categories and statuses | ||
| BR-33 | Could Have | While precise case duration may not always be available, the CMS should provide average or estimated ranges for how long different case types (drug cases, DUI cases, violent cases) generally take to be resolved | ||
| BR-34 | Must Have | The CMS must support the generation of repeatable, defensible, and reliable reports that can be used in budgetary discussions and other formal settings | ||
| Dashboard and Visulaization | ||||
| BR-35 | Must Have | The CMS should have a dashboard feature that visually displays the status of all cases. The dashboard should differentiate cases based on case type, case weight, attorney assignment, case age (with a color coding system, similiar to the current system used for tracking case age) | ||
| BR-36 | Must Have | The system should allow supervisors to view cases by attorney assignment, similar to how case wight and age are currently visulaized for supervisors | ||
| Document Management and Automation | ||||
| BR-37 | Must Have | Document management must involve, secure storage, controlled access, and seamless sharing of documents | ||
| BR-38 | Must Have | The system should automatically generate standard documents (e.g. the office's standard opening letter) when a new case is entered into the CMS | ||
| BR-39 | Could Have | The CMS should provide the ability to upload and store discovery documents without requiring additional equipment (e.g. scanners). This feature should aim to minimize equipment expenditure | ||
| Communication and Collaboration | ||||
| BR-40 | Must Have | Communication and collaboration tools are needed for internal and client communications, supporting case stategy development | ||
| Notification System | ||||
| BR-41 | Must Have | The CMS should have a notification system to track court dates, deadlines, and important case events for calendaring purposes | ||
| Archiving and Data Retention | ||||
| BR-42 | Must Have | The CMS must include the ability to archive cases from the system allowing for case management even after they are closed for inactive | ||
| User Access and Training | ||||
| BR-43 | Must Have | All assistants in the office should be trained on the system and have access, allowing them to step in when the main database person is unavailable | ||
| Public Defender Policies | ||||
| BR-44 | Must Have | https://wyodefender.wyo.gov/policies-resources | ||
| Wyoming State Statutes | ||||
| BR-45 | Must Have | https://www.wyoleg.gov/stateStatutes/StateStatutes |
https://wyodefender.wyo.gov/policies-resourceshttps://www.wyoleg.gov/stateStatutes/StateStatutes
File details come from the government source that posted it. Updated .