On June 1, 2022 a new warrant tracking feature launched into ICOTS. Since launch, the national office has analyzed data creating a new warrant tracking dashboard. The training will cover how the new dashboard manages warrant entries and how other existing reports can be used to identify cases which may require a warrant. As noted in the functional details of the warrant feature, emails serve as reminders for warrant data entries but actual case information should be reviewed when determining warrant requirements and timeframes for compliance.
In May, DCAs and compact staff received training on use of the new features. (You may find resources from that training (including a recording, PowerPoint, and Q&A) here.)
The training will also provide an opportunity to ask questions regarding the FY23 compliance audit.
Register for Training
New Warrant Tracking Dashboard
Q & A
Warrant Status Feature
Q: Is there a way to lock the access down to make warrant entries so only supervisor above have access to enter the warrant information for data integrity?
A: This enhancement was approved by the Commission to allow for any sending state associated user to be able to make warrant entries. To change permissions in ICOTS would require a future enhancement to be approved again by the Commission. States should direct users on which users in their state will be tasked at making entries.
FY23 Compliance Audit Details
Q: To make corrections to erred data many times requires involvement of a receiving state. Why can't the sending state correct via the 'edit demographic' administrative functions?
A: Editing core demographics is locked down to the supervising state (where the client currently is under supervision). Sending states are expected to review transfer documentation PRIOR to submission for requesting transfer. At this stage (and until a NOA is submitted by the receiving state) the sending state is the supervising state and can make such changes. Instances in which a sending state requires receiving state involvement to correct data (the client has already transferred) means the sending state failed to catch such error in its initial outgoing activity review and should be addressed with staff to avoid requiring receiving state involvement in future data cleanup.