Dispatch Entries

Dispatch Entries

Purpose and when to use this record

Record a dispatched call or activity with its time, unit/officer context, location, disposition, and narrative.

At a glance

• Identify it by: Label.

• Check its business context: Dispatcher, Agency, and Officer.

• 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.

Before you begin

You need the Brisk storespermission for the action you are taking on dispatch entries. 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 Dispatcher, and Officer records ready first. Those selections determine where this Dispatch Entry belongs and which later screens can find it.

Find and review dispatch entries

as

This

Use generatedthe referenceDispatch Entries list to find the correct record before opening or changing it. Compare Dispatcher, Agency, Officer, and Shift Date. Records with similar names or numbers can still belong to different Dispatcher, Agency, and Officer.

Open the Dispatch Entry whose Dispatcher, Agency, Officer, and Shift Date match the task. If it is awaitingmissing, workflowclear review.the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.

Create a recordDispatch Entry

TheCreate evidencea packetDispatch identifiesEntry only after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first: Dispatcher, Agency, and Officer.

2. Enter the required identifying and operational values: Dispatcher, Officer, and Shift Date.

3. Review Label against the source locationdocument or approved setup decision.

4. Save the Dispatch Entry, then confirm Label on its detail page before continuing.

After saving: Verify Dispatcher, Agency, and Officer on the detail page, then continue the law enforcement workflow only when those values agree with the source document and actual work performed.

Delete a Dispatch Entry

Delete this Dispatch Entry 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 Dispatch Activities, and Dispatch Tallies. Brisk may refuse deletion when another record depends on this page.

one;

View record details

The evidence packet identifiesresolve the viewduplicate andor sourceuse locationthe forsupported thiscorrection action.workflow Confirminstead user-facingof stepsbreaking beforethe approving this page.trail.

Find

On andthe reviewconfirmation records

page,

Entry was removed.

Review Dispatch Entry details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Dispatch Entry currently means. Verify Dispatcher, Agency, Officer, and sourceShift locationDate before relying on it for thisa action.decision.

Confirm

Follow user-facingDispatcher, stepsAgency, beforeand approvingOfficer to determine whether the issue is on this page.Dispatch Entry or on one of those linked records.

Next check: Verify Dispatcher, Agency, and Officer 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 recordDispatch Entry

TheEdit evidencethis packetDispatch identifiesEntry to correct or complete the viewsame 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 Dispatcher, Agency, and Officer with the supporting document or approved request.

2. Recheck the identifying information shown on the screen. 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 Dispatch Entry now appears under the expected Label.

After the change: Verify Dispatcher, Agency, and Officer 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 5 user-relevant fields for this action.Dispatch ConfirmEntry, user-facingincluding steps3 beforelinked-record approvingselections and 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Deletearecord

The

evidencepacket user-facingstepsbeforeapproving

Field	Required	What identifiesit controls
Dispatcher	Yes	Sets the view and source locationdispatcher for this action.log Confirmentry.
Agency	No	Sets the agency for this page.dispatch entry.
Officer	Yes	Sets the officer for this log entry.
Shift Date	Yes	The calendar date of this shift. If shift carries into a 2nd day, please use the first/starting day.
Label	No	Optionally set a label for this dispatch entry.

What happens next

Verify Dispatcher, Agency, and Officer 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 Dispatcher, Officer, and Shift Date and any message beside the field. A required related record may also be inactive or unavailable to your role.

• The values look right but the result is wrong: Open Dispatcher, Agency, and Officer from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.