Skip to main content

Boot Management and Self-Release System

It provides a comprehensive overview of the Boot Management and Self-Release System. This feature allows enforcement officers to apply a physical boot to a vehicle and enables the vehicle owner to pay their violation(s) and receive a release code via email to remove the boot themselves.

The self-release boot system is designed to increase operational efficiency, reduce administrative and labor costs, and provide a more convenient resolution process for end-users.

Setup and Configuration

To use the boot management system, an administrator must first enable and configure several settings within the admin portal.

System-Wide Settings

  • Go to System Config, then General Settings.

  • Locate the boot management section.

  • Enable the Boot Management Active setting to turn the entire feature on.

  • Configure the payment requirement setting. You can choose to require a user to pay only the violation associated with the boot or pay all outstanding violations on their account before the release code is sent. This setting is deployed Off by default.

Boot Inventory Setup

You must create an inventory of your physical boots before they can be assigned to violations.

  • Go to Permit Management and click on Boot Management.

  • Click the Boot Editor button.

  • Click Add New Boot.

  • Enter a descriptive Boot Name (e.g., "Red Boot 01") and the corresponding Boot Release Code.

  • Click Save. Repeat for all boots in your inventory. You can edit the name and release code here at any time.

Violation Type Configuration

You must specify which violation types are eligible for booting.

  • Navigate to Violation Admin and click Ticket Types.

  • Select the specific ticket type you wish to edit.

  • Enable the Can Be Used With Boot checkbox.

  • Click Save. When this violation type is selected during violation entry, the option to assign a boot will now appear.

Email Template Customization

The email containing the release code and instructions is customizable.

  • Navigate to System Config, then Email Template Management.

  • Locate and select the Boot Release Email template.

  • Customize the content to include specific instructions for how the user should remove the boot and where they should return it.

  • Click Save.

Using this Feature

This section details the daily operational use of the boot management system, from issuing a booted violation to managing the boot's return.

Issuing a Booted Violation

When issuing a violation for a boot-eligible offense, both on the handheld device and in the admin portal, the officer will see a new option.

  • During the violation entry process, select a ticket type that has been configured for boot use.

  • A new field, Apply Boot, will appear.

  • From the dropdown menu, select the specific boot being applied to the vehicle. The list will show available boots first.

  • Complete and save the violation as usual. The system now logs that the selected boot is In Use and linked to this violation.

The User Payment and Release Process

Once a vehicle is booted, the user must pay the required violation(s) to receive the release code.

  • The user can pay via the online portal, either by logging into their account or using the Guest Payment option.

  • When a violation with an associated boot is in the payment cart, a boot icon will be displayed next to it.

  • Upon successful payment, the system automatically sends the Boot Release Email to the user's provided email address. This email contains the release code and return instructions you configured in the template.

A valid email address is mandatory to complete the payment. Logged-in users must have an email on file, and guest users will be required to enter one before checkout. (They do not need an account)

Boot Management Report

This report is your central hub for tracking the status of all your boots. To access it, navigate to Permit Management and click Boot Management.

Key Information Displayed

  • Vehicle Plate: The license plate of the vehicle the boot is assigned to.

  • Boot Identifier: The name of the boot.

  • Violation Ticket Number: The linked violation.

  • Status: The current status of the boot (In Use, Released/Not Returned, or Returned).

  • Date Created: When the boot was assigned to the violation.

  • Date Released: When the payment was made and the code was sent.

  • Date Returned: When an admin marked the boot as physically returned.

Available Actions

From the report, administrators can perform key actions:

  • Mark as Returned: When a user returns a boot, locate it in the report and click the Return button. This updates the boot's status to Returned, making it available for reuse.

  • Manage Deposit Refund: If the boot was issued with a deposit, you will have an option to Process Refund when marking the boot as returned. This initiates the standard refund process for the deposit amount.

Best Practices and Considerations

  • Develop a Business Rule for Non-Returns: It's crucial to establish a clear policy for handling boots that are not returned. This may involve applying additional fines or fees to the user's account after a specified period.

  • Consider using the Boot as a Deposit functionality for high-risk situations. By adding a separate, refundable fee item to the violation, you create a financial incentive for the user to return the equipment promptly. 

  • Keep Inventory Accurate: Regularly audit your physical boots against the Boot Management Report to ensure all information, especially release codes and statuses, is correct.

  • Clear Email Instructions: Ensure your Boot Release Email template provides simple, clear, and comprehensive instructions. Including photos or diagrams of the boot removal process and a map to the drop-off location can greatly improve the user experience and increase return rates.

Back to top