Alert Types

Cards Alerts 

Fuel purchase irregularity alerts

Fuel purchase irregularity alerts notify fleets when a Motive Card fuel purchase is flagged for suspicious activity due to a mismatched fuel type, vehicle location, or because the driver was off-duty when the transaction occurred.

• Fuel level mismatch: Triggers when Motive Card fuel transactions are flagged for issues like the tank level not increasing in line with the amount purchased or the total fuel purchased exceeding expected tank capacity.
• Spend mismatch: Relies on Spend Mismatch detection, which compares Motive Card transaction data against vehicle telematics (location, tank level, fuel type) to highlight potential fraud or misuse.
• Review details in Fleet Dashboard: Flagged transactions can be reviewed from the Fleet Dashboard Cards hub (and related Fuel views where enabled), where fleets can inspect details, add notes, mark transactions as reviewed, or freeze a card if needed.

Best practices 

• Ensure fuel type and tank capacity are correctly set in vehicle profiles so irregularity detection is reliable.
• Send alerts to roles like card program owners or operations leaders who can investigate, adjust controls, or freeze cards.
• Review each flagged transaction promptly using card details and vehicle history (location and fuel level), and document the outcome (confirmed irregularity vs. cleared).
• Periodically audit alerts across drivers, vehicles, and locations to refine spend policies, training, and coaching where issues repeat.

Compliance Alerts

HOS violation alerts 

HOS violation alerts notify fleet users when a driver’s log shows an hours-of-service violation based on the HOS rule set assigned to that driver.

• Availability: This alert is available to fleets using Motive’s HOS compliance features and relies on each driver’s assigned U.S. or Canadian HOS cycle rule.
• Trigger logic: Once Motive’s HOS analyzers detect that a shift, driving, break, or cycle limit has been exceeded under the assigned rule, the system records a violation and generates an alert.
• Regulatory thresholds: Violation conditions (drive time, shift length, cycle hours, required breaks, etc.) are fixed by regulation and the driver’s assigned rule. Thresholds cannot be customized.

Secondary power mode alerts 

Secondary power mode alerts are triggered when a hardwired Vehicle Gateway (3.6+) switches from primary vehicle power to secondary or hardwired power, indicating that the primary wiring path has been disconnected or changed.

• Availability: This alert is only available for vehicles with supported hardwired installations and Vehicle Gateway version 3.6 or later, where secondary power mode has been enabled by Motive.
• Real-time alert: Secondary Power Mode alerts can only be configured as immediate for real-time delivery. Their alert frequency cannot be set as scheduled because power-source changes usually require quick investigation. 

Unidentified trip alerts 

Unidentified trip alerts notify fleet users when the ELD records a trip without a driver connected to the Vehicle Gateway through the Driver App or static pairing. These alerts flag unassigned driving events so fleets can quickly assign or annotate the trip, keeping driver logs accurate and compliant with HOS regulations.

• Availability: This alert is available to fleets using Motive Vehicle Gateway with HOS enabled.
• Trigger logic: Unidentified Trip alerts fire when the system detects that a completed trip has drive time but no driver connection for its duration, creating unassigned driving events.

Unidentified vehicle motion alerts 

Unidentified vehicle motion alerts notify fleet users whenever a vehicle moves without a driver connected to the Vehicle Gateway by pairing with the Motive Driver App. These real-time alerts flag unassigned or unidentified drive time so admins can follow up with drivers, correct HOS records, and reinforce proper login and duty-status habits.

• Availability: This alert is available to fleets using the Motive Vehicle Gateway and the Motive Driver App.
• Real-time alert: This alert cannot be scheduled. It fires in real time when motion is detected from a Vehicle Gateway but no driver is currently connected or paired.

Vehicle Gateway disconnect alerts 

Vehicle Gateway disconnect alerts are triggered when a Vehicle Gateway loses power or connection and goes offline, typically due to power loss, wiring issues, tampering, or removal.

