> 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/documentation/fulfillment/completed-positions.md).

# Completed positions

Somebody asks which notebook their colleague was given in March, and whether it was the one with the cracked screen. Completed positions is where that is answered.

A position lands here when its work is done: the shipment was submitted, the last production step was closed, or the return was processed. It leaves [Open positions](/documentation/fulfillment/open-positions.md) at the same moment.

## What it answers

**Which device went to whom.** The position keeps the serial number, the employee, the location and the dates. When a customer disputes what was delivered, this is the evidence.

**When the term started.** Activation and completion are recorded separately, which matters when they were not the same day.

**What went out and when.** Filter by date for a month's output, or by customer for everything one account received.

The list opens on a date range rather than everything, so widen the completion date filter if what you need is older than the default window. A **Show canceled** toggle brings cancelled positions in; it is off by default, so what you see is delivered work only.

## What is still editable, and why

Opening a completed position, most of it is fixed. No cancelling, no status change, no editing the provisioning or activation dates. Each stage carries the timestamp of when it was done.

The device fields stay open, though: the serial number, the inventory number, service components, the internal comment.

That split is deliberate. The order is history and should not change. The device is still out there, and a serial number typed wrongly during picking has to be correctable, otherwise every later exchange refers to the wrong unit.

## Completed is not the end of the service

The distinction worth holding on to.

The **position** is finished. Your work on that order is done.

The **service instance** carries on. It runs for its term, it is billed every month, and it can be exchanged, stored, returned or cancelled. Each of those creates a position of its own, which appears back in [Open positions](/documentation/fulfillment/open-positions.md) or in [Changes](/documentation/fulfillment/changes.md).

So a service running for two years may have several completed positions behind it: the original delivery, an exchange, a change of location. Read together, they are its history. Read alone, any one of them is misleading.

## Where to look instead

| You are looking for             | Go to                                            |
| ------------------------------- | ------------------------------------------------ |
| What a customer currently holds | Sales, the customer, Active services             |
| The state of a single device    | Operations, Service instances                    |
| A cancelled order               | Cancellations                                    |
| An exchange in progress         | [Changes](/documentation/fulfillment/changes.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 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/documentation/fulfillment/completed-positions.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.