# Cases

# Cases

<h2 id="bkmrk-overview">Purpose and when to use this record</h2>

Maintain the central incident or investigation record that ties together jurisdiction, status, people, evidence, tallies, and activity.

## At a glance

- **Identify it by:** **Case Number**, **Request Date**, **Incident Date**, and **Status**.

- **Check its business context:** **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status**.

- **Why care:** Use the agency’s approved terminology and access policy. Preserve dates, responsible personnel, case links, and audit history because these records may support official reporting or custody review.

- **Why care:** Status communicates workflow progress to other staff. Change it only when the underlying work, approval, payment, or handoff has actually occurred.

## Before you begin

You need the Brisk permission for the action you are taking on cases. If a Create, Edit, or Delete control is absent, do not work around it with another user’s account; ask an administrator to review your role.

Have valid **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status** records ready first. Those selections determine where this Case belongs and which later screens can find it.

<h2 id="bkmrk-create">Create a Case</h2>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/article-modellaw-enforcementcase-create-law-enforcement-case-create.png" alt="Brisk Cases create screen displayed with fictional documentation-demo data." loading="lazy" style="max-width:100%;height:auto;"><figcaption>The Cases create screen in the Brisk documentation demo.</figcaption></figure>

Create a Case only after confirming that the source document or operational event has not already been entered.

1. Select the business context first: **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status**.

2. Enter the required identifying and operational values: **Officer**, **Request Date**, **Incident Date**, **Type**, **Felony/Misdemeanor**, and **Jurisdiction**, plus the remaining screen fields.

3. Review **Felony/Misdemeanor** deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Case, then confirm **Case Number**, **Request Date**, **Incident Date**, and **Status** on its detail page before continuing.

After saving: Verify **Felony/Misdemeanor**, **Status**, **Officer**, **Type**, **Jurisdiction**, and **Seizure** on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed.

<h2 id="bkmrk-delete">Delete a Case</h2>

Delete this Case only when it was entered by mistake and no downstream history depends on it. Use a reversal, void, credit, counter-adjustment, or status correction for a real event that later changed.

Before confirming, check for related **Arrests**, **Case Info**, **Case Tallies**, and **Evidence Items**. Brisk may refuse deletion when another record depends on this one; resolve the duplicate or use the supported correction workflow instead of breaking the trail.

On the confirmation page, verify **Case Number**, **Request Date**, **Incident Date**, and **Status**. After confirmation, return to the Cases list and make sure only the intended Case was removed.

<h2 id="bkmrk-detail">Review Case details</h2>

Use the detail page as the shared record of what this Case currently means. Verify **Request Date**, **Incident Date**, **Felony/Misdemeanor**, and **Status** before relying on it for a decision.

Follow **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status** to determine whether the issue is on this Case or on one of those linked records.

Next check: Verify **Felony/Misdemeanor**, **Status**, **Officer**, **Type**, **Jurisdiction**, and **Seizure** on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed.

<h2 id="bkmrk-update">Edit an existing Case</h2>

Edit this Case to correct or complete the same source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.

1. Open the detail page. Compare **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status** with the supporting document or approved request.

2. Recheck **Request Date**, **Incident Date**, **Felony/Misdemeanor**, and **Status**. These values are most likely to change case history, custody, dispatch, official reporting, or audit review.

3. Save the change, return to the list, and confirm that the Case now appears under the expected **Felony/Misdemeanor**, and **Status**.

After the change: Verify **Felony/Misdemeanor**, **Status**, **Officer**, **Type**, **Jurisdiction**, and **Seizure** on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed.

<h2 id="bkmrk-list">Find and review cases</h2>

<figure class="brisk-doc-media"><img src="https://help.brisksystems.us/uploads/images/gallery/2026-08/article-modellaw-enforcementcase-list-law-enforcement-cases.png" alt="Brisk Cases list screen displayed with fictional documentation-demo data." loading="lazy" style="max-width:100%;height:auto;"><figcaption>The Cases list screen in the Brisk documentation demo.</figcaption></figure>

Use the Cases list to find the correct record before opening or changing it. Compare **Case Number**, **Request Date**, **Incident Date**, and **Status**. Records with similar names or numbers can still belong to different **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status**.

Open the Case whose **Case Number**, **Request Date**, **Incident Date**, and **Status** match the task. If it is missing, clear the list filters and recheck **Felony/Misdemeanor**, and **Status** rather than creating a replacement immediately.

## Fields and business rules

Brisk stores 11 user-relevant fields for this Case, including 5 linked-record selections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.

| Field | Required | What it controls |
|---|---:|---|
| **Officer** | Yes | Sets the officer for this case. |
| **Case Number** | No | Sets the case number. |
| **Request Date** | Yes | The date that paperwork began for this case. |
| **Incident Date** | Yes | The date for which events in this case occurred. |
| **Description** | No | Record the title or description for this case. |
| **Type** | Yes | Sets the type for this case. |
| **Felony/Misdemeanor** | Yes | Enter what type of crime. Available values: Felony, Misdemeanor, Violation, Traffic. |
| **Jurisdiction** | Yes | Select the jurisdiction for this incident. |
| **Address/Location** | Yes | Set address or location of the incident. |
| **Seizure** | Yes | Select a forfeiture condition for this case. |
| **Status** | Yes | Select the status for this incident. |

## What happens next

Verify **Felony/Misdemeanor**, **Status**, **Officer**, **Type**, **Jurisdiction**, and **Seizure** on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed.

## Common mistakes and troubleshooting

- **The record will not save:** Recheck **Officer**, **Request Date**, **Incident Date**, **Type**, **Felony/Misdemeanor**, and **Jurisdiction**, plus the remaining screen fields and any message beside the field. A required related record may also be inactive or unavailable to your role.

- **The record saved but is not available where expected:** Recheck **Felony/Misdemeanor**, and **Status**, then clear the filters on the destination list. A saved record can still be inactive, unpublished, locked, unapproved, or in the wrong workflow state.

- **The values look right but the result is wrong:** Open **Officer**, **Type**, **Jurisdiction**, **Seizure**, and **Status** from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.