> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/mobile-app/working-offline.md).

# Working Offline

Taskmaverick lets employees [claim and complete Missions](/mobile-app/perform-a-mission.md) on Team Boards without an internet connection. Work is saved locally and syncs automatically when the device goes back online.

## Why Offline Mode matters

Not every workplace has reliable Wi-Fi. Basements, warehouses, rural locations, construction sites — employees need to keep working even when connectivity drops. Offline Mode ensures that a lost signal doesn't mean lost productivity.

## How it works

### Before going offline

When an employee signs in and navigates to a [Team Board](/mobile-app/your-mobile-boards.md#team-board) while online, the app **caches** that board's Missions and navigation path. This cached data is what makes offline work possible — so employees should open their boards at least once while connected.

### While offline

* An **offline icon** appears on every screen to indicate there's no connection
* Action buttons change to **"Claim - Offline"**, **"Close - Offline"**, and **"Continue - Offline"**
* The employee can claim Missions, work through questions, attach [photos and videos](/mobile-app/perform-a-mission.md#photo-and-video-proof), and close Missions — all as usual
* Completed work is stored locally on the device

### When back online

* The app **automatically syncs** all offline work with the server
* Points are awarded, ratings become available, and any Tickets or follow-up Missions are triggered
* Buttons revert to their normal labels, and the offline icon disappears

## What works offline

* **All** [**Mission types**](/missions/what-are-missions.md#mission-types-at-a-glance)**:** Task, Survey, Checklist, Media, Test, and Audit
* **Photo and video proof:** can be captured and attached while offline
* **Mission Settings that apply after sync:** Rating, Points, Ticket on Response, Ticket on Test Score, Ticket on Long/Short Claim Duration, Media on wrong answer, Claimed Duration alerts
* **Process Activities:** if the Mission is part of a Process, the Process continues after sync
* **Question Feedback and Skip Steps** ([Test/Audit settings](/missions/how-to-guides/configure-mission-settings.md#test-and-audit-specific)) work normally offline

## What doesn't work offline

<table><thead><tr><th width="317.3333740234375">Feature</th><th>Why</th></tr></thead><tbody><tr><td><strong>Boost Mission on Timer</strong></td><td>Requires server-side timer evaluation</td></tr><tr><td><strong>Auto-Bounce Back</strong></td><td>Requires server-side timer evaluation</td></tr><tr><td><strong>Show Score After Completion</strong> (Test/Audit)</td><td>Score is calculated and displayed after sync, not during offline completion</td></tr><tr><td><strong>Time Restriction to Complete Test</strong></td><td>Not enforced offline</td></tr><tr><td><strong>Notify About Related Media</strong> (Test)</td><td>Notification appears after sync</td></tr><tr><td><strong>Personal Board</strong></td><td>Not cached for offline use</td></tr><tr><td><strong>Ticket Board</strong></td><td>Not cached for offline use</td></tr></tbody></table>

## What happens when two people complete the same Mission offline

In team environments, multiple employees might claim the same Mission while offline. Taskmaverick handles this with a simple rule: **the first version to sync wins**.

* The first-synced version becomes the **primary version** — it goes to [Reporting](/analytics-and-monitoring/reporting.md), appears in the Closed column, and triggers any configured [Tickets](/missions/what-are-missions/ticket.md) or follow-ups
* Any later-synced versions become **secondary versions** — they're kept for history but don't trigger Tickets or affect reports
* Secondary versions are visible in the Mission details on mobile and in [Overview → History](/analytics-and-monitoring/overview/review-mission-history.md) on the web, so managers can review all responses

### Specific scenarios

* **Online user closes first, offline user syncs later** → online version is primary
* **Offline user syncs first, online user hasn't closed yet** → offline version is primary
* **Two offline users** → whoever syncs first is primary
* **Mission is canceled while a user is offline** → the cancellation takes priority; the offline work is discarded
* **Mission is bounced back while a user is offline, then the offline user syncs** → the offline user's completed version is accepted

## For managers: reviewing offline data

In [**Overview → Team Board → History**](/analytics-and-monitoring/overview/review-mission-history.md), a column called **"Offline Sync Data"** shows how many offline versions exist for each Mission instance. Filter by "Yes" to see only Missions that were completed offline.

The exported Excel file includes additional fields: sync timestamp, whether the version was fully completed or only claimed, and whether it's the primary (considered in reports) or secondary version.

## Good to know

* Offline Mode works on **Team Boards and Personal only** — Ticket Boards require an online connection
* Boards must be **visited while online** before they're available offline (the app needs to cache the data)
* When the device goes online, sync happens **automatically** — no manual action needed
* Only the **primary version** of a Mission appears in [Reporting](/analytics-and-monitoring/reporting.md) — secondary versions are historical records only


---

# 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://documentation.taskmaverick.com/mobile-app/working-offline.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.