Update

CWS-CARES Production Simulation Schedule Adjustment & Converted Data Kickoff Rescheduling

CARES SPOCs, Implementation Coordinators, OCM Coordinators, County Leadership, Tribe Leadership, Probation Leadership, and State Leadership:

We are providing an important update regarding an adjustment to the CWS-CARES Production Simulation schedule and kickoff for access to converted data.  

During our final technical setup and validation phase yesterday, issues were uncovered related to data conversion and user access. To allow time to address these issues, the converted data deployment originally targeted for May 26, 2026, will now occur on June 8, 2026.  

The Production Simulation Converted Data Kickoffs currently scheduled on May 26th and May 27th will be rescheduled to June 8th and June 9th to align with when the environment is officially released to the counties and organizations.  

We are actively working to resolve these validation items and fully expect to maintain our July 6th timeline for the rollout of Production Simulation to all users. Please continue to use the current environment for now. Note that the SDM and Case Management Assessment interfaces will be available in that environment.

Action Required

No action required.

Issue Discovered with CWS/CMS Release 9.6.1 - UPDATE

All SPOCs and Technical Contacts:

May 20, 2026 UPDATE: IBM has developed and successfully tested a fix to resolve the issue introduced with Release R9.6.1. IBM will implement CWS/CMS R9.6.2 on Thursday, May 21, 2026, at 6:00 PM. There is no outage associated with this release. IBM expects the R9.6.2 MSI file to be available in the afternoon on Thursday, May 21, 2026.

R9.6.2 is an optional release for Co-Existent Counties; however, IBM strongly recommends pushing out the R9.6.2 code as soon as possible to the workstations that are currently running R9.6.1.

IBM will push out R9.6.2 to the Dedicated Counties on the evening of Thursday, May 21, 2026.

__________________________________________________________

This message is to inform you that an issue introduced in CWS/CMS Release R9.6.1, implemented on Wednesday, May 13, 2026, is causing an APP29956 error message impacting the JV‑101 and JV‑110 forms. The issue occurred due to updates made to another form in R9.6.1, which unintentionally affected JV‑101 and JV‑110.

There is currently no workaround for this issue. IBM is actively analyzing the issue and working to identify a fix. We will provide an update as soon as more information is available.

At this time, we recommend that any counties that have not yet installed R9.6.1 pause deployment until further notice.


Action Required

No action needed.
 

We do recommend postponing the installation of R9.6.1 if you have not yet installed it.

Major Update: CWS-CARES Providing Vendor Resources for County Forms Development

CARES SPOCs, Implementation Coordinators, OCM Coordinators, County Leadership, and State Leadership:

We recognize that forms development has been a significant concern for counties, so we are excited to share a major update that will drastically reduce county time building forms and ease the pressure on county teams.  

The CWS-CARES project is currently finalizing a work order with one of our vendors to provide dedicated resources to build the top-prioritized 2,400 county CWS/CMS forms. This ensures that county forms in CWS/CMS are developed for testing in CWS-CARES Production Simulation prior to Code Freeze on July 31, 2026. 

Below are the details on how the two types of county forms will be handled: 

  • County Forms Maintained in CWS/CMS: Our project vendor will begin developing the top-prioritized 2,400 county forms that are currently stored within the legacy CWS/CMS system. The project is providing resources to develop these specific forms.  
  • County Forms Maintained Outside of CWS/CMS: Please note that the vendor-led development applies only to county forms stored in CWS/CMS. It does not include county forms stored in external or local systems. Counties will remain responsible for developing and updating any forms housed in their own external systems. Forms may be built within the CARES 102 environment. Once built, forms may be published to the Production Simulation environment to test and validate. 

Additional guidance, timelines, and instructions will be shared with county form authors soon. 

We know how much of a priority — and a concern — forms have been for county teams, which is why we are incredibly pleased to share this news. Thank you for your continued partnership, dedication, and invaluable feedback as we work together to build CWS-CARES . 

