> For the complete documentation index, see [llms.txt](https://wiki.roaddirect.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.roaddirect.co.nz/eboard/settings/vehicle-checks.md). # Vehicle checks Vehicle checks are the items staff work through when they do a pre-start check of a vehicle in the Road Direct mobile app (for example brake lights, attenuator operation, tyre pressure and mirrors). To open it, go to **Settings** → **Vehicle Checks - Mobile App**. You can also get there from the **Go to Vehicle Check Settings** button on the [Vehicles](/eboard/resources/vehicles.md) page. ## Manage the check list * Click **Add New Check** to add an item to the list. * Click **Edit Checks** to rename, reorder or remove existing items. The page also has shortcuts to **Go to Vehicles**, **Go to Vehicle Scheduler**, and **Get the Mobile App here**. To see the pre-start checks recorded for a particular vehicle, use **Pre-start Checks** from that vehicle's ⋮ menu on the [Vehicles](/eboard/resources/vehicles.md) page. --- # 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://wiki.roaddirect.co.nz/eboard/settings/vehicle-checks.md?ask=&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.