> This page is for version Staging.
> For other versions, use one of these documentation indexes:
> - Prod (default): https://docs.chrt.com/prod/llms.txt
> - Staging: https://docs.chrt.com/staging/llms.txt
> - Dev: https://docs.chrt.com/dev/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.chrt.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.chrt.com/_mcp/server.

# Compliance Documents

Keep compliance evidence with the organization or driver it describes. Uploading a document records evidence; it does not establish legal compliance, carrier qualification, regulatory approval or a retention guarantee.

## Before you start

Confirm the active organization and the person or company named in the document. Organization compliance is available in Provider mode. The current organization and driver management screens enable document management for **Owner** or **Admin** roles; other viewing access still depends on the resource and service permissions.

Use an authorized document and review its type and dates before uploading. Do not upload unrelated private records to test the flow.

## Organization evidence

1. Open [Compliance settings](https://chrt.com/settings/compliance) in the intended provider organization.

2. Review **Organization Compliance** and any existing document records.

3. If management controls are available, choose **Document type** 1 and select the file or files 2.

   ![The Organization Compliance upload form before any upload; numbers 1 to 5 point at the Document type select, the Select files or drag and drop zone, Valid from and Valid until, the disabled Upload evidence button and the No compliance evidence yet list.](/_fern-img/5b022021070eb1e917109fd72dccf0856df212536c362cf5ce5cab91ddba9524.webp)

   *Settings > Compliance > **Organization Compliance**, before any upload. **1** **Document type**, **2** **Select files or drag and drop**, **3** **Valid from** and **Valid until**, **4** **Upload evidence**, disabled until a file is ready, **5** **No compliance evidence yet**.*

4. For a new document-type record, review the offered **Valid from** and **Valid until** fields 3.

5. Wait for file preparation to finish, then use **Upload evidence** 4.

6. Reopen the compliance section and confirm the correct document type, validity information and uploaded files 5.

An existing document-type record can receive additional files; the upload form's validity fields appear when creating a new record. Selected files lock the type choice until removed. Review the saved record instead of assuming an upload changed existing dates.

## Driver evidence

Open the intended driver's profile and its **Compliance** section. Confirm the driver's identity before reviewing **Driver Compliance** or using **Upload evidence**.

Where permitted, select the appropriate document type, review the fields offered in the upload sheet and submit the evidence. Reopen that driver's compliance table and inspect the saved document and files. Administrative upload controls on a driver profile do not imply every driver has self-service upload access.

The current driver table can expose **Edit document** for permitted managers. Review the selected record and confirm the saved result after editing. Resolve load or upload errors before treating the evidence as available to the team.

## Review the evidence

Compare the displayed document type, description, validity dates and actual file to the operational requirement. A displayed validity range is document metadata, not a decision that the evidence is sufficient or approved.

Ask the responsible organization administrator about missing or incorrect evidence. For privacy, retention or deletion requests, use the current [security and privacy sources](/docs/security). This guide does not define a legal retention policy or promise automatic expiry alerts or assignment blocking.