> 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/on-site-records.md).

# On-site records

On-site records (OSRs) are the CoPTTM records you complete on site. They're sent to eBoard, where the office can see them against the job.

## Record types

**Static sites**

* [Toolbox briefings](/mobile-app/on-site-records/toolbox-briefings.md)
* [Site inspections](/mobile-app/on-site-records/site-inspections.md)
* [Temporary speed limits (TSLs)](/mobile-app/on-site-records/temporary-speed-limits.md)
* [Site handovers and delegations](/mobile-app/on-site-records/site-handovers.md)

**Mobile and semi-static sites**

* [Pre-start checks](/mobile-app/on-site-records/pre-start-checks.md)
* [Operation records](/mobile-app/on-site-records/operation-records.md)
* [Site checks](/mobile-app/on-site-records/site-checks.md)

**General**

* [Incident reports](/mobile-app/on-site-records/incident-reports.md)
* [Site audits (SCR)](/mobile-app/on-site-records/site-audits.md)
* [Generic TMP checks](/mobile-app/on-site-records/generic-tmp-checks.md)
* [Vehicle checks](/mobile-app/on-site-records/vehicle-checks.md)

## Adding a record

You can add a record two ways:

* **From a job** (recommended): open the job, tap **Onsite Records**, then the **Add** option for the record. The record is linked to that job and day automatically.
* **From the main menu**: tap the round button in the bottom bar, then the **Add** option. If you don't have a job open, choose the job the record is for first.

<figure><img src="https://4286947481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F98XhbhrRRLsZR32fcYPt%2Fuploads%2Fgit-blob-f459102acc12113bcd7c3fe72050c66d8af90ed3%2Fmobile-onsite-records-menu.png?alt=media" alt="The Onsite Records menu on a job" width="300"><figcaption><p>The Onsite Records menu on a job</p></figcaption></figure>

Every record:

* is stamped with your name and the date and time
* records your GPS location where your phone allows it. The location icon at the top shows whether a location was found; tap it to see it on a map.
* can have photos. Tap the camera icon at the top to take or choose a photo, and the gallery icon to view them.

Checklist items start as **No**: tap each one that applies. When you're done, tap **Save**. If you try to leave a record you've started, the app asks you to confirm first.

Records can't be changed once saved.

## Viewing records

Use the **View** option for the record type. Opened from a job, the list shows only that job's records; from the main menu, it shows them all. Each record shows when it was recorded and the road name. **Not sent yet** means it's saved on the device and will be sent when there's a connection (see [Working offline and syncing](/mobile-app/offline-and-sync.md)).

Tap a record to open it read-only.

On the [Calendar](/mobile-app/calendar.md), each job card shows whether a toolbox briefing, site inspections and a site audit have been done that day.


---

# 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/on-site-records.md?ask=<question>&goal=<user_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.
