Mileage Records

Mileage Records

Purpose and when to use this record

BriskRecord storesvehicle mileage recordstied asto partlaw-enforcement ofactivity, dates, officers, or routes.

At a glance

• Identify it by: Date.

• Check its business context: Officer.

• 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 mileage records. 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 Mileage Record belongs and which later screens can find it.

Create a recordMileage Record

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

1. Select the business context first: Officer.

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

3. Review Beginning Miles, and Ending Miles against the source locationdocument or approved setup decision.

4. Save the Mileage Record, then confirm Date on its detail page before continuing.

After saving: Use Officer to interpret this Mileage Record. 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 Mileage Record

Delete this Mileage Record 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

On thisthe page.confirmation page, verify Date. After confirmation, return to the Mileage Records list and make sure only the intended Mileage Record was removed.

ViewReview recordMileage Record details

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

Follow Officer to determine whether the issue is on this Mileage Record or on one of those linked records.

Next check: Use Officer to interpret this Mileage Record. If it records a failure or exception, correct the source process and sourcecreate locationa fornew successful event rather than rewriting the audit trail.

Edit an existing Mileage Record

Edit this action.Mileage ConfirmRecord user-facingto stepscorrect beforeor approvingcomplete 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 with the supporting document or approved request.

2. Recheck Date. 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 Mileage Record now appears under the expected Date.

After the change: Use Officer to interpret this page.Mileage Record. 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 mileage records

The evidence packet identifiesUse the viewMileage Records list to find the correct record before opening or changing it. Compare Date. Records with similar names or numbers can still belong to different Officer.

Open the Mileage Record whose Date match the task. If it is missing, clear the list filters and sourcerecheck locationthe identifying information shown on the screen rather than creating a replacement immediately.

Fields and business rules

Brisk stores 5 user-relevant fields for this action.Mileage ConfirmRecord, user-facingincluding steps1 beforelinked-record approvingselection and 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

Field	Required	What packetit identifiescontrols
Beginning Miles	No	Records the viewmileage andof sourcethe locationvehicle at the beginning of the shift.
Ending Miles	No	Records the mileage of the vehicle at the end of the shift.
Mileage	Yes	The number of miles recorded.
Date	Yes	The date that this mileage will appear on the activity report.
Officer	Yes	Sets the officer for this action.log Confirmentry.

approving

What happens next

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

DeleteCommon mistakes and troubleshooting

• The record will not save: Recheck Mileage, Date, and Officer 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 from the detail page. Correct the specific relationship that is wrong instead of forcing a recordtotal

  Theor evidencestatus packetto identifies the view and source locationcompensate for this action. Confirm user-facing steps before approving this page.it.