> 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/investigations/detective-sop.md).

# Detective and Investigator SOP

**Resource baseline:** `nwrrp_ers_investigations` v0.6.3-beta.1

## Mission

Process ERS scenes, conduct witness interviews, follow investigative leads, preserve physical evidence, and record findings in the correct DOJ case.

## Readiness

* Fully loaded QBCore character
* Recognized law-enforcement job
* Active ERS police service and shift for live assignments
* Detective authorization
* Availability enabled in `/investigations`

## Standard lifecycle

1. Open `/investigations` and set availability.
2. Accept the detective ERS assignment.
3. Respond and secure the scene.
4. Use Third Eye on the assigned subject and select **Begin Scene Investigation**.
5. Select the correct DOJ case, or use unassigned evidence only when necessary.
6. Process each objective through Third Eye.
7. Save clear findings and notes.
8. Use **Conclude Investigation** after all required objectives are complete.
9. Verify ERS success and the resulting evidence/interview/lead record.

## Crime-scene objectives

Typical target options include:

* **Examine Deceased**
* **Collect Blood Sample**
* **Collect Trace Evidence**
* **Conclude Investigation**

Follow the routed objective and use Third Eye on the target zone. The ERS yellow arrow over the subject is not an evidence objective.

## Witness interviews

Use Third Eye on the assigned witness and select **Conduct Witness Interview**. Link the correct DOJ case, ask relevant questions, add concise detective notes, and confirm the saved interview and any generated lead.

## Follow-up leads

Open **Leads & Assignments**, review and accept the lead, launch the ERS callout while on shift, respond to the contact, and select **Process Investigative Lead** through Third Eye. Record facts supporting a confirmed, disproven, or exhausted result.

## Documentation standard

Separate direct observations from witness statements. Document location, condition, actions, timeline, and evidence with enough detail for another investigator to continue the case.

## Recovery

Use `/clearinvestigation` for stuck targets, routes, props, UI focus, or active state. `/processevidence` is a recovery fallback, not the routine interaction method.


---

# 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/investigations/detective-sop.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.