• Availability: Available for vehicles using supported Vehicle Gateway hardware (LBB 3.6 and later) with the Real-Time Vehicle Gateway Disconnects feature enabled.
• Real-time disconnects: Uses a real-time disconnect signal so a disconnect event is created as soon as the device is detected as disconnected, instead of only after it reconnects.
• Configurable frequency: Fleets can define how often they receive repeat alerts while a Vehicle Gateway remains disconnected. 

Data Alerts

WiFi hotspot alerts 

WiFi hotspot alerts are triggered when WiFi hotspot data usage crosses configured thresholds at the company or vehicle level (for example, 75% and 100% of a company data pool, or a vehicle’s individual limit). 

• Availability: This alert is available for fleets using Vehicle Gateways with the Motive WiFi hotspot feature enabled.
• Company data pool: Usage is tracked against a company-level data pool. When the pool is reached, a 5-day grace period begins.
• Segment-level thresholds: During the grace period, vehicles that cross their segment-level thresholds (for example, specific groups or tiers) have hotspot access shut off rather than merely throttled.
• Fleet-wide shutdown: After the 5-day grace period, hotspot access is shut off for all vehicles until additional data is added or the pool is reset.
• Top-up and recovery: Fleets can work with their Account Manager to top up data or adjust the pool, and alerts are supported by proactive notifications so admins know when they are nearing or have crossed key thresholds.
• Real-time alert: WiFi hotspot alerts can only be configured as immediate for real-time delivery. Their alert frequency cannot be set as scheduled. 

Best practices

• When company-level or segment-level thresholds are reached, use the 5-day grace window to review usage, apply top-ups with your account manager, or tighten controls so essential vehicles stay online.
• For operations that rely heavily on hotspot connectivity (for example, certain regions or job types), consider more conservative thresholds and closer monitoring so they are less likely to be shut off.

Document Alerts

Document upload alerts 

Document upload alerts notify fleet users when a driver submits a document from the Motive Driver App or a fleet user submits a document in the Fleet Dashboard. This alert enables fleet admins and managers to monitor document submissions instead of manually checking for uploads, ensuring each document is reviewed and processed according to the fleet’s workflows.

• Target by document template: Alerts can be set up for specific groups and document templates by selecting which groups the alert should watch and which document types (for example, trip or other driver-initiated documents) should trigger notifications.

Best practices

• Editing a template that is set to trigger an alert will not affect the alert. Duplicating a template that is set to trigger an alert will not automatically apply the new, duplicated template to the existing alert nor will a new alert automatically be created.
• If your fleet receives a large number of uploads, consider scheduled (batched) delivery so reviewers can handle documents in a daily or weekly review block instead of many one-off, real-time alerts. 

Driver qualification document upload alerts 

Driver qualification document upload alerts send notifications when new driver qualification documents are uploaded so fleets can quickly review and track submissions.

• Target by document template: Fleets can set up alerts for one or many DQ document types.

Best practices

• Use this alert primarily for documents that require active review or approval (for example, driver-initiated uploads, medical certificates, or high-risk documents) rather than every DQ template. 
• Combine document type filters with role-based recipients so alerts route to the right compliance or safety owners.
• If your fleet receives a large number of uploads, consider scheduled (batched) delivery so reviewers can handle documents in a daily or weekly review block instead of many one-off, real-time alerts. 

Driver qualification expiration alerts 

Driver qualification (DQ) expiration alerts notify fleets when driver qualification documents are expired or approaching expiration so they can take action before a driver becomes non-compliant.

• Target by document template: Alerts can be targeted to specific drivers and document templates (for example, Medical Examiner’s Certificate, Driver’s License, MVR, or Road Test Certificate).
• Expiration windows: These alerts support multiple expiration windows, such as expired or expiring within 3, 7, 15, 30, 45, 60, or 90 days. This helps fleets choose how early they want to be notified.

Best practices

• Use document template and expiration status filters to focus alerts on the highest-risk documents (for example, Medical Examiner’s Certificates and Driver Licenses) and the most action-able time windows (for example, 30–60 days before expiration). 
• Configure recipients at the role (compliance, DOT manager) to ensure the right individual is accountable for follow-up.
• Avoid over-alerting by reserving expired alerts for a smaller set of stakeholders who handle exceptions and escalations.

