Skip to main content

Boot Management and Self-Release System

This article 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 Configuration, then System Settings.

  • Locate the Third Party section.

  • Enable the Universal Boot Enabled checkbox to turn the entire feature on.

  • Configure the Require Overdue Paid checkbox. You can choose to require a user to pay only the violation associated with the boot (Disabled) or pay all overdue violations on their account (Enabled) 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 System Configuration, then Violations, and click on Setup Boot Devices.

  • Click + in the top right to Add Booting Device.

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

  • Click Save. The system will automatically generate a printable QR code for the physical boot, allowing booted users to scan it and directly pay their associated ticket.

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

Editing the Release Code value will only change the code that is stored in OPSCOM and sent to user for boot release. It must be obtained from the booting device's instructions first and updated as necessary.

Violation Type Configuration

You must specify which violation types are eligible for booting.

  • Go to Violations and click on Offense Types.

  • Select the ticket category where you want to add the booting offense type.

  • Click Add New Offense Item.

  • In the Violation Type Description field, enter a descriptive name (e.g., "Boot Applied").

  • Enable the Apply Boot checkbox.

  • Click Save. When this offence 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.

  • Go to System Configuration, then Content and Design, and click Email Templates.

  • 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.

  • This

    email template has a set of available shortcodes displayed under the template editor that you can use to dynamically insert specific information into your message.

  • Click Save.

    Save Email Template.

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 the ticket type Boot Applied

  • A dropdown calledmenu field,called, Apply Boot, will appear.

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

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

You MUST make sure you do not assign an occupied boot to another vehicle. If no boots are marked as Available, the list will start with a title saying either Released or Issued. Issued boots are currently occupied, while Released means that the code was sent to the user and payment received for the violation, but the boot hasn't necessarily been returned.

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 bootBoot iconApplied tag will be displayed next towithin 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. 
    For more information on how the user side process works please see Self-Release Boot System: User Portal.

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)

BootBooting DeviceActivity Report

This report is your central hub for tracking the status of all your boots. To access it, go to Violations, and and click UniversalBooting BootActivity Devices.Report.

Key Information Displayed

  • BootSearch IdentifierText: The name of the boot.boot, plate number of a booted vehicle, or ticket number.

  • ViolationFilter TicketDate NumberBy: Date Created, Date Released, or Date Returned.

  • Start Date: The linkedbeginning violation.date for the report's search range.

  • Up To and Including: The end date for the report's search range (includes data from this day).

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

Active Boot Assignments Overview

The DateActive CreatedBoot Assignments: Whendashboard provides a real-time overview of your physical booting inventory, allowing administrators to monitor device statuses, track active violations, and manage configurations from a single interface.

Dashboard Key Features
  • Real-Time Status Tracking: Monitor the current state of each device at a glance using color-coded status badges:
    • Issued: The boot wasis assignedcurrently deployed on a vehicle.
    • Released: The boot has been paid for or authorized for removal, pending return to theinventory.
      • violation.

    • Returned: The boot has been removed and brought back, ready for deposit/refund processing.
    • Available: The boot is in inventory and ready to be assigned.

    And

    • if
  • Violation applicable;

    & Ticket Linking:     View active ticket details directly tied to an issued boot, including the Issued date, Ticket (hyperlinked for quick access), and the applicable Boot Fee.
  • Quick Actions & Navigation:

    • DateBooting Released:Activity Report:When Click this button at the paymenttop wasright madeto generate historical data and thesearch code was sent.reports.

    • DateSetup Returned:Boot Devices:When anQuickly adminjump markedto the bootinventory assetup 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 Edit button, and select Return from the status dropdown. This updates the boot's statuspage to Returned,add makingor itedit availablebooting for reuse.devices.

    • ManageAction DepositGear RefundIcon:: IfClick the bootgear wasicon issuedon withthe aright deposit,of youany will have an optionrow to Processupdate Refunddevice whenstates, marking the boot as returned. This initiates the standard refundor process for the deposit amount.refunds.

    • For
    example, you may choose NOT to issue the refund of the boot deposit, if the boot is damaged, or was not returned in satisfactory condition.

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, isare 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