Request Warrant

Business Processes

Warrant Business Functions

Two common scenarios for requesting warrants have been identified. The first scenario supports jurisdictions where a Requesting Entity submits a warrant application directly to an Approving Entity. The second scenario supports jurisdictions where warrant requests must first be screened by an intermediary before being submitted to the Approving Entity. Note that both of these scenarios are supported by a single process flow.

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

Primary Flow
Request Warrant-Primary (png)
Request Warrant-Primary (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

A Requesting Entity (Law Enforcement, Prosecution, Corrections, Probation, Parole, etc.) generates a Warrant Request Message containing the details of the warrant request and any documentation required to support the request (incident report, witness statement, etc.)

The Warrant Request Message is sent to a Screening Entity for review. In jurisdictions where intermediate screening of warrant requests is required, the Screening Entity will typically be the Prosecution. In jurisdictions where there is no intermediate screening, the Screening Entity will be the Approving Entity, or, alternatively, the screening step can be omitted entirely.

The Screening Entity reviews the warrant request and decides whether to authorize or deny the warrant request.

	If denies the warrant request, a Warrant Request Decision Message is sent to the Requesting Entity indicating the reason the request was denied (further investigation required, insufficient documentation, prosecution declined, etc.).
	If authorizes the warrant request, a Warrant Request Message is generated and sent to an Approving Entity (typically the Court).

The Approving Entity reviews the warrant request and decides whether to approve or deny the warrant request.

	If denies the warrant request, a Warrant Request Decision Message is sent to the Requesting Entity indicating the reason the request was denied.
	If approves the warrant request, a Warrant Message is generated and sent to an Issuing Entity (typically the Court Clerk or the Court itself). A Warrant Request Decision Message is also sent to the Requesting Entity indicating the request was approved.

The Issuing Entity receives the Warrant Message and issues the warrant.

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

Role

Responsibilities

Actors

Requesting Entity

	Prepares and submits a warrant request to an Approving Entity or, in jurisdictions with intermediate screening, a Screening Entity
	Receives the outcome of a previously-submitted warrant request from either a Screening Entity or Approving Entity

	Law Enforcement
	Prosecution
	Corrections
	Probation
	Parole

Screening Entity

	In jurisdictions with intermediate screening, receives and reviews requests for warrants
	Authorizes or denies the warrant request
	Notifies the requesting entity of the review outcome
	If the request is authorized, submits the request to an Approving Entity

	Prosecution
	Court

Approving Entity

	Receives requests for warrants from Requesting and Screening Entities
	Approves or denies the warrant request
	Notifies an Issuing Entity that a warrant should be issued

Court

Issuing Entity

	Receives approved warrants from an Approving Entity
	Issues the warrant by distributing the warrant document to appropriate entities

	Court
	Court Clerk

In jurisdictions where there is no intermediate screening the Approving Entity would also fulfill the role of the Screening Entity. This responsibility typically lies with the Court. In the interest of generality they are depicted separately in the process flow. In jurisdictions that do not require intermediate screening by a separate entity (e.g. Prosecution) this role may be omitted entirely. In these implementations the Requesting Entity would submit requests directly to an Approving Entity.