Vehicle document expiration alerts 

Vehicle document expiration alerts are triggered when a vehicle document (for example, registration, permit, insurance, or inspection) has expired or will expire within a selected window (30, 45, 60, or 90 days), helping fleets track document renewals.

• Target by document template: Alerts can be targeted to specific vehicles and selected document types (for example, registration, insurance, permits, and inspections).
• Expiration windows: These alerts support multiple expiration windows, such as expired or expiring within 30, 45, 60, or 90 days, so fleets can choose how early they want to be notified.

EV Battery Alerts

EV battery activity alerts 

EV battery activity alerts notify fleet users when an electric or plug-in hybrid vehicle’s battery crosses configured thresholds, such as dropping below low or critical levels, reaching a target charge percentage, or when charging starts or stops.

• Real-time SOC signals: Uses real-time battery state-of-charge (SOC) data from EVs and plug-in hybrids to detect low, critical, and target charge levels, helping fleets keep EVs adequately charged, avoid unexpected depletion on route, and return vehicles to service as soon as they have enough charge to complete upcoming jobs.
• Configurable thresholds: Fleets can configure which SOC thresholds should trigger alerts (for example, below 20%, critical below 10%, or reached 80% charge).
• Charge state events: Alerts can also fire when charging sessions start or stop so teams know when a vehicle is ready to be moved or returned to service.

Best practices

• Set low and critical thresholds that reflect your real-world route needs, so vehicles are flagged before they risk running out of charge mid-trip.
• Use target charge reached alerts to signal dispatch or operations that an EV is ready to be reassigned to a job.

Fuel Alerts

Idling alerts 

Idling alerts notify fleet users when a vehicle idles longer than a configured time threshold while taking into account geofence and temperature conditions.

• Duration-based: Triggers only after a vehicle has idled for more than the set time (for example, a certain number of minutes).
• Context filters: Focus on truly avoidable idling by specifying geofences (specific sites, yards, or regions) and temperature (for example, only alert when idling is not needed for comfort or equipment).

Maintenance Alerts 

Defect in inspection report alerts 

Defect in inspection report alerts notify fleet users when a driver submits an inspection report that contains one or more reported defects.

• Defect-based trigger: Fires when an inspection is submitted with at least one defect recorded for a vehicle or asset.
• Target by severity level and defect type: This alert can be configured to trigger only for certain defect types or severities, such as major, minor, or unsafe inspections, so fleets can focus on the most urgent issues.

TPMS alerts  

TPMS alerts trigger when a vehicle experiences a tire health alert from a Motive-partnered tire pressure monitoring system (TPMS) such as PressurePro, based on critical tire condition signals sent to Motive.

• Integration-dependent: Only works when a supported TPMS integration is enabled for the fleet and correctly mapped to the Vehicle Gateway.
• Tire health signals: The alert fires on tire condition events sent by the TPMS provider (such as low pressure, rapid deflation, or other critical tire status alerts).

Vehicle fault code alerts 

Vehicle Fault Code alerts notify fleet users whenever Motive receives a new diagnostic trouble code (DTC) from a vehicle’s onboard system via the Vehicle Gateway, indicating a detected malfunction.

• DTC-based trigger: Fires when the Vehicle Gateway reports a new fault code from the engine, transmission, emissions system, or other monitored components.
• Fault code details in the Fleet Dashboard: Surfaces fault code information in the Fleet Dashboard so managers can see code details, the affected vehicle, and when the issue was detected and take proactive maintenance action before the fault code can lead to breakdowns or safety risks.

Safety Alerts

Cell phone usage alerts 

Cell phone usage alerts trigger when the AI Dashcam detects a driver actively using a handheld phone while the vehicle is in motion.

• AI detection: Uses the AI Dashcam’s in-cab video and vision models to identify when a driver is holding, looking at, or interacting with a phone while driving.
• Speed and motion aware: This alert only triggers while the vehicle is in motion, so cell phone usage when stationary (for example, parked or stopped) does not generate alerts.

