Frequently Asked Questions
Features & Functionality
Q: How did the Project determine that referral work takes about 30 minutes, and will there be a walkthrough of that process?
A: In general, processing referrals in CWS‑CARES is expected to take roughly the same amount of time as in CWS/CMS. Staff considered 'expert' in CWS/CMS ran multiple referral scenarios to establish a time estimate: staff considered 'novice' in CWS/CMS completed the minimum requirements in about 30 minutes, and expert staff completed them in less time. The Project team is currently working to schedule walk-through sessions with Fresno and Los Angeles Counties to demonstrate the Hotline functionality, highlight recent enhancements to the Search tool, and gather additional feedback.
Counties later identified that search functionality contributed to concerns about overall processing time. In response, the Project has implemented improvements to search functionality. For more information on improved search functionality, see Improvements to Search in Prod Sim (CARES100).
Q: When is the code freeze scheduled?
A: Code freeze will occur August 24. In alignment with the September 3 Board of Directors decision to adjust the go-live date, the Defect freeze is now November 7.
Q: When is the April 2027 V1.3 release planned?
A: What was previously planned for April 2027 Version 1.3 (V1.3) release was adjusted to move forward with only two releases, rather than three. This allows additional time for post-launch stabilization and system validation. This schedule completes enhancement story delivery by May 1, 2027.
Q: When is the February 2027 V1.2 release planned?
A: What was previously planned for February 2027 Version 1.2 (V1.2) release is now scheduled for May 1, 2027.
Q: When is the December 2026 V1.1 release scheduled?
A: What was previously planned for December 2026 Version 1.1 (V1.1) release is now scheduled for March 1, 2027.
Q: What should counties expect from the Version 1.0 (V1.0) September Production Simulation release, and will they be able to test the new functionality?
A: Counties can expect the September V1.0 Production Simulation release to include a set of upcoming fixes that OTSI is currently compiling and preparing to share. This will give counties a clear understanding of what changes are included and what they should look for during testing.
Once a bug, defect, or story has been fixed, release notes will be updated so counties know when to go back in and retest the functionality. This provides counties with a clear feedback loop and ensures they can validate the new behavior as part of the Production Simulation release.
Q: Will there be improvements to the search functionality, and what enhancements can users expect?
A: The following Search enhancements were deployed to Production Simulation (Prod Sim, or CARES100) on August 29, 2026:
- The Person and RM (Resource Management) Directory Search now use the “And” operator instead of “Or,” resulting in more precise and narrowed search results.
- In Person Search, the “Sex at Birth” and “Approximate Age” criteria are now fully functional. Phonetic search for first and last names has also been enabled to make it easier to locate the intended individual. Previously reported performance issues, where searches took up to 2 minutes to return results, have been resolved.
- In RM Directory Search, multi-select capability for placement category types is now available.
Q: How will the ticketing system identify training needs and system issues, and how will users receive feedback through the ticket process?
A: The ticketing system helps identify both system defects and training needs by tracking issue trends and reviewing how tickets are submitted and resolved. Tickets stay open until fixes are confirmed, ensuring accurate visibility into recurring problems. Tier 2 follows established workaround guidance before escalating or closing issues, and users retest fixes or tickets close after five business days without response.
Service desk reviews and data analysis highlight where additional user training is needed and whether training-related issues are entering the ticket system. OTSI will also verify that current county messaging on ticket closure aligns with actual ticket behavior.
Through this process, the system provides users with clear updates while helping identify both technical issues and training gaps.
Q: When will Organizations know whether they need to go back into CWS-CARES to update any data entered through workarounds?
A: Weekly release notes will include which functionality is being released and any workarounds that are being retired. To access the release notes, log into the System Updates & Release Notes page of the Production Simulation Hub.
Q: Where can I find more information on when each workaround will be replaced by full system functionality?
A: Weekly release notes will include which functionality is being released and any workarounds that are being retired. To access the release notes, log into the System Updates & Release Notes page of the Production Simulation Hub.