Will this be mandatory?

Use of the eWarrants system is not currently mandatory and there is not a date that it is expected to be mandatory. Language is pending in the currently proposed state budget bill that will mandate the entry of Tier one offenses as well as protection orders into LEADS and NCIC; however, the language does not specifically address the new eWarrants system, as we have not completed the build of that system.

Do users have to enter all the information into the program and then turn around and re-enter it into LEADS/NCIC?

No. All information that hits the eWarrants system is automatically forwarded to LEADS/NCIC provided all information meets LEADS/NCIC requirements.

Does eWarrants interface with our current RMS?

We are still identifying all systems that are in play, but the goal is to interface with any system an agency currently utilizes for their warrant & protection order workflows.

Will this process replace LEADS/NCIC entry or is it in addition?

This process does not replace LEADS/NCIC, but is in sync with LEADS/NCIC. Once a warrant/protection order has been approved within the eWarrants system and meets all LEADS/NCIC requirements, it automatically goes into LEADS/NCIC which eliminates redundant work.

Who will be responsible for entry of warrants and CPOs?

This remains the discretion of each agency and will be discussed during the implementation process.

Prior to entering warrants and CPOs, we are required to run CCH, OL, etc. information in order to find out if they should be entered with cautions. Will we (the LEADS terminal operator) still continue doing this?

Operators will still need to "pack the record" and this process will be completed either before or after authorization.

Is this an additional system we will need to check to find out if someone has an active warrant or CPO?

eWarrants is not an additional system that you will have to check, instead it will be linked up with your existing systems to streamline the flow whether you enter/remove the warrant/protection order into your current in-house method or you do these steps directly within eWarrants. All actions hit the eWarrants system which sync directly with LEADS/NCIC.

When an agency begins using the eWarrants interface for new warrants and protection orders, what happens to the pre-existing entries already entered into LEADS?

The existing warrant and protection order entries in LEADS will be back filled into eWarrants.

Once the eWarrants interface is in place for my agency, how does it impact the way we conduct validations?

Validations will continue to be accessed on the LEADS validations website, processed and reported complete as required by the FBI NCIC Operating Manual - Introduction Chapter, Section 3.4.

eWarrants and LEADS are working to automate the warrant and protection order validation process by cross checking entries in LEADS against the electronic source record in eWarrants.

Once the eWarrants interface is in place for my agency, how does it impact the audit processes?

The LEADS audit process will be less time consuming for agencies. All warrants and protection orders will be reviewed prior to the audit and not at the local agency.

Once a warrant has been authorized by a judge and the base entry automatically goes into LEADS/NCIC, how long does an operator have to pack the record?

The FBI NCIC Manual - Introduction Chapter, Section 3.1.2.3 requires the entry, modification, update and removal of information to be completed as soon as possible after information is available and information is processed and transmitted.

In a situation where a warrant and/or protection order has been authorized by a judge, thereby causing the base record to go directly into LEADS/NCIC, what happens if the base information is incorrect and remains entered until packing? Who is responsible if the wrong person is arrested?

The NCIC Manual – Introduction Chapter, Section 1.3 requires records to be kept accurate and up-to-date. Agencies that enter records in the system are responsible for their accuracy, timeliness, and completeness. The law enforcement agency and court must coordinate modification of the record as soon as possible if incorrect information is noted.

Who and how are forms recalled in the system and how quickly are recalled forms reflected in LEADS?

The "Authorizer" role in eWarrants my rescind warrants, dismiss orders, and transition orders from EXPARTE to Full. In the real world these roles include Judge/Magistrate, Clerk granted authority to sign warrants/orders, LEADS Operator/TAC which is the user that packs the record and prepares it for transfer to and interface with LEADS/NCIC, and a server that serves the warrants/orders and enforces active orders. The record can be recalled/cleared with a click of a button within eWarrants. Of course, the process caries from agency to agency as to when the instruction to recall is provided which can impact timeliness.