> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://support.haddock.app/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# I can't delete an employee - causes and solution 🧩🙅‍♂️

This article explains **why you cannot delete an employee** in haddock HR and which steps to follow to **unblock** deletion, if you really need it.

---

### Why it cannot be deleted 🚫

haddock HR protects the **integrity of the information**: an employee **cannot be deleted** if **any recorded data** references them, whether it is **active or inactive**. The most common cases are:

- **Planned shifts** in the **Plan** associated with that employee.
- **Clock-ins / time records** linked to their user.

As long as this data exists, the system will **block** deletion to avoid historical inconsistencies.

💡 **Important**: an employee who has been **deactivated** does **not consume subscriptions** in haddock HR. If you do not need to remove them completely, **deactivating** them is the recommended option and **does not cost you anything**.

---

### How to allow deletion ✅

1. **Deactivate** the employee (optional but recommended)
  This keeps costs down and lets you review the references calmly.
2. **Delete shifts**
  Open the **Plan**, filter by the employee, and **delete all shifts** (past and future) associated with them.
3. **Delete clock-ins**
  Go to the **Clock-ins / Time tracking** module, filter by the employee, and **delete the existing records**.
4. **Verify references**
  Make sure **no data remains** linked to them (check future periods, templates/rotations that include them, etc.).
5. **Try deleting again**
  Go back to the employee's profile and use the **Delete** option.

---

### Best practices 💡

- **Keep the history**: unless there is a specific need, **deactivate** the employee instead of deleting them to keep traceability (planning, clock-ins, approvals).
- **Closing window**: if you do monthly or legal closings, wait until after the **closing** before deleting data.
- **Transparency**: leave an **internal note** stating the reason for deletion, if applicable, before deleting.

---

### Frequently asked questions ❓

**Does an inactive employee block deletion too?**
Yes. If they have **shifts** or **clock-ins** saved, they **prevent** deletion even if they are deactivated.

**Is it enough to remove future shifts?**
No. You must **delete all** existing shifts (past and future) and the **clock-ins**.

**Does it cost me to keep them inactive?**
No. A **deactivated** employee does not consume a license in haddock HR.

**I deleted shifts and clock-ins, and I still cannot delete.**
Check whether there are any **recurring assignments** left (rotations/templates that include them) or residual data. If it persists, contact support and include the **employee ID**.