> 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/incident-reports.md).
# Incident reports
Use the incident report to record a crash or incident at a worksite, following the CoPTTM incident report. The form is set out in steps; use **Next** and **Back** to move between them. Tap **?** next to any field for help with what to enter.
## Before you start
You'll need to attach:
* a photo of the **Hazard ID form** being used by the working space contractor at the time of the incident
* **photos of the worksite layout** showing all TTM equipment installed at the time
Use the camera button at the top of the form to add them.
The incident report guidelines
## The steps
1. **Incident details**: the date and time of the incident (or tick **No-one on-site to record time of incident**) and the company.
2. **People involved**: the STMS name and STMS number, the contractor/TTM company and a contact number.
3. **Location & work**: the road location (including direction and lane) and a description of the work being done.
4. **Checklists**: mark each item that applies.
5. **Injuries & crash details**: injuries to road workers and road users (**Minor**, **Notifiable** or **Fatal**), the crash code (download *CoPTTM Incident Report Appendix 1* from the form for the codes), the vehicle/road user type and the registration number.
6. **TMA & police**: which TMA was hit (if any) and in which lane, whether police attended, and any further information.
7. **Description of events**: what happened.
8. **Crash diagram**: draw the worksite layout, showing all TTM equipment and the position of the vehicles and road users involved. **Reset diagram** starts again. You can also attach a photo of a drawing instead.
9. **Review**: check the summary. Anything missing is marked **Required field not completed**. Tap **Save**.
## After you save
A copy of the report, with the drawing and photos, is emailed to the address saved in your settings. Before you submit the report, attach:
* a copy of the TMP being used at the time
* a copy of the on-site record being used at the time
Then send it to **** and the RCA in charge of the network (including NZTA for state highways).
---
# 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/incident-reports.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.