Close following alerts 

Close following alerts trigger when a driver follows another vehicle at an unsafe distance for a sustained period, based on speed and time-to-collision.

• AI and telematics driven: Uses road-facing video and telematics (speed and distance) to estimate headway and identify when following distance is too short for the current speed.
• Duration-based: This alert only triggers when unsafe following is maintained for a minimum duration, reducing noise from brief, unavoidable cut-ins.

Collision alerts 

Collision alerts trigger when a vehicle is involved in a collision with another vehicle, object, or animal on the road, including both confirmed and unconfirmed collisions for both life-threatening and non-life-threatening events.

• Video confirmation and review: Confirmed collision alerts trigger when video is available and the Motive Safety Review Team has reviewed and verified that a collision occurred.
• Telematics-based: Unconfirmed collisions trigger when telematics data (for example, extreme G-forces or abrupt speed changes) strongly suggests an impact, but no video is available and there is no human review. 

Best practices

• Because unconfirmed collisions are more prone to false positives than confirmed collisions, restrict unconfirmed collision alerts to a small set of safety managers or supervisors who are authorized to speak with drivers.
• Treat unconfirmed collision alerts as prompts to review data and talk with the driver, not as definitive proof of a collision, so drivers do not feel monitored for every bump or road irregularity.

Distraction alerts 

Distraction alerts trigger when the AI Dashcam detects behaviors such as looking away from the road for extended periods, interacting with objects in the cab, or repeated glances down while the vehicle is in motion.

• AI-based detection: Uses driver-facing video and vision models to identify distraction patterns (for example, head/eye movement away from the road, prolonged downward gaze, reaching for objects).
• Duration and pattern aware: These alerts trigger when distraction is sustained or repeated and ignore single, brief glances.

Driver capture alerts 

Driver capture alerts are triggered when the dashcam captures a front-facing image of the driver, typically for identity verification or profile management.

• Image-based event: This alert fires when the driver-facing camera takes a clear front-facing image (for example, during enrollment, re-enrollment, or periodic verification).
• Identity workflows: Often used to support Face Match or identity workflows by keeping driver profiles up-to-date with recent images.

Driving with PTO engaged alerts 

Driving with PTO engaged alerts trigger when a vehicle is in motion while its PTO (Power Take Off) is engaged.

• AUX and motion logic: Uses AUX wiring (PTO signal) together with vehicle motion data to detect when PTO-powered equipment is on while the vehicle is driving.
• Equipment-aware: Designed for setups where PTO is connected to external devices (for example, boom arms, lifts, or pumps) that should not be engaged while the vehicle is in motion.

Drowsiness alerts 

Drowsiness alerts trigger when facial and head-pose cues indicate fatigue, such as drooping eyelids, prolonged micro-sleep behavior, or nodding off while driving.

• AI-based detection: Uses driver-facing camera and vision models to monitor eye closure, blink patterns, and head position to infer fatigue.
• Motion-aware: Only triggers while the vehicle is being driven, so resting or sleeping while safely parked does not generate alerts.

Fatigue alerts 

Fatigue alerts trigger when a driver shows progressive signs of fatigue based on a composite fatigue score. 

• Composite scoring: Uses multiple inputs (for example, driving behavior, shift length, HOS context, and in-cab camera signals) to calculate a fatigue score instead of relying on a single event.
• Progressive risk detection: The alert fires when the score crosses configured thresholds that indicate progressive or high fatigue risk.

Forward collision warning alerts 

Forward collision warning alerts trigger when sensors detect a high likelihood of a forward collision, typically when a vehicle rapidly closes the distance to another vehicle or object.

• Sensor and telematics-based: Uses speed, distance, and time-to-collision metrics (and, where available, camera/radar inputs) to detect when the vehicle is approaching an object too quickly.
• Proactive warning: Designed to fire before impact, giving drivers and fleets an opportunity to react and avoid or mitigate a crash.

Forward parking alerts 