Action Required

No action required.

CWS-CARES Implementation Timeline

CARES SPOCs, Implementation Coordinators, OCM Coordinators, County Leadership, Tribe Leadership, Probation Leadership, and State Leadership:

We are sharing a high-level CWS-CARES Implementation Timeline from May 2026 to January 2027. This timeline includes the key activities for Implementation, Training, and Organizational Change Management (OCM) and is provided to support counties and organizations in their internal planning and awareness efforts.

Please note that this is a draft currently undergoing final validation for the project’s master schedule. Dates may be slightly adjusted following these final reviews.  Following the commitment to distribute this initial information by May 15th, a finalized version will be published soon.

Key County Activities and Dates: May 2026 to January 2027

Implementation

  • Monthly Readiness Checkpoints to mid-October
  • Develop Project Go-Live Support Plan: 5/11– 6/30
  • Org Support Plan Template: 7/1–7/31
  • Go-Live Support starting on 10/26 (Over-the-Shoulder Support to 11/25; Virtual Command Center to 1/24/2027)
Training

1. In-App Learning: Self-Paced Online Training (Enablement): 5/26–10/23Enablement Programs are step-by-step instructions viewable in CWS-CARES and will be available in the production simulation environment beginning 5/26, with additional modules added on a rolling basis through 7/17. Post-launch, the Enablement suite will undergo iterative updates to stay aligned with the system.

2. Train-the-Trainer: 6/15–10/23

  • Self-Paced Online Training (Enablement): 6/1– 8/1
  • Participate in TTT Sessions: 6/15 - 8/14
  • Ongoing TTT Office Hours & Support Channel 6/15-10/23

3. End Users Training: 6/15–10/23

  • Self-Paced Online Training (Enablement): 6/15–10/9
  • Instructor-Led Training (ILT): 8/3–10/23
  • Refresher Training: 10/8–10/23

Organizational Change Management (OCM)

1. Change Champion/Super User Network: 5/11–11/1

  • Establish Network and Planning: 5/11 to 6/15
  • Execute Network Plan: 6/15 to 11/1

2. Business Process Redesign (BPR): 6/15–11/1

  • OAS, Deep Dives, Delta Workshops 6/15 - 9/15
  • Organization Support Materials to Document Deltas: 7/15 – 9/15
  • Statewide Impact Register 9/15 - 10/15
  • Key Findings: 10/15 -11/1

Training Structure and Durations
The training strategy utilizes a blended approach of on-demand and live sessions, with specific prerequisites for each phase:

1. On-Demand Training (Prerequisite):

  • Up to 40 hours of on-demand material will be available.
  • This is a mandatory prerequisite for both Train-the-Trainer (TTT) and End-User Training (EUT).
  • The actual number of hours required will vary depending on a user's specific role.

2. Train-the-Trainer (TTT):

  • The estimated duration is up to 2 weeks.
  • Timing is adjustable based on a trainer's prior experience with CWS/CMS and CWS-CARES; those new to both systems will have more prep time.
  • Exact schedules will be finalized once all trainers are identified.

3. End-User Training (EUT):

  • Most staff will require 1 to 3 days of training.
  • A small subset of users needing comprehensive training across all modules may require additional time.

We will provide further details as they become available, with a target update scheduled for the end of this month. We look forward to partnering with the counties and organizations to ensure a smooth transition and will continue to provide regular updates as we approach the October 2026 Go-Live.

Action Required
No action needed.

CWS/CMS: End-date of Inactive CWS/CMS User Logins for CWS-CARES Readiness – UPDATE

All SPOCs and Technical Contacts:

May 7, 2026 UPDATE: The automated process to end‑date inactive CWS/CMS user logins continues in May. The new reports were generated and saved to SAFE on Thursday, May 7, 2026. The SAFE file is titled, “SCR9039_END-DATE_USERID_2026-05-07.xlsx.” REMINDER: this is the first month will list CWS/CMS user accounts that have been inactive for the previous 90 days.

