Frequently Asked Questions
Features & Functionality
Q: For contacts that remain in "draft" status, will outcome/compliance reports indicate that the Social Worker (SW) is not in compliance, and the contact needs to be in "final" status that the SW saw the child?
A: Yes, outcome and compliance reports would indicate that a social worker (SW) is out of compliance if kept in "draft", the contact would need to be in "final" status in order for it to count toward compliance. A contact that remains in Draft status would generally be considered incomplete and would not demonstrate that the required contact with the child was completed/documented.
Q: What is the long-term solution for the Azure Object ID requirement?
A: The Object ID is a mandatory attribute and will be needed until we build an automated way to sync. The system also supports another flow, called Just in Time (JIT), for obtaining the object ID automatically during SSO, if the following conditions are true:
- This is a new user and does not exist in the CWS-CARES system
- The user is already added to Azure security group on the county (integrated county) side
- County administrator requests the user to login to CWS-CARES
Q: In CWS-CARES, the Emergency Response Notice of Referral Disposition (ERNRD) Letter is automatically emailed to mandated reporters who select email follow-up. Can the State confirm the notice will only be generated after supervisor approval of the referral disposition? Can counties adjust the timing if needed?
A: The ERNRD document can be generated once the response type is set to Evaluated Out in Screening, and at any point during Referrals. Ideally, workers should wait until a disposition is entered in Referrals, because the document will not populate correctly if the allegation conclusions are still missing (for example: unfounded, inconclusive, or substantiated without final allegation determinations).
If the mandated reporter selected email as their preferred communication method, the system will not send the ERNRD electronically until either the evaluated-out screening or the referral is approved.
No, timing is not something counties can change at this time. If counties would like this capability based on the workflow described above, please submit a user feedback item for consideration in future enhancements.
Q: Can dedicated counties receive some sort of guides or direction on how we will handle user management? With three different systems at play here having some official guidance on the process will help to prepare better. Everything from requesting a new user, closing out a new user, and disabling access. The CWS-CARES team is not responsible for all three (Windows Active Directory, Okta/Zscaler, Okta/CARES) but they all play into the same pot to get users up and running.
A: There will be a dedicated county administrator for dedicated counties from their county who will have privileges to create, update, grant access and suspend their county-specific users in the CWS-CARES application. The county administrator also has the option to suspend users if the user does not need access to the CWS-CARES application. The suspended user will be automatically deactivated after 90 days of last successful login. Regarding deleting users, as a best practice and aligning with the retention policy, users are never deleted from the system. They are transitioned into a deactivated status and maintained in the system. Processes regarding user management such as enhancements to streamline onboarding including the Zscaler + SPOC alignment continue to be a work in progress and updates provided by the Project will be communicated out as information becomes available. If County Administrators have questions or issues about user management in Okta/CWS-CARES, then they can come to the Production Simulation Support office hours. For more information and resources on the County Admin and deactivation processes, please refer to the user onboarding video on the IP Quick Access CWS-CARES V1 webpage. Additionally, there are guides on user management for County admins that are available on the System Updates & Release Notes | Child Welfare Digital Services webpage.
Q: Will the Resource Family Approval (RFA) Portal include or link to the CDSS RFA county contact list so applicants can easily identify the correct county contact?
A: No, the RFA Portal will not include a link to the CDSS RFA County contact list. The RFA applicant will need to ensure that they are submitting to the correct county when entering their address. This will trigger a notification in CWS-CARES and an RFA worker will be assigned to that application. Once a worker has been assigned a notification will be sent to the applicant of their worker and the next steps. If the applicant cannot remember who their worker is, they would be able to log into the portal and see that information.
Q: We may be able to use narrative fields but cannot collect data in CWS-CARES, does this mean we can enter it but not in a reportable way? And we haven’t received guidance as to whether or not there will be direction by Go-Live so we don’t know if we should spend time determining our own plan.
A: At this time, we are not able to collect additional SOGIE data in CWS-CARES. In the future, additional guidance will be provided by CDSS Program Policy that will outline how to document. Additionally, CWS-CARES cannot issue guidance on any workarounds outside of the two allowable data fields required; future guidance on this will also have to come from CDSS Policy.
Q: Does CWS-CARES allow social workers to send service referrals through the system?
A: No, the only referrals that can be sent through the system to a service provider would be Prevention Services referrals.
- Prevention Services can be provided via three distinct pathways.
- IV-E Pathway, Case: The focus child has an open Child Welfare Court or Child Welfare Voluntary case with a Family Maintenance service component managed by either Child Welfare or the IV-E Tribe.
- IV-E Pathway, No Case: This pathway can be triggered by a Request for Prevention Services from Hotline, Self-Referral or a Community Provider Referral. The focus child does not have an open case. A Prevention Services Container needs to be opened to provide the child and family with prevention services. The IV-E Agency will oversee this work. This pathway is most likely to be utilized by smaller counties who will oversee and manage all their Prevention work.
- Community Pathway: This pathway can be triggered by a Request for Prevention Services from Hotline, Self-Referral or a Community Provider Referral. The focus child does not have an open case. The Community Based Organization receives a Request for Prevention Services via the Portal. The CBO will then open a Prevention Services Container via the portal. The CBO oversees the work.
- A Prevention Services Request will be utilized by all pathways in some manner.
- For the case pathway, only youth living at home with their parents/legal guardians/Indian Custodians can be referred for prevention services. To receive prevention services a youth in out of home care must be pregnant or parenting.
- Both the IV-E Case and No-Case pathways will be able to create the Prevention Services Request and submit it to the Prevention Services Supervisor to be assigned to a Prevention Services Worker.
- The IV-E Case and No Case Pathways will be able to assign the Prevention Services request to an internal CWS-CARES Prevention Services user or an external CBO Prevention Services user via the portal.
- In all pathways, the Prevention Services Request will be used to track referrals to Prevention Services.
Q: Will the release date of CWS-CARES Version 1 (CARES V1) be adjusted?
A: At an ad hoc CWS-CARES Board of Directors meeting on September 3, 2026, the following decisions were voted and approved:
Go-Live Date: The system launch is moved to Monday, December 7, 2026. This later date gives counties more time to complete data validation and continue with readiness activities before the system goes live.
Post–Go-Live Release Strategy: After the December launch, the system will receive two scheduled releases, one in March 2027 and another in May 2027. This approach gives additional time after Go-Live to stabilize the system and thoroughly validate functionality before enhancements are introduced. All planned enhanced stories are expected to be completed by May 1, 2027.
Cutover Plan: For the transition from current systems to CWS-CARES, CWS/CMS will switch into read-only on Thursday, December 3, 2026 at 5 PM.
For full details, see the Important Update: CWS-CARES Go-Live Date Adjusted to December 7, 2026 communication on the CWDS website.
Q: What is the final disposition of the Essential Stories?
A: There were 313 total stories considered and discussed to determine essentiality for Go-Live launch.
- 83 enhancement stories delivered in Version 1.1 by March 1, 2027;
- 115 enhancement stories delivered in Version 1.2 by May 1, 2027.
Q: What updates can you share regarding improvements to access and permissions in CARES?
A: The Project reports that Roles Based Access will be ready for testing during Production Simulation, the CWS-CARES Administration team is supporting user setup, and staff lists have been updated to include only active users.