Skip to main content

Case Import Field Reference Guide

A reference guide for all fields supported in the Case Importer CSV, including descriptions, formats, and validation rules.

Reka Lakatos avatar
Written by Reka Lakatos
Updated over a month ago

Field name in import

Description

Validation rules

Example values

Case categories (required)

Main category or categories associated with the case.

Multiple values separated by semicolons(;).

Must match categories configured in Vault.

"Harassment"; "Code of Conduct"

Case status (required)

The current status of the case.

Only accepted value: "Closed"

"CLOSED"

Event description (required)

Summary of the incident or event.

We recommend using this field to capture any additional details that do not fit into other available Vault fields by mapping those fields to the ‘Event description’.

Must be a string of text.

"Employee reported inappropriate comments…"

Reporter Anonymous (required)

Indicates if reporter details are redacted.

Must be TRUE or FALSE.

TRUE

Submission date (required)

Date the report was submitted.

Valid date format dd/mm/yyyy.

01/12/2024

Substantiation status (required)

Outcome of the investigation.

Must be: Undetermined, Unsubstantiated, Partially-substantiated, or Substantiated.

"Unsubstantiated"

Original case ID

Legacy case ID from prior system.

This ID will be retained, and a new Vault system ID will also be assigned.

Must be a string.

"NAVEX-2021-0045"

Case lead EID

Employee ID of case lead.

Must match user in Vault; if email also provided, both must match same user.

"E12345"

Case lead email

Email of the case lead.

Must match user in Vault.

Case lead name

Name of the case lead.

Not a unique identifier; cannot match user alone.

"Alex Chen"

Case name

Title or summary of the case.

Must be a string.

"Allegations of Misconduct"

Closed date

Date case was marked closed.

Must be ≥ submission, created, investigated dates.

Format: dd/mm/yyyy

02/10/2024

Created date

Date case was created.

Must be ≥ submission date; if empty falls back to submission date.

Format: dd/mm/yyyy

01/12/2024

Event date

Date incident occurred.

Format: dd/mm/yyyy

01/10/2024

Event time

Time incident occurred.

HH:mm 24-hour format.

14:30

Event emotional impact

Emotional or psychological impact notes.

Must be a string.

"Reporter experienced stress…"

Event location

Where the incident occurred.

Must be a string.

"Berlin Office"

Event witnesses

Individuals who witnessed or were told about the incident.

String; names separated by semicolons(;).

"John Doe; Alice Smith"

Investigating date

Date investigation began.

Must be ≥ submission & created; ≤ closed; fallback: submission date.

01/03/2024

Name offender EID

Employee ID(s) of accused individuals.

Must match user(s) in Vault; semicolon-separated(;).

"E5678; E9876"

Name offender email

Email(s) of accused individuals.

Must match user(s) in Vault; semicolon-separated(;).

Name offender name

Name(s) of accused individuals.

Not a unique identifier. Names separated by semicolons(;).

"John Doe; Jane Doe"

Original intake method

How report was submitted in legacy system.

Retained as "Source" on report level.

Must be a string.

"Hotline"

Reporter EID

Employee ID of reporter.

Must match user in Vault or creates user.

"E11223"

Reporter Email

Email of reporter.

Must match user in Vault or creates user.

Reporter Name

Name of the reporter.

Not a unique identifier.

"Maria Gomez"

Did this answer your question?