<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.tracsflorida.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Admin</id>
	<title>TraCS Florida Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.tracsflorida.org/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Admin"/>
	<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Special:Contributions/Admin"/>
	<updated>2026-06-15T04:38:34Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3717</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3717"/>
		<updated>2026-06-12T21:25:08Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;TraCS Crash Form&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should select Other Pedestrian for the Non-Motorist Description, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and document that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3716</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3716"/>
		<updated>2026-06-12T21:21:09Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;text-align: center;&amp;quot;&amp;gt;&#039;&#039;&#039;TraCS Crash Form&#039;&#039;&#039;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should select Other Pedestrian for the Non-Motorist Description, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and document that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3715</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3715"/>
		<updated>2026-06-12T21:20:54Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&amp;lt;div style=&amp;quot;text-align: center;&amp;quot;&amp;gt;&#039;&#039;&#039;TraCS Crash Form&#039;&#039;&#039;&amp;lt;/div&amp;gt;&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should select Other Pedestrian for the Non-Motorist Description, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and document that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3714</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3714"/>
		<updated>2026-06-12T21:14:11Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;TraCS Crash Form&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should select Other Pedestrian for the Non-Motorist Description, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and document that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3713</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3713"/>
		<updated>2026-06-11T21:04:00Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should select Other Pedestrian for the Non-Motorist Description, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and document that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3712</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3712"/>
		<updated>2026-06-11T21:03:18Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should select Other Pedestrian for the Non-Motorist Description, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and report that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3711</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3711"/>
		<updated>2026-06-11T21:01:04Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micro-mobility device, officers should mark the Non-Motorist Description as Other Pedestrian, mark the E-Bike/Scooter/Micro-mobility Device field as Yes, and report that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3710</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3710"/>
		<updated>2026-06-11T21:00:19Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, e-scooter, or other micromobility device, officers should mark the Non-Motorist Description as Other Pedestrian, mark the E-Bike/Scooter/Micromobility Device field as Yes, and report that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3709</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3709"/>
		<updated>2026-06-11T14:33:05Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, scooter, or other micromobility device, officers should mark the Non-Motorist Description as Other Pedestrian, mark the E-Bike/Scooter/Micromobility Device field as Yes, and report that information in the narrative.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3708</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3708"/>
		<updated>2026-06-11T14:31:13Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating an e-bike, scooter, or other micromobility device, officers should mark the Non-Motorist Description as Other Pedestrian and mark the E-Bike/Scooter/Micromobility Device field as Yes.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3707</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3707"/>
		<updated>2026-06-11T14:30:05Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating a scooter or micromobility device, officers should mark the Non-Motorist Description as Other Pedestrian and mark the E-Bike/Scooter/Micromobility Device field as Yes.&lt;br /&gt;
&lt;br /&gt;
[[File:NonMotoristCrash.png]]&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=File:NonMotoristCrash.png&amp;diff=3706</id>
		<title>File:NonMotoristCrash.png</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=File:NonMotoristCrash.png&amp;diff=3706"/>
		<updated>2026-06-11T14:28:01Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=File:ScooterField2.png&amp;diff=3705</id>
		<title>File:ScooterField2.png</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=File:ScooterField2.png&amp;diff=3705"/>
		<updated>2026-06-11T14:26:03Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3704</id>
		<title>Crash - Motorcycles, Mopeds, &amp; Micro-Mobility Devices</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Crash_-_Motorcycles,_Mopeds,_%26_Micro-Mobility_Devices&amp;diff=3704"/>
		<updated>2026-06-11T14:25:39Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Micro-Mobility Devices */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;====Overview====&lt;br /&gt;
&lt;br /&gt;
When completing a crash, officers should be sure they are using the correct designations for motorcycles, mopeds, autocycles, and micro-mobility devices as well as the persons involved in those incidents. &lt;br /&gt;
&lt;br /&gt;
A Florida crash report must include a motor vehicle ([https://www.flhsmv.gov/pdf/courts/crash/crashmanualcomplete.pdf FLHSMV Crash Manual - Page 3]). &amp;amp;nbsp; If an incident does not involve a motor vehicle, then it does not belong on a crash form.&lt;br /&gt;
&lt;br /&gt;
====FLHSMV Guidelines====&lt;br /&gt;
&lt;br /&gt;
The following information has been provided by FLHSMV. &lt;br /&gt;
&lt;br /&gt;
=====Motorized Scooter vs. Motorcycle=====&lt;br /&gt;
&lt;br /&gt;
If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
If you are not sure, check the speed measurement device and/or decode the VIN. &amp;amp;nbsp; Click here for the [https://vpic.nhtsa.dot.gov/decoder/ NHTSA VIN Decoder].&lt;br /&gt;
&lt;br /&gt;
=====Mopeds, Motorcycles, and Autocycles=====&lt;br /&gt;
&lt;br /&gt;
Definitions of Moped, Motorcycle, and Autocycle are in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003].&lt;br /&gt;
:Moped - 316.003 (44)&lt;br /&gt;
:Motorcycle - 316.003 (47)&lt;br /&gt;
:Autocycle - 316.003 (2)&lt;br /&gt;
&lt;br /&gt;
Mopeds have pedals to permit propulsion by human power.  &amp;amp;nbsp; They cannot exceed 50cc and their top speed cannot be greater than 30 MPH.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Vehicle Body Type: Moped vs Motorcycle&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Type of Vehicle !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| Moped || Driver || Moped || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (50cc or below) || Driver || Motorcycle || No - [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0322/Sections/0322.01.html FSS 322.01(28)]&lt;br /&gt;
|-&lt;br /&gt;
| Motorcycle (above 50cc) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|-&lt;br /&gt;
| Autocycle (2 wheels in front, 1 in back) || Driver || Motorcycle || Yes - [http://www.leg.state.fl.us/statutes./index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0322/Sections/0322.03.html FSS 322.03(5)]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=====Micro-Mobility Devices=====&lt;br /&gt;
&lt;br /&gt;
The definition of a micro-mobility device is in [http://www.leg.state.fl.us/STATUTES/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.003.html FSS 316.003(41)]&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0320/Sections/0320.01.html FSS 320.01(a)], micro-mobility devices are not considered motor vehicles. &amp;amp;nbsp; Their speed cannot be greater than 20 MPH. &amp;amp;nbsp; If a motorized scooter has a top speed that is above 20 MPH, then it is a motorcycle.&lt;br /&gt;
&lt;br /&gt;
Per [http://www.leg.state.fl.us/Statutes/index.cfm?App_mode=Display_Statute&amp;amp;Search_String=&amp;amp;URL=0300-0399/0316/Sections/0316.2128.html FSS 316.2128] micro-mobility devices and motorized scooters do not require their operator to have a license, registration, or insurance.&lt;br /&gt;
&lt;br /&gt;
Since micro-mobility devices are not considered motor vehicles, they are not listed in the vehicle section of the crash form.  &amp;amp;nbsp; Explain the micro-mobility device in the narrative. &lt;br /&gt;
&lt;br /&gt;
Operators of micro-mobility devices are considered non-motorists.&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; style=&amp;quot;margin: auto;&amp;quot;&lt;br /&gt;
|+ Non-Motorist Description: Micro-Mobility Device&lt;br /&gt;
|-&lt;br /&gt;
! !! Person Type !! Non-Motorist Description !! Endorsement Required&lt;br /&gt;
|-&lt;br /&gt;
| E-Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Motorized Scooter || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| Hoverboard || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|-&lt;br /&gt;
| E-Bike || Non-Motorist || Other Pedestrian || No&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
When non-motorists are operating a scooter or micromobility device, officers should mark the Scooter? field in the Non-Motorist section as Yes.&lt;br /&gt;
&lt;br /&gt;
[[File:ScooterField2.png]]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=TraCS_FDLE_Audit_Checklist&amp;diff=3703</id>
		<title>TraCS FDLE Audit Checklist</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=TraCS_FDLE_Audit_Checklist&amp;diff=3703"/>
		<updated>2026-06-10T20:51:01Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* MFA Options */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;TraCS is approved by FDLE as a CJIS compliant vendor and meets all FBI security policy requirements.&lt;br /&gt;
&lt;br /&gt;
===Authorized Personnel===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/EmployeeMemo.pdf Employee Memo]&lt;br /&gt;
&lt;br /&gt;
===Security and Privacy Training===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Amy.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Jamie.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Seth.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Mike.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Kathy.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Roman.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Shawn.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Gary.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===FCIC/NCIC Limited Access Certification===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/AmyLA.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/JamieLA.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/SethLA.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/MikeLA.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/KathyLA.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/RomanLA.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/ShawnLA.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/GaryLA.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===Security Addendum===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/AmySA.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/JamieSA.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/SethSA.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/MikeSA.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/KathySA.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/RomanSA.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/ShawnSA.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/GarySA.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===FIPS 140-2 Certificates===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/BeyondTrustFIPS.pdf BeyondTrustFIPS]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/CISCOASA5516FIPSCertificate.pdf CISCOASA5516FIPSCertificate]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/TraCSFIPS.pdf TraCSFIPS]&lt;br /&gt;
&lt;br /&gt;
===TraCS Florida License Agreement===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/TraCSFLLicenseAgreement.pdf TraCSFLLicenseAgreement]&lt;br /&gt;
&lt;br /&gt;
===MFA Options===&lt;br /&gt;
&lt;br /&gt;
TraCS integrates with DUO, Microsoft Authenticator, and Google Authenticator for MFA using a 6-digit code. &amp;amp;nbsp; The settings must be turned on for each user by support staff. &lt;br /&gt;
&lt;br /&gt;
Below is a link to a short video that shows how easy the setup is for officers.  &lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=VnxKQFoyP18 MFA Set Up for Officers]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=TraCS_FDLE_Audit_Checklist&amp;diff=3702</id>
		<title>TraCS FDLE Audit Checklist</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=TraCS_FDLE_Audit_Checklist&amp;diff=3702"/>
		<updated>2026-06-10T20:50:32Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* MFA Options */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;TraCS is approved by FDLE as a CJIS compliant vendor and meets all FBI security policy requirements.&lt;br /&gt;
&lt;br /&gt;
===Authorized Personnel===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/EmployeeMemo.pdf Employee Memo]&lt;br /&gt;
&lt;br /&gt;
===Security and Privacy Training===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Amy.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Jamie.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Seth.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Mike.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Kathy.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Roman.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Shawn.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Gary.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===FCIC/NCIC Limited Access Certification===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/AmyLA.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/JamieLA.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/SethLA.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/MikeLA.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/KathyLA.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/RomanLA.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/ShawnLA.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/GaryLA.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===Security Addendum===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/AmySA.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/JamieSA.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/SethSA.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/MikeSA.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/KathySA.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/RomanSA.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/ShawnSA.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/GarySA.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===FIPS 140-2 Certificates===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/BeyondTrustFIPS.pdf BeyondTrustFIPS]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/CISCOASA5516FIPSCertificate.pdf CISCOASA5516FIPSCertificate]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/TraCSFIPS.pdf TraCSFIPS]&lt;br /&gt;
&lt;br /&gt;
===TraCS Florida License Agreement===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/TraCSFLLicenseAgreement.pdf TraCSFLLicenseAgreement]&lt;br /&gt;
&lt;br /&gt;
===MFA Options===&lt;br /&gt;
&lt;br /&gt;
TraCS integrates with DUO, Microsoft Authenticator, and Google Authenticator for MFA using a 6-digit code. &amp;amp;nbsp; The settings must be turned on for each user by support staff. &amp;amp;nbsp; Below is a link to a short video that shows how easy the setup is for officers.  &lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=VnxKQFoyP18 MFA Set Up for Officers]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=TraCS_FDLE_Audit_Checklist&amp;diff=3701</id>
		<title>TraCS FDLE Audit Checklist</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=TraCS_FDLE_Audit_Checklist&amp;diff=3701"/>
		<updated>2026-06-10T20:49:30Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;TraCS is approved by FDLE as a CJIS compliant vendor and meets all FBI security policy requirements.&lt;br /&gt;
