Warrant Issue
There are three common scenarios for issuing warrants:
    1. The Issuing Entity notifies the Owning Entity that a warrant has been issues and the Owning Entity distributes this information to other interested parties.
    2. The Issuing Entity notifies the Repository that a warrant has been issued and the Repository distributes this information to other interested parties. 
    3. The Issuing Entity notifies both the Owning Entity and Repository simultaneously and both distribute the information to the interested parties. 

The distinction among these three scenarios lies in the process concept "Subscribing Entity" used for distributing information about issued warrants. When a warrant is issued, any number of entities may need to receive notification. Because there is considerable jurisdictional variation in routing notifications, this model does not specify the lines of business that might receive a warrant notification. For example, one implementation may send these notifications to involved parties (Requesting Entity, Screening Entity, etc.) based on the content of the warrant or the type of warrant update. Other implementations may have no need for such notifications.

The following links provide Business Process Flow Diagrams for the Warrant Issue Business Function:

Primary Flow
Warrant Issue-Primary (png)
Warrant Issue-Primary (bpm)

Alternate Flow 1
Warrant Issue-Alternate 1 (png)
Warrant Issue-Alternate 1 (bpm)

Alternate Flow 2
Warrant Issue-Alternate 2 (png)
Warrant Issue-Alternate 2 (bpm)

The sample process flow diagram was developed in standard Business Process Model and Notation using the Windows-based Bizagi Modeler tool and can be modified to represent the specific process in your jurisdiction. To download a free copy of the Bizagi Modeler tool, go to bizagi.com.

Primary Flow Description
An Issuing Entity (Court, Court Clerk) receives a Warrant Message from an Approving Entity (Court) indicating that a new warrant is to be issued. 
The Issuing Entity generates and sends a Warrant Message to the Owning Entity (Law Enforcement) that will be responsible for maintaining and servicing the warrant. 
The Owning Entity generates and sends a Warrant Message to the Repository. The Repository processes this message and adds the warrant to the repository. 
If necessary, the Owning Entity generates and sends a Warrant Notification to any Subscribing Entities. Which entities receive such notifications will depend on the type of warrant and jurisdiction. 
If necessary, the Repository submits the warrant information to NCIC.

Alternative Flow 1 Description

An Issuing Entity (Court, Court Clerk) receives a Warrant Message from an Approving Entity (Court) indicating that a new warrant is to be issued. 
The Issuing Entity generates and sends a Warrant Message to the Repository. The Repository processes this message and adds the warrant to the repository. 
The Repository generates and sends a Warrant Message to the Owning Entity (Law Enforcement) that will be responsible for maintaining and servicing the warrant. 
If necessary, the Repository generates and sends a Warrant Notification to any Subscribing Entities. Which entities receive such notifications will depend on the type of warrant and jurisdiction. 
If necessary, the Repository submits the warrant information to NCIC. 
 Alternate Flow 2 Description
An Issuing Entity (Court, Court Clerk) receives a Warrant Message from an Approving Entity (Court) indicating that a new warrant is to be issued. 
The Issuing Entity generates and sends a Warrant Message to the Owning Entity (Law Enforcement) that will be responsible for maintaining and servicing the warrant as well as the Repository.
If necessary, the Owning Entity generates and sends a Warrant Notification to any Subscribing Entities. Which entities receive such notifications will depend on the type of warrant and jurisdiction. 
The Repository processes the Warrant Message and adds the warrant to the repository. 
If necessary, the Repository submits the warrant information to NCIC. 


The following table summarizes the responsibilities of each role depicted in the business process flows:

Role Responsibilities Actors

Requesting Entity

Receives the outcome of a previously-submitted warrant request from either a Screening Entity or Approving Entity 
Law Enforcement 
Prosecution 
Corrections 
Probation 
Parole 

Issuing Entity

Issues the warrant by distributing the warrant document to appropriate entities 
Court 
Court Clerk 

Owning Entity

Receives issued warrants from an Issuing Entity 
Maintains the warrant (submits updated information, locates warrant subject, etc.) 
Law Enforcement 

Subscribing Entity

Receives notification that a warrant has been issued 
  •  
Law Enforcement 
  •  
Prosecution 
Corrections 
Probation 
Parole 
Court 
Court Clerk 


The Issuing Entity generates and sends a Warrant Message to the Repository. The Repository processes this message and adds the warrant to the repository. 
The Repository generates and sends a Warrant Message to the Owning Entity (Law Enforcement) that will be responsible for maintaining and servicing the warrant. 
If necessary, the Repository generates and sends a Warrant Notification to any Subscribing Entities. Which entities receive such notifications will depend on the type of warrant and jurisdiction.