> For the complete documentation index, see [llms.txt](https://docs.nwrrp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nwrrp.com/getting-started/emergency-services.md).

# Emergency Services Guide

## Start of shift

1. Use `/roster` to open FiveRoster.
2. Go on duty in the roster/tablet workflow.
3. Equip the correct uniform and approved equipment.
4. Open Imperial CAD and set the correct status.
5. Join the appropriate radio channel.
6. Log into the correct ERS service and begin the ERS shift.

## Shared controls

* **Third Eye (`R-ALT`)** — world interactions, patients, witnesses, evidence, and scene objectives.
* **`Y` / `N`** — accept or decline a nearby ERS crew invitation.
* **`Escape`** — close the focused NUI.
* **Radio push-to-talk** — configured in FiveM; verify it before starting duty.

## Law enforcement

Use Imperial CAD for reports, citations, arrests, records checks, and dispatch. Use `/doj` only for the DOJ workspace appropriate to your permissions. Arrest and citation workflows remain tied to the correct subject and official Imperial report reference.

## Fire and EMS

MedicBridge patient treatment now opens through Third Eye on the correct patient by selecting **Treat ERS Patient**. F4 is not the normal MedicBridge control in the current build.

## Technical issues

Use `/report` for staff assistance. Include the resource, call type, action attempted, and an F8 or server-console error when available.


---

# 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.nwrrp.com/getting-started/emergency-services.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.