> 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/shop-staff/kanban-board.md).

# Mechanics: the Kanban board

The **Kanban** board is where the work happens. Each card is one job on one bike — a part and a service, for example *Rear Derailleur · Drivetrain service*.

![The Kanban board as Jonas, a mechanic, sees it](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-ca032ef44a300c8a55e3a101a451b368a1465eed%2Fkanban-mechanic.jpg?alt=media)

Work flows left to right: **Open → In progress → Done**. A job only appears once the bike has been checked in.

## Read a card

* The frame colour tells you the bike class: green bike, blue e-bike, red cargo, pale green scooter, pale blue e-scooter.
* The card shows the part and service, the customer's contact details, the part fitted now, and the **due date** — red when it is overdue.
* **HighPrio** marks an urgent booking.

## Pick up a job

1. In **Open**, press **Assign to me** on a card. Your name appears on it; it stays in Open.
2. Choose **Move to In progress** when you start.

![Jonas has assigned the job to himself](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-90f1744124d07a6d3394587aa2f0ce02d28127a3%2Fkanban-assigned.jpg?alt=media)

3. When you finish, choose **Move to Done**. The card is struck through and dated. Moved it too early? **Back to open** undoes it.

![The finished job in Done](https://3342305839-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUV849rO8Um1JqzscvFEf%2Fuploads%2Fgit-blob-19b6fcb20cda1ea2b691b3bee4257f72119d8a15%2Fkanban-done.jpg?alt=media)

The owner and receptionists can also put a mechanic on a job with **Add mechanic…**. The owner can pick **Me** there to take the job themselves, once the owner's name is set in **Business details**. More than one mechanic can share a job, each with their own time and cost (**Edit** next to their name).

## Jobs that need a value before Done

* **Bolts** — if the owner has a bolt setup for the part, the card lists each bolt with the manufacturer's and the owner's recommended torque. Enter the torque you actually used for every bolt (comma for decimals, up to 99,9). The owner sees them in the bike's log.
* **Weight the bike** — enter what the scale reads, in kg. At check-out it becomes the bike's weight.
* **Replace**, **Install** — enter the new part's brand, model and colour; at check-out the bike's parts list is updated.

## The deadline

The due date comes from the estimated check-out agreed with the customer. If it has to move, press **Edit** next to the due date, set the **new deadline** and give a reason (5 to 30 characters). The customer is notified with your text.

When every job on a booking is **Done**, the front desk can check the bike out.


---

# 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/shop-staff/kanban-board.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.