Please review your organization’s report, saved in the SAFE folder. Organizations that do not have any potential accounts to end‑date in their report will, instead, find the following statement, “NO ROWS FOR DATA QUALITY CLEANSE”.

If needed, up to ten (10) listed accounts may be requested to be excluded from the automated end‑date process. Please submit your exclusion file by Thursday, May 21, 2026, at 5:00 PM, to request listed user logins from being end-dated when the process runs on Saturday, May 23, 2026. If more than ten (10) user logins are needed to be excluded, please send your justification to the CWDS Customer Relations mailbox (CWS_CustRel@otsi.ca.gov). The justification will be forwarded to the review team for consideration. No action is required if your county agrees with the list as provided.

As stated in the attached SCR 9039 FAQ document, CWS/CMS User IDs that need to be reactivated following the automated end‑date process can be accomplished by contacting the IBM Help Desk at 800-428-8268. Please note that the process to reactive the accounts is complex and does take one or two weeks to be completed by the IBM team. However, in order to expedite this timeline, it is important when calling in the ticket to explain the reason the user ID login was end dated was due to SCR 9039. User accounts from the reports that are logged in prior to Friday, May 22, 2026, at 5:00 PM, will not be end‑dated in the automated process on May 23, 2026.

All User ID accounts, both active and inactive, will be migrated to CWS-CARES. End-dated User ID accounts that need to be reactivated in CWS-CARES can be completed by the Administrators within CWS-CARES. This process will be much more direct and easier to complete in CWS-CARES than it is currently accomplished in CWS/CMS.

__________________________________________________________

April 7, 2026 UPDATE: After a one-month hiatus for March, the automated process to end‑date inactive CWS/CMS user logins has resumed for April. The new reports were generated and saved to SAFE on Tuesday, April 7, 2026. The SAFE file is titled, “SCR9039_END-DATE_USERID_2026-04-07.xlsx.” REMINDER: this is the final month that the report will list CWS/CMS user accounts that have been inactive for the previous 180 days. Beginning in May, the reports will list accounts that have been inactive for 90 days.

Please review your organization’s report, saved in the SAFE folder. Organizations that do not have any potential accounts to end‑date in their report will, instead, find the following statement, “NO ROWS FOR DATA QUALITY CLEANSE”.

If needed, up to ten (10) listed accounts may be requested to be excluded from the automated end‑date process. Only a few organizations currently have more than ten (10) accounts listed. Please submit your exclusion file by Thursday, April 23, 2026, at 5:00 PM, to request listed user logins from being end-dated when the process runs on Saturday, April 25, 2026. If more than ten (10) user logins are needed to be excluded, please send your justification to the CWDS Customer Relations mailbox (CWS_CustRel@otsi.ca.gov). The justification will be forwarded to the review team for consideration. No action is required if your county agrees with the list as provided.

As stated in the attached SCR 9039 FAQ document, CWS/CMS User IDs that need to be reactivated following the automated end‑date process can be accomplished by contacting the IBM Help Desk at 800-428-8268. Please note that the process to reactive the accounts is complex and does take one or two weeks to be completed by the IBM team. User accounts from the reports that are logged in prior to Friday, April 24, 2026, at 5:00 PM, will not be end‑dated in the automated process on April 25, 2026.

__________________________________________________________________________

March 5, 2026 UPDATE: The CWDS Project has decided to not run the automated process to end-date inactive CWS/CMS user logins during March. The monthly process will resume in April. The next reports will be sent to the SAFE folder approximately April 7, 2026.

____________________________________________________________________

February 18, 2026 UPDATE: This is a reminder to submit an exclusion file, if needed, by Thursday, February 19, 2026, at 5:00 PM to prevent up to ten (10) user logins from being end-dated. No action is required if your county agrees with the list as provided.

______________________________________________________________________________________________

