> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/guides/working-offline.md).
# Working Offline
Job sites have bad signal. The Cogram mobile app is built for that: everything you capture is saved on your phone first and uploaded when a connection is available. This page explains what works offline, what the statuses mean, and the one habit that keeps your work safe.
## What works without signal
* Capturing observations, photos, and notes: fully.
* Creating and finalizing field reports: fully. They upload once you are back online.
* Recording in-person meetings: fully. The recording uploads later.
* Viewing drawings: only the ones you downloaded beforehand. See [Drawings](/guides/drawings.md) for downloading sets before you head out.
When the app is offline it shows a banner: "Your device is offline. New data will be uploaded for processing once you're online." Keep working; nothing is lost.
Offline on site: the banner shows, and everything keeps working
## What the statuses mean
Reports, observations, and meetings show a status badge:
| Status | Meaning |
| ---------------- | ------------------------------------------------------------------------------------- |
| Draft | Still being edited, only on your phone. Drafts do not upload until you finalize them. |
| Awaiting Upload | Finalized and queued. It uploads at the next opportunity. |
| Uploading | On its way to the server right now. |
| Uploaded | Safely on the server and visible to your team. |
| Failed to Upload | The upload hit a problem. The app keeps retrying on its own. |
| Processing | (Meetings) uploaded, and Cogram is writing the summary and notes. |
Uploads run automatically: when you finalize, about every minute in the background, and whenever the connection comes back. Pull down on any list to refresh it.
{% hint style="warning" %}
A **Draft** never uploads. Before you wipe the app, switch phones, or hand a device back, check that nothing on the Reports or Observations tabs says **Draft** or **Awaiting Upload**.
{% endhint %}
## If an upload keeps failing
The app retries failed uploads on its own, so **Failed to Upload** usually resolves itself once you have a solid connection. If it persists, open the item and use **Copy Error Details** to send the details to your admin or to .
Two cases cannot be retried, and the app says so: the item was deleted from another device, or the recording's audio file is no longer on the phone.
## Logging out with unsynced work
If you log out while items are still waiting to upload, the app warns you: they stay on the device and finish uploading after you sign back in. They are not lost, but they are also not on the server yet, so finish the upload before deleting the app or resetting the phone.
## Before you leave the office
A 30-second checklist for a site day with poor signal:
1. Open the app and sign in while you still have connection.
2. On the **Drawings** tab, download the drawing sets you will need.
3. Confirm yesterday's work shows **Uploaded**, not **Awaiting Upload**.
## Related
* [Drawings](/guides/drawings.md): downloading drawing sets for offline use.
* [Create a Field Report on Site](/guides/field-reports.md): drafts, finalizing, and what happens after.
* [Cogram on Your Phone](/guides/mobile-app.md): signing in and finding your way around.
---
# 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.cogram.com/guides/working-offline.md?ask=&goal=
```
`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.