Forward parking alerts trigger when drivers park nose-in and then reverse out of a parking space.

• Maneuver-based detection: Uses motion and direction data to detect parking sequences where the vehicle enters a spot moving forward and later exits by reversing.
• Risk-focused: Highlights behaviors that can increase collision risk with cross-traffic, pedestrians, or nearby assets when backing out of spaces.

Geofence speeding violation alerts 

Geofence speeding violation alerts notify safety teams when a driver is speeding within one or more specified geofences (for example, yards, customer sites, or risk zones).

• Geofence-scoped: Applies only inside selected geofences, so fleets can enforce stricter speed expectations in sensitive areas like yards, terminals, customer locations, schools, or risk zones.
• Configurable speed limit: Allows configuration of a custom speed limit to determine when a driver is considered speeding within the geofence.

Hard acceleration alerts 

Hard acceleration alerts notify safety teams when there is an abrupt increase in vehicle speed where more force than normal is applied during overly aggressive acceleration.

• Telematics-based: Uses G-force and speed change from the Vehicle Gateway to detect aggressive acceleration events.
• Threshold-driven: Triggered based on event generation settings (for example, minimum G-force and duration) defined for hard acceleration severity.

Hard braking alerts 

Hard braking alerts notify safety teams when there is a sudden change in the direction or speed of the vehicle, where more force than normal is applied while accelerating, braking, or turning too aggressively.

• Telematics-based: Uses G-force and speed-change data from the Vehicle Gateway to detect abrupt deceleration events.
• Threshold-driven: Triggered based on configured event generation settings (for example, minimum negative G-force and duration) that define what counts as hard braking for the fleet.

Hard cornering alerts 

Hard cornering alerts notify safety teams when a driver makes sharp turns with excessive force.

• Telematics-based: Uses G-force and lateral movement from the Vehicle Gateway to detect aggressive cornering events.
• Threshold-driven: Triggered based on configured event generation settings (for example, minimum lateral G-force) that define what counts as hard cornering.

Lane swerving alerts 

Lane swerving alerts trigger when a vehicle drifts repeatedly within or across lanes, indicating poor control, distraction, or potential impairment.

• Telematics and vision-based: Uses lateral movement, steering behavior, and when available, road-facing and driver-facing video to detect repeated weaving or drifting.
• Pattern-focused: Looks for recurring swerves over a period of time rather than a single small correction, reducing noise from normal lane adjustments.

Near collision alerts 

Near collision alerts can be used to notify safety teams about a near collision or close call where there was a clear potential for harm but no confirmed impact.

• Risk-based detection: Uses a combination of telematics and/or video signals (for example, harsh maneuvers, rapid deceleration, close following, and steering corrections) to identify events that strongly resemble a collision scenario but do not have a verified impact.
• Event review: Near Collision events can be reviewed alongside video when available so safety teams can confirm context and decide whether follow-up coaching or investigation is needed.

Obstructed camera alerts 

Obstructed camera alerts trigger when the dashcam’s view is blocked (for example, covered lens, extreme glare, or misalignment), preventing accurate event detection and video capture.

• Vision-based detection: Uses camera health signals and in-cab or road-facing video to detect when the lens is blocked, heavily obscured, or pointed away from the intended field of view.
• Impact on safety features: Indicates that AI events and video evidence may be incomplete or unavailable until the obstruction is resolved.

Seat belt violation alerts 

Seat belt violation alerts trigger when the dashcam detects a driver operating the vehicle without a fastened seat belt.

• Vision-based detection: Uses driver-facing dashcam footage and AI models to identify when the seat belt is not properly fastened while the vehicle is being driven.
• Motion-aware: Only triggers when the vehicle is in motion, avoiding alerts for drivers who are unbuckled while parked or safely stopped.

Smoking alerts 

Smoking alerts trigger when in-cab video detects a driver smoking while operating the vehicle.

• AI-based detection: Uses driver-facing camera and vision models to identify when a driver is holding or using a cigarette or similar smoking device while driving.
• Motion-aware: Only triggers while the vehicle is being driven so that off-duty or parked behavior does not generate unnecessary alerts.

