Transportation Checkpoints

Transportation Checkpoints

Purpose and when to use this record

BriskDefine storesa scheduled or required checkpoint along a transportation checkpointsroute.

as

At parta ofglance

• Identify it by: Checkpoint Date/Time.

• Check its business context: Transportation Entry, and 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 transportation checkpoints. 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 Transportation Entry records ready first. Those selections determine where this Transportation Checkpoint belongs and which later screens can find it.

Create a recordTransportation Checkpoint

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

1. Select the business context first: Transportation Entry, and Officer.

2. Enter the required identifying and operational values: Transportation Entry.

3. Review Checkpoint Type deliberately; these choices control availability or workflow rather than merely describing the record.

4. Save the Transportation Checkpoint, then confirm Checkpoint Date/Time on its detail page before continuing.

After saving: Verify Checkpoint Type, Transportation Entry, 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.

Delete a Transportation Checkpoint

Delete this Transportation Checkpoint 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 Checkpoint Date/Time. After confirmation, return to the Transportation Checkpoints list and make sure only the intended Transportation Checkpoint was removed.

ViewReview recordTransportation Checkpoint details

The evidence packet identifiesUse the viewdetail page as the shared record of what this Transportation Checkpoint currently means. Verify Checkpoint Type, and sourceCheckpoint locationDate/Time before relying on it for thisa action.decision.

Confirm

Follow user-facingTransportation stepsEntry, beforeand approvingOfficer to determine whether the issue is on this Transportation Checkpoint or on one of those linked records.

Next check: Verify Checkpoint Type, Transportation Entry, 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 Transportation Checkpoint

Edit this Transportation Checkpoint 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 Transportation Entry, and Officer with the supporting document or approved request.

2. Recheck Checkpoint Type, and Checkpoint Date/Time. 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 Transportation Checkpoint now appears under the expected Checkpoint Type.

After the change: Verify Checkpoint Type, Transportation Entry, 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.

Find and review recordstransportation checkpoints

The evidence packet identifiesUse the viewTransportation Checkpoints list to find the correct record before opening or changing it. Compare Checkpoint Date/Time. Records with similar names or numbers can still belong to different Transportation Entry, and sourceOfficer.

location

• The initial order emphasizes Checkpoint Date/Time, and Id. Select a column heading when you need a different comparison.

Open the Transportation Checkpoint whose Checkpoint Date/Time match the task. If it is missing, clear the list filters and recheck Checkpoint Type rather than creating a replacement immediately.

Fields and business rules

Brisk stores 6 user-relevant fields for this action.Transportation ConfirmCheckpoint, user-facingincluding steps2 beforelinked-record approvingselections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this page.full reference.

Editanexistingrecord

location arecord

source user-facingstepsbeforeapproving

Field	Required	What it controls
Transportation Entry	Yes	The evidencetransportation packetentry identifiesassociated thewith viewthis andtransportation sourcecheckpoint.
Checkpoint Type	No	The checkpoint type recorded for this action.transportation Confirmcheckpoint. user-facingAvailable stepsvalues: beforeIntake, approvingDeparture, Arrival, Release, Transfer, Other.
Checkpoint Date/Time	No	Date and time recorded for checkpoint date/time on this page. transportation Deletecheckpoint.
Officer	No	The evidenceofficer packetassociated identifieswith thethis viewtransportation andcheckpoint.
Location	No	The location recorded for this action.transportation Confirmcheckpoint.
Notes	No	Additional internal notes about this page.transportation checkpoint.

What happens next

Verify Checkpoint Type, Transportation Entry, 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 Transportation Entry 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 Transportation Entry, and Officer from the detail page. Correct the specific relationship that is wrong instead of forcing a total or status to compensate for it.