Define a scheduled or required checkpoint along a transportation route.
## At a glance
- **Identify it by:** **Checkpoint Date/Time**.
- **Check its business context:** **Transportation Entry**, 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 permission for the action you are taking on transportation checkpoints. 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 **Transportation Entry** records ready first. Those selections determine where this Transportation Checkpoint belongs and which later screens can find it.
Create a Transportation Checkpoint
The Transportation Checkpoints create screen in the Brisk documentation demo.
Create a Transportation Checkpoint only after confirming that the source 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 document 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 a real event that later changed.
On the confirmation page, verify **Checkpoint Date/Time**. After confirmation, return to the Transportation Checkpoints list and make sure only the intended Transportation Checkpoint was removed.
Review Transportation Checkpoint details
Use the detail page as the shared record of what this Transportation Checkpoint currently means. Verify **Checkpoint Type**, and **Checkpoint Date/Time** before relying on it for a decision.
Follow **Transportation Entry**, and **Officer** 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 transportation checkpoints
The Transportation Checkpoints list screen in the Brisk documentation demo.
Use the Transportation 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 **Officer**.
- 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 Transportation Checkpoint, including 2 linked-record selections and 1 controlled-choice field. Create and edit screens may hide calculated or workflow-managed values from this full reference.
| Field | Required | What it controls |
|---|---:|---|
| **Transportation Entry** | Yes | The transportation entry associated with this transportation checkpoint. |
| **Checkpoint Type** | No | The checkpoint type recorded for this transportation checkpoint. Available values: Intake, Departure, Arrival, Release, Transfer, Other. |
| **Checkpoint Date/Time** | No | Date and time recorded for checkpoint date/time on this transportation checkpoint. |
| **Officer** | No | The officer associated with this transportation checkpoint. |
| **Location** | No | The location recorded for this transportation checkpoint. |
| **Notes** | No | Additional internal notes about this 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.
