> 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/report-a-stolen-bike.md).

# Report a stolen bike

A stolen flag marks the bike on its public record and blocks transfers and sales until it is resolved. Anyone who looks the bike up — a shop at check-in, a buyer on the marketplace — sees it.

## Raise the flag

1. Open the bike's page and choose **Flag stolen**.
2. Under **What happened**, describe where and how the bike was taken (at least 10 characters).
3. Add the **location** and, if you have one, the **police reference** (the crime or report number). Both are optional, but a police reference strengthens the record.
4. Add photos as evidence if you have them.
5. Choose **Flag as stolen**.

People connected to the bike are notified, and you get an email confirmation. You need a verified identity to raise a flag.

{% hint style="info" %}
Only whoever has the bike at the time can flag it: you, while the bike is with you; the shop, while the bike is checked in there.
{% endhint %}

## Add a police reference later

Open the bike's page, choose **Resolve flag**, and add the police reference and the issuing authority.

## The bike is back

Open the bike's page and choose **Resolve flag**:

* **Clear the flag** if the bike was recovered. Say how in **Outcome**.
* **Retract the flag** if it was a mistake.

Confirm your password. The transfer block is lifted. Only the person who raised the flag can clear or retract it.


---

# 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/report-a-stolen-bike.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.