February 11, 2026 UPDATE:  As presented at the February 10, 2026 Technical Advisory Committee (TAC) Meeting, we are sharing the updated SCR 9039 FAQ document for your reference.   

_____________________________________________________________________

February 6, 2026 UPDATE: Based on received feedback, the reports are being updated for the following criteria:

Report criteria:

Identifies CWS/CMS user logins that have not been used in the past 180 days 

However, users are omitted from the report if they fall into one of these two categories:

  1. Have NOT logged into CWS/CMS within the previous 180 days, but HAVE logged into CARES-Live within the previous 180 days.
  2. The User ID has been created within the previous 90 days, and has NOT logged into CWS/CMS.

Updated reports, using the new criteria listed above, will be made available in SAFE in the FromOSI folder no later than 5:00 PM, on Friday, February 6, 2026, titled: SCR9039_END-DATE_USERID_2026-02-06.xlsx. 

Please use this updated report when reviewing the list of user logins identified for deactivation.

_____________________________________________________________________

To prepare for CWS-CARES Mock Cycles and Production Simulation, the CWS-CARES Project will begin an automated process to end-date inactive CWS/CMS user logins. This effort helps ensure that only active users are set up with access in CWS-CARES. 

This process identifies CWS/CMS user logins that have not been used in the past 180 days and schedules those logins to be end-dated. This is standard account cleanup intended to reduce inactive or outdated system access as counties prepare for CWS-CARES. 

What This Means for Counties 

  • This activity affects system access only. There are no impacts to caseloads, staff roles, office assignments, or authority. 
  • User logins associated with an active County License Case (CLC) are excluded from the report. 
  • All user accounts (active and inactive) will still be carried forward to CWS-CARES. 

County Review and Option to Exclude User Logins  

Counties will have an opportunity to review the list of user logins identified for deactivation. To accommodate staff on extended leave (such as administrative or maternity leave), counties may exclude up to 10 user logins from deactivation, if needed. 

A report will be available in SAFE in the FromOSI folder on February 2, 2026, titled: 
SCR9039_END-DATE_USERID_2026-02-02.xlsx. 

If your county wishes to exclude user logins: 

  1. Use the Excel file provided. 
  2. Keep only the rows (up to 10) for user logins you want excluded. 
  3. Do not modify the file layout or formatting. 
  4. Upload the file to SAFE in the ToOSI folder. 

If more than 10 exclusions are needed, please contact CWDS Customer Relations and include a brief explanation. 

Deadline: February 19 at 5:00 PM 
Files received after this deadline will not be accepted, and all user logins listed in the original report will be end-dated. 

Timing and Ongoing Process 

  • This first run will process and end-date User IDs on February 21, 2026. 
  • The 180-day inactivity threshold will remain in place through April 2026, giving counties additional time to review the list and adjust to new processes. 
  • Beginning May, the inactivity threshold will change to 90 days, consistent with CWS-CARES access policy and the Production Simulation environment
  • After February, this process will occur monthly until the transition to CWS-CARES: 
  • Reports will be posted after the first weekend of each month 
  • User logins will be deactivated during the fourth weekend of the month 
  • Counties will receive advance notice of specific dates 

Restoring a User Login 

If a user login is end-dated and later needs to be restored, counties may submit a Help Desk ticket to reinstate the existing login and associated staff access. 

Action Required 

  • Review the report of inactive CWS/CMS user logins when it becomes available in SAFE. 
  • Submit an exclusion file (if needed) by February 19 at 5:00 PM to prevent up to 10 user logins from being end-dated. 
  • No action is required if your county agrees with the list as provided. 

For questions or concerns, please contact the CWDS Customer Relations mailbox. 

CWS-CARES: Update on Salesforce Recorded Webinar

Salesforce Webinar Recording Participants:

Thank you for your participation in the Salesforce Recorded Webinar on April 9, 2026. We appreciate the time you took to join the session and share your feedback.