Speeding over posted alerts 

Speeding over posted alerts trigger when a driver travels above the posted speed limit for a specified duration.

• Map-based limits: Uses road speed-limit data to compare the vehicle’s speed against the posted limit for the specific road segment.
• Threshold-driven: Triggered based on event generation settings (for example, how far above the limit and for how long) that allows fleets to define what counts as a speeding-over-posted event.

Stop sign violation alerts 

Stop sign violation alerts trigger when a vehicle does not come to a sufficient stop at a detected stop sign location before proceeding.

• Map and vision-aware: Uses mapped stop sign locations and computer vision from the road-facing camera (where available) together with speed data to detect rolling stops.
• Stop threshold: Evaluates whether the vehicle’s speed drops below a low threshold and remains there briefly to qualify as a complete stop, reducing false positives from slow roll-throughs.

Unsafe lane change alerts 

Unsafe lane change alerts trigger when drivers change lanes aggressively or without sufficient gap, often based on lateral motion patterns and turn-signal behavior.

• Telematics and vision-based: Uses lateral movement, speed, and camera data to detect abrupt lane changes or swerves into adjacent lanes.
• Gap and behavior logic: Looks for combinations of high lateral acceleration, limited headway, and missing or late turn-signal use to distinguish unsafe maneuvers from normal lane changes.

Unsafe parking alerts 

Unsafe Parking alerts trigger when drivers park in locations or orientations that indicate elevated risk (for example, roadway shoulders or other unsafe stopping areas).

• Context-aware: Uses location and vehicle state to detect when a vehicle is stopped or parked in areas that are typically unsafe, such as road shoulders.
• Safety-focused: Highlights situations where a stopped vehicle could increase collision risk or violate company parking policies.

Tracking Alerts

AUX status change alerts 

AUX Status Change alerts trigger when the status of equipment connected via AUX inputs (for example, PTO, panic button, plow, and generator) changes from on to off or off to on, based on AUX wiring and configuration.

• Hardware-dependent: Requires AUX lines to be correctly wired from the Vehicle Gateway to external equipment (PTO, switches, or sensors) and correctly configured in Motive.
• State-change logic: Fires on transitions (on→off or off→on) rather than continuous state, so alerts are tied to specific actions (for example, PTO engaged, door opened, or pump started).
• Flexible equipment types: This alert can be mapped to different AUX-connected devices depending on fleet needs.

Asset activity alerts 

Asset Activity alerts trigger when a previously inactive asset starts moving or generating activity.

• Movement-based: Fires when an asset that was stationary crosses a motion threshold (for example, speed or distance) indicating the start of movement or a new trip.
• Visibility focus: Designed to highlight unplanned movements, after-hours usage, or the start of asset utilization that might otherwise go unnoticed.

Asset Gateway offline alerts 

Asset Gateway offline alerts trigger when an asset gateway stops communicating with the Motive platform for a set duration.

• Connectivity-based: Triggers when Motive no longer receives regular check-ins or telemetry from an Asset Gateway for longer than the configured offline window.
• Possible causes: Often indicates cellular coverage gaps, depleted battery, loss of external power, or hardware issues that can impact asset tracking and monitoring.

Asset Gateway low battery alerts 

Asset Gateway low battery alerts trigger when the internal battery level of an Asset Gateway falls below a set threshold.

• Battery-level trigger: Fires when the device’s battery drops under a configured level (for example, when an Asset Gateway Solar remains under 10% for more than a set period).
• Continuity warning: Designed to warn before the device stops reporting so fleets have time to recharge, replace, or service the Asset Gateway.

Carrier alarms alerts 

Carrier alarms alerts notify you when a Carrier reefer unit reports a fault or alarm condition through the telematics connection.

• Direct reefer integration: Triggers on fault or alarm codes sent from Carrier reefer units into the Motive Platform via the telematics link.
• Critical issue reporting: Surfaces events such as unit shutdowns, sensor failures, or performance faults that can affect temperature control and load integrity.

Dashcam disconnect alerts 

