> For the complete documentation index, see [llms.txt](https://docs.incident-tracker.com/llms.txt). Every page is available as Markdown by appending `.md` to its URL.

# Tracking Unidentified Individuals

How library staff document repeat incidents involving people whose names aren't known, connect them with an alias, and share records with law enforcement.

Source: https://docs.incident-tracker.com/admin-guide/misc/tracking-unidentified-individuals  
Last updated: 2026-11-10

Staff use a standard alias for people whose names aren't known, so repeat incidents can be connected in Incident Tracker and shared with law enforcement when the library chooses or is required to.

| Role            | Responsibility                                                                                    |
| --------------- | ------------------------------------------------------------------------------------------------- |
| Frontline staff | File incident reports with a person description and photos                                        |
| Security lead   | Assign aliases, maintain Person of Interest Profiles, and handle any sharing with law enforcement |

> **Note**
>
> Values in [brackets] are set by your library.

> **Tip**
>
> **One report per incident, one profile per person.** File a separate report for every incident. Each alias also gets one Person of Interest Profile, which holds the reference photos and a running list of the linked reports. Separate incident reports keep accurate dates, locations, and authors for search and analytics, trigger your workflows and notifications, and make it easier to share and redact only what's needed.

---

## Filing a report (frontline staff)

File the report as usual, then add the person and their description so the security lead can connect it to other incidents. See [Submit Report](https://docs.incident-tracker.com/user-guide/submit-report).

1. Complete the date, location, category, and write-up as you normally would.
2. In **People & Witnesses**, add the person:
   * If you know their alias (for example, from the [Banned List](https://docs.incident-tracker.com/admin-guide/misc/banned-list) or a coworker), enter it as the name exactly as written, such as `UNK-0042`.
   * If you don't know it, enter `Unknown` as the name. The security lead will assign or match an alias.
3. Complete the **Person Description** form: the dropdowns for age range, height, build, and hair, a checkbox for each location and type of distinguishing feature, and a short description of those features, clothing, and items carried.
4. Describe behavior and distinguishing features. Don't rely on race or ethnicity alone to describe someone.
5. Attach photos or video, uploading the original files without cropping or editing.

> **Warning**
>
> **Attach files at the right time.**
>
> * **Web:** attach files on the confirmation screen before you leave it.
> * **Mobile:** attach files before you submit.
>
> After that, you can add files only if you can view the report and have **Append Rights** (included in Edit Rights).

---

## Assigning aliases (security lead)

The security lead reviews reports with an `Unknown` person at least [weekly] and either matches them to an existing alias or assigns a new one.

1. In **Reports and Analytics > Reports > [Advanced Search](https://docs.incident-tracker.com/user-guide/reports-and-analytics/advanced-search)**, filter **People / Witnesses** for `Unknown`. Save this as a search to reuse.
2. Look for possible matches with **Form Fields** on the Person Description form (for example, tattoo + left arm), plus location and date range.
3. **Match found:** edit the report and replace `Unknown` with the alias. Then append a note on the matching Person of Interest Profile: _Linked to report #\_\_\_\_, [location], [date]._
4. **No match, and the person is likely to return:** assign the next alias from the master list and create a profile (next section).
5. **No match, one-time incident:** leave the person as `Unknown`.

> **Note**
>
> Keep a master alias list with the alias, the date assigned, and the profile's report ID. Never reuse an alias number.

---

## Creating a Person of Interest Profile (security lead)

Each alias gets one profile report, which holds the reference photos and a running log of every linked incident.

1. Submit a new report in the **[Person of Interest Profile]** category. Access to this category is restricted to security and management.
2. In **People & Witnesses**, enter the alias as the name.
3. In the write-up, summarize why the profile was created and list the first incident's report ID.
4. Complete the **Person Description** form with the best description available.
5. Attach the clearest reference photos. Use copies; the originals stay on the incident reports where they were captured.
6. Set the status to **Active**, or **Banned** if the person has been barred. For a ban, record the end date in the write-up and add the alias and profile report ID to the [Banned List](https://docs.incident-tracker.com/admin-guide/misc/banned-list).
7. Each time a new incident is linked, append a note: _Linked to report #\_\_\_\_, [location], [date]._

> **Caution**
>
> Only assign profile reports to members of the security group. Assignment gives a user access to the report even if they're otherwise restricted from the category.

---

## When the person is identified (security lead)

Update the profile and keep the alias in the name, so searches on the alias still return every linked report.

1. Edit the profile report and change the name in **People & Witnesses** to the real name followed by the alias, for example `Jane Doe (UNK-0042)`.
2. Set the status to **Identified**.
3. Append a note recording how and when the person was identified.
4. Update the master alias list.

Updating the individual incident reports is optional. The alias already connects them to the profile.

---

## Sharing records with law enforcement

Only the security lead or [library director] shares records, following library policy on when a subpoena or court order is required. Refer any other request from an officer to them.

1. In **Advanced Search**, filter **People / Witnesses** for the alias with the date range set to **All Reports Ever Entered**.
2. Click **Export Reports** to create a summary spreadsheet of the linked reports.
3. For each report, open **Report Actions**, select **PDF Report**, and redact any text that shouldn't be shared, such as names of other patrons, witnesses, and minors. Redaction applies only to that one-time PDF download and doesn't change the original report.
4. Download the original photo and video attachments from each report.
5. Append a note on the profile recording the date, agency, officer, case number, and what was shared.

> **Note**
>
> Each report's history and edit log show who created and changed it, which supports the records if they're questioned later.

---

## Review and retention (security lead)

The security lead reviews all Active and Banned profiles every [quarter] so profiles don't stay open indefinitely.

1. In **Advanced Search**, filter the **[Person of Interest Profile]** category, excluding Identified and Inactive statuses, and set **Days Stale** to more than [365]. Appended notes reset Days Stale, so these are the profiles with no linked incidents in that time.
2. Set those profiles to **Inactive**, or handle them according to the library's retention policy.
3. Check ban end dates. Update the profile status and remove expired entries from the Banned List.
4. Update the master alias list to match.

> **Tip**
>
> Days Stale resets whenever a profile changes, including edits made during these reviews. If your library clears old data on a fixed schedule, also set a reminder on each profile when you create it. A reminder's day count doesn't reset when the report changes.