Following feedback from our county partners, we have decided not to release the recent webinar recording. As the session focused on general Salesforce navigation, some content may not fully reflect the CWS-CARES user experience.

Instead, these topics will be integrated into upcoming CWS-CARES training to ensure users receive guidance tailored to our platform.

We appreciate your continued partnership as we refine our materials to better serve CWS-CARES users.

Action Required

If you have any questions, please contact CWS_CustRel@otsi.ca.gov.

CWS/CMS: SBC Access to CWS/CMS Warning Message - RESOLVED

All SPOCs, Technical Contacts, and SBC Administrators:

May 5, 2026 UPDATE: In addition to the warning message issue, a second issue within the Server Based Computing (SBC) / Citrix environment was discovered. This second issue was a “High Level Problem Occurred” message. Unlike the first issue, users who encountered the second issue were blocked from proceeding access to the CWS/CMS application.

IBM worked with the California Department of Technology (CDT) and implemented a fix to resolve the “High Level Problem Occurred” last night. Users should not be encountering this issue when accessing the CWS/CMS application via SBC.

In addition, a separate fix has been implemented this morning to resolve the issue that was causing the warning message. This message should no longer appear.

____________________________________________________

The California Department of Technology (CDT) upgraded the SBCS servers to the Windows 2022 server. This activity has caused the following warning message to appear when accessing CWS/CMS via an SBC connection:

IBM and the CWDS Office are working with the CDT on a fix, to be implemented later this week, to prevent this warning message from appearing. No action will be needed from the user once this update is made. In the meantime, users are able to connect to CWS/CMS by simply clicking the ‘OK’ button to close out the warning message.

Action Required

If users experience any issues with CWS/CMS, please follow your county process for reporting issues or you may contact the IBM Boulder Help Desk at 1-800-428-8268.

Data Conversion Mock Cycle 2 Now in Production Simulation - UPDATE

CWS-CARES SPOCs:

May 1, 2026 UPDATE: This is an update to the February 19, 2026, communication requesting participants for Data Conversion

Mock Cycles 1 and 2.  Mock Cycle 2 is the next full load of organization data from CWS/CMS and select systems into CWS-CARES for review. This validation helps confirm that real-world records appear accurately and completely in the system. 

Mock Cycle 2 data will now be loaded into the Production Simulation environment. Beginning May 26, 2026, participants will be able to validate converted data as part of Production Simulation activities rather than through a separate Mock Cycle 2 process. 

Support for data validation will be provided through regular support channels, including Office Hours. 

Thank you for your continued partnership and flexibility as we align Production Simulation and data conversion readiness activities. 

If you have questions about data conversion, please contact CWDS Data Conversion.

______________________________________________________________________

February 19, 2026

Participants Requested for Data Conversion Mock Cycles 1 and 2 – Survey Due March 2, 2026

All CWS-CARES SPOCs:

As CWS-CARES continues statewide readiness efforts, we appreciate your continued partnership in data validation activities.

The next phase is Data Conversion Mock Cycles 1 and 2. These are full test runs where organization data from CWS/CMS and select systems are converted into CWS-CARES to review real-world records and confirm the data appears accurately and completely in the system.

We are seeking one (1) to five (5) participants per organization who are familiar with their data to support this effort. All participants will receive calendar invitations and communications for both cycles, so you do not need to indicate which cycle(s) they plan to support.

Timeline

Mock Cycle 1: March 23, 2026 – April 10, 2026
Mock Cycle 2: April 21, 2026 – May 4, 2026

Participants may support one or both cycles. Mock Cycle 2 will include system improvements, sealed and sensitive records, and updated user access settings in preparation for Production Simulation.

Support

Participation includes a one-hour kickoff and a wrap-up session. Orientation sessions and semi-weekly office hours will be available to support questions and issue review. Time spent on validation is flexible and based on each organization’s level of review.

Action Required:

Please complete the brief survey by March 2, 2026, so we can set up user access:

CWS-CARES Data Conversion Mock Cycles 1 and 2 Survey

Only one survey response per organization is needed, so please coordinate internally before submitting.

If you have questions, please contact CWDS Data Conversion.

CWS-CARES Implementation Update: Timeline and Implementation Lead Assignments 

CARES SPOCs, Implementation Coordinators, OCM Coordinators, County Leadership, Tribe Leadership, Probation Leadership, and State Leadership:

As we move closer to the statewide launch of CWS-CARES this October, we want to provide you with an update on our implementation roadmap and the team dedicated to supporting your organizations through this transition. 

Attached are the Implementation Lead (IL) Assignments and a high-level timeline encompassing key activities across Implementation, Organizational Change Management (OCM), and Training. This overview outlines the major milestones leading up to our Go-Live, with a focus on the following upcoming phases: 

  • Train-the-Trainer/Super Users training: We are combining Train-the-Trainer and Super User sessions into a single, streamlined curriculum. Starting in late June 2026, multiple sessions will be offered throughout an eight-week window to accommodate schedules. 
  • End User Instructor-Led Training: Beginning in August 2026, leading up to the CWS-CARES Version Go-Live in October 2026. 

The team is currently working on the detailed plans for these activities, and we look forward to sharing more information with you in May. 

With the successful restart of our monthly Implementation Readiness meetings on April 13, 2026 we have confirmed interim Implementation Lead (IL) assignments for both Child Welfare and Probation. Please find the current assignment roster attached. 

As we continue to onboard resources and assess the specific needs of each organization, please note that there may be further adjustments to these assignments in June. These updates will ensure that every partner receives the dedicated support required for a successful transition. 

We appreciate your ongoing partnership as we continue to prepare for these significant milestones. 

Action Required:  
No action is required.

CWS/CMS: End-date of Inactive CWS/CMS User Logins for CWS-CARES Readiness – UPDATE

All SPOCs and Technical Contacts:

April 7, 2026 UPDATE: After a one-month hiatus for March, the automated process to end‑date inactive CWS/CMS user logins has resumed for April. The new reports were generated and saved to SAFE on Tuesday, April 7, 2026. The SAFE file is titled, “SCR9039_END-DATE_USERID_2026-04-07.xlsx.” REMINDER: this is the final month that the report will list CWS/CMS user accounts that have been inactive for the previous 180 days. Beginning in May, the reports will list accounts that have been inactive for 90 days.

Please review your organization’s report, saved in the SAFE folder. Organizations that do not have any potential accounts to end‑date in their report will, instead, find the following statement, “NO ROWS FOR DATA QUALITY CLEANSE”.

If needed, up to ten (10) listed accounts may be requested to be excluded from the automated end‑date process. Only a few organizations currently have more than ten (10) accounts listed. Please submit your exclusion file by Thursday, April 23, 2026, at 5:00 PM, to request listed user logins from being end-dated when the process runs on Saturday, April 25, 2026. If more than ten (10) user logins are needed to be excluded, please send your justification to the CWDS Customer Relations mailbox (CWS_CustRel@otsi.ca.gov). The justification will be forwarded to the review team for consideration. No action is required if your county agrees with the list as provided.

As stated in the SCR 9039 FAQ document, CWS/CMS User IDs that need to be reactivated following the automated end‑date process can be accomplished by contacting the IBM Help Desk at 800-428-8268. Please note that the process to reactive the accounts is complex and does take one or two weeks to be completed by the IBM team. User accounts from the reports that are logged in prior to Friday, April 24, 2026, at 5:00 PM, will not be end‑dated in the automated process on April 25, 2026.

__________________________________________________________________________

March 5, 2026 UPDATE: The CWDS Project has decided to not run the automated process to end-date inactive CWS/CMS user logins during March. The monthly process will resume in April. The next reports will be sent to the SAFE folder approximately April 7, 2026.

____________________________________________________________________

