> 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/mobile-app/offline-and-sync.md). # Working offline and syncing The app is built for sites with poor or no signal. Once you've opened it with a connection, you can keep using it offline: the Calendar, jobs, forms and lists your organisation has set up are all stored on the device. ## What happens when you save offline When you save something without a connection (a task time, an equipment update, a note, an on-site record or a photo), it's kept on the device and sent automatically when you're back online. Until then: * a **sync badge** (a cloud with a number) appears in the top bar, showing how many changes are waiting * records you've saved show **Not sent yet** in their list ## Waiting to sync Tap the sync badge, or your name → **Waiting to sync**, to see each change that's waiting, when you saved it and how many times the app has tried to send it. * **Send now**: try to send everything straight away. * **Retry**: try again to send a change that failed. * **Discard**: throw a change away. Only do this if you're sure you don't need it. If a change has failed, the badge turns red. Open **Waiting to sync** to see why. If your login has expired, you'll see **Your session has expired. Log in again to send these**. Tap **Log in**. Your changes stay on the device until you do. {% hint style="warning" %} **Logout** and **Reset Data** clear everything stored on the device, including changes that haven't been sent. The app warns you first. Send your changes before you log out. {% endhint %} ## Shared devices If several people share a phone or tablet, each person should log out when they finish. Logging out clears that person's data and anything waiting to sync, so the next person never sees 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://wiki.roaddirect.co.nz/mobile-app/offline-and-sync.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.