Overview
In Coyote Measurement, a load is a truck transaction — a measured pickup or delivery recorded at a terminal bay. Loads become live transactions after you import and approve bay files, create them manually, or sync them from an integration such as LoadCall.
Bays are the physical loading/unloading positions at a facility. Each bay has a number, type, and optional API alarm settings used during import validation.
Drivers are managed separately under Admin → Drivers for compliance (CDL, medical card, training documents). Driver names on loads usually come from the import file or integration; Coyote links them to a registered driver when a match exists.
How loads enter Coyote
| Source | Result |
|---|---|
| Approved import | Bay TransLog or CSV file → transaction with bay, volumes, shipper, carrier |
| Manual entry | New Transaction on the Transactions page |
| LoadCall sync | Integration pulls dispatch tickets → transactions (when configured) |
| Import session — manual add | Add a missing load during import review before approve |
Most terminal operators use Imports daily, then work loads on the Transactions page.
Loads, bays, and facilities
Facility └── Bay 1 (Loading) └── Bay 2 (Unloading) └── Bay 3 (Bidirectional) └── Transactions (loads) assigned per bay- Each transaction belongs to one facility and usually one bay.
- Bay type controls default movement direction during import:
- Loading → carrier out (delivery from terminal)
- Unloading → carrier in (receipt to terminal)
- Bidirectional → direction from file context
- Report day on a load follows the facility operational day (typically 7 AM–7 AM).
Transaction types
| Type | Typical meaning |
|---|---|
| Receipt | Product received at the facility |
| Delivery | Product delivered from the facility |
| Transfer In / Out | Internal movement |
| Adjustment | Volume correction |
| Return | Returned load |
Reconciliation status
Every load has a reconciliation status used in reporting and producer matching:
| Status | Meaning |
|---|---|
| Unreconciled | Not yet matched to producer statement |
| Reconciled | Matched successfully |
| Volume Mismatch | Matched but volumes differ |
| Manual Override | Accepted with manual adjustment |
Daily workflow
flowchart LR A[Import bay files] --> B[Approve import session] B --> C[Transactions live] C --> D[View / filter loads] D --> E[Reconcile & report]- Import and approve bay files for the production day.
- Open Transactions to review loads by facility, date, producer, or status.
- Open a load detail page for ticket, volume, bay, carrier, and driver info.
- Use Reconciliation and Reports for downstream workflows.
Permissions
| Area | Permission |
|---|---|
| View transactions (loads) | facility:transactions:list |
| Create / edit transactions | facility:transactions:create, facility:transactions:update |
| Manage bays | facility:bays:create, facility:bays:update, facility:bays:delete |
| View / manage drivers | org:drivers:list, org:drivers:create, org:drivers:update |
You must have access to the facility shown in the app header.
Related topics
- Uploading Import Files — how loads are created from terminal files
- Viewing Loads — Transactions list and detail
- Bay Management — configure bays at a facility
- Driver Assignments — driver records and compliance