# Document Uploads

Each insurance policy in the system must include a supporting document — typically a certificate of insurance or policy summary — to validate coverage and meet audit/compliance requirements.

***

### When Documents Are Required

* When **adding a new policy**
* When **editing or renewing** an expired policy
* For all types: General Liability, Auto, Cargo, Physical Damage, Interchange

> 📎 Upload is mandatory. The system will block saving if no document is attached.

***

### Supported File Formats

| Format | Description                   |
| ------ | ----------------------------- |
| PDF    | Preferred (certificate scans) |
| PNG    | Accepted (clear screenshots)  |
| JPG    | Accepted (photo of document)  |

> 🚫 Word documents, Excel, or other formats are not supported.

***

### Upload UI Behavior

* Drag & drop area or “Browse” file selector
* Filename appears under the upload zone
* Uploaded files can be replaced by uploading a new one
* File is stored and accessible from the policy view

\
\&#xNAN;*Figure: Upload component with drag-and-drop support and preview.*

***

### Where Documents Appear

* In the **policy detail row** inside the insurance list
* In the **unit details page** for truck/trailer-linked policies
* In downloadable formats (coming soon)

***

### Notes

* Admins can re-upload or update documents at any time
* Expired policies still require a valid document for archival purposes
* Uploaded files may be used in compliance exports or audits

> ✅ Tip: Always upload the latest PDF provided by your insurance company to avoid dispatch or visibility issues.


---

# 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/company/settings/insurance-policies/document-uploads.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.