> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/driver-app/orders/check-in-process/check-in-settings.md).

# Check-In Settings

{% hint style="info" %}
These settings are configurable through the support team.
{% endhint %}

There are two configurable settings that determine when a driver can mark themselves as **Ready** in the app:

## Check-In Distance

* This setting defines **how close the driver must be to the venue** before they are allowed to check in.
* The distance is configured in **metres** (e.g., 100m).
* This ensures that a driver can only mark themselves as waiting once they are **physically near the venue**.

## Check-In Frequency

* This setting controls **how often a driver is allowed to check in** (e.g., once every 10 minutes).
* It prevents drivers from repeatedly ending their shift and checking in again in order to reset their waiting time.
* The frequency rule helps maintain **fairness** by ensuring that the driver who has genuinely been waiting the longest is prioritised for the next order.
* The interval can be customised (e.g., set to 10 minutes,  set to 15 minutes, or another suitable duration).


---

# 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://docs.bossithq.com/driver-app/orders/check-in-process/check-in-settings.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.