&lt;br /&gt;
===Authorized Personnel===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/EmployeeMemo.pdf Employee Memo]&lt;br /&gt;
&lt;br /&gt;
===Security and Privacy Training===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Amy.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Jamie.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Seth.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Mike.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Kathy.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Roman.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Shawn.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/Gary.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===FCIC/NCIC Limited Access Certification===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/AmyLA.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/JamieLA.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/SethLA.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/MikeLA.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/KathyLA.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/RomanLA.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/ShawnLA.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/GaryLA.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===Security Addendum===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/AmySA.pdf Amy Pontillo]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/JamieSA.pdf Jamie Ingalls]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/SethSA.pdf Seth Bartee]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/MikeSA.pdf Michael Wilkinson]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/KathySA.pdf Kathleen Perry]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/RomanSA.pdf Roman Serrano]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/ShawnSA.pdf Shawn Moore]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/GarySA.pdf Gary Eggebraaten]&lt;br /&gt;
&lt;br /&gt;
===FIPS 140-2 Certificates===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/BeyondTrustFIPS.pdf BeyondTrustFIPS]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/CISCOASA5516FIPSCertificate.pdf CISCOASA5516FIPSCertificate]&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/TraCSFIPS.pdf TraCSFIPS]&lt;br /&gt;
&lt;br /&gt;
===TraCS Florida License Agreement===&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/downloads/FDLE/TraCSFLLicenseAgreement.pdf TraCSFLLicenseAgreement]&lt;br /&gt;
&lt;br /&gt;
===MFA Options===&lt;br /&gt;
&lt;br /&gt;
TraCS integrates with DUO, Microsoft Authenticator, and Google Authenticator for MFA using a 6-digit code.  The settings must be turned on for each user by support staff.  Below is a short video to show how easy the set up is for officers.  &lt;br /&gt;
&lt;br /&gt;
[https://www.youtube.com/watch?v=VnxKQFoyP18 MFA Set Up for Officers]&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3700</id>
		<title>Access Levels</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3700"/>
		<updated>2026-06-10T19:36:58Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following access levels are available in TraCS. &amp;amp;nbsp; For more on managing these levels for users, see [https://www.tracsflorida.org/wiki/index.php?title=Managing_Users Managing Users.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Standard Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records&#039;&#039;&#039; - Users may view, print, and export reports for other users, create searches, and run analysis reports.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reporter&#039;&#039;&#039; - In addition to Records permissions, users may create reports and edit and update their own reports. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewing Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, reviewing supervisors may Edit, Reject, and Review their own reports and reports for other users. &amp;amp;nbsp; &#039;&#039;Reviewing a report is not the same as Accepting (approving) a report.&#039;&#039; &amp;amp;nbsp; &#039;&#039;Reviewing Supervisor is only needed if your agency uses a two-tiered approval process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, supervisors may Edit, Reject, and Accept (approve) their own reports and reports for other users.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Agency Administrator (hosted)&#039;&#039;&#039; - Agency admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, and search for/view deleted forms. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;System Administrator (non-hosted)&#039;&#039;&#039; - System admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, search for and view deleted forms, unlock forms, archive forms, add form numbers to the database, and more.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Special Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking (hosted only)&#039;&#039;&#039; - Users may view parking citations and mark them as Paid but cannot create them or or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking Reporter (hosted only)&#039;&#039;&#039; - Users may create parking citations but cannot create or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records Data Entry&#039;&#039;&#039; - Users may keypunch [https://www.tracsflorida.org/wiki/index.php?title=UTC_Keypunching_Paper_Citations paper citations] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#How_to_Update_a_Crash_From_a_Previous_Vendor crashes from a previous vendor]. &amp;amp;nbsp; This level allows the user to type the HSMV number onto the form.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Investigator&#039;&#039;&#039; - This level is only used in conjunction with certain agency local rules.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3699</id>
		<title>Access Levels</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3699"/>
		<updated>2026-06-10T19:36:27Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following access levels are available in TraCS. &amp;amp;nbsp; For more on managing these levels for users, see [https://www.tracsflorida.org/wiki/index.php?title=Managing_Users Managing Users.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Standard Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records&#039;&#039;&#039; - Users may view, print, and export reports for other users, create searches, and run analysis reports.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reporter&#039;&#039;&#039; - In addition to Records permissions, users may create reports and edit and update their own reports. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewing Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, reviewing supervisors may edit, reject, and review their own reports and reports for other users. &amp;amp;nbsp; &#039;&#039;Reviewing a report is not the same as Accepting (approving) a report.&#039;&#039; &amp;amp;nbsp; &#039;&#039;Reviewing Supervisor is only needed if your agency uses a two-tiered approval process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, supervisors may Edit, Reject, and Accept (approve) their own reports and reports for other users.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Agency Administrator (hosted)&#039;&#039;&#039; - Agency admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, and search for/view deleted forms. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;System Administrator (non-hosted)&#039;&#039;&#039; - System admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, search for and view deleted forms, unlock forms, archive forms, add form numbers to the database, and more.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Special Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking (hosted only)&#039;&#039;&#039; - Users may view parking citations and mark them as Paid but cannot create them or or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking Reporter (hosted only)&#039;&#039;&#039; - Users may create parking citations but cannot create or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records Data Entry&#039;&#039;&#039; - Users may keypunch [https://www.tracsflorida.org/wiki/index.php?title=UTC_Keypunching_Paper_Citations paper citations] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#How_to_Update_a_Crash_From_a_Previous_Vendor crashes from a previous vendor]. &amp;amp;nbsp; This level allows the user to type the HSMV number onto the form.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Investigator&#039;&#039;&#039; - This level is only used in conjunction with certain agency local rules.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3698</id>
		<title>Access Levels</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3698"/>
		<updated>2026-06-10T18:55:53Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following access levels are available in TraCS. &amp;amp;nbsp; For more on managing these levels for users, see [https://www.tracsflorida.org/wiki/index.php?title=Managing_Users Managing Users.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Standard Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records&#039;&#039;&#039; - Users may view, print, and export reports for other users, create searches, and run analysis reports.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reporter&#039;&#039;&#039; - In addition to Records permissions, users may create reports and edit and update their own reports. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewing Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, reviewing supervisors may edit, reject, and review their own reports and reports for other users. &amp;amp;nbsp; &#039;&#039;Reviewing a report is not the same as Accepting (approving) a report.&#039;&#039; &amp;amp;nbsp; &#039;&#039;This level is only needed if your agency uses a two-tiered approval process.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, supervisors may Edit, Reject, and Accept (approve) their own reports and reports for other users.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Agency Administrator (hosted)&#039;&#039;&#039; - Agency admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, and search for/view deleted forms. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;System Administrator (non-hosted)&#039;&#039;&#039; - System admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, search for and view deleted forms, unlock forms, archive forms, add form numbers to the database, and more.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Special Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking (hosted only)&#039;&#039;&#039; - Users may view parking citations and mark them as Paid but cannot create them or or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking Reporter (hosted only)&#039;&#039;&#039; - Users may create parking citations but cannot create or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records Data Entry&#039;&#039;&#039; - Users may keypunch [https://www.tracsflorida.org/wiki/index.php?title=UTC_Keypunching_Paper_Citations paper citations] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#How_to_Update_a_Crash_From_a_Previous_Vendor crashes from a previous vendor]. &amp;amp;nbsp; This level allows the user to type the HSMV number onto the form.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Investigator&#039;&#039;&#039; - This level is only used in conjunction with certain agency local rules.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3697</id>
		<title>Access Levels</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3697"/>
		<updated>2026-06-10T18:52:32Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following access levels are available in TraCS. &amp;amp;nbsp; For more on managing these levels for users, see [https://www.tracsflorida.org/wiki/index.php?title=Managing_Users Managing Users.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Standard Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records&#039;&#039;&#039; - Users may view, print, and export reports for other users, create searches, and run analysis reports.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reporter&#039;&#039;&#039; - In addition to Records permissions, users may create reports and edit and update their own reports. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewing Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, reviewing supervisors may edit, reject, and review their own reports and reports for other users. &amp;amp;nbsp; This level is only needed if your agency uses a two-tiered approval process.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, supervisors may edit, reject, and accept (approve) their own reports and reports for other users.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Agency Administrator (hosted)&#039;&#039;&#039; - Agency admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, and search for/view deleted forms. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;System Administrator (non-hosted)&#039;&#039;&#039; - System admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, search for and view deleted forms, unlock forms, archive forms, add form numbers to the database, and more.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Special Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking (hosted only)&#039;&#039;&#039; - Users may view parking citations and mark them as Paid but cannot create them or or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking Reporter (hosted only)&#039;&#039;&#039; - Users may create parking citations but cannot create or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records Data Entry&#039;&#039;&#039; - Users may keypunch [https://www.tracsflorida.org/wiki/index.php?title=UTC_Keypunching_Paper_Citations paper citations] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#How_to_Update_a_Crash_From_a_Previous_Vendor crashes from a previous vendor]. &amp;amp;nbsp; This level allows the user to type the HSMV number onto the form.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Investigator&#039;&#039;&#039; - This level is only used in conjunction with certain agency local rules.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3696</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3696"/>
		<updated>2026-06-05T19:37:22Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Long and Short Form Crashes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash. &lt;br /&gt;
&lt;br /&gt;
If you are adding additional information to the narrative, press the red bar that reads &amp;quot;Click Here to Add Another Narrative Page&amp;quot; to open a new narrative section.&lt;br /&gt;
&lt;br /&gt;
Validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you are updating a crash from a previous vendor, you have recreated the original   &lt;br /&gt;
crash in TraCS, and it is in Open status. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3695</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3695"/>
		<updated>2026-06-05T19:35:08Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Long and Short Form Crashes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash. &amp;amp;nbsp; If you are adding additional information to the narrative, press the red bar that reads &amp;quot;Click Here to Add Another Narrative Page&amp;quot; to open a new narrative section.&lt;br /&gt;
&lt;br /&gt;
Validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you are updating a crash from a previous vendor, you have recreated the original   &lt;br /&gt;
crash in TraCS, and it is in Open status. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3694</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3694"/>
		<updated>2026-06-05T19:32:22Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Long and Short Form Crashes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash. &amp;amp;nbsp; If you are adding additional information to the narrative, press the red bar that reads &amp;quot;Click Here to Add Another Narrative.&amp;quot; &lt;br /&gt;
&lt;br /&gt;
Validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you are updating a crash from a previous vendor, you have recreated the original   &lt;br /&gt;
crash in TraCS, and it is in Open status. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs&amp;diff=3693</id>
		<title>How To Use the Search Tabs</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs&amp;diff=3693"/>
		<updated>2026-06-03T13:53:37Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
There are several ways to search for information in TraCS.  &amp;amp;nbsp; Virtually any field that is on a form may be queried. &amp;amp;nbsp; All users have the ability to perform searches.&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Quick_Searches Quick searches] may be completed by using the buttons at the upper left side of the Forms Manager.&lt;br /&gt;
&lt;br /&gt;
[https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Basic_Searches Basic searches] may be performed by using the Form, Case, and Custom tabs in the Forms Manager. &amp;amp;nbsp; These searches may be saved as [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Favorite_Searches Favorites]. &lt;br /&gt;
&lt;br /&gt;
More complex searches may be created using an [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Advanced_Search Advanced Search] or [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#AdHoc_Queries Ad Hoc Query].  &lt;br /&gt;
&lt;br /&gt;
There are also over 40 pre-built [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports Analysis Reports] and over 25 pre-built [https://www.tracsflorida.org/wiki/index.php?title=Ad_Hoc_Queries Ad Hoc Queries] that are available. &lt;br /&gt;
&lt;br /&gt;
The search tabs are at the bottom of the Forms Manager. &amp;amp;nbsp; If you do not see them, go to the View tab at the top of the Forms Manager and press Show Search. &lt;br /&gt;
&lt;br /&gt;
[[File:ShowSearch.png]]&lt;br /&gt;
&lt;br /&gt;
The search tabs will automatically dock at the bottom. &amp;amp;nbsp; If you would like them at the top, right click on one of the tab names and click Dock Top. &lt;br /&gt;
&lt;br /&gt;
[[File:SearchDock.png]]&lt;br /&gt;
&lt;br /&gt;
===Quick Searches===&lt;br /&gt;
&lt;br /&gt;
Officers may quickly search for their open and rejected forms by pressing the My Open Forms or My Rejected Forms buttons at the upper left side of Home tab in the Forms Manager. &lt;br /&gt;
&lt;br /&gt;
Users with Reviewing Supervisor and/or Supervisor permissions may search for validated and reviewed forms for all users by pressing the Agency Validated Forms or Agency Reviewed Forms buttons. &lt;br /&gt;
&lt;br /&gt;
[[File:QuickSearchButtons.png]]&lt;br /&gt;
&lt;br /&gt;
===Basic Searches===&lt;br /&gt;
&lt;br /&gt;
Basic searches may be performed using the Form, Case, or Custom tabs, or any combination of the three. &amp;amp;nbsp; These searches are limited to the fields that you see on the tabs. &lt;br /&gt;
&lt;br /&gt;
These tabs build off one another when searching. &amp;amp;nbsp; This means that TraCS reads criteria entered on all three tabs when the Search button is pressed.  &amp;amp;nbsp; For example, you may search for crashes (Form) within a date range (Form) involving a vehicle with tag ABC123 (Custom). &amp;amp;nbsp; See [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Combining_Search_Criteria Combining Search Criteria] for additional examples.&lt;br /&gt;
&lt;br /&gt;
Always press Clear before performing a new search to remove any previous search parameters that have been entered.&lt;br /&gt;
&lt;br /&gt;
On fields that allow you to type text, you may use the asterisk (*) as a wildcard. &lt;br /&gt;
&lt;br /&gt;
====Form Tab====&lt;br /&gt;
&lt;br /&gt;
The Form tab may be used to search for forms using any combination of the fields that are on the tab.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Searching from the Form tab is not the same as searching from the Case tab.  &amp;amp;nbsp; See the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Case_Tab Case Tab] section for details.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Always press Clear before performing a new search to remove any previous search parameters that have been entered.&lt;br /&gt;
&lt;br /&gt;
Most of the search fields are self-explanatory. &amp;amp;nbsp; Clarification on the other fields is below. &lt;br /&gt;
&lt;br /&gt;
:&amp;lt;u&amp;gt;Form Number&amp;lt;/u&amp;gt; - The unique number that is assigned to the form (citation number, warning number, HSMV crash number, etc.). &amp;lt;br&amp;gt; &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; - The agency case number that is entered on the form. &amp;amp;nbsp; Use the asterisk (*) as a wildcard if needed. &amp;lt;br&amp;gt; &amp;lt;u&amp;gt;Secondary ID&amp;lt;/u&amp;gt; - The badge/ID number assigned to the user profile.&amp;lt;br&amp;gt; &amp;lt;u&amp;gt;Data Source&amp;lt;/u&amp;gt; - Change it to All to search for forms that have been Archived.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Form Tab&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
[[File:SearchClearButton.png | center]]&lt;br /&gt;
&lt;br /&gt;
====Case Tab====&lt;br /&gt;
&lt;br /&gt;
The Case tab may be used to search for any combination of the fields that are on the tab. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Searching from the Case tab is not the same as searching from the Form tab. &amp;amp;nbsp; See the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Case_Tab Form Tab] section for details.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
The Case tab is used to search cases that have been created by the agency. &amp;amp;nbsp; See [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Case_Information Case Information] for details.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If a Number was not added on the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Case_Information Case Information] screen, you cannot search by agency case number using this tab. &amp;amp;nbsp; You must use Form or Custom tabs to search by agency case number.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Always press Clear before performing a new search to remove any previous search parameters that have been entered.&lt;br /&gt;
&lt;br /&gt;
Some of the search fields are self-explanatory. &amp;amp;nbsp;  Clarification on the other fields is below.&lt;br /&gt;
&lt;br /&gt;
:&amp;lt;u&amp;gt;[https://www.tracsflorida.org/wiki/index.php?title=TraCS_Form_and_Case_Definable_Field_Codes#Case/Folder_Types Type]&amp;lt;/u&amp;gt; - The Case Type category that was entered on the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Case_Information Case Information] screen (Burglary/Breaking and Entering, Fatality/SBI, Hit &amp;amp; Run, Robbery, etc.). &amp;amp;nbsp; If no case type was entered, it will default to General. &amp;lt;br&amp;gt;&amp;lt;u&amp;gt;[https://www.tracsflorida.org/wiki/index.php?title=TraCS_Form_and_Case_Definable_Field_Codes#Case_Definable_Fields Status]&amp;lt;/u&amp;gt; - The current status of the case (Open, Inactive, Closed, Referred to CID, etc.). &amp;amp;nbsp; &#039;&#039;This is different from the Form Status.&#039;&#039;&amp;lt;br&amp;gt;&amp;lt;u&amp;gt;Owner ID&amp;lt;/u&amp;gt; - The officer or investigator assigned to the case. &amp;amp;nbsp; &#039;&#039;This may be different than the person who created the form.&#039;&#039; &amp;lt;br&amp;gt; &amp;lt;u&amp;gt;Case Number&amp;lt;/u&amp;gt; - The Number that was entered on the Case Information screen. &amp;amp;nbsp; If there are multiple forms under the same case number, all of them will come up in the search results. &amp;lt;br&amp;gt; &amp;lt;u&amp;gt;Description&amp;lt;/u&amp;gt; - Search for text entered in the Description field on the Case Information screen. &amp;amp;nbsp; You may use the asterisk (*) as a wildcard. &amp;amp;nbsp; For example, THI* will search for words that start with the letters THI. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Case Tab&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:CaseTab.png|center]]&lt;br /&gt;
&lt;br /&gt;
=====Case Information=====&lt;br /&gt;
&lt;br /&gt;
You may create a case by adding a case number on the Case Information screen that pops up when you first create your form.  &amp;amp;nbsp; You may add other details such as case type and a brief description of the case.&lt;br /&gt;
&lt;br /&gt;
If the initial Case Information screen popup was bypassed, you may also assign a case number by doing one of the following: &lt;br /&gt;
&lt;br /&gt;
:With the form closed, highlight it, go to the RMS tab, and press the Case Information button. &amp;lt;br&amp;gt; With the form closed, highlight it, right click, and press the Case Information button near the bottom of the list.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Case Information Screen&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[File:CaseInfoScreen.png]]&lt;br /&gt;
&lt;br /&gt;
====Custom Tab====&lt;br /&gt;
&lt;br /&gt;
The Custom tab may be used to query the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Custom_Search_Fields Custom Search Fields] listed below. &amp;amp;nbsp; You may also use the Custom tab to search for forms that have attachments or forms that are locked.&lt;br /&gt;
&lt;br /&gt;
Always press Clear before performing a new search to remove any previous search parameters that have been entered. &lt;br /&gt;
&lt;br /&gt;
Some fields will allow for free typing of text and others will require that a selection be made from a list. &amp;lt;br&amp;gt; For fields that allow free text, you may use the asterisk (*) as a wildcard. &amp;lt;br&amp;gt; For fields that require a selection from a list, you may only choose one. &amp;lt;br&amp;gt; You may enter parameters into multiple fields, for example, First Name &amp;amp; Last Name.&amp;lt;br&amp;gt;If you want to search a date range, enter the range on the Form tab. &amp;amp;nbsp; If you want to narrow the search to a certain Form Status or Form type, enter it on the Form tab. &amp;amp;nbsp; See [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Combining_Search_Criteria Combining Search Criteria] for details. &amp;lt;br&amp;gt; To search for forms with attachments, check the Only Forms with Attachments box. &amp;lt;br&amp;gt; To search for locked forms, check the Only Locked Forms box.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;center&amp;gt;&#039;&#039;&#039;Custom Tab&#039;&#039;&#039;&amp;lt;/center&amp;gt;&lt;br /&gt;
[[File:CustomTab.png | center]]&lt;br /&gt;
&lt;br /&gt;
=====Custom Search Fields=====&lt;br /&gt;
&lt;br /&gt;
Keep in mind that information that is entered onto forms may have typographical or spelling errors, may have special characters, or may have characters that look alike (O &amp;amp; 0, I &amp;amp; 1, B &amp;amp; 8, S &amp;amp; 5, etc.).  &lt;br /&gt;
&lt;br /&gt;
Additionally, names may be spelled in a variety of ways and may have spaces, hyphens, periods, or apostrophes within them. &amp;amp;nbsp; Case numbers may be entered with or without a hyphen (-) and/or with or without padded zeros. &lt;br /&gt;
&lt;br /&gt;
If you do not get the search results you are looking for when using the free text fields, search again using the asterisk (*) as a wildcard.  &lt;br /&gt;
&lt;br /&gt;
Examples: &amp;lt;br&amp;gt; Last Name - S*t*Patrick will include St. Patrick, Saint Patrick, St Patrick, Saint-Patrick&amp;lt;br&amp;gt;First Name - M*ch*l* will include Michelle, Michele, Michael, Michel, Michaela &amp;lt;br&amp;gt;Case Number - *24*45678 will look for 24-45678, 2024-45678, 24-0045678, 240045678, OR24045678, etc.&amp;lt;br&amp;gt;DL Number - A*123*456*78*910* will include results with and without hyphens.&lt;br /&gt;
&lt;br /&gt;
======All Forms======&lt;br /&gt;
:Agency Case Number&amp;lt;br&amp;gt;First Name&amp;lt;br&amp;gt;Last Name&amp;lt;br&amp;gt;Tag&amp;lt;br&amp;gt;VIN&amp;lt;br&amp;gt;DL Number&amp;lt;br&amp;gt;Zone or District - This search will only return accurate results if your officers use the Zone field, use it consistently, and enter the information uniformly.&lt;br /&gt;
&lt;br /&gt;
======Crash Searches======&lt;br /&gt;
:Alcohol Tested &amp;lt;br&amp;gt; Alcohol Test Results &amp;lt;br&amp;gt; Injury Severity&amp;lt;br&amp;gt;Manner of Collision&amp;lt;br&amp;gt;Suspected Alcohol Use&amp;lt;br&amp;gt;Hit and Run&amp;lt;br&amp;gt;Emergency Vehicle Use&amp;lt;br&amp;gt;Hazmat Release&amp;lt;br&amp;gt;Unit Number&amp;lt;br&amp;gt;Driver Distracted By&amp;lt;br&amp;gt;Driver Vision Obstruction&amp;lt;br&amp;gt;Event Relation to Junction&amp;lt;br&amp;gt;Vehicle Body Type&amp;lt;br&amp;gt;Road System Identifier&amp;lt;br&amp;gt;Non-Motorist Description&lt;br /&gt;
&lt;br /&gt;
======Citation &amp;amp; Warning Searches======&lt;br /&gt;
:UTC by Statute - UTC &amp;amp; Warning&amp;lt;br&amp;gt;UTC Court Disposition - UTC only&amp;lt;br&amp;gt;UTC County - UTC only&lt;br /&gt;
&lt;br /&gt;
======Property &amp;amp; Evidence Search======&lt;br /&gt;
:Property Item&lt;br /&gt;
&lt;br /&gt;
======Parking/Ordinance Search======&lt;br /&gt;
:Ordinance Type&lt;br /&gt;
&lt;br /&gt;
======Narrative Search======&lt;br /&gt;
&lt;br /&gt;
:The narrative search may be used on forms that have a Narrative section, such as Crash, FIBRS, UAA, FIR, and Trespass.&amp;lt;br&amp;gt; You may use the asterisk (*) as a wildcard.&lt;br /&gt;
&lt;br /&gt;
====Combining Search Criteria====&lt;br /&gt;
&lt;br /&gt;
You may combine search criteria across the Form, Case, and Custom tabs to narrow your search. &lt;br /&gt;
&lt;br /&gt;
Always press Clear before performing a new search to remove any previous search parameters that have been entered.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Remember, the Case tab searches for information that is entered on the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Use_the_Search_Tabs#Case_Information Case Information] screen. &amp;amp;nbsp; If you don&#039;t update the default information with your case details, you will not get results. &lt;br /&gt;
&lt;br /&gt;
Examples of searches with combined criteria are below. &lt;br /&gt;
&lt;br /&gt;
Crashes (Form tab) in Submitted status (Form) within a date range (Form) involving Last Name - Doe (Custom) First Name - Jane (Custom) &amp;lt;br&amp;gt; Crashes (Form) in Submitted status (Form) with a case type marked as Hit and Run (Case) in Open or Pending status (Case) &amp;lt;br&amp;gt; Crashes (Form) in Submitted status (Form) where Hit &amp;amp; Run is marked Yes (Custom) &amp;lt;br&amp;gt; Crashes (Form) in Submitted status (Form) where the Driver Distracted By is Texting (Custom)&amp;lt;br&amp;gt; FIBRS Offense/Incident reports (Form) in Accepted status (Form) assigned to Detective Jones (Case) in Open or Inactive status (Case) &amp;lt;br&amp;gt; Any form in Accepted, Mailed, or Submitted status (Form) within a date range (Form) involving a vehicle with tag ABC123 (Custom)&amp;lt;br&amp;gt;Citations in Mailed or Submitted status (Form) within a date range (Form), written for 316.075(1)(c)1 - Fail to Stop at STEADY RED signal (Custom).&lt;br /&gt;
&lt;br /&gt;
===Favorite Searches===&lt;br /&gt;
&lt;br /&gt;
Search criteria entered on the Form, Case, and Custom tabs may be saved as a Favorite search.&lt;br /&gt;
&lt;br /&gt;
Always press Clear before creating a new Favorite new search to remove any previous search parameters that have been entered.&lt;br /&gt;
&lt;br /&gt;
====Creating a Favorite Search====&lt;br /&gt;
&lt;br /&gt;
Add your search criteria to the Form, Case, and/or Custom tabs. &amp;lt;br&amp;gt; Press Search. &amp;amp;nbsp; This will verify that your search is working and returning the desired results. &amp;lt;br&amp;gt; On the Form tab, under Favorites, Press Save. &amp;lt;br&amp;gt; You will be taken to the Favorites tab. &amp;lt;br&amp;gt; Give your search a logical name, like &amp;quot;My Open &amp;amp; Rejected Forms.&amp;quot;&lt;br /&gt;
&lt;br /&gt;
====Running, Renaming, &amp;amp; Deleting Searches====&lt;br /&gt;
&lt;br /&gt;
To run the search, go to the Favorites tab, highlight it, and press Run Selected Search.  &lt;br /&gt;
&lt;br /&gt;
If you have multiple Favorite searches, you may use the blue up/down arrows to put them in the order you desire.&lt;br /&gt;
&lt;br /&gt;
To rename a search, click on the Search Name to make changes.&lt;br /&gt;
&lt;br /&gt;
To delete a search, highlight it and press Delete Search.&lt;br /&gt;
&lt;br /&gt;
====Setting a Favorite Search to Run at Login====&lt;br /&gt;
&lt;br /&gt;
If you would like a Favorite search to automatically run when you log in, check the box in the column labeled Is Default. &lt;br /&gt;
&lt;br /&gt;
Go to the Tools tab at the top of the Forms manager and then User Preferences. &amp;amp;nbsp; Click on Perform Auto Search After Login and a checkmark will appear.&lt;br /&gt;
&lt;br /&gt;
You may only choose one Favorite at a time to run at login.&lt;br /&gt;
&lt;br /&gt;
[[File:AutoSearchLogin.png]]&lt;br /&gt;
&lt;br /&gt;
====Search Examples====&lt;br /&gt;
&lt;br /&gt;
Example 1 - This is a Favorite search for all forms under the TraCS user ID for a rolling 30-day range. &amp;amp;nbsp; It is set to run at login.&lt;br /&gt;
&lt;br /&gt;
[[File:FavoriteSearch3.png]]&lt;br /&gt;
&lt;br /&gt;
Example 2 - This is a Favorite search for all Validated forms for User ID&#039;s doral, kathleenp, and romans. &amp;amp;nbsp; It is set to run at login. &lt;br /&gt;
&lt;br /&gt;
[[File:FavoriteSearch4.png]]&lt;br /&gt;
&lt;br /&gt;
====Updating a Favorite Search====&lt;br /&gt;
&lt;br /&gt;
If you make any changes to an existing Favorite search, &#039;&#039;&amp;lt;u&amp;gt;you must resave it as a brand new search&amp;lt;/u&amp;gt;.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Take Example 2 above.  &amp;amp;nbsp;  You are a sergeant, and you have a Favorite search set up to query Validated forms for your squad members, doral, kathleenp, and romans.  &amp;amp;nbsp; You have it saved as Squad A - Validated Forms.  &amp;amp;nbsp; Amyc joins the squad. &lt;br /&gt;
&lt;br /&gt;
Add amyc to the User ID list, and under Favorites, press Save. &amp;amp;nbsp; Give the search a new name and check the box in the Is Default Column. &amp;amp;nbsp; Delete the old search if desired by highlighting it and pressing Delete Search.&lt;br /&gt;
&lt;br /&gt;
[[File:FavoriteSearch5.png]]&lt;br /&gt;
&lt;br /&gt;
===Advanced Searches &amp;amp; Ad Hoc Queries===&lt;br /&gt;
&lt;br /&gt;
You may perform more complex searches by creating an Advanced Search or Ad Hoc Query.  &amp;amp;nbsp; These searches can query virtually any field on a form. &lt;br /&gt;
&lt;br /&gt;
For instructions on how to create them, see [https://www.tracsflorida.org/wiki/index.php?title=How_To_Create_an_Advanced_Search How to Create an Advanced Search] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Create_an_Ad_Hoc_Query How to Create an Ad Hoc Query].&lt;br /&gt;
&lt;br /&gt;
The process of creating the queries is the same. &amp;amp;nbsp; Both types of queries may be [https://www.tracsflorida.org/wiki/index.php?title=How_To_Share_Queries shared with other users].&lt;br /&gt;
&lt;br /&gt;
Which should you use? &amp;amp;nbsp; That depends on how you or your end client wish to view the results and what you want to do with them. &lt;br /&gt;
&lt;br /&gt;
If you would like your results to show in the Forms Manager where you can open and view the forms, use an Advanced Search. &lt;br /&gt;
&lt;br /&gt;
If you would like your results in a list format that can be emailed or printed, go with an Ad Hoc Query.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Advanced Search&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Advanced Search results show in the Forms Manager. &amp;lt;br&amp;gt; Because the results show in the Forms Manager, an advanced search may be created more quickly than an ad hoc query. &amp;lt;br&amp;gt; You do not need to add fields to your query that already exist in the forms manager, such as Case Number or User ID. &amp;lt;br&amp;gt; You may open forms and look at them right away. &amp;lt;br&amp;gt; You may copy and paste your results into Excel, CSV, Word, or Notepad (Ctrl-A, Ctrl-C, Ctrl-V). &amp;amp;nbsp; Excel is best. &amp;lt;br&amp;gt; You may create an [https://www.tracsflorida.org/wiki/index.php?title=How_To_Create_an_Advanced_Search_Email_Notification email notification] based on your criteria. &lt;br /&gt;
&lt;br /&gt;
You cannot print or email your results. &amp;lt;br&amp;gt; You cannot customize the way the results look in the Forms Manager.&amp;lt;br&amp;gt;You cannot export your results. &amp;amp;nbsp; You may only copy and paste to another application, such as Excel. &amp;lt;br&amp;gt; Query [https://www.tracsflorida.org/wiki/index.php?title=How_To_Share_Queries sharing] may only be done via the Configuration Manager. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Ad Hoc Query&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Ad Hoc query results show as a list in a report format. &amp;lt;br&amp;gt; You may group the results. &amp;lt;br&amp;gt; Because the results show in a report format, creating the query takes longer than an Advanced Search. &amp;lt;br&amp;gt; Each field that you want to see in your results must be added to the criteria. &amp;lt;br&amp;gt; The report may be exported to Excel or CSV file &amp;lt;br&amp;gt; The report may be printed or emailed. &amp;lt;br&amp;gt; You may customize the report by resizing, renaming, and reordering the columns, and adding a header, footer, and other information. &amp;lt;br&amp;gt; Query [https://www.tracsflorida.org/wiki/index.php?title=How_To_Share_Queries sharing] may be done via the Configuration Manager or by exporting and sending the file to others. &lt;br /&gt;
&lt;br /&gt;
You cannot open forms directly from the search results. &amp;lt;br&amp;gt; You cannot set up a scheduled email notification.&lt;br /&gt;
&lt;br /&gt;
There are approximately 28 prebuilt ad hoc queries available for use. &amp;amp;nbsp; A list of the queries and information on how to import them to your machine are on [https://www.tracsflorida.org/wiki/index.php?title=Ad_Hoc_Queries this page].&lt;br /&gt;
&lt;br /&gt;
===Analysis Reports===&lt;br /&gt;
&lt;br /&gt;
There are over 40 pre-built analysis reports available to agencies.  &amp;amp;nbsp; All users have access to them. &amp;amp;nbsp; The results are in a report format with the agency name at the top. &amp;amp;nbsp; The results may be printed, emailed, or exported to PDF or image file. &lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports Analysis Reports] page for further information.&lt;br /&gt;
&lt;br /&gt;
===Master Index Search===&lt;br /&gt;
&lt;br /&gt;
The Master Index search is located on the RMS tab. &amp;amp;nbsp; Instructions on how to use it are in this [https://www.tracsflorida.org/downloads/TrainingGuides/MasterIndexSearching.pptx Master Index Searching] PowerPoint.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3692</id>
		<title>Access Levels</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3692"/>
		<updated>2026-06-03T13:51:13Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following access levels are available in TraCS. &amp;amp;nbsp; For more on managing these levels for users, see [https://www.tracsflorida.org/wiki/index.php?title=Managing_Users Managing Users.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Standard Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records&#039;&#039;&#039; - Users may view, print, and export reports for other users, create searches, and run analysis reports.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reporter&#039;&#039;&#039; - In addition to Records permissions, users may create reports and edit and update their own reports. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewing Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, reviewing supervisors may edit, reject, and review their own reports and reports for other users. &amp;amp;nbsp; This level is only needed if your agency uses a two-tiered approval process.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, supervisors may edit, reject, and accept (approve) their own reports and reports for other users.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Agency Administrator (hosted)&#039;&#039;&#039; - In addition to Records, Reporter, Reviewing Supervisor, and Supervisor permissions, agency admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, and search for/view deleted forms. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;System Administrator (non-hosted)&#039;&#039;&#039; - In addition to Records, Reporter, Reviewing Supervisor, and Supervisor permissions, system admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, search for and view deleted forms, unlock forms, archive forms, add form numbers to the database, and more.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Special Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking (hosted only)&#039;&#039;&#039; - Users may view parking citations and mark them as Paid but cannot create them or or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking Reporter (hosted only)&#039;&#039;&#039; - Users may create parking citations but cannot create or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records Data Entry&#039;&#039;&#039; - Users may keypunch [https://www.tracsflorida.org/wiki/index.php?title=UTC_Keypunching_Paper_Citations paper citations] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#How_to_Update_a_Crash_From_a_Previous_Vendor crashes from a previous vendor]. &amp;amp;nbsp; This level allows the user to type the HSMV number onto the form.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Investigator&#039;&#039;&#039; - This level is only used in conjunction with certain agency local rules.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3691</id>
		<title>Access Levels</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Access_Levels&amp;diff=3691"/>
		<updated>2026-06-03T13:50:57Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The following access levels are available in TraCS. &amp;amp;nbsp; For more on managing these levels for users, see [https://www.tracsflorida.org/wiki/index.php?title=Managing_Users Managing Users.]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Standard Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records&#039;&#039;&#039; - Users may view, print, and export reports for other users, create searches, and run Analysis Reports.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reporter&#039;&#039;&#039; - In addition to Records permissions, users may create reports and edit and update their own reports. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Reviewing Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, reviewing supervisors may edit, reject, and review their own reports and reports for other users. &amp;amp;nbsp; This level is only needed if your agency uses a two-tiered approval process.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Supervisor&#039;&#039;&#039; - In addition to Records and Reporter permissions, supervisors may edit, reject, and accept (approve) their own reports and reports for other users.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Agency Administrator (hosted)&#039;&#039;&#039; - In addition to Records, Reporter, Reviewing Supervisor, and Supervisor permissions, agency admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, and search for/view deleted forms. &lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;System Administrator (non-hosted)&#039;&#039;&#039; - In addition to Records, Reporter, Reviewing Supervisor, and Supervisor permissions, system admins may manage users, pull numbers on other users&#039; forms, print unapproved crashes without the watermark, dismiss citations, seal and expunge forms, clear export dates on forms that have been exported for RMS, bypass the location tool requirement on crashes and other forms where it is required, view form logs, delete/undelete forms, search for and view deleted forms, unlock forms, archive forms, add form numbers to the database, and more.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Special Levels&amp;lt;/u&amp;gt;&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking (hosted only)&#039;&#039;&#039; - Users may view parking citations and mark them as Paid but cannot create them or or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Parking Reporter (hosted only)&#039;&#039;&#039; - Users may create parking citations but cannot create or see other agency forms like crash, citation, etc.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Records Data Entry&#039;&#039;&#039; - Users may keypunch [https://www.tracsflorida.org/wiki/index.php?title=UTC_Keypunching_Paper_Citations paper citations] and [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#How_to_Update_a_Crash_From_a_Previous_Vendor crashes from a previous vendor]. &amp;amp;nbsp; This level allows the user to type the HSMV number onto the form.&lt;br /&gt;
&lt;br /&gt;
:&#039;&#039;&#039;Investigator&#039;&#039;&#039; - This level is only used in conjunction with certain agency local rules.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports&amp;diff=3690</id>
		<title>Analysis Reports</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports&amp;diff=3690"/>
		<updated>2026-06-02T20:17:37Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Analysis Reports - Coming in a Future Release! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
There are over 50 pre-built analysis reports available within TraCS.  &lt;br /&gt;
&lt;br /&gt;
All TraCS users may access them by going to the Advanced tab and then choosing Analysis Reports. &lt;br /&gt;
&lt;br /&gt;
You may use the blue Up/Down arrows to change the order of the reports to your liking.&lt;br /&gt;
&lt;br /&gt;
[[File:AnalysisReport1.png]]&lt;br /&gt;
&lt;br /&gt;
Highlight the report you wish to run and double click or press Run Report. &amp;amp;nbsp; Some reports will require a date range and/or offer optional parameters, and others will not. &lt;br /&gt;
&lt;br /&gt;
Reports may be printed or sent via email and they may be exported to PDF, Excel, or image file. &amp;amp;nbsp; The Print, Export, and Email buttons are in the upper left corner of the report. &lt;br /&gt;
&lt;br /&gt;
[[File:AnalysisReport4.png]]&lt;br /&gt;
&lt;br /&gt;
===Available Analysis Reports===&lt;br /&gt;
&lt;br /&gt;
=====Available Form Numbers=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of the remaining form numbers for the agency.  &lt;br /&gt;
&lt;br /&gt;
Someone at the agency should run this report on a regular basis.  &amp;amp;nbsp; Do not rely on the [https://www.tracsflorida.org/wiki/index.php?title=Low_Number_Email_Notification Low Number Email] notification to tell you when form numbers are low.&lt;br /&gt;
&lt;br /&gt;
=====Available Form Numbers - Detailed=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of Available and/or Used form numbers.  &lt;br /&gt;
&lt;br /&gt;
The results include the form number, form type, form number, who pulled the number, status (Available or Used), and the date of that status. &lt;br /&gt;
&lt;br /&gt;
Available means that the number has been loaded into TraCS and has not been pulled onto a form. &amp;amp;nbsp; The Modify Date is the date the form number was added to TraCS.  &lt;br /&gt;
&lt;br /&gt;
Used means the number has been pulled onto a form. &amp;amp;nbsp; The Modify Date is the date the number was pulled.&lt;br /&gt;
&lt;br /&gt;
Examples of how this report may be used are as follows: &lt;br /&gt;
&lt;br /&gt;
:You are looking for a crash, citation, warning, or other numbered form and you cannot locate it in TraCS.  &amp;amp;nbsp; The report will tell you who pulled the number and when.&lt;br /&gt;
:Your FDLE auditor is requesting a list of your Available citation numbers.&lt;br /&gt;
:Your FDLE auditor is requesting a list of your Used citation numbers.&lt;br /&gt;
:Your FDLE auditor has given you a list of specific UTC numbers to research and you cannot locate them in TraCS.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Keep in mind that there are thousands of numbers that are loaded into the system. &amp;amp;nbsp; The report you run may end up being hundreds or thousands of pages long, even if you are a small agency. &amp;amp;nbsp; Think before you print!&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====Bypass Location Tool Report=====&lt;br /&gt;
&lt;br /&gt;
Agency administrators may run this report to see if anyone at the agency has the location tool requirement turned off. &amp;amp;nbsp; This is rare. &amp;amp;nbsp; Only the TraCS team may turn off the requirement for individuals and it is only done when they are unable to use the location tool on their local machine.  &lt;br /&gt;
&lt;br /&gt;
=====CFS Time Analysis Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of Calls for Service (CFS) with the response time for each.&lt;br /&gt;
&lt;br /&gt;
=====Crash by Location=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes within a date range along with the location that the crash occurred.  &lt;br /&gt;
&lt;br /&gt;
The results include the HSMV #, form date, form type, location, latitude, longitude, and the statute # and statute description of citations that were issued. &lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Crashes and Citations on a Map=====&lt;br /&gt;
&lt;br /&gt;
This report plots crashes and citations on a map within a date range. &lt;br /&gt;
&lt;br /&gt;
The locations are plotted using the latitude and longitude that populates when the [https://www.tracsflorida.org/wiki/index.php?title=Signal_4_Location_Tool geolocation tool] is used. &amp;amp;nbsp; If the geolocation tool was not used, the incident will not show on the map.&lt;br /&gt;
&lt;br /&gt;
The geolocation tool is required on all crash forms. &amp;amp;nbsp; If you would like the requirement turned on for citations as well, contact us. &lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Crash Injury Severity Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes within a date range with a specific FLHSMV Injury Severity type. &lt;br /&gt;
&lt;br /&gt;
HSMV Injury Types are None, Possible, Non-Incapacitating, Incapacitating, Fatal (within 30 days), and Non-Traffic Fatality. &lt;br /&gt;
&lt;br /&gt;
The results show crash date, form type, form status, and the names of involved parties with the injury type selected.&lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Detailed eCitation Submission Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations within a Submission Date range. &lt;br /&gt;
&lt;br /&gt;
The results show the form number, officer name, statute, and charge description, and the submission date. &lt;br /&gt;
&lt;br /&gt;
Citations in both Submitted and Mailed status are included.  &lt;br /&gt;
&lt;br /&gt;
If you want a count of how many Mailed and Submitted citations were processed within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#eCitation_Submissions eCitation Submissions Report].&lt;br /&gt;
&lt;br /&gt;
=====Detailed eCrash Submission Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes and updates within a Submission Date range. &lt;br /&gt;
&lt;br /&gt;
The results show the form number, case number, officer name, form type, and submission date. &lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status.  &lt;br /&gt;
&lt;br /&gt;
If you want a count of how many crashes were submitted within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#eCrash_Submissions eCrash Submissions Report].&lt;br /&gt;
&lt;br /&gt;
=====DHSMV UTC Safety Belt Violations Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for safety belt violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.614.html FSS 316.614].  &lt;br /&gt;
&lt;br /&gt;
This report meets the requirements in FSS 316.614(9) for annual race and ethnicity reporting to FDLE and comes up in a table that matches the format for entry into DAVID. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted or Submitted status.&lt;br /&gt;
&lt;br /&gt;
If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_FDLE_Bias_Based_Policing UTC FDLE Bias Based Policing] report.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - Only violations under 316.614 are included in these results. &amp;amp;nbsp; Violations under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.613.html FSS 316.613] are not included because FDLE does not require reporting of race and ethnicity for child restraint violations. &amp;amp;nbsp; If you want a list of both 316.613 and 316.614 violations, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_Click_it_or_Ticket UTC Click It or Ticket] report.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====DHSMV UTC Texting and Driving Violations Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for wireless communication device violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.305.html FSS 316.305].  &lt;br /&gt;
&lt;br /&gt;
This report meets the requirements in FSS 316.305(5) for annual race and ethnicity reporting to FDLE and comes up in a table that matches the format for entry into DAVID.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted or Submitted status.&lt;br /&gt;
&lt;br /&gt;
If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_FDLE_Bias_Based_Policing UTC FDLE Bias Based Policing] report.&lt;br /&gt;
&lt;br /&gt;
=====DHSMV Warning Safety Belt Violations Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for safety belt violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.614.html FSS 316.614]. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
The report comes up in a table. &amp;amp;nbsp; If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Warning_Ethnicity_Race_and_Gender Warning Ethnicity Race and Gender] report.&lt;br /&gt;
&lt;br /&gt;
=====DHSMV Warning Texting and Driving Violations Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of warnings written for wireless communication device violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.305.html FSS 316.305]. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
The report comes up in a table. &amp;amp;nbsp;If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Warning_Ethnicity_Race_and_Gender Warning Ethnicity Race and Gender] report.&lt;br /&gt;
&lt;br /&gt;
=====DUI Race and Gender Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of race and gender on DUI citations for the current year and the previous three years. &lt;br /&gt;
&lt;br /&gt;
NOTE - If the officer did not fill in the Gender and Race on the citation, it will not be included in the count on this report.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status. &lt;br /&gt;
&lt;br /&gt;
=====eCitation Submissions=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of Mailed and Submitted citations within a Submission Date Range.  &amp;amp;nbsp; The results are broken down by submission date. &lt;br /&gt;
&lt;br /&gt;
If you want a list of Mailed and Submitted citations within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Detailed_eCitation_Submission_Report Detailed eCitation Submission] report. &lt;br /&gt;
&lt;br /&gt;
=====eCrash Submissions=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of long form, short form, and update crashes within a Submission Date Range. &amp;amp;nbsp; The results are broken down by submission date. &lt;br /&gt;
&lt;br /&gt;
If you want a list of crashes Submitted within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Detailed_eCrash_Submission_Report Detailed eCrash Submission] report. &lt;br /&gt;
&lt;br /&gt;
=====Failed Login Attempts=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of failed login attempts within a date range. &lt;br /&gt;
&lt;br /&gt;
The results include the User ID, Date, Time, Machine ID, and event description.&lt;br /&gt;
&lt;br /&gt;
=====FDLE Active User Log=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of both active and inactive users for the agency. &lt;br /&gt;
&lt;br /&gt;
=====FDLE User Audit Log=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of login activity for users within a date range, including failed login attempts.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Crashes with Suspected Alcohol/Drug Use=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes where Suspected Alcohol Use and/or Suspected Drug Use for a driver or non-motorist is marked Yes. &lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Motorcycle UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range where the Vehicle Style is Motorcycle. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Motorcycle Warning=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of traffic warnings within a date range where the Vehicle Style is Motorcycle. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Work Zone UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range where Workers? is marked Yes.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Work Zone Warning=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of traffic warnings within a date range where the Workers? is marked Yes. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FIBRS Location Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of FIBRS reports along with the occurred location, latitude, and longitude. &lt;br /&gt;
&lt;br /&gt;
Reports must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
=====Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range that contain a moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====My UTC Stats=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations within a date range that were issued by the officer who is currently logged into TraCS. &lt;br /&gt;
&lt;br /&gt;
The date range will look for forms based on the citation date that is entered on the form, not the date the form was created.  &amp;amp;nbsp; This is not always the same as the form date. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Non Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range that contain a non-moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Number Audit All Forms=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of form numbers that have been used within a date range.  &lt;br /&gt;
&lt;br /&gt;
The results include the form number, form type, current form status, date the number was pulled, and who pulled it.&lt;br /&gt;
&lt;br /&gt;
=====Officer Summary Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of the following forms written by officers within a date range: &lt;br /&gt;
&lt;br /&gt;
UTC, Parking, DUI Citations, Crashes (Long/Short Form only), Crash Updates, FIBRS Incident, UAA/Arrest, Traffic Warnings, Boating, FIR, and Tow. &lt;br /&gt;
&lt;br /&gt;
Crashes and Updates must be in Submitted status to appear on this report. &amp;amp;nbsp; All other forms must be in Accepted status. &lt;br /&gt;
&lt;br /&gt;
=====Pending Citation=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s in Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Pending Crash=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes and updates in Accepted, Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Pending Offense=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of FIBRS/Incident reports in Accepted, Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Personnel List=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of agency personnel.  &lt;br /&gt;
&lt;br /&gt;
The results include the employee ID, first &amp;amp; last Name, phone number, and hire date.&lt;br /&gt;
&lt;br /&gt;
This report will only work if your agency uses the Personnel Tracking form. &lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit Crash=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of crashes that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit Offense-Incident=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of FIBRS Offense/Incident reports that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit UTC=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of UTC&#039;s that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====RMS Uploads Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of forms that were exported to the agency as XML, PDF, and/or TIFF file.&lt;br /&gt;
&lt;br /&gt;
=====Seatbelt Tickets by Ethnicity=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations written for violations of FSS 316.613 (child restraint) and 316.614 (seatbelt) along with the ethnicity and race of the violator.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====THI Crashes=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes where the injury severity for any involved party is marked as Fatal and the Completed field is marked as No.&lt;br /&gt;
&lt;br /&gt;
=====Toxicology Pending Reminder Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes where Alcohol Test Result and/or Drug Test Result fields are marked as Pending.&lt;br /&gt;
&lt;br /&gt;
=====UTC Aggressive Driving Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations where the Aggressive? field is marked yes.&lt;br /&gt;
&lt;br /&gt;
The results include statute, violation description, and the location of the violation.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC by Location=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations along with the issuing officer&#039;s name, the statute, and the charge description. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC by Officer=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations written by individual officers within a date range.  &lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name, the statute number, and the charge description.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Classification Analysis=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations and warnings written by individual officers within a date range.  &lt;br /&gt;
&lt;br /&gt;
The UTC results are broken down into moving, non-moving, criminal, pedestrian, bicyclist violations.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report. &amp;amp;nbsp; Warnings must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Click it or Ticket=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s written for violations of FSS 316.613 (child restraint) and 316.614 (seatbelt) along with the issuing officer&#039;s name.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status in to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Required Court Appearance=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC infractions and criminal violations within a date range where a court appearance is required.&lt;br /&gt;
&lt;br /&gt;
Citations in Open, Accepted, Reviewed, Rejected, Mailed, and Voided status will show on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC FDLE Bias Based Policing=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations along with the ethnicity, race, and gender of the violator and may be used for accreditation requirements.&lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name and FSS for the violation that was written. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status in to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Voided DUI UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of DUI citations that have been voided along with the issuing officer and the reason for the void.  &lt;br /&gt;
&lt;br /&gt;
This report is used for reporting voids to FLHSMV. &amp;amp;nbsp; Therefore, only citations with HSMV numbers are included on this report.&lt;br /&gt;
&lt;br /&gt;
=====Voided UTCs=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations that have been voided along with the issuing officer and the reason for the void.  &lt;br /&gt;
&lt;br /&gt;
This report is used for reporting voids to FLHSMV. &amp;amp;nbsp; Therefore, only citations with HSMV numbers are included on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Ethnicity Race and Gender=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings along with the ethnicity, race, and gender of the violator and may be used for accreditation requirements.&lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name and FSS for the violation that was written. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status to show on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings within a date range that contain a moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Non-Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings within a date range that contain a non-moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
===Analysis Reports - &#039;&#039;Coming in a Future Release!&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
The following analysis reports are in development and are targeted for a future release: &lt;br /&gt;
&lt;br /&gt;
Civil Citations &amp;amp; Warnings&amp;lt;br&amp;gt;Expunged Records Report&amp;lt;br&amp;gt;FDOT Safety Grant - DUI Crashes with Injury or Fatality&amp;lt;br&amp;gt;FDOT Safety Grant - Unrestrained Crashes&amp;lt;br&amp;gt;FIBRS Submission Results&amp;lt;br&amp;gt;FLHSMV QPI Audit&amp;lt;br&amp;gt;Pending Hit &amp;amp; Run Crashes&amp;lt;br&amp;gt;Pending Offense Reports&amp;lt;br&amp;gt;Pending UAA Reports&amp;lt;br&amp;gt;Towed Vehicle Report&amp;lt;br&amp;gt;Warnings by Officer&amp;lt;br&amp;gt;Warning Classification Analysis&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports&amp;diff=3689</id>
		<title>Analysis Reports</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports&amp;diff=3689"/>
		<updated>2026-06-02T20:12:55Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Analysis Reports - Coming in a Future Release! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
