> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/classes/administrative-functions/manage-organizational-structure/employee-management/offboarding-employees.md).

# Offboarding employees

When someone leaves, two things have to line up: the employee record needs to reflect it, and whatever they were using has to come back. equipme connects those two, so in most cases you react to something the system already noticed instead of tracking leavers yourself.

#### How equipme learns that someone is leaving

If you work with HR Sync, you usually do not set anything manually. When an employee disappears from your HR system, or is excluded by your sync filter — for example when the filter only syncs active accounts and the account gets deactivated — equipme picks this up on the next sync.

What happens then depends on a single question: does the employee still have services assigned?

* **No services assigned.** The employee is removed automatically. Nothing left for you to do.
* **Services still assigned.** The employee is set to the **Offboarding** status and the record stays, because someone has to decide what happens to those services.

That second case is why offboarding is not fully automatic. equipme will not quietly drop a record while a laptop is still out there.

If you do not use HR Sync, the same status exists. You set it on the employee record yourself.

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/UTyFPQC2JUdHXr0xMH59" %}
[Managing Employee Status in equipme](/equipme/my-company/employees/managing-employee-status-in-equipme.md)
{% endcontent-ref %}

#### Finding who is currently offboarding

The status is visible in the employee list. Filter on **Offboarding** and save the result as a view, so the overview is simply there when you need it instead of something you rebuild each time.

Treat that list as your working queue. Everyone on it still has something outstanding.

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/ETTrSu9XAY89YIncNeLS" %}
[HR-Sync FAQs](/equipme/settings-1/integrations/hr-sync-overview/hr-sync-faqs.md)
{% endcontent-ref %}

#### Deciding what happens to the services

Open the employee and look at the services assigned to them. For each one you have a few directions:

* **Store it.** Choose internal to keep the item in your own warehouse, or external to send it back to the provider.
* **Move it.** If the device goes straight to a colleague or stays with a location, you can move the service instead of returning it.
* **Cancel it.** For services that simply end with the person, such as a subscription.

One thing worth knowing about returns: they are not finished the moment you request them. The request lands in order processing and has to be completed there before the item actually appears in your warehouse. That split is deliberate — it gives whoever handles processing a chance to catch mistakes before stock officially changes.

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/HYzVkSCDvZgxGVyD1XKr" %}
[Warehouse mangagement](/equipme/assets/warehouse-mangagement.md)
{% endcontent-ref %}

#### Why this matters beyond tidiness

An employee record that stays open with services attached is the most common way equipment quietly disappears. The Offboarding status exists to make that visible rather than leaving it to memory. Working through the list is what keeps your inventory honest.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://hub.equipme.io/classes/administrative-functions/manage-organizational-structure/employee-management/offboarding-employees.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.