Frequently Asked Questions
Q: If CWS/CMS has an incomplete address and Binti data fills in the blank fields, is there a verification process to ensure the addresses are correct and should be merged?
A: The hierarchical conversion logic preserves CWS/CMS addresses, and Binti addresses are only utilized if the CWS/CMS field is blank. The Smarty Streets tool is used in CWS-CARES to automatically correct and complete address information.
As a reminder, CWS/CMS is the statewide system of record and the primary source of CWS-CARES data. For more information, please refer to the Binti to CWS-CARES V1 Data Conversion Fact Sheet.
Q: If a field in CWS-CARES already contains data, will the field be overwritten by the data received from the external system (Binti)?
A: No, if a field in CWS-CARES already contains data from the Child Welfare Services/Case Management System (CWS/CMS), it will not be augmented or overwritten by Binti data. For more information, please refer to the Binti to CWS-CARES V1 Data Conversion Fact Sheet.
Q: When will counties be expected to assume responsibility for the cost of Binti in a read-only capacity?
A: At CWS-CARES Version 1 (CARES V1) Go-Live on October 26, 2026, Binti must be decommissioned or used in a strictly read-only capacity. The continued use of Binti in inactive or read only status beyond the CARES V1 Go-Live will be at the county’s own expenses the existing Commercial Off-The-Shelf (COTS) waiver for Binti and ETO will become inactive. Please refer to ACL 25-44.
Q: We were wondering if CWS-CARES will incorporate Safety Organized Practice (SOP) into the system. This is the state approved model approach we use in practice.
A: CWS-CARES incorporates elements aligned with Safety Organized Practice (SOP) where appropriate within system functionality. For example, provisional Harm and Danger Statements are available at Intake (Screening) and can be further developed throughout the referral and case lifecycle. Additionally, SOP-aligned language has been integrated into relevant areas of the system, including structured contact notes and other documentation features, where applicable.
Q: Who will be responsible for adding users to the FFPSA and RFA portals?
A: The County Administrator will be responsible for adding county users to county FFPSA and RFA portals.
Q: Are there plans on implementing a document imaging solution for CWS-CARES?
A: Currently, there are no plans for a document imaging solution directly into CWS-CARES at this time. Users can scan documents to their computers and upload any saved documents as needed.
Q: Since Binti is scheduled for decommissioning but will still be required until CWS-CARES goes live in October, how should counties handle Advance Planning Documents (APDs) and contracts expiring/ renewals for the period now until 11/01/2026?
A: Please note that the below response also applies to counties using Efforts to Outcomes (ETO) recruitment and licensing functionality.
An APD is required for the initiation, amendment, or renewal of a software licensing agreement. Written approval must be obtained from the State prior to executing any contracts, agreements or renewals. County Fiscal Letter 23/24-12 discusses APD requirements, including when an APD is necessary, in detail.
All County Letter 25-44 explains that the existing COTS waiver for Binti or ETO Resource Family Approval recruitment and licensing functionality will remain active until CWS-CARES Version 1 is implemented in October 2026. State approval of federal funds for these contracts extending beyond CWS-CARES Version 1 go-live will be prorated, since the software will be ineligible for federal funding once the COTS waiver becomes inactive.
Beginning with ACL 18-47, CDSS has been encouraging counties to include early termination language in their contracts for external systems to enable them to decommission duplicative functionality when required. Decommissioning of Binti/ETO or moving it to a read-only status is required at the time of Version 1 go-live, scheduled for October 26, 2026. If the county is opting to fully decommission Binti/ETO at go-live, counties should review their contracts now and identify when to exercise their early termination language. If the county has chosen to move the software to a read-only status, counties should consider how long their internal contract amendment processes take and determine when to initiate that process to accomplish a read-only status by October 26, 2026. Continued use of Binti in a read-only capacity beyond the CWS-CARES Version 1 go-live date will be at the county’s own expense until it is decommissioned or for the duration of its availability in read-only status. Costs associated with activities related to converting RFA data into CWS-CARES are eligible for Core Constituent Participation (CCP) funding, as they are aligned with the activities discussed in All County Letter 23-62 and County Fiscal Letter 23/24-03.
Q: Outside of Child & Family Services (CFS) staff, will other Health & Human Services (HHS) partners, like Behavioral Health and Recovery Services (BHRS) for example, who have access to CWS-CARES be able to access all information or will they only have access to limited information/functions in CWS-CARES?
A: Access to CWS-CARES is role-based, and counties are responsible for determining how system access is assigned to their users based on local operational needs.
At this time, there is no dedicated worker permission specifically configured for Behavioral Health staff. For secondary role assignment, a “Public Health Nurse” role is available and may be leveraged by counties as appropriate. However, there is currently no distinct Behavioral Health role with a separate, limited permission set.
Q: It is noted that there is the ability in CWS-CARES to e-sign a lot of documents i.e. courts, state forms etc. Has the State already approved e-signatures? We have been previously instructed they need wet signatures for many different documents.
A: While CWS-CARES has the functionality to e-sign documents such as court reports and state forms, e-signatures are not required. Counties will have the flexibility to follow their own County and Court policies around e-signing documents. Please view Rule 2.257 for further details on use of e-signatures.
Q: Will counties be able to copy and modify reports created by other counties? If so, when will those reports be available for counties to access and copy?
A: In the CWS-CARES 102 environment, County Report Developers have permission to view reports developed by other counties. However, they do not have the ability to download, copy, or modify these reports because they are not members of the respective county or project folder structures where the reports are stored. Counties will continue to have read-only access to reports developed by other counties.
Reports developed by the project are managed and maintained under the project vendor warranty. For this reason, County Report Developers are not granted permissions to download or modify these reports. All CWS-CARES users will have the ability to run and view available reports as part of the CWS-CARES solution.
Reports are organized within their respective folder structures (such as county-specific folders or project folders), and access permissions are managed accordingly.