> 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/admin/offboarding-employees.md).

# Offboarding employees

{% hint style="info" %}
Walkthrough goes here.
{% endhint %}

When someone leaves, two things have to line up: the employee record and whatever they were using. equipme connects them, so you usually react to something the system already noticed rather than tracking leavers yourself.

With HR Sync, a leaver drops out of your sync scope, either because the account disappears or because your filter only syncs active accounts. What happens next depends on one question: does the person still have services assigned?

No services, and the record is removed automatically. Services still assigned, and the employee goes to the **Offboarding** status and stays, because someone has to decide what happens to that laptop. equipme will not quietly drop a record while equipment is still out there.

That status is your working queue. Filter the employee list on Offboarding and save it as a view, then it is simply there when you need it. Without HR Sync the same status exists, you set it yourself.

For each service you have three directions: store it, internally or back to the provider, move it to a colleague or a location, or cancel it when it ends with the person.

One thing about returns: requesting one is not the end of it. The request goes into order processing and has to be completed there before the item actually appears in your warehouse. That split gives whoever handles processing a chance to catch a mistake before stock changes.

An open record with services attached is the most common way equipment quietly disappears. Working through this list is what keeps your inventory honest.

### Read more

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/UTyFPQC2JUdHXr0xMH59" %}
[Managing Employee Status in equipme](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/my-company/employees/managing-employee-status-in-equipme)
{% endcontent-ref %}

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/ETTrSu9XAY89YIncNeLS" %}
[HR-Sync FAQs](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/settings/integrations/hr-sync-overview/hr-sync-faqs)
{% endcontent-ref %}

{% content-ref url="/spaces/sefXXH6Iz8RCwoM5daoW/pages/HYzVkSCDvZgxGVyD1XKr" %}
[Warehouse management](https://app.gitbook.com/o/tyg0OyVUuxExVkZRRN7N/s/sefXXH6Iz8RCwoM5daoW/assets/warehouse-management)
{% endcontent-ref %}

### Next

The last chapter of this track is the support side: [Manage Tickets](/classes/admin/manage-tickets.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/classes/admin/offboarding-employees.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.