Dashcam disconnect alerts trigger when a dashcam loses connection to the Vehicle Gateway (or when an AI Dashcam is no longer connected), indicating potential unplugging, cabling, power, or device issues.

• Connection-based: Fires when the platform detects that a dashcam is no longer communicating with its paired Vehicle Gateway, even if the gateway itself remains online.
• Device coverage impact: Signals that video and AI detection from that dashcam may be unavailable until the connection or power issue is resolved.

Door open alerts 

Door open alerts trigger when a cargo door is open under configured time and location conditions and can automatically recall video so customers can check for possible cargo theft or tampering.

• Time-based door logic: Users can configure the alert to fire only when a door remains open longer than a set duration, reducing noise from brief, expected openings.
• Geofence conditions: Alerts can be scoped to only trigger when the door is opened inside or outside selected geofences (for example, outside warehouse geofences or inside risk zone geofences).
• Automatic video recall: When conditions are met and an Omnicam is part of the setup, the platform automatically recalls video around the event (up to a defined maximum window, such as 60 minutes) so users have visual evidence for investigation.
• Hardware dependencies: Requires an AI Omnicam plus AG Mini connected to DES-2, with both the AG Mini and Omnicam powered consistently for reliable detection and video recall.

Best practices

• Wire the AG Mini and Omnicam so they are powered at all times, ideally from the vehicle battery, which is why this setup is best suited for heavy trucks. Lighter vehicles (for example, sprinters) may only support alerts when the vehicle is on.
• Configure alerts for high-risk scenarios such as doors opening outside warehouse geofences or within risk zone geofences to focus on likely theft or tampering events.
• Design your investigation workflow around the fact that the recalled video is limited to a fixed window of 60 minutes, and pull and review footage promptly when alerts fire.

Dormancy alerts 

Dormancy alerts trigger when an asset has not reported movement or activity for an extended period of time.

• Duration-based: Fires only after an asset remains inactive beyond a threshold you set, for example, days or weeks without any movement or updates since the asset’s last active time.
• Utilization and security focus: Highlights assets that may be under-utilized, misplaced, or potentially stolen due to unusually long inactivity.

Geofence entry alerts 

Geofence entry alerts trigger when a driver or vehicle enters a defined geofence.

• Boundary-based: Uses fleet-configured geofences (for example, yards, customer sites, terminals, and risk zones) to detect when a vehicle crosses into the geofenced area.

Geofence exit alerts 

Geofence exit alerts trigger when a driver or vehicle exits a defined geofence.

• Boundary-based: Uses fleet-configured geofences (for example, yards, customer sites, terminals, and risk zones) to detect when a vehicle crosses out of the geofenced area.

Geofence nearby alerts 

Geofence nearby alerts trigger when a vehicle or asset is within a configurable distance (up to 6 miles) of a selected geofence, typically a risk zone.

• Proximity-based: Fires when an asset enters a radius around a geofence boundary (for example, within 1–6 miles), not only when it crosses into the geofence itself.
• Risk-zone focus: Commonly used with risk zone geofences so fleets know when vehicles are approaching sensitive or high-risk areas.
• Configurable distance: Admins can set how close to the geofence the vehicle must be before the alert fires, allowing for customized warning windows.

Reefer temperature alerts 

Reefer temperature alerts trigger when a refrigerated trailer’s temperature moves outside the configured set point or allowable range.

• Set point-based: Triggers when actual trailer temperature deviates beyond a defined threshold from the target set point or falls outside a configured minimum or maximum range.
• Cargo-protection focus: Designed specifically to catch conditions that could lead to cargo spoilage or quality issues (too warm, too cold, or unstable temperatures).

Stopped inside geofence alerts 

Stopped inside geofence alerts trigger when a vehicle or asset is stationary inside a geofence for longer than a configured time.

• Duration-based: Fires only after a vehicle or asset remains stopped within the geofence beyond a threshold you set (for example, 10, 30, or 60 minutes), reducing noise from short, expected stops.
• Geofence-specific: Tied to selected geofences such as yards, customer sites, job locations, or risk zones where dwell time matters.

