> For the complete documentation index, see [llms.txt](https://docs.okup.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.okup.ai/okupai-platform/staff-and-operations/damages.md).

# Damages

Report, track, and resolve property damages — with photos and videos attached.

Open it via **Staff → Damages** in the left menu. Use **Filter Created** (date range) to narrow everything down.

***

## 📊 Damage KPIs & charts

Four cards summarize the situation:

| KPI                       | What it shows                              |
| ------------------------- | ------------------------------------------ |
| **Damages (30d)**         | Damages reported in the last 30 days       |
| **Open Damages**          | Damages not yet solved                     |
| **Resolution Rate**       | Share of reported damages already solved   |
| **Avg Resolution (days)** | How long solving a damage takes on average |

Four charts show trends: **Monthly Damages Reported**, **Status Distribution**, **Current Open Damages by Property**, and **Resolution Time**.

***

## 📋 Damages Register

Every damage as a table row: **Created**, **Property**, **Status**, **Media**, and **Description**. Use the status filter (**All / Open / Solved**) to focus on what still needs attention, and click the media icons to open the attached images or videos.

Click a row to open and **edit** the damage — update the description, add media, change the assignee, mark it solved, or use **Delete damage** to remove it permanently.

***

## ➕ Report a new damage

1. Click **Add a new damage**
2. **Base information** — choose the **Property** and optionally an **Assigned to** maintenance user
3. Describe the damage under **New damage description**
4. **Upload Media** — click or drag & drop; **images and videos are supported**
5. Click **Create damage**

{% hint style="info" %}
When you select a property, the modal also lists the **open damages for the selected property** — so you can check whether the issue was already reported before creating a duplicate.
{% endhint %}

***

**➡️ Next steps**

* Check your teams' work quality on the Cleaning page
* Review property basics in Property Settings