> For the complete documentation index, see [llms.txt](https://bikecheck.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bikecheck.gitbook.io/guide/riders/drop-off-and-collect.md).

# Drop off and collect your bike

The handover at the counter uses two one-time codes, so the record shows exactly when the bike changed hands.

## Drop-off: your check-in code

1. Go to the shop on the agreed day.
2. On your **Dashboard**, open the booking card in **Waiting check-in**.
3. The card shows an **8-digit check-in code**. Read it to the shop.
4. The shop types it in. The booking moves to **Open**, and the bike shows *In progress* in your garage.

![Lena's check-in code for Radwerk Bergmann](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-b054703326fec6d15501e9911c6a1593dcc18a15%2Frider-checkin-code.jpg?alt=media)

{% hint style="info" %}
A code works once and expires after 10 minutes. If it expires, the card simply shows a new one.
{% endhint %}

While the bike is at the shop, you can follow each job on the booking card: every part and service, its status (*Open*, *In progress*, *Done*), and who is working on it. If the shop has to move the completion date, you get a notification with the reason.

![A booking in progress, with its two jobs](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-9c52b780999a8076ca05e2d0d203b8ccc8fc7f59%2Fbooking-in-progress.jpg?alt=media)

## Collect: the shop's check-out code

1. When every job is done, the booking moves to **Waiting check-out** and you are notified.
2. At the shop, ask for the **check-out code**. The shop's screen shows it.
3. Open the booking card, type the 8-digit code under **Check out**, and press **Check out**.

![Entering the shop's check-out code](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-f9f46a1fa97f980442f220400db541001e9446de%2Frider-checkout-enter.jpg?alt=media)

The booking is completed, the bike is back in your custody, and every job is written into the bike's log — including new parts, torques the mechanic used on your bolts, and the bike's weight if it was weighed.

Next: [Rate the service](/guide/riders/rate-a-service.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://bikecheck.gitbook.io/guide/riders/drop-off-and-collect.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.