February 18, 2026 UPDATE: This is a reminder to submit an exclusion file, if needed, by Thursday, February 19, 2026, at 5:00 PM to prevent up to ten (10) user logins from being end-dated. No action is required if your county agrees with the list as provided.

______________________________________________________________________________________________

February 11, 2026 UPDATE:  As presented at the February 10, 2026 Technical Advisory Committee (TAC) Meeting, we are sharing the updated SCR 9039 FAQ document for your reference.   

_____________________________________________________________________

February 6, 2026 UPDATE: Based on received feedback, the reports are being updated for the following criteria:

Report criteria:

Identifies CWS/CMS user logins that have not been used in the past 180 days 

However, users are omitted from the report if they fall into one of these two categories:

  1. Have NOT logged into CWS/CMS within the previous 180 days, but HAVE logged into CARES-Live within the previous 180 days.
  2. The User ID has been created within the previous 90 days, and has NOT logged into CWS/CMS.

Updated reports, using the new criteria listed above, will be made available in SAFE in the FromOSI folder no later than 5:00 PM, on Friday, February 6, 2026, titled: 
SCR9039_END-DATE_USERID_2026-02-06.xlsx. 

Please use this updated report when reviewing the list of user logins identified for deactivation.

_____________________________________________________________________

To prepare for CWS-CARES Mock Cycles and Production Simulation, the CWS-CARES Project will begin an automated process to end-date inactive CWS/CMS user logins. This effort helps ensure that only active users are set up with access in CWS-CARES. 

This process identifies CWS/CMS user logins that have not been used in the past 180 days and schedules those logins to be end-dated. This is standard account cleanup intended to reduce inactive or outdated system access as counties prepare for CWS-CARES. 

What This Means for Counties 

  • This activity affects system access only. There are no impacts to caseloads, staff roles, office assignments, or authority. 
  • User logins associated with an active County License Case (CLC) are excluded from the report. 
  • All user accounts (active and inactive) will still be carried forward to CWS-CARES. 

County Review and Option to Exclude User Logins  

Counties will have an opportunity to review the list of user logins identified for deactivation. To accommodate staff on extended leave (such as administrative or maternity leave), counties may exclude up to 10 user logins from deactivation, if needed. 

A report will be available in SAFE in the FromOSI folder on February 2, 2026, titled: 
SCR9039_END-DATE_USERID_2026-02-02.xlsx. 

If your county wishes to exclude user logins: 

  1. Use the Excel file provided. 
  2. Keep only the rows (up to 10) for user logins you want excluded. 
  3. Do not modify the file layout or formatting. 
  4. Upload the file to SAFE in the ToOSI folder. 

If more than 10 exclusions are needed, please contact CWDS Customer Relations and include a brief explanation. 

Deadline: February 19 at 5:00 PM 
Files received after this deadline will not be accepted, and all user logins listed in the original report will be end-dated. 

Timing and Ongoing Process 

  • This first run will process and end-date User IDs on February 21, 2026. 
  • The 180-day inactivity threshold will remain in place through April 2026, giving counties additional time to review the list and adjust to new processes. 
  • Beginning May, the inactivity threshold will change to 90 days, consistent with CWS-CARES access policy and the Production Simulation environment
  • After February, this process will occur monthly until the transition to CWS-CARES: 
  • Reports will be posted after the first weekend of each month 
  • User logins will be deactivated during the fourth weekend of the month 
  • Counties will receive advance notice of specific dates 

Restoring a User Login 

If a user login is end-dated and later needs to be restored, counties may submit a Help Desk ticket to reinstate the existing login and associated staff access. 

Action Required 

  • Review the report of inactive CWS/CMS user logins when it becomes available in SAFE. 
  • Submit an exclusion file (if needed) by February 19 at 5:00 PM to prevent up to 10 user logins from being end-dated. 
  • No action is required if your county agrees with the list as provided. 

For questions or concerns, please contact the CWDS Customer Relations mailbox.