Frequently Asked Questions

Forms & Reports

Q: What forms can the two systems CalSAWS and CWS-CARES share?

A: CalSAWS and CWS-CARES can share documents. From CWS-CARES, an Eligibility Resource can upload any document to the Eligibility Record, so long as they're following county business practices, and it will be shared with CalSAWS. Forms that can be shared between CalSAWS and CWS-CARES includes all the regular forms related to Foster Care, ARC, Kin-GAP, AAP and foster care-related Medi-Cal. It also includes forms like birth certificates, affidavits, etc, as well as county forms.

Additionally, there are documents from CWS-CARES and the Focus Child's person record that are automatically pulled from the Eligibility Record such as birth certificates, court orders, regional center rate letters, placement agreements, etc. From CalSAWS, case-level documents are shared to CWS-CARES. If documents such as these mentioned are uploaded to the Eligibility Record in CWS-CARES or to the Case in CalSAWS, they will be shared in that way with the other system.
 

Q: What is the process to deactivate a user? Can it be done by the user themselves, or another party at the CBO, or can it only be done by a Child Welfare staff member with a CWS-CARES administrator login? What permissions does a CWS-CARES worker need to be able to add individuals to the provider portal? Will reports on logins/utilization by individuals be available, so counties can monitor users?

A: Regarding deactivation of a user in CWS-CARES, the CBO Portal Administrator will control activation and deactivation for their organization. To add and remove users, A CBO Portal Administrator permission their specific organization is required. The Project did not build native reports on data aspects such as logins and utilization by individual in CWS-CARES V1, but the data will exist within each organization’s portal and for the county Prevention Services Supervisor. County Prevention Services Supervisors will be able to monitor this data in CWS-CARES and could possibly have their own county Super Users build their own reports.
 

Q: Will the reports available in CWS-CARES be able to replace some or all of the reports in Safe Measures?

A: CWS-CARES reports will not replace all SafeMeasures reports. SafeMeasures will continue to provide a defined set of reports that users will have access to after the implementation and Go-live of CWS-CARES V1.

As part of the CWS-CARES reporting scope decisions, certain reports originally planned for CWS-CARES were intentionally descoped and moved to SafeMeasures. Other reports were developed and delivered within CWS-CARES. Please review the Reports Available in CWS-CARES V1 - 08.28.26 spreadsheet to see what reports are currently scheduled to be available in CWS-CARES Version 1. This list is point-in-time and may change when finalized.

Therefore, CWS-CARES and SafeMeasures will both support reporting needs following implementation. SafeMeasures will continue to produce the identified reports for as long as they are needed.
 

Q: What updates can you share regarding progress on improving the reporting functionality?

A: The Project is currently assessing options to support counties and evaluating improvements to the reporting experience aligned with post‑CWS-CARES Version 1 (CARES V1) priorities and capacity.
 

Q: What progress has been made to improve the reliability and usability of form generation in WORD and AEM?

A: IBM is developing the top‑priority 2,400 county forms in Adobe Experience Manager (AEM) by mid August, and counties may create or modify forms in either format and upload them themselves. California Juvenile (JV) court forms are not allowed to be edited per JCC.
 

Q: What progress has been made to improve Contact Note functionality, given the current challenges with multiple sections, limited space, and the inability to edit finalized notes?

A: At Go‑Live, counties will have the option to choose structured or unstructured contact notes. Supervisors will also have the option to require approval before submission. Unstructured notes currently support applying one contact to multiple children.
 

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: What guidance will be provided on the timelines for entering RFA manual data into CARES after go‑live, and how will this align with the Binti transition?

A: Additional information was released to all counties on August 31, 2026. For full details, see the Interim Guidance Document: Managing RFA, Emergency Placements, and External Systems Processes at CARES V1 Go-Live in the CWDS website.

To reduce impacts to the families and children we serve, counties will be permitted to complete Resource Family Home Applications initiated prior to CWS-CARES V1 Go-Live in the external system in which it was initiated until data conversion to CWS-CARES is complete. For systems with data conversion deferred to until after CWS-CARES Go-Live, conversion is currently anticipated to occur in July 2027. Once all active applications have been completed in the external system or data conversion is complete, whichever comes first, the external systems identified are required to be made inactive or read-only.

Q: Will e-signatures be allowed on adoption forms?

A: E-signatures will be allowed on specific adoption forms, not necessarily all forms. The list of E-signable Adoption Forms below contains a current and verified list of Adoption forms where E-signature is allowed:

  • PPADOP
  • AD0856
  • AD0513
  • AD0580
  • AD0090
  • AD0551A
  • AD0067
  • AD0067A
  • AD0907
  • AD0907A
  • AD0558
  • AD0230
  • AD0824
  • AD0200
  • AD0225
  • AD4320
  • JV0477
  • JV0475

Q: Is there a mechanism within CWS-CARES to modify or remove “finalized” forms?

A: To modify or remove any form within CWS-CARES, a GEN 158 form must be filled and filed from the program that owns the form and sent to the Forms Management Unit (FMU) using the FMU Mailbox. Please view the Forms Edits and Design webpage for more information.