> ## Documentation Index
> Fetch the complete documentation index at: https://dpssop.equinoxroleplay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# 6.4 - Traffic Enforcement - Driver Strike Procedures

> DPS officer procedure for assessing, documenting, and referring driver license strikes.

The DOJ **Driver Strike & License Point System** is the authoritative source for values, active periods, thresholds, suspension and revocation. This DPS page addresses **officer workflow**; it does not establish competing point values or licensing powers.

## Officer Checklist

1. Verify the individual's identity, driver's license status, and driving record.
2. Establish the underlying Traffic & Vehicle Code violation with supporting evidence.
3. Identify the correct offense and its currently authorized strike value.
4. Apply anti-stacking safeguards: do not assess multiple versions of the same continuous violation or use overlapping charges merely to reach a threshold.
5. Complete the incident/citation and supporting documentation in the MDT.
6. Assess strikes **only after** a qualifying final determination (finalized citation, conviction, authorized administrative decision, or court ruling); probable cause alone is insufficient.
7. Confirm active strikes and the 30-real-world-day active window.
8. Where 15+ strikes are verified, initiate only the suspension/referral steps authorized to the officer and document the result.
9. At 25+, notify a supervisor and refer the matter to DOJ or Traffic Court for revocation review. Do not independently revoke a license without authority.
10. Record notices, supervisor review, referrals, and disposition in the MDT.

## Non-Negotiable Restrictions

* Never use a strike total alone as grounds for detention, arrest, seizure, impoundment, or forfeiture.
* Never suspend, revoke, or remove valid strikes without the applicable authorization.
* Strike expiration does **not** automatically terminate a suspension or revocation.
* Community service changes sentencing only when authorized and does **not** automatically remove points.
* Impound or seizure must satisfy the controlling DPS impound policy and applicable law.

## Threshold Response

| Active total | Required officer response |
| - | - |
| 0–9 | Document normal enforcement and lawful dispositions |
| 10–14 | Consider supervisor review and document repeat conduct |
| 15–24 | Verify points and commence authorized suspension process |
| 25+ | Notify supervisor; refer to DOJ/Traffic Court for revocation review |

## Documentation Standard

Record the incident or report number, final determination and date, assigned offense and strike value, prior active point calculation, anti-stacking assessment, restriction imposed (if any), authorization, and applicable supervisor/DOJ referral. Preserve supporting evidence.

***

# Driver Strikes - Quick Reference

| Active points | Status | Field action |
| -: | - | - |
| **0–9** | Standard | Normal enforcement; document |
| **10–14** | Elevated | Document repeat offenses; supervisor review as appropriate |
| **15–24** | Suspension threshold | Verify final determinations; initiate authorized process |
| **25+** | Revocation review | Supervisor notice and DOJ/Traffic Court referral |

* **Active period:** 30 real-world days after qualifying final determination.
* **Proof:** Conviction, finalized citation, authorized administrative determination, or court order—not probable cause alone.
* **Anti-stacking:** No duplicate speeding classifications; Reckless Evading replaces ordinary Evading for same pursuit; no duplicate point assessments for overlapping conduct.
* **Suspensions:** First 3 days; second within 30 days 7 days; third within 30 days 14 days + mandatory court review.
* **Revocation:** Requires authorized action, not automatic at 25; 14-day minimum before an application for reinstatement.
* **Never:** Arrest, detain, tow, seize, or forfeit based solely on points.

Consult the DOJ Driver Strike & License Point System pages for offense-by-offense point values, authorization requirements, and appeals. This quick reference is not a substitute for controlling policy.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.