Skip to main content

Inspections

Fleet's Inspections module supports structured vehicle safety checks — from daily pre/post-trip inspections to DOT annual inspections. Each inspection captures item-by-item pass/fail results, inspector details, and a digital signature.

Inspection Types​

TypeDescription
Pre-TripDriver inspection before the start of a shift or trip. Typically required by DOT for commercial vehicles
Post-TripDriver inspection at end of shift. Documents any issues found during the day
DOT AnnualAnnual DOT safety inspection by a certified inspector. Required for commercial vehicles
DOT PeriodicPeriodic DOT inspection (every 90 days or as required by jurisdiction)
SafetyGeneral safety inspection, not tied to a specific regulatory schedule
CustomAny other inspection type you define

Inspection Statuses​

StatusMeaning
PendingInspection has been created but not yet completed or reviewed
PassedAll inspection items passed with no failures
FailedOne or more inspection items failed
Requires AttentionItems that aren't failures but need follow-up

Inspection Items​

Each inspection consists of a list of items, each with:

FieldDescription
CategoryGrouping for the item (e.g., Brakes, Lights, Tires, Engine)
ItemSpecific item being checked (e.g., Front brake pads, Left headlight, Tire tread depth)
Resultpass, fail, or na (not applicable)
NotesOptional notes for this specific item

Creating an Inspection​

  1. Navigate to Inspections in the left sidebar
  2. Click Add Inspection
  3. Select the Vehicle
  4. Choose the Inspection Type
  5. Set the Inspection Date
  6. Enter the Inspector Name (and optionally inspector ID if they have a Fleet driver profile)
  7. Set the Expiry Date if this inspection has a validity period (e.g., DOT annual lasts 12 months)
  8. Add Inspection Items:
    • Click Add Item
    • Enter the category, item name, and result (pass/fail/na)
    • Add notes for any failed or questionable items
  9. Add general Notes for the overall inspection
  10. Optionally enter a Signature URL if a digital signature was captured
  11. Click Save

The inspection is created with Pending status. Update the status after review.

Updating Inspection Status​

After reviewing the inspection results:

  1. Open the inspection record
  2. Click Edit
  3. Update Status to reflect the outcome: Passed, Failed, or Requires Attention
  4. Click Save

Filtering Inspections​

On the Inspections page, filter by:

  • Vehicle — Show inspections for a specific vehicle
  • Type — Show only pre-trip, DOT annual, etc.
  • Status — Show pending, failed, or passed inspections

Inspection Expiry Alerts​

For inspections with an Expiry Date (typically DOT annual and DOT periodic), Fleet generates an inspection_expiring alert before the expiry date. This ensures you never miss a renewal deadline.

Alerts appear in the Fleet Alerts page and on the dashboard.

⚠️DOT annual inspections must be renewed every 12 months. Always set the Expiry Date when logging a DOT annual inspection so Fleet can generate the renewal reminder.

Compliance Summary​

The Inspections page gives a compliance view of your entire fleet:

  • Vehicles with overdue or expiring inspections
  • Percentage of recent inspections that passed
  • Vehicles that have failed items requiring corrective maintenance

For inspection items that result in a Fail:

  1. Note the failing item in the inspection record
  2. Create a corresponding Maintenance record for the corrective repair
  3. After the repair is completed, perform a follow-up inspection

Vehicle Inspection History​

On the vehicle detail page, the Inspections tab shows the complete inspection history for that vehicle — including all inspection types, dates, statuses, and item-level results.

Driver Signature Capture​

Fleet supports capturing digital signatures on inspections via the signature_url field. Store the signature image in a secure location (e.g., Azure Blob Storage) and save the URL in this field when creating the inspection record.

Pre/post-trip inspection workflows that collect signatures from drivers can submit the signature URL programmatically via the API at POST /api/inspections.