> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Investigations

> Track formal workplace investigations — create, view details with documents and timeline, and edit investigation records.

The Investigations page, at route `/hr/employee-relations/investigations`, lists all formal workplace investigations and lets you open new ones.

## Overview

The Investigations list displays each investigation's type (Incident, Grievance, Disciplinary, or Other), its status (Open, In Progress, Completed, or Closed), the opened date, the assigned reviewer, and a link to the source record when one exists. Filters for type and status narrow the list. Selecting an investigation opens its detail view. The **New Investigation** button navigates to `/hr/employee-relations/investigations/new`.

## Who it's for

Access follows your organization's role and module configuration.

## Before you start

* The source incident, grievance, or disciplinary record (if any) should already exist in Employee Relations.
* You need enough role access to view Employee Relations pages.

## Steps

1. Go to **HR → Employee Relations → Investigations**.
2. Optionally filter by **Type** or **Status** to narrow results.
3. Select **View Details** on any investigation row to open the detail page.
4. To open a new investigation, select **New Investigation** and complete the form.

## Key concepts

| Concept            | Meaning                                                                                                                              |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
| Source link        | An investigation may be linked to an originating incident, grievance, or disciplinary record. The list shows this link when present. |
| Status             | Open → In Progress → Completed → Closed (aligned with database CHECK constraints).                                                   |
| Investigation type | Incident, Grievance, Disciplinary, or Other.                                                                                         |

## Viewing an investigation

The Investigation Details page (`/hr/employee-relations/investigations/:id`) displays the full record for a single ER investigation, including type, status, dates, investigator, linked incidents, and documents, with edit and action options.

The page uses `useInvestigationDetail` to load by `:id` and sets a breadcrumb. A status badge is shown (secondary for `open`, default for `in_progress`, outline for `completed`/`closed`). Tabs include case details, linked incidents, a `CaseDocuments` component, and timeline. Organization context is available. A `PermissionGate` controls which actions are shown. An **Edit** button navigates to the edit form.

Before you start: the investigation record must exist in your organization.

1. Navigate to **HR → Employee Relations → Investigations** and click a row, or go to `/hr/employee-relations/investigations/:id`.
2. Review the status, type, dates, and investigator assignment.
3. Switch to the **Documents** tab to review attached files.
4. Click **Edit** to update the investigation record.

**Key detail concepts:**

| Concept              | Meaning                                    |
| -------------------- | ------------------------------------------ |
| Status `in_progress` | Investigation is actively being conducted  |
| Status `completed`   | Investigation concluded; findings recorded |
| Status `closed`      | Case administratively closed               |

## Creating an investigation

The New Investigation page renders `InvestigationFormPage` in create mode and is available at `/hr/employee-relations/investigations/new`. On successful submission the user is returned to the investigations list. Investigation records are sensitive employee relations data.

Before you start: gather all available information about the matter being investigated before opening the form. Confirm that the involved employees' records exist in the system.

1. Navigate to `/hr/employee-relations/investigations/new` or choose **New Investigation** from the investigations list.
2. Complete the required form fields.
3. Submit; on success you will be returned to the investigations list.

**Key concept:** An **Investigation** is a formal HR process to examine a workplace allegation, incident, or policy concern.

## Editing an investigation

The Edit Investigation page provides a form for updating an existing investigation record. It is available at route `/hr/employee-relations/investigations/:id/edit`. The route renders `InvestigationFormPage` in edit mode (because the `id` param is present). The existing record is fetched via `useInvestigationDetail`. Source fields (`source_incident_id`, `source_grievance_id`, `source_disciplinary_id`) are cleaned based on the `source_type` UI field before submission. On submit, `updateMutation.mutateAsync` is called.

Before you start: navigate from an investigation detail page at `/hr/employee-relations/investigations/:id`.

1. From an investigation detail page, click the edit action. You land on `/hr/employee-relations/investigations/:id/edit`.
2. Update investigation type, status, assigned to, dates, findings, conclusions, or recommendations.
3. Submit the form. On success, you are redirected to the detail page.

## Related

<Columns cols={2}>
  <Card title="Human Resources" icon="users" href="/hr/overview">
    Human Resources core overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/hr/employee-relations-routes.tsx
  * src/cores/hr/employee-relations/pages/InvestigationListPage.tsx
  * src/cores/hr/employee-relations/pages/InvestigationDetailPage.tsx
  * src/cores/hr/employee-relations/pages/InvestigationFormPage.tsx
  * src/cores/hr/employee-relations/hooks/useInvestigationList.ts
  * src/cores/hr/employee-relations/hooks/useInvestigationDetail.ts
  * src/cores/hr/employee-relations/hooks/useInvestigationMutation.ts
  * src/cores/hr/employee-relations/types/index.ts
</Accordion>
