A: The Project has decided to continue supporting both the Dedicated and Co-Existent models for CWS-CARES to avoid disruption to county operations. The Project is currently conducting an analysis to determine how these models will be implemented within CWS-CARES and to further assess their impacts. Any updates or new information resulting from this analysis will be communicated and shared as they become available.

A: There will be another opportunity for counties to provide feedback prior to rollout. The next phase of feedback will occur during Production Simulation, where users will be able to validate system functionality, confirm updates made from EUST 3 findings, and submit any additional feedback that was not captured previously. Details on the Production Simulation schedule and feedback process will be shared in advance so counties can plan accordingly. Regarding the volume of EUST 3 feedback, the team reviewed and triaged all items using a consistent methodology to ensure each item received a determination. We understand that some users were not able to submit all their feedback during EUST 3, and Production Simulation is designed to provide that additional opportunity. Our goal is to ensure feedback is gathered comprehensively before rollout, support system readiness and a smooth transition for users.

A: All Implementation Leads (ILs) attend the weekly PDT Standup on Fridays where demos are provided. In addition, ILs are assigned to each Service Area where designs are discussed with the core constituents. Functionality is also reviewed and practiced each week during Office Hours: Staging Environment Practice meetings.

A: The project engaged California Youth Connection (CYC) in developing the CWS-CARES Child Journey Map, which identifies pain points and opportunities, from a child and youth perspective, across the lifecycle of child welfare involvement. The project is currently exploring options to fund further lived experience research directly involving additional child and family advocate groups. The project has also provided updates to the quarterly meeting with advocates and California Department of Social Servies (CDSS) and intends to leverage that meeting as an opportunity to solicit feedback in system development.

A: To join the TAW, the County SPOC should request during their scheduled RUGs meeting for approval. Once approved, they will be added to the distro list for meeting series, and added to the participants list.

A: Feedback will be implemented based on priority and severity, guided by the determination type assigned to each item. Items identified as high‑priority or critical will be addressed before code freeze whenever possible.

A: The OCM Advisory Workgroup is a larger overreaching group comprised of select people from different counties within each region and is used as a forum to gather counties perspectives on the materials and communications. This group will assist the OCM branch of the Implementation Team in creating global To-be processes, validate communication products like email announcements, FAQs, and will participate in various stakeholder engagement activities such as system demos, videos, and change impact analysis. The County OCM Coordinator works directly within their county only and handles county specific communication and OCM activities. Things like leading and supporting staff through migration, coordinating tailoring and delivery of communications, and understanding and tailoring as-is and to-be business processes to align with county processes and procedures.

A: SME selection will vary by topic. Depending on the nature of the readiness task, SMEs in general should have expert knowledge of related business processes, technology, training, and or policy within your organization.

A: The estimates provided for each of the implementation roles are based on past experience designing and delivering similar implementations for other statewide IT projects. They are intended to be a range and will vary by organization. We anticipate these time commitments to increase as we advance towards Go-Live.

A: No, Production Simulation will not be available post Go-Live. It should not be used to store active case data during cutover.