There are over 50 pre-built analysis reports available within TraCS.  &lt;br /&gt;
&lt;br /&gt;
All TraCS users may access them by going to the Advanced tab and then choosing Analysis Reports. &lt;br /&gt;
&lt;br /&gt;
You may use the blue Up/Down arrows to change the order of the reports to your liking.&lt;br /&gt;
&lt;br /&gt;
[[File:AnalysisReport1.png]]&lt;br /&gt;
&lt;br /&gt;
Highlight the report you wish to run and double click or press Run Report. &amp;amp;nbsp; Some reports will require a date range and/or offer optional parameters, and others will not. &lt;br /&gt;
&lt;br /&gt;
Reports may be printed or sent via email and they may be exported to PDF, Excel, or image file. &amp;amp;nbsp; The Print, Export, and Email buttons are in the upper left corner of the report. &lt;br /&gt;
&lt;br /&gt;
[[File:AnalysisReport4.png]]&lt;br /&gt;
&lt;br /&gt;
===Available Analysis Reports===&lt;br /&gt;
&lt;br /&gt;
=====Available Form Numbers=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of the remaining form numbers for the agency.  &lt;br /&gt;
&lt;br /&gt;
Someone at the agency should run this report on a regular basis.  &amp;amp;nbsp; Do not rely on the [https://www.tracsflorida.org/wiki/index.php?title=Low_Number_Email_Notification Low Number Email] notification to tell you when form numbers are low.&lt;br /&gt;
&lt;br /&gt;
=====Available Form Numbers - Detailed=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of Available and/or Used form numbers.  &lt;br /&gt;
&lt;br /&gt;
The results include the form number, form type, form number, who pulled the number, status (Available or Used), and the date of that status. &lt;br /&gt;
&lt;br /&gt;
Available means that the number has been loaded into TraCS and has not been pulled onto a form. &amp;amp;nbsp; The Modify Date is the date the form number was added to TraCS.  &lt;br /&gt;
&lt;br /&gt;
Used means the number has been pulled onto a form. &amp;amp;nbsp; The Modify Date is the date the number was pulled.&lt;br /&gt;
&lt;br /&gt;
Examples of how this report may be used are as follows: &lt;br /&gt;
&lt;br /&gt;
:You are looking for a crash, citation, warning, or other numbered form and you cannot locate it in TraCS.  &amp;amp;nbsp; The report will tell you who pulled the number and when.&lt;br /&gt;
:Your FDLE auditor is requesting a list of your Available citation numbers.&lt;br /&gt;
:Your FDLE auditor is requesting a list of your Used citation numbers.&lt;br /&gt;
:Your FDLE auditor has given you a list of specific UTC numbers to research and you cannot locate them in TraCS.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Keep in mind that there are thousands of numbers that are loaded into the system. &amp;amp;nbsp; The report you run may end up being hundreds or thousands of pages long, even if you are a small agency. &amp;amp;nbsp; Think before you print!&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====Bypass Location Tool Report=====&lt;br /&gt;
&lt;br /&gt;
Agency administrators may run this report to see if anyone at the agency has the location tool requirement turned off. &amp;amp;nbsp; This is rare. &amp;amp;nbsp; Only the TraCS team may turn off the requirement for individuals and it is only done when they are unable to use the location tool on their local machine.  &lt;br /&gt;
&lt;br /&gt;
=====CFS Time Analysis Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of Calls for Service (CFS) with the response time for each.&lt;br /&gt;
&lt;br /&gt;
=====Crash by Location=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes within a date range along with the location that the crash occurred.  &lt;br /&gt;
&lt;br /&gt;
The results include the HSMV #, form date, form type, location, latitude, longitude, and the statute # and statute description of citations that were issued. &lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Crashes and Citations on a Map=====&lt;br /&gt;
&lt;br /&gt;
This report plots crashes and citations on a map within a date range. &lt;br /&gt;
&lt;br /&gt;
The locations are plotted using the latitude and longitude that populates when the [https://www.tracsflorida.org/wiki/index.php?title=Signal_4_Location_Tool geolocation tool] is used. &amp;amp;nbsp; If the geolocation tool was not used, the incident will not show on the map.&lt;br /&gt;
&lt;br /&gt;
The geolocation tool is required on all crash forms. &amp;amp;nbsp; If you would like the requirement turned on for citations as well, contact us. &lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Crash Injury Severity Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes within a date range with a specific FLHSMV Injury Severity type. &lt;br /&gt;
&lt;br /&gt;
HSMV Injury Types are None, Possible, Non-Incapacitating, Incapacitating, Fatal (within 30 days), and Non-Traffic Fatality. &lt;br /&gt;
&lt;br /&gt;
The results show crash date, form type, form status, and the names of involved parties with the injury type selected.&lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Detailed eCitation Submission Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations within a Submission Date range. &lt;br /&gt;
&lt;br /&gt;
The results show the form number, officer name, statute, and charge description, and the submission date. &lt;br /&gt;
&lt;br /&gt;
Citations in both Submitted and Mailed status are included.  &lt;br /&gt;
&lt;br /&gt;
If you want a count of how many Mailed and Submitted citations were processed within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#eCitation_Submissions eCitation Submissions Report].&lt;br /&gt;
&lt;br /&gt;
=====Detailed eCrash Submission Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes and updates within a Submission Date range. &lt;br /&gt;
&lt;br /&gt;
The results show the form number, case number, officer name, form type, and submission date. &lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status.  &lt;br /&gt;
&lt;br /&gt;
If you want a count of how many crashes were submitted within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#eCrash_Submissions eCrash Submissions Report].&lt;br /&gt;
&lt;br /&gt;
=====DHSMV UTC Safety Belt Violations Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for safety belt violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.614.html FSS 316.614].  &lt;br /&gt;
&lt;br /&gt;
This report meets the requirements in FSS 316.614(9) for annual race and ethnicity reporting to FDLE and comes up in a table that matches the format for entry into DAVID. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted or Submitted status.&lt;br /&gt;
&lt;br /&gt;
If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_FDLE_Bias_Based_Policing UTC FDLE Bias Based Policing] report.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - Only violations under 316.614 are included in these results. &amp;amp;nbsp; Violations under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.613.html FSS 316.613] are not included because FDLE does not require reporting of race and ethnicity for child restraint violations. &amp;amp;nbsp; If you want a list of both 316.613 and 316.614 violations, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_Click_it_or_Ticket UTC Click It or Ticket] report.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====DHSMV UTC Texting and Driving Violations Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for wireless communication device violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.305.html FSS 316.305].  &lt;br /&gt;
&lt;br /&gt;
This report meets the requirements in FSS 316.305(5) for annual race and ethnicity reporting to FDLE and comes up in a table that matches the format for entry into DAVID.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted or Submitted status.&lt;br /&gt;
&lt;br /&gt;
If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_FDLE_Bias_Based_Policing UTC FDLE Bias Based Policing] report.&lt;br /&gt;
&lt;br /&gt;
=====DHSMV Warning Safety Belt Violations Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for safety belt violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.614.html FSS 316.614]. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
The report comes up in a table. &amp;amp;nbsp; If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Warning_Ethnicity_Race_and_Gender Warning Ethnicity Race and Gender] report.&lt;br /&gt;
&lt;br /&gt;
=====DHSMV Warning Texting and Driving Violations Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of warnings written for wireless communication device violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.305.html FSS 316.305]. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
The report comes up in a table. &amp;amp;nbsp;If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Warning_Ethnicity_Race_and_Gender Warning Ethnicity Race and Gender] report.&lt;br /&gt;
&lt;br /&gt;
=====DUI Race and Gender Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of race and gender on DUI citations for the current year and the previous three years. &lt;br /&gt;
&lt;br /&gt;
NOTE - If the officer did not fill in the Gender and Race on the citation, it will not be included in the count on this report.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status. &lt;br /&gt;
&lt;br /&gt;
=====eCitation Submissions=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of Mailed and Submitted citations within a Submission Date Range.  &amp;amp;nbsp; The results are broken down by submission date. &lt;br /&gt;
&lt;br /&gt;
If you want a list of Mailed and Submitted citations within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Detailed_eCitation_Submission_Report Detailed eCitation Submission] report. &lt;br /&gt;
&lt;br /&gt;
=====eCrash Submissions=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of long form, short form, and update crashes within a Submission Date Range. &amp;amp;nbsp; The results are broken down by submission date. &lt;br /&gt;
&lt;br /&gt;
If you want a list of crashes Submitted within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Detailed_eCrash_Submission_Report Detailed eCrash Submission] report. &lt;br /&gt;
&lt;br /&gt;
=====Failed Login Attempts=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of failed login attempts within a date range. &lt;br /&gt;
&lt;br /&gt;
The results include the User ID, Date, Time, Machine ID, and event description.&lt;br /&gt;
&lt;br /&gt;
=====FDLE Active User Log=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of both active and inactive users for the agency. &lt;br /&gt;
&lt;br /&gt;
=====FDLE User Audit Log=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of login activity for users within a date range, including failed login attempts.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Crashes with Suspected Alcohol/Drug Use=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes where Suspected Alcohol Use and/or Suspected Drug Use for a driver or non-motorist is marked Yes. &lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Motorcycle UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range where the Vehicle Style is Motorcycle. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Motorcycle Warning=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of traffic warnings within a date range where the Vehicle Style is Motorcycle. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Work Zone UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range where Workers? is marked Yes.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Work Zone Warning=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of traffic warnings within a date range where the Workers? is marked Yes. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FIBRS Location Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of FIBRS reports along with the occurred location, latitude, and longitude. &lt;br /&gt;
&lt;br /&gt;
Reports must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
=====Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range that contain a moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====My UTC Stats=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations within a date range that were issued by the officer who is currently logged into TraCS. &lt;br /&gt;
&lt;br /&gt;
The date range will look for forms based on the citation date that is entered on the form, not the date the form was created.  &amp;amp;nbsp; This is not always the same as the form date. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Non Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range that contain a non-moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Number Audit All Forms=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of form numbers that have been used within a date range.  &lt;br /&gt;
&lt;br /&gt;
The results include the form number, form type, current form status, date the number was pulled, and who pulled it.&lt;br /&gt;
&lt;br /&gt;
=====Officer Summary Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of the following forms written by officers within a date range: &lt;br /&gt;
&lt;br /&gt;
UTC, Parking, DUI Citations, Crashes (Long/Short Form only), Crash Updates, FIBRS Incident, UAA/Arrest, Traffic Warnings, Boating, FIR, and Tow. &lt;br /&gt;
&lt;br /&gt;
Crashes and Updates must be in Submitted status to appear on this report. &amp;amp;nbsp; All other forms must be in Accepted status. &lt;br /&gt;
&lt;br /&gt;
=====Pending Citation=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s in Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Pending Crash=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes and updates in Accepted, Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Pending Offense=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of FIBRS/Incident reports in Accepted, Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Personnel List=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of agency personnel.  &lt;br /&gt;
&lt;br /&gt;
The results include the employee ID, first &amp;amp; last Name, phone number, and hire date.&lt;br /&gt;
&lt;br /&gt;
This report will only work if your agency uses the Personnel Tracking form. &lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit Crash=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of crashes that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit Offense-Incident=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of FIBRS Offense/Incident reports that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit UTC=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of UTC&#039;s that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====RMS Uploads Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of forms that were exported to the agency as XML, PDF, and/or TIFF file.&lt;br /&gt;
&lt;br /&gt;
=====Seatbelt Tickets by Ethnicity=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations written for violations of FSS 316.613 (child restraint) and 316.614 (seatbelt) along with the ethnicity and race of the violator.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====THI Crashes=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes where the injury severity for any involved party is marked as Fatal and the Completed field is marked as No.&lt;br /&gt;
&lt;br /&gt;
=====Toxicology Pending Reminder Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes where Alcohol Test Result and/or Drug Test Result fields are marked as Pending.&lt;br /&gt;
&lt;br /&gt;
=====UTC Aggressive Driving Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations where the Aggressive? field is marked yes.&lt;br /&gt;
&lt;br /&gt;
The results include statute, violation description, and the location of the violation.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC by Location=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations along with the issuing officer&#039;s name, the statute, and the charge description. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC by Officer=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations written by individual officers within a date range.  &lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name, the statute number, and the charge description.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Classification Analysis=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations and warnings written by individual officers within a date range.  &lt;br /&gt;
&lt;br /&gt;
The UTC results are broken down into moving, non-moving, criminal, pedestrian, bicyclist violations.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report. &amp;amp;nbsp; Warnings must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Click it or Ticket=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s written for violations of FSS 316.613 (child restraint) and 316.614 (seatbelt) along with the issuing officer&#039;s name.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status in to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Required Court Appearance=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC infractions and criminal violations within a date range where a court appearance is required.&lt;br /&gt;
&lt;br /&gt;
Citations in Open, Accepted, Reviewed, Rejected, Mailed, and Voided status will show on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC FDLE Bias Based Policing=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations along with the ethnicity, race, and gender of the violator and may be used for accreditation requirements.&lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name and FSS for the violation that was written. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status in to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Voided DUI UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of DUI citations that have been voided along with the issuing officer and the reason for the void.  &lt;br /&gt;
&lt;br /&gt;
This report is used for reporting voids to FLHSMV. &amp;amp;nbsp; Therefore, only citations with HSMV numbers are included on this report.&lt;br /&gt;
&lt;br /&gt;
=====Voided UTCs=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations that have been voided along with the issuing officer and the reason for the void.  &lt;br /&gt;
&lt;br /&gt;
This report is used for reporting voids to FLHSMV. &amp;amp;nbsp; Therefore, only citations with HSMV numbers are included on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Ethnicity Race and Gender=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings along with the ethnicity, race, and gender of the violator and may be used for accreditation requirements.&lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name and FSS for the violation that was written. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status to show on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings within a date range that contain a moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Non-Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings within a date range that contain a non-moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
===Analysis Reports - &#039;&#039;Coming in a Future Release!&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
The following analysis reports are in development and are targeted for a future release: &lt;br /&gt;
&lt;br /&gt;
Expunged Records Report&amp;lt;br&amp;gt;FDOT Safety Grant - DUI Crashes with Injury or Fatality&amp;lt;br&amp;gt;FDOT Safety Grant - Unrestrained Crashes&amp;lt;br&amp;gt;FIBRS Submission Results&amp;lt;br&amp;gt;Pending Hit &amp;amp; Run Crashes&amp;lt;br&amp;gt;Pending Offense Reports&amp;lt;br&amp;gt;Pending UAA Reports&amp;lt;br&amp;gt;Traffic Warning Classification Analysis&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports&amp;diff=3688</id>
		<title>Analysis Reports</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports&amp;diff=3688"/>
		<updated>2026-06-02T20:01:02Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Analysis Reports - Coming in a Future Release! */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