Thermo King alarms alerts 

Thermo King alarms alerts trigger when a Thermo King refrigeration unit reports a fault, an alarm code, or an abnormal operating condition. 

• Integration-based: This alert is only available for Thermo King reefers integrated with the Motive Platform and fires when an alarm or fault code is sent from Thermo King units into Motive via the telematics connection.
• Temperature and health focus: Surfaces issues that can affect temperature control or equipment health so fleets can act before cargo is compromised.

Unfamiliar driver alerts 

Unfamiliar driver alerts trigger when Motive’s AI Dashcam and real-time Face Match detect a person driving who does not match any registered driver profile.

• AI and Face Match detection: Once the vehicle exceeds 5 km/h or 3.10mph, the AI Dashcam captures the driver’s face and compares it against the fleet’s catalog of registered driver profiles. If the face does not match any existing profile, an Unfamiliar Driver alert is triggered and a new unfamiliar profile is created.
• One-time alert per profile: The alert fires only when that unfamiliar profile is first created. On later trips by the same unidentified person, the system adds more images to the existing unfamiliar profile but does not send additional alerts.

Best practices

• To maximize effectiveness, ensure that at least 80% of your fleet is already identified using Face Match before activating Unfamiliar Driver alerts. This helps ensure unfamiliar detections are true exceptions instead of alerts for known, authorized drivers.

Vehicle activity alerts 

Vehicle activity alerts are flexible tracking alerts that trigger based on engine and motion behavior, often within specific geofences.

• Engine and movement-based: This alert can be configured to fire on key behaviors such as engine start, movement above a speed threshold, or other activity patterns within designated areas.
• Geofence-scoped: Often limited to designated areas (for example, yards, terminals, job sites, or high-risk zones) so you only see activity where it matters most.

Workforce Alerts 

Motor vehicle record alerts 

Motor vehicle record alerts are triggered when a driver’s Motor Vehicle Record (MVR) has one or more violations. 

• Availability: This alert is available to customers with a Paid Workforce Management subscription and access to the integrated MVR records feature.
• MVR statuses: Within Integrated MVRs, each Motor Vehicle Record can have one of the following three MVR statuses:
  • Clear status indicates no reportable issues. 
  • Activity status indicates a reportable driving activity that requires review by the safety and compliance team.
  • Exception status indicates more serious or potentially disqualifying activity or license issues on the MVR that require immediate attention from the safety and compliance team.
• Configurable triggers: Fleets can choose whether alerts are triggered when MVRs show Activity, Exception, or both.
  • Activity: Notify teams when a driver has a valid license but one or more violations. 
  • Exception: Notify teams when an MVR indicates multiple minor or major violations or suspension.
• Direct access to records: Clicking the alert from the Notification Center or email takes users directly to the relevant MVR on the Qualifications page so they can immediately review the record and take follow-up action. 

Best practices

• Fleets should use integrated MVRs as the primary way to request MVRs so alerts are consistently based on vendor‑scored records. 
• Start by enabling alerts for both Activity and Exception, then narrow the alert to specific driver groups or roles to focus on higher‑risk segments and reduce noise. 
• Pair MVR activity alerts with existing qualification document uploads and expiration alerts to ensure both driving history and key driver documents are monitored together.

Training alerts 

Training alerts notify fleets and drivers when a training module is assigned, is approaching its due date, or is overdue, helping ensure training is completed on time.

• Flexible timing: Fleet admins can configure when the alert fires, for example, on assignment, a set number of days before the due date, or on a recurring cadence after the due date has passed.

Best practices

• Start with a small set of touchpoints (for example, on assignment, a few days before the due date, and a periodic overdue reminder) to nudge completion without causing alert fatigue.
• Target alerts to the drivers responsible for completing training and to the managers who monitor compliance, using groups that mirror how the fleet organizes training (regions, terminals, and job roles).
• Review training alert setup along with training summary and detail reports to monitor completion trends and fine-tune reminder timing or frequency over time.

Share this with others