> 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/log-self-service.md).

# Log work you did yourself

Did you change a chain, fit new tyres or bleed the brakes yourself? Log it, so the bike's history stays complete.

## Steps

1. Open your bike's page and choose **Service**.
2. Slide the **Who does the work** switch to **Self-service**.
3. For each row, pick the **part**, then under **Work done** what you did:
   * **Install** — fit a part that wasn't there; enter its brand, model and colour.
   * **Replace** — swap a part for a new one; enter the new part's brand, model and colour.
   * **Remove** — take a part off.
   * **Service** — any other work; give it a short title and description.
4. To weigh the bike, pick **Bike** as the part and enter the weight in kg.
5. Use **Add part** for more rows, set the date, and choose **Add to log**.

Install, Replace and Remove update the bike's parts list straight away. Everything is written into the bike's log, framed yellow as owner work.

{% hint style="info" %}
Self-service entries are your own statement. Work done by a shop is recorded by the shop and carries more weight with a future buyer.
{% endhint %}


---

# 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/log-self-service.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.