Logs

Logs

Purpose and when to use this record

BriskRecord storeschronological logsagency asactivity partfor ofoperational review and reporting.

At a glance

• Identify it by: Officer, Shift Date, On-Shift Time, and Off-Shift Time.

• Check its business context: Officer, and Vehicle.

• Why care: Use the lawagency’s enforcementapproved module.terminology Thisand generatedaccess referencepolicy. 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 logs. 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 records ready first. Those selections determine where this Log belongs and which later screens can find it.

Create a recordLog

TheCreate evidencea packetLog identifiesonly after confirming that the viewsource document or operational event has not already been entered.

1. Select the business context first: Officer, and Vehicle.

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

3. Review On-Shift Time, Off-Shift Time, Beginning Miles, Ending Miles, and Total Miles against the source locationdocument or approved setup decision.

4. Save the Log, then confirm Officer, Shift Date, On-Shift Time, Off-Shift Time, Vehicle, and Beginning Miles, plus the remaining screen fields on its detail page before continuing.

After saving: Use Officer, and Vehicle to interpret this Log. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Delete a Log

Delete this Log 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 Activities, and Tallies. 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 Officer, Shift Date, On-Shift Time, and Off-Shift Time. After confirmation, return to the Logs list and make sure only the intended Log was removed.

ViewReview recordLog details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Log currently means. Verify Total Miles before relying on it for a decision.

Follow Officer, and sourceVehicle locationto fordetermine whether the issue is on this action.Log Confirmor user-facingon stepsone beforeof approvingthose linked records.

Next check: Use Officer, and Vehicle to interpret this Log. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Edit an existing Log

Edit this Log 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, and Vehicle with the supporting document or approved request.

2. Recheck Total Miles. 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 Log now appears under the expected the identifying information shown on the screen.

After the change: Use Officer, and Vehicle to interpret this Log. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Find and review recordslogs

The evidence packet identifiesUse the viewLogs list to find the correct record before opening or changing it. Compare Officer, Shift Date, On-Shift Time, and sourceOff-Shift locationTime. Records with similar names or numbers can still belong to different Officer, and Vehicle.

Open the Log whose Officer, Shift Date, On-Shift Time, and Off-Shift Time match the task. If it is missing, clear the list filters and recheck the identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 8 user-relevant fields for this action.Log, Confirmincluding user-facing2 stepslinked-record beforeselections approvingand 0 controlled-choice fields. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

The

evidence user-facingstepsbefore sourcelocation Confirmuser-facingstepsapproving

Field	Required	What packetit identifiescontrols
Officer	Yes	Sets the view and source locationofficer for this action.log Confirmentry.
Shift approvingDate	Yes	The calendar date of this page. shift. DeleteIf shift carries into a record 2nd Theday, evidenceplease packet identifiesuse the viewfirst/starting andday.
On-Shift Time	No	The on-shift time recorded for this action.log.
Off-Shift beforeTime	No	The off-shift time recorded for this page.log.
Vehicle	No	Sets the vehicle that the officer is using this day.
Beginning Miles	No	Records the mileage of the vehicle at the beginning of the shift.
Ending Miles	No	Records the mileage of the vehicle at the end of the shift.
Total Miles	No	Records the difference between the beginning and ending mileage.

What happens next

Use Officer, and Vehicle to interpret this Log. If it records a failure or exception, correct the source process and create a new successful event rather than rewriting the audit trail.

Common mistakes and troubleshooting

• The record will not save: Recheck 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 Officer, and Vehicle from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.