# Compliance

The Compliance section groups all driver-related regulatory records required for DOT safety and operations. Each record type (CDL, MVR, Medical, Test) is managed through its own sub-page, with fields, validation, and expiration logic designed to ensure complete documentation and prevent compliance violations.

`![DriverCompliance](../assets/driver-compliance.png)`\
\&#xNAN;*Figure: Driver profile with compliance cards and status indicators.*

#### Sub-sections

* **CDL**\
  Manage commercial license data including class, endorsements, expiration, and renewal logic.
* **MVR**\
  Track motor vehicle record documents tied to a valid CDL, with logic for handling expired or missing licenses.
* **Medical**\
  Store DOT medical exam records with expiration dates and optional notes or uploads.
* **Drug & Alcohol Test**\
  Record test type, reason, result, and documentation to support audit or incident reviews.

#### Compliance Logic Summary

* Expired records are flagged in both the driver list and detail view.
* Each compliance type is validated individually, but their combined status impacts hiring, assignment, and payroll visibility.
* Drivers missing required documentation may be visually marked or blocked from certain workflows (based on company enforcement settings).

#### Notes

* All compliance sections support document upload and history tracking.
* Alerts and reminders may be configured per company under Notification Preferences in the driver’s profile.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rute.gitbook.io/carrier/compliance.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
