Agencies
Agencies
Purpose and when to use this record
BriskMaintain storesthe law-enforcement and partner agencies asreferenced partby ofcases, officers, evidence, transport, and dispatch work.
At a glance
-
Identify it by: Name.
-
Why care: Use the
lawagency’senforcementapprovedmodule.terminologyThisandgeneratedaccessreferencepolicy. Preserve dates, responsible personnel, case links, and audit history because these records may support official reporting or custody review.
Before you begin
You need the Brisk permission for the action you are taking on agencies. 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.
Find and review agencies

Use the Agencies list to find the correct record before opening or changing it. Compare Name. Compare the full identifier rather than relying on a similar name.
Open the Agency whose Name match the task. If it is missing, clear the list filters and recheck Agency Type rather than creating a replacement immediately.
Create aan recordAgency

TheCreate evidencean packetAgency identifiesonly after confirming that the viewsource document or operational event has not already been entered.
-
Select the business context first.
-
Enter the required identifying and operational values: Name, and Agency Type.
-
Review Agency Type deliberately; these choices control availability or workflow rather than merely describing the record.
-
Save the Agency, then confirm Name on its detail page before continuing.
After saving: Verify Agency Type on the detail page, then continue the law enforcement workflow only when those values agree with the source locationdocument and actual work performed.
Delete an Agency
Delete this Agency 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.
Before confirming, check for related Dispatch Entries, and Officers. 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 Name. After confirmation, return to the Agencies list and make sure only the intended Agency was removed.
ViewReview recordAgency details
The evidence packet identifiesUse the viewdetail page as the shared record of what this Agency currently means. Verify Agency Type before relying on it for a decision.
Compare the Agency with its source document or approved setup request before deciding that it needs correction.
Next check: Verify Agency Type on the detail page, then continue the law enforcement workflow only when those values agree with the source document and sourceactual locationwork for this action. Confirm user-facing steps before approving this page.
Find and review records

The evidence packet identifies the view and source location for this action. Confirm user-facing steps before approving this page.performed.
Edit an existing recordAgency
TheEdit evidencethis packetAgency identifiesto correct or complete the viewsame source document or operational event; use the supported reversal or follow-up workflow when the business event itself changed.
-
Open the detail page. Compare Name with the supporting document or approved request.
-
Recheck Agency Type. These values are most likely to change case history, custody, dispatch, official reporting, or audit review.
-
Save the change, return to the list, and confirm that the Agency now appears under the expected Agency Type.
After the change: Verify Agency Type on the detail page, then continue the law enforcement workflow only when those values agree with the source locationdocument and actual work performed.
Fields and business rules
Brisk stores 3 user-relevant fields for this action.Agency, Confirmincluding user-facing0 stepslinked-record beforeselections approvingand 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.
| Field | Required | What it controls |
|---|---|---|
| Name | Yes | Use this field to give the category a name (e.g. Felony, Misdemeanor, Federal, etc.). |
| Agency Type | Yes | Enter what type of agency. Available values: EMS, Fire, Law Enforcement, Other. |
| Notes | No | Use this field to record any notes about the agency. |
What happens next
Verify Agency Type on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed.
DeleteCommon amistakes and troubleshooting
-
The record
Thewillevidencenotpacketsave:identifiesRecheck Name, and Agency Type and any message beside theviewfield.andA required related record may also be inactive or unavailable to your role. -
The values look right but the result is wrong: Compare this Agency with the source
locationdocumentfororthisapprovedaction.setupConfirmdecision,user-facingthenstepscheckbeforetheapprovingdownstreamthisscreenpage.where it is used.