> 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/field-reports.md).
# Create a Field Report on Site
A field report collects everything from a site visit in one place: your observations with photos, the site conditions, and the details your firm's report format asks for. You create it on your phone during the visit, finalize it when you are done, and download the finished Word document from the web afterward.
## Starting a report
To start one:
1. On the **Home** tab, tap **Start Field Report**.
2. Enter a report title, pick the **Project**, and pick the **Report Type**. The Report Type decides which details the form asks for; your admin sets these up under [Report Types](/administration/report-types.md).
3. Tap **Start Report**.
The report editor opens. Everything you enter is saved on your phone as you go, so losing signal never loses work.
## Adding observations
A report is built from observations: individual findings, each with its own notes and photos. In the report editor:
* Tap **Add Observation** to capture a new one. See [Capture Observations](/guides/observations.md) for the full flow.
* Tap **Link Existing** to pull in observations you captured earlier, for example with **Quick Observation** while walking the site.
Swipe an observation to remove it from the report.
The report editor. Everything keeps working offline.
## Filling in the report details
Below the observations, the form shows the fields your Report Type asks for, like the client firm or persons present. Required fields are marked with `*`. Table fields, like an attendance list, take one row per entry: tap the add row button, fill in the columns, and tap **Save**.
The report also records the site location and pulls the weather for it automatically.
## Finalizing the report
When the visit is done, tap **Finalize Report**. Finalizing uploads the report and makes it available to your team.
If the button is not available, the editor tells you exactly what is missing, for example "Add an observation to start", "Each observation needs a type and status", or "Complete required field: Client Firm". Fix what it names and finalize again.
{% hint style="info" %}
A report you back out of stays as a **Draft** on the Reports tab. Drafts live only on your phone and do not upload until you finalize them. Tap a draft to pick up where you left off.
{% endhint %}
If an admin changed the Report Type while you were drafting, the app shows "Report template was updated" and lists any new required fields. Tap **Review form**, fill in what is new, and finalize.
## After finalizing
The report uploads and shows **Uploaded** once it is safely on the server (see [Working Offline](/guides/working-offline.md) for what the statuses mean). From then on:
* On your phone, open the report to review its details, weather, observations, and Cogram's summary of the findings.
A finalized report on your phone
\- On the web, open the report and click \*\*Download\*\* to export it as a Word document in your firm's layout. See \[Field on the Web]\(field-on-the-web.md) for the full review and export workflow.
Exporting is a web feature. The mobile report page points you to the web app for the full details.
## Deleting a report
The trash icon in the report editor deletes the report and all of its observations and photos permanently. There is no undo.
## Related
* [Capture Observations](/guides/observations.md): notes, dictation, photos, and drawing pins.
* [Working Offline](/guides/working-offline.md): drafts, upload statuses, and weak-signal behavior.
* [Report Types](/administration/report-types.md): how admins set up the report forms and export layouts.
---
# 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/field-reports.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.