Cases

Cases

Purpose and when to use this record

Brisk stores cases as part ofMaintain the lawcentral enforcementincident module.or Thisinvestigation generatedrecord referencethat 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 awaitingabsent, workflowdo review.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.

Create a recordCase

TheCreate evidencea packetCase identifiesonly after confirming that the viewsource 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 locationdocument and actual work performed.

Delete a Case

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 thisa action.real Confirmevent user-facingthat stepslater beforechanged.

approving

Before confirming, check for related Arrests, Case Info, Case Tallies, and Evidence Items. Brisk may refuse deletion when another record depends on this page.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.

ViewReview recordCase details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Case currently means. Verify Request Date, Incident Date, Felony/Misdemeanor, and sourceStatus locationbefore relying on it for thisa action.decision.

Confirm

Follow user-facingOfficer, stepsType, beforeJurisdiction, approvingSeizure, 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.

Edit an existing Case

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.

Find and review recordscases

The evidence packet identifiesUse the viewCases list to find the correct record before opening or changing it. Compare Case Number, Request Date, Incident Date, and sourceStatus. locationRecords 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 action.Case, Confirmincluding user-facing5 stepslinked-record beforeselections approvingand 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidence Confirmuser-facingstepsapprovingthis page.

Delete a record

The evidence packet identifies

sourcelocation Confirmuser-facingstepsapproving

Field	Required	What packetit identifiescontrols
Officer	Yes	Sets the view and source locationofficer for this action.case.
Case beforeNumber	No	Sets the viewcase andnumber.
Request Date	Yes	The date that paperwork began for this action.case.
Incident beforeDate	Yes	The date for which events in this page.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.