There are over 50 pre-built analysis reports available within TraCS.  &lt;br /&gt;
&lt;br /&gt;
All TraCS users may access them by going to the Advanced tab and then choosing Analysis Reports. &lt;br /&gt;
&lt;br /&gt;
You may use the blue Up/Down arrows to change the order of the reports to your liking.&lt;br /&gt;
&lt;br /&gt;
[[File:AnalysisReport1.png]]&lt;br /&gt;
&lt;br /&gt;
Highlight the report you wish to run and double click or press Run Report. &amp;amp;nbsp; Some reports will require a date range and/or offer optional parameters, and others will not. &lt;br /&gt;
&lt;br /&gt;
Reports may be printed or sent via email and they may be exported to PDF, Excel, or image file. &amp;amp;nbsp; The Print, Export, and Email buttons are in the upper left corner of the report. &lt;br /&gt;
&lt;br /&gt;
[[File:AnalysisReport4.png]]&lt;br /&gt;
&lt;br /&gt;
===Available Analysis Reports===&lt;br /&gt;
&lt;br /&gt;
=====Available Form Numbers=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of the remaining form numbers for the agency.  &lt;br /&gt;
&lt;br /&gt;
Someone at the agency should run this report on a regular basis.  &amp;amp;nbsp; Do not rely on the [https://www.tracsflorida.org/wiki/index.php?title=Low_Number_Email_Notification Low Number Email] notification to tell you when form numbers are low.&lt;br /&gt;
&lt;br /&gt;
=====Available Form Numbers - Detailed=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of Available and/or Used form numbers.  &lt;br /&gt;
&lt;br /&gt;
The results include the form number, form type, form number, who pulled the number, status (Available or Used), and the date of that status. &lt;br /&gt;
&lt;br /&gt;
Available means that the number has been loaded into TraCS and has not been pulled onto a form. &amp;amp;nbsp; The Modify Date is the date the form number was added to TraCS.  &lt;br /&gt;
&lt;br /&gt;
Used means the number has been pulled onto a form. &amp;amp;nbsp; The Modify Date is the date the number was pulled.&lt;br /&gt;
&lt;br /&gt;
Examples of how this report may be used are as follows: &lt;br /&gt;
&lt;br /&gt;
:You are looking for a crash, citation, warning, or other numbered form and you cannot locate it in TraCS.  &amp;amp;nbsp; The report will tell you who pulled the number and when.&lt;br /&gt;
:Your FDLE auditor is requesting a list of your Available citation numbers.&lt;br /&gt;
:Your FDLE auditor is requesting a list of your Used citation numbers.&lt;br /&gt;
:Your FDLE auditor has given you a list of specific UTC numbers to research and you cannot locate them in TraCS.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;Keep in mind that there are thousands of numbers that are loaded into the system. &amp;amp;nbsp; The report you run may end up being hundreds or thousands of pages long, even if you are a small agency. &amp;amp;nbsp; Think before you print!&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====Bypass Location Tool Report=====&lt;br /&gt;
&lt;br /&gt;
Agency administrators may run this report to see if anyone at the agency has the location tool requirement turned off. &amp;amp;nbsp; This is rare. &amp;amp;nbsp; Only the TraCS team may turn off the requirement for individuals and it is only done when they are unable to use the location tool on their local machine.  &lt;br /&gt;
&lt;br /&gt;
=====CFS Time Analysis Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of Calls for Service (CFS) with the response time for each.&lt;br /&gt;
&lt;br /&gt;
=====Crash by Location=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes within a date range along with the location that the crash occurred.  &lt;br /&gt;
&lt;br /&gt;
The results include the HSMV #, form date, form type, location, latitude, longitude, and the statute # and statute description of citations that were issued. &lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Crashes and Citations on a Map=====&lt;br /&gt;
&lt;br /&gt;
This report plots crashes and citations on a map within a date range. &lt;br /&gt;
&lt;br /&gt;
The locations are plotted using the latitude and longitude that populates when the [https://www.tracsflorida.org/wiki/index.php?title=Signal_4_Location_Tool geolocation tool] is used. &amp;amp;nbsp; If the geolocation tool was not used, the incident will not show on the map.&lt;br /&gt;
&lt;br /&gt;
The geolocation tool is required on all crash forms. &amp;amp;nbsp; If you would like the requirement turned on for citations as well, contact us. &lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Crash Injury Severity Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes within a date range with a specific FLHSMV Injury Severity type. &lt;br /&gt;
&lt;br /&gt;
HSMV Injury Types are None, Possible, Non-Incapacitating, Incapacitating, Fatal (within 30 days), and Non-Traffic Fatality. &lt;br /&gt;
&lt;br /&gt;
The results show crash date, form type, form status, and the names of involved parties with the injury type selected.&lt;br /&gt;
&lt;br /&gt;
Forms must be in Submitted status. &lt;br /&gt;
&lt;br /&gt;
=====Detailed eCitation Submission Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations within a Submission Date range. &lt;br /&gt;
&lt;br /&gt;
The results show the form number, officer name, statute, and charge description, and the submission date. &lt;br /&gt;
&lt;br /&gt;
Citations in both Submitted and Mailed status are included.  &lt;br /&gt;
&lt;br /&gt;
If you want a count of how many Mailed and Submitted citations were processed within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#eCitation_Submissions eCitation Submissions Report].&lt;br /&gt;
&lt;br /&gt;
=====Detailed eCrash Submission Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes and updates within a Submission Date range. &lt;br /&gt;
&lt;br /&gt;
The results show the form number, case number, officer name, form type, and submission date. &lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status.  &lt;br /&gt;
&lt;br /&gt;
If you want a count of how many crashes were submitted within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#eCrash_Submissions eCrash Submissions Report].&lt;br /&gt;
&lt;br /&gt;
=====DHSMV UTC Safety Belt Violations Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for safety belt violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.614.html FSS 316.614].  &lt;br /&gt;
&lt;br /&gt;
This report meets the requirements in FSS 316.614(9) for annual race and ethnicity reporting to FDLE and comes up in a table that matches the format for entry into DAVID. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted or Submitted status.&lt;br /&gt;
&lt;br /&gt;
If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_FDLE_Bias_Based_Policing UTC FDLE Bias Based Policing] report.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - Only violations under 316.614 are included in these results. &amp;amp;nbsp; Violations under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.613.html FSS 316.613] are not included because FDLE does not require reporting of race and ethnicity for child restraint violations. &amp;amp;nbsp; If you want a list of both 316.613 and 316.614 violations, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_Click_it_or_Ticket UTC Click It or Ticket] report.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=====DHSMV UTC Texting and Driving Violations Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for wireless communication device violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.305.html FSS 316.305].  &lt;br /&gt;
&lt;br /&gt;
This report meets the requirements in FSS 316.305(5) for annual race and ethnicity reporting to FDLE and comes up in a table that matches the format for entry into DAVID.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted or Submitted status.&lt;br /&gt;
&lt;br /&gt;
If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#UTC_FDLE_Bias_Based_Policing UTC FDLE Bias Based Policing] report.&lt;br /&gt;
&lt;br /&gt;
=====DHSMV Warning Safety Belt Violations Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations written for safety belt violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.614.html FSS 316.614]. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
The report comes up in a table. &amp;amp;nbsp; If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Warning_Ethnicity_Race_and_Gender Warning Ethnicity Race and Gender] report.&lt;br /&gt;
&lt;br /&gt;
=====DHSMV Warning Texting and Driving Violations Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of warnings written for wireless communication device violations written under [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.305.html FSS 316.305]. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
The report comes up in a table. &amp;amp;nbsp;If you want a list of violations by ethnicity, race, and gender, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Warning_Ethnicity_Race_and_Gender Warning Ethnicity Race and Gender] report.&lt;br /&gt;
&lt;br /&gt;
=====DUI Race and Gender Summary=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of race and gender on DUI citations for the current year and the previous three years. &lt;br /&gt;
&lt;br /&gt;
NOTE - If the officer did not fill in the Gender and Race on the citation, it will not be included in the count on this report.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status. &lt;br /&gt;
&lt;br /&gt;
=====eCitation Submissions=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of Mailed and Submitted citations within a Submission Date Range.  &amp;amp;nbsp; The results are broken down by submission date. &lt;br /&gt;
&lt;br /&gt;
If you want a list of Mailed and Submitted citations within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Detailed_eCitation_Submission_Report Detailed eCitation Submission] report. &lt;br /&gt;
&lt;br /&gt;
=====eCrash Submissions=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of long form, short form, and update crashes within a Submission Date Range. &amp;amp;nbsp; The results are broken down by submission date. &lt;br /&gt;
&lt;br /&gt;
If you want a list of crashes Submitted within a date range, use the [https://www.tracsflorida.org/wiki/index.php?title=Analysis_Reports#Detailed_eCrash_Submission_Report Detailed eCrash Submission] report. &lt;br /&gt;
&lt;br /&gt;
=====Failed Login Attempts=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of failed login attempts within a date range. &lt;br /&gt;
&lt;br /&gt;
The results include the User ID, Date, Time, Machine ID, and event description.&lt;br /&gt;
&lt;br /&gt;
=====FDLE Active User Log=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of both active and inactive users for the agency. &lt;br /&gt;
&lt;br /&gt;
=====FDLE User Audit Log=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of login activity for users within a date range, including failed login attempts.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Crashes with Suspected Alcohol/Drug Use=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes where Suspected Alcohol Use and/or Suspected Drug Use for a driver or non-motorist is marked Yes. &lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Motorcycle UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range where the Vehicle Style is Motorcycle. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Motorcycle Warning=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of traffic warnings within a date range where the Vehicle Style is Motorcycle. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Work Zone UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range where Workers? is marked Yes.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FDOT Safety Grant - Work Zone Warning=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of traffic warnings within a date range where the Workers? is marked Yes. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====FIBRS Location Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of FIBRS reports along with the occurred location, latitude, and longitude. &lt;br /&gt;
&lt;br /&gt;
Reports must be in Accepted status.&lt;br /&gt;
&lt;br /&gt;
=====Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range that contain a moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====My UTC Stats=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations within a date range that were issued by the officer who is currently logged into TraCS. &lt;br /&gt;
&lt;br /&gt;
The date range will look for forms based on the citation date that is entered on the form, not the date the form was created.  &amp;amp;nbsp; This is not always the same as the form date. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Non Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s within a date range that contain a non-moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Number Audit All Forms=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of form numbers that have been used within a date range.  &lt;br /&gt;
&lt;br /&gt;
The results include the form number, form type, current form status, date the number was pulled, and who pulled it.&lt;br /&gt;
&lt;br /&gt;
=====Officer Summary Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of the following forms written by officers within a date range: &lt;br /&gt;
&lt;br /&gt;
UTC, Parking, DUI Citations, Crashes (Long/Short Form only), Crash Updates, FIBRS Incident, UAA/Arrest, Traffic Warnings, Boating, FIR, and Tow. &lt;br /&gt;
&lt;br /&gt;
Crashes and Updates must be in Submitted status to appear on this report. &amp;amp;nbsp; All other forms must be in Accepted status. &lt;br /&gt;
&lt;br /&gt;
=====Pending Citation=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s in Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Pending Crash=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of long and short form crashes and updates in Accepted, Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Pending Offense=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of FIBRS/Incident reports in Accepted, Open, Rejected, Reviewed, or Validated status.&lt;br /&gt;
&lt;br /&gt;
=====Personnel List=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of agency personnel.  &lt;br /&gt;
&lt;br /&gt;
The results include the employee ID, first &amp;amp; last Name, phone number, and hire date.&lt;br /&gt;
&lt;br /&gt;
This report will only work if your agency uses the Personnel Tracking form. &lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit Crash=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of crashes that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit Offense-Incident=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of FIBRS Offense/Incident reports that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====Rejection Audit UTC=====&lt;br /&gt;
&lt;br /&gt;
The report returns a list of UTC&#039;s that were rejected along with the current status of the form.  &lt;br /&gt;
&lt;br /&gt;
The results include the case number, officer name, the rejection reason, rejection date, and rejecting supervisor.&lt;br /&gt;
&lt;br /&gt;
=====RMS Uploads Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of forms that were exported to the agency as XML, PDF, and/or TIFF file.&lt;br /&gt;
&lt;br /&gt;
=====Seatbelt Tickets by Ethnicity=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations written for violations of FSS 316.613 (child restraint) and 316.614 (seatbelt) along with the ethnicity and race of the violator.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====THI Crashes=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes where the injury severity for any involved party is marked as Fatal and the Completed field is marked as No.&lt;br /&gt;
&lt;br /&gt;
=====Toxicology Pending Reminder Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of crashes where Alcohol Test Result and/or Drug Test Result fields are marked as Pending.&lt;br /&gt;
&lt;br /&gt;
=====UTC Aggressive Driving Report=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations where the Aggressive? field is marked yes.&lt;br /&gt;
&lt;br /&gt;
The results include statute, violation description, and the location of the violation.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC by Location=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations along with the issuing officer&#039;s name, the statute, and the charge description. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC by Officer=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations written by individual officers within a date range.  &lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name, the statute number, and the charge description.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Classification Analysis=====&lt;br /&gt;
&lt;br /&gt;
This report returns a count of citations and warnings written by individual officers within a date range.  &lt;br /&gt;
&lt;br /&gt;
The UTC results are broken down into moving, non-moving, criminal, pedestrian, bicyclist violations.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status to appear on this report. &amp;amp;nbsp; Warnings must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Click it or Ticket=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC&#039;s written for violations of FSS 316.613 (child restraint) and 316.614 (seatbelt) along with the issuing officer&#039;s name.&lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status in to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC Required Court Appearance=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of UTC infractions and criminal violations within a date range where a court appearance is required.&lt;br /&gt;
&lt;br /&gt;
Citations in Open, Accepted, Reviewed, Rejected, Mailed, and Voided status will show on this report.&lt;br /&gt;
&lt;br /&gt;
=====UTC FDLE Bias Based Policing=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations along with the ethnicity, race, and gender of the violator and may be used for accreditation requirements.&lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name and FSS for the violation that was written. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted, Mailed, or Submitted status in to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Voided DUI UTC=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of DUI citations that have been voided along with the issuing officer and the reason for the void.  &lt;br /&gt;
&lt;br /&gt;
This report is used for reporting voids to FLHSMV. &amp;amp;nbsp; Therefore, only citations with HSMV numbers are included on this report.&lt;br /&gt;
&lt;br /&gt;
=====Voided UTCs=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of citations that have been voided along with the issuing officer and the reason for the void.  &lt;br /&gt;
&lt;br /&gt;
This report is used for reporting voids to FLHSMV. &amp;amp;nbsp; Therefore, only citations with HSMV numbers are included on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Ethnicity Race and Gender=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings along with the ethnicity, race, and gender of the violator and may be used for accreditation requirements.&lt;br /&gt;
&lt;br /&gt;
The results include the issuing officer&#039;s name and FSS for the violation that was written. &lt;br /&gt;
&lt;br /&gt;
Warnings must be in Accepted status to show on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings within a date range that contain a moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
=====Warning Non-Moving Violations=====&lt;br /&gt;
&lt;br /&gt;
This report returns a list of warnings within a date range that contain a non-moving violation. &lt;br /&gt;
&lt;br /&gt;
Citations must be in Accepted status to appear on this report.&lt;br /&gt;
&lt;br /&gt;
===Analysis Reports - &#039;&#039;Coming in a Future Release!&#039;&#039;===&lt;br /&gt;
&lt;br /&gt;
The following analysis reports are in development and are targeted for a future release: &lt;br /&gt;
&lt;br /&gt;
Expunged Records Report&lt;br /&gt;
&lt;br /&gt;
FDOT Safety Grant - DUI Crashes with Injury or Fatality&lt;br /&gt;
&lt;br /&gt;
FDOT Safety Grant - Unrestrained Crashes&lt;br /&gt;
&lt;br /&gt;
FIBRS Submission Results&lt;br /&gt;
&lt;br /&gt;
Pending Hit &amp;amp; Run Crashes&lt;br /&gt;
&lt;br /&gt;
Pending Offense Reports&lt;br /&gt;
&lt;br /&gt;
Pending UAA Reports&lt;br /&gt;
&lt;br /&gt;
Traffic Warning Classification Analysis&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=TraCS_Login_Session_Timeout&amp;diff=3687</id>
		<title>TraCS Login Session Timeout</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=TraCS_Login_Session_Timeout&amp;diff=3687"/>
		<updated>2026-06-02T16:19:06Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
====Overview====&lt;br /&gt;
&lt;br /&gt;
As of TraCS Version 16, Baseline 20.0.55, TraCS login sessions will expire after 12 hours, regardless of activity. &lt;br /&gt;
&lt;br /&gt;
This is per CJIS policy. &amp;amp;nbsp; Questions regarding the CJIS policy should be directed to your agency LASO or your FDLE auditor.&lt;br /&gt;
&lt;br /&gt;
====Session Timeout====&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, they will not be able to pull form numbers or open attachments, and they will get no results when searching. &amp;amp;nbsp; If they create a citation from a crash form, it will not generate a UTC number.  &amp;amp;nbsp; Forms they are working on will not sync with the server.&lt;br /&gt;
&lt;br /&gt;
Users must exit out of TraCS and log back in to restore connectivity. &lt;br /&gt;
&lt;br /&gt;
If a user cannot pull numbers, open attachments, or perform searches, the first step in resolving the issue is to log out and back in to restore connectivity. &lt;br /&gt;
&lt;br /&gt;
Users will get a prompt to sign out at 11 hours and 30 minutes and again at 11 hours and 45 minutes. &amp;amp;nbsp; Example below.&lt;br /&gt;
&lt;br /&gt;
[[File:TimeoutExpiration3.jpg]]&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, they will get a prompt like the one below when attempting to pull form numbers. &lt;br /&gt;
&lt;br /&gt;
[[File:TimeoutExpiration.jpg]]&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, TraCS will still be open and the green bars at the upper right will indicate that they are online. &lt;br /&gt;
&lt;br /&gt;
However, they are not connected to the database. &amp;amp;nbsp; They will get no results when searching and will get a prompt like the one below when attempting to pull form numbers on crashes, citations, and warnings.  &amp;amp;nbsp; Any forms they are working on will not sync with the server.&lt;br /&gt;
&lt;br /&gt;
Also, any new defaults set up during that session will not save to the user profile, such as name and agency info on forms, zoom level, night mode, and favorite searches. &lt;br /&gt;
&lt;br /&gt;
Users must exit out of TraCS and log back to restore connectivity and then attachments, searches, and pulling numbers will work again. &amp;amp;nbsp; Any forms that are pending upload will sync with the server. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If a user cannot pull numbers, open attachments, or perform searches, the first step in resolving the issue is to log out and back in to restore connectivity.&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
[[File:TimoutExpiration2.jpg]]&lt;br /&gt;
&lt;br /&gt;
====Best Practices====&lt;br /&gt;
&lt;br /&gt;
Do not leave TraCS open for an extended period of time. &lt;br /&gt;
&lt;br /&gt;
If you won&#039;t be using the system for a time (meal break, dispatched to a call, end of shift, etc.), exit out of forms that you are working on, and log out by pressing the X at the upper right corner or by pressing the Exit button on the File tab at the upper left. &amp;amp;nbsp; If you are prompted to upload forms, answer Yes.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=TraCS_Login_Session_Timeout&amp;diff=3686</id>
		<title>TraCS Login Session Timeout</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=TraCS_Login_Session_Timeout&amp;diff=3686"/>
		<updated>2026-06-02T16:18:06Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* Session Timeout */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
====Overview====&lt;br /&gt;
&lt;br /&gt;
As of TraCS Version 16, Baseline 20.0.55, TraCS login sessions will expire after 12 hours, regardless of activity. &lt;br /&gt;
&lt;br /&gt;
This is per CJIS policy. &amp;amp;nbsp; Questions regarding the CJIS policy should be directed to your agency LASO or your FDLE auditor.&lt;br /&gt;
&lt;br /&gt;
====Session Timeout====&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, they will not be able to pull form numbers or open attachments, and they will get no results when searching. If users create a citation from a crash form, it will not generate a UTC number.  &amp;amp;nbsp; Forms they are working on will not sync with the server.&lt;br /&gt;
&lt;br /&gt;
Users must exit out of TraCS and log back in to restore connectivity. &lt;br /&gt;
&lt;br /&gt;
If a user cannot pull numbers, open attachments, or perform searches, the first step in resolving the issue is to log out and back in to restore connectivity. &lt;br /&gt;
&lt;br /&gt;
Users will get a prompt to sign out at 11 hours and 30 minutes and again at 11 hours and 45 minutes. &amp;amp;nbsp; Example below.&lt;br /&gt;
&lt;br /&gt;
[[File:TimeoutExpiration3.jpg]]&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, they will get a prompt like the one below when attempting to pull form numbers. &lt;br /&gt;
&lt;br /&gt;
[[File:TimeoutExpiration.jpg]]&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, TraCS will still be open and the green bars at the upper right will indicate that they are online. &lt;br /&gt;
&lt;br /&gt;
However, they are not connected to the database. &amp;amp;nbsp; They will get no results when searching and will get a prompt like the one below when attempting to pull form numbers on crashes, citations, and warnings.  &amp;amp;nbsp; Any forms they are working on will not sync with the server.&lt;br /&gt;
&lt;br /&gt;
Also, any new defaults set up during that session will not save to the user profile, such as name and agency info on forms, zoom level, night mode, and favorite searches. &lt;br /&gt;
&lt;br /&gt;
Users must exit out of TraCS and log back to restore connectivity and then attachments, searches, and pulling numbers will work again. &amp;amp;nbsp; Any forms that are pending upload will sync with the server. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If a user cannot pull numbers, open attachments, or perform searches, the first step in resolving the issue is to log out and back in to restore connectivity.&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
[[File:TimoutExpiration2.jpg]]&lt;br /&gt;
&lt;br /&gt;
====Best Practices====&lt;br /&gt;
&lt;br /&gt;
Do not leave TraCS open for an extended period of time. &lt;br /&gt;
&lt;br /&gt;
If you won&#039;t be using the system for a time (meal break, dispatched to a call, end of shift, etc.), exit out of forms that you are working on, and log out by pressing the X at the upper right corner or by pressing the Exit button on the File tab at the upper left. &amp;amp;nbsp; If you are prompted to upload forms, answer Yes.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=TraCS_Login_Session_Timeout&amp;diff=3685</id>
		<title>TraCS Login Session Timeout</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=TraCS_Login_Session_Timeout&amp;diff=3685"/>
		<updated>2026-06-02T16:17:25Z</updated>

		<summary type="html">&lt;p&gt;Admin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;__TOC__&lt;br /&gt;
&lt;br /&gt;
====Overview====&lt;br /&gt;
&lt;br /&gt;
As of TraCS Version 16, Baseline 20.0.55, TraCS login sessions will expire after 12 hours, regardless of activity. &lt;br /&gt;
&lt;br /&gt;
This is per CJIS policy. &amp;amp;nbsp; Questions regarding the CJIS policy should be directed to your agency LASO or your FDLE auditor.&lt;br /&gt;
&lt;br /&gt;
====Session Timeout====&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, they will not be able to pull form numbers, or open attachments, and they will get no results when searching. If users create a citation from a crash form, it will not generate a UTC number.  &amp;amp;nbsp; Forms they are working on will not sync with the server.&lt;br /&gt;
&lt;br /&gt;
Users must exit out of TraCS and log back in to restore connectivity. &lt;br /&gt;
&lt;br /&gt;
If a user cannot pull numbers, open attachments, or perform searches, the first step in resolving the issue is to log out and back in to restore connectivity. &lt;br /&gt;
&lt;br /&gt;
Users will get a prompt to sign out at 11 hours and 30 minutes and again at 11 hours and 45 minutes. &amp;amp;nbsp; Example below.&lt;br /&gt;
&lt;br /&gt;
[[File:TimeoutExpiration3.jpg]]&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, they will get a prompt like the one below when attempting to pull form numbers. &lt;br /&gt;
&lt;br /&gt;
[[File:TimeoutExpiration.jpg]]&lt;br /&gt;
&lt;br /&gt;
If users are still signed in after 12 hours, TraCS will still be open and the green bars at the upper right will indicate that they are online. &lt;br /&gt;
&lt;br /&gt;
However, they are not connected to the database. &amp;amp;nbsp; They will get no results when searching and will get a prompt like the one below when attempting to pull form numbers on crashes, citations, and warnings.  &amp;amp;nbsp; Any forms they are working on will not sync with the server.&lt;br /&gt;
&lt;br /&gt;
Also, any new defaults set up during that session will not save to the user profile, such as name and agency info on forms, zoom level, night mode, and favorite searches. &lt;br /&gt;
&lt;br /&gt;
Users must exit out of TraCS and log back to restore connectivity and then attachments, searches, and pulling numbers will work again. &amp;amp;nbsp; Any forms that are pending upload will sync with the server. &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;If a user cannot pull numbers, open attachments, or perform searches, the first step in resolving the issue is to log out and back in to restore connectivity.&#039;&#039; &lt;br /&gt;
&lt;br /&gt;
[[File:TimoutExpiration2.jpg]]&lt;br /&gt;
&lt;br /&gt;
====Best Practices====&lt;br /&gt;
&lt;br /&gt;
Do not leave TraCS open for an extended period of time. &lt;br /&gt;
&lt;br /&gt;
If you won&#039;t be using the system for a time (meal break, dispatched to a call, end of shift, etc.), exit out of forms that you are working on, and log out by pressing the X at the upper right corner or by pressing the Exit button on the File tab at the upper left. &amp;amp;nbsp; If you are prompted to upload forms, answer Yes.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3684</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3684"/>
		<updated>2026-05-14T20:44:53Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you are updating a crash from a previous vendor, you have recreated the original   &lt;br /&gt;
crash in TraCS, and it is in Open status. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3683</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3683"/>
		<updated>2026-05-14T20:44:21Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you are updating a crash from a previous vendor, you have recreated the original   &lt;br /&gt;
crash in TraCS, and it is in Open status. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3682</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3682"/>
		<updated>2026-05-14T20:29:33Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS and that you put it in Open status. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3681</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3681"/>
		<updated>2026-05-14T20:28:08Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash,  and flag it as Submitted. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then the officer may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3680</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3680"/>
		<updated>2026-05-14T20:26:23Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information on the original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3679</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3679"/>
		<updated>2026-05-14T20:26:02Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3678</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3678"/>
		<updated>2026-05-14T20:24:51Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:If there are any validation errors, correct them and validate again. &amp;amp;nbsp; Validation warnings may be ignored.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3677</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3677"/>
		<updated>2026-05-14T20:23:41Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
5. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team member will change it to the original number in Step 7.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
6. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
7. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
8. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3676</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3676"/>
		<updated>2026-05-14T20:22:50Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &amp;lt;br&amp;gt; You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram and add the narrative. &amp;amp;nbsp; If it is a short form, go to Step 4.&lt;br /&gt;
&lt;br /&gt;
4. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team memberwill change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&amp;lt;br&amp;gt;When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3675</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3675"/>
		<updated>2026-05-14T20:20:03Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram.&lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative from your original crash. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team memberwill change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3674</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3674"/>
		<updated>2026-05-14T20:19:17Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to recreate the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative from your original crash. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team memberwill change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3673</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3673"/>
		<updated>2026-05-14T20:18:56Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to keypunch the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative from your original crash. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team memberwill change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and let us know that you need to update a crash from a previous vendor and that you have recreated the original crash in TraCS. &lt;br /&gt;
&lt;br /&gt;
:Provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3672</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3672"/>
		<updated>2026-05-14T20:16:12Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to keypunch the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative from your original crash. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team memberwill change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support, explain that you need to update a crash from a previous vendor and provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3671</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3671"/>
		<updated>2026-05-14T20:15:02Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to keypunch the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative from your original crash. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; A TraCS team memberwill change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support, and provide the following information: &lt;br /&gt;
:The agency case number&amp;lt;br&amp;gt;The name of the officer who created the crash in TraCS.&amp;lt;br&amp;gt;The 8-digit HSMV number from the original crash form.&lt;br /&gt;
:Request that the original HSMV number be added to the crash and that it be flagged as Submitted. &lt;br /&gt;
&lt;br /&gt;
9. A TraCS team member will add the HSMV number, validate and accept the crash, flag it as Submitted, and remove it from the outgoing HSMV batch. &lt;br /&gt;
&lt;br /&gt;
10. Once TraCS has flagged the crash as Submitted, we will notify you and then you may complete the Update.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3670</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3670"/>
		<updated>2026-05-14T20:09:27Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to keypunch the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &lt;br /&gt;
:The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative from your original crash. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; TraCS will change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and request that the crash be flagged as Submitted. &amp;amp;nbsp; We will flag it and then remove it from the outgoing transmission batch. &lt;br /&gt;
:If TraCS will be adding the HSMV number to the form, provide the 8-digit number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, you may complete the Update as usual.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3669</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3669"/>
		<updated>2026-05-14T20:08:08Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to keypunch the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &amp;amp;nbsp; The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; TraCS will change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and request that the crash be flagged as Submitted. &amp;amp;nbsp; We will flag it and then remove it from the outgoing transmission batch. &lt;br /&gt;
:If TraCS will be adding the HSMV number to the form, provide the 8-digit number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, you may complete the Update as usual.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
	<entry>
		<id>https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3668</id>
		<title>How To Update a Crash Form</title>
		<link rel="alternate" type="text/html" href="https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form&amp;diff=3668"/>
		<updated>2026-05-14T20:07:53Z</updated>

		<summary type="html">&lt;p&gt;Admin: /* How to Update a Crash From a Previous Vendor */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;===Overview===&lt;br /&gt;
&lt;br /&gt;
Once a crash has been submitted to FLHSMV, any changes must be made via Update. &lt;br /&gt;
&lt;br /&gt;
The updated crash will transmit to the state and overwrite the original crash in their system.  &lt;br /&gt;
&lt;br /&gt;
IMPORTANT NOTE: &amp;amp;nbsp; Per HSMV, if the submitted crash is a Short Form, you cannot complete an update to change the Injury Severity from None to any of the other injury types. &amp;amp;nbsp; If there is ANY indication or complaint of pain or discomfort by any of the parties involved, a Long form MUST be completed initially. &amp;amp;nbsp; See [http://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&amp;amp;URL=0300-0399/0316/Sections/0316.066.html FSS 316.066(1)(a)] for details.&lt;br /&gt;
&lt;br /&gt;
===Tips for Completing FSBI Crash Updates===&lt;br /&gt;
&lt;br /&gt;
Per FLHSMV, when updating a Fatality/Serious Bodily Injury (FSBI) crash report, ensure that: &lt;br /&gt;
&lt;br /&gt;
1. The vehicles are in the same order as the initial crash report&lt;br /&gt;
&lt;br /&gt;
2. All persons involved in the crash are included&lt;br /&gt;
&lt;br /&gt;
3. The crash date and time are unchanged&lt;br /&gt;
&lt;br /&gt;
4. Previously marked traffic fatalities (Injury Severity - Fatal) are confirmed by the Medical Examiner&#039;s report&lt;br /&gt;
&lt;br /&gt;
5. The type of median is reported accurately and not left Unknown&lt;br /&gt;
&lt;br /&gt;
6. Exclude animals as decedents&lt;br /&gt;
&lt;br /&gt;
See the [https://www.tracsflorida.org/wiki/index.php?title=Crash_Fatality_Reporting Crash Fatality Reporting] page for further information.&lt;br /&gt;
&lt;br /&gt;
===How to Update an Existing Crash===&lt;br /&gt;
&lt;br /&gt;
====Driver Exchange Crashes====&lt;br /&gt;
&lt;br /&gt;
You cannot complete an Update to a Driver Exchange form. &lt;br /&gt;
&lt;br /&gt;
If you need make changes to a Driver Exchange, open it and press Edit. &amp;amp;nbsp; If you get a pop message that it has been approved by administration and cannot be edited, contact your administrator or TraCS Support and request that it be put back in Open status. &lt;br /&gt;
&lt;br /&gt;
Be sure to revalidate once your changes are complete.&lt;br /&gt;
&lt;br /&gt;
====Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
Crashes must be in Submitted status in order to complete an Update. &amp;amp;nbsp; If you are updating to correct a case number, click [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Correcting_Case_Numbers_on_Long_and_Short_Form_Crashes here].&lt;br /&gt;
&lt;br /&gt;
If the crash is in Accepted or Validated status, open it, press Edit to make changes, and revalidate when finished.&lt;br /&gt;
&lt;br /&gt;
If the crash is in Submitted status, open the original crash, or, if the crash has already been updated, open the most recent update.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;NOTE - When you open a version of the crash that has update(s), you will get a prompt telling you there is an update to the crash and it asks if you want to open it. &amp;amp;nbsp; &amp;lt;u&amp;gt;This is broken&amp;lt;/u&amp;gt;. &amp;amp;nbsp; The update will not open in a new tab. &amp;amp;nbsp; You should search for the crash by the 8-digit HSMV number to get a list of all versions of the crash.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
Press the Update Crash Form button at the top. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew.png]]&lt;br /&gt;
&lt;br /&gt;
If there is already an existing update, you will get a prompt telling you this and asking if you are sure you want to update this version of the crash.  &amp;amp;nbsp; If you are sure, press Yes.  &amp;amp;nbsp; If you are not sure, press No, exit out, and check to make sure that you are updating the most recent version.  &amp;amp;nbsp; To do this type the 8-digit HSMV number into the Form Number field and Search. &amp;amp;nbsp; All versions of the crash will appear in the forms manager.  &amp;amp;nbsp;  Find the most recent version by looking at the Form Date and update that version.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew5.png]]&lt;br /&gt;
&lt;br /&gt;
If you are updating the most recent version of the crash, you will get a prompt asking if you want to update the crash. &amp;amp;nbsp; Press Yes.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew3.png]] &lt;br /&gt;
&lt;br /&gt;
On the next prompt, enter the reason you are updating the crash.  The text entered here is for agency reference only and does not transmit to HSMV. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew2.png]]&lt;br /&gt;
&lt;br /&gt;
If you are not the officer who completed the original crash, you will get a prompt stating this and telling you that the original officer will be added as a witness. &amp;amp;nbsp;  Press OK. &lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew6.png]]&lt;br /&gt;
&lt;br /&gt;
Make any changes to the crash and validate as usual.&lt;br /&gt;
&lt;br /&gt;
Once the crash is accepted by a supervisor it will transmit to the state.&lt;br /&gt;
&lt;br /&gt;
The original crash will show as form type L (long form) or S (short form).  &amp;amp;nbsp; Updates will show as form type U.&lt;br /&gt;
&lt;br /&gt;
[[Image: UpdateCrashFormNew4.png]]&lt;br /&gt;
&lt;br /&gt;
====Correcting Case Numbers on Long and Short Form Crashes====&lt;br /&gt;
&lt;br /&gt;
As of Version 16, if a mistake is made on the Agency Case Number and the crash is in Submitted status (meaning it has transmitted to FLHSMV), it may be fixed.  &lt;br /&gt;
&lt;br /&gt;
&#039;&#039;You still have to complete an Update so that HSMV gets a corrected copy of the crash. &amp;amp;nbsp; Steps are below.&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
1. Create an Update using the steps in the [https://www.tracsflorida.org/wiki/index.php?title=How_To_Update_a_Crash_Form#Long_and_Short_Form_Crashes Long and Short Form Crash Section]. &amp;lt;br&amp;gt; 2. Change the case number on the update and validate as usual. &amp;lt;br&amp;gt; 3. Contact [mailto:support@tracsflorida.org TraCS Support] (hosted) or your System Administrator (non-hosted) to request that the case number on the original be changed to reflect the correct number.&lt;br /&gt;
&lt;br /&gt;
When you contact TraCS or your System Administrator to request the change, we will check to confirm that an update exists. &amp;amp;nbsp; If there is no update, we will not change the case number until one is completed.&lt;br /&gt;
&lt;br /&gt;
Steps for System Administrators (non-hosted):&lt;br /&gt;
&lt;br /&gt;
The button will work in both Mobile mode and Workstation mode.&lt;br /&gt;
&lt;br /&gt;
1. Verify that the officer has completed and validated a crash update with the corrected case number.&amp;lt;br&amp;gt; 2. Search for the crash, highlight the original long or short form in the forms manager, and press the Update Case Number button. &amp;lt;br&amp;gt; 3. Enter the new case number in the box that comes up and press OK. &amp;lt;br&amp;gt; 4. Check the case number on the update against the case number on the original to verify that they match.&lt;br /&gt;
&lt;br /&gt;
NOTE: This button will only work on crash forms.  &amp;amp;nbsp; It will not work on any of the other forms.&lt;br /&gt;
&lt;br /&gt;
[[File:CrashUpdateCaseNumber.png|center]]&lt;br /&gt;
&lt;br /&gt;
===How to Update a Crash From a Previous Vendor===&lt;br /&gt;
&lt;br /&gt;
If you need to update a crash from a previous vendor, you will have to keypunch the original crash into TraCS first.  &amp;amp;nbsp; Once the original crash is completed and flagged as Submitted, you may complete the Update.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;You will need a copy of the original crash report with the HSMV number before starting the process&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
&amp;lt;u&amp;gt;Steps&amp;lt;/u&amp;gt;: &lt;br /&gt;
&lt;br /&gt;
1. Create a new crash in TraCS.&lt;br /&gt;
&lt;br /&gt;
2. Fill out the crash according to the information original crash report. &amp;amp;nbsp; The information must match the original EXACTLY. &amp;amp;nbsp; Do not change anything or add updated information to the fields or the narrative. &lt;br /&gt;
:You will be required to use the Location Tool to plot the location of the crash. &lt;br /&gt;
&lt;br /&gt;
3. If the crash is a long form, create a Signal 4 diagram. &lt;br /&gt;
&lt;br /&gt;
4. If the crash is a long form, add the narrative. &lt;br /&gt;
&lt;br /&gt;
5. Fill out the Reporting Officer section according to the information on the original crash.&lt;br /&gt;
&lt;br /&gt;
6. Press Validate.  &amp;amp;nbsp; A new HSMV number will be automatically added to the form. &amp;amp;nbsp; TraCS will change it to the original number in Step 8.&lt;br /&gt;
:Validation warnings may be ignored. &amp;amp;nbsp; If there are any validation errors, correct them and validate again.&lt;br /&gt;
:When you get the pop-up message that the form has been successfully validated, press OK. &lt;br /&gt;
&lt;br /&gt;
7. IMPORTANT - After the crash is validated, &#039;&#039;immediately&#039;&#039; press Edit to put the form back in Open status and then close out of the crash. &lt;br /&gt;
:&amp;lt;u&amp;gt;Do not revalidate&amp;lt;/u&amp;gt;. &amp;amp;nbsp; You don&#039;t want a supervisor to see a validated crash and accept it.  &amp;amp;nbsp; If it&#039;s accepted it will transmit to the state be added to their system as a brand new crash under a new HSMV number.&lt;br /&gt;
&lt;br /&gt;
8. Contact TraCS support and request that the crash be flagged as Submitted. &amp;amp;nbsp; We will flag it and then remove it from the outgoing transmission batch. &lt;br /&gt;
:If TraCS will be adding the HSMV number to the form, provide the 8-digit number from the original crash form.&lt;br /&gt;
&lt;br /&gt;
9. Once TraCS has flagged the crash as Submitted, you may complete the Update as usual.&lt;/div&gt;</summary>
		<author><name>Admin</name></author>
	</entry>
</feed>