Carriers & Visitors
A carrier profile records who is moving an asset. Attaching one at check-in is what lets you later answer "which carrier brought this in?" and filter the activity feed and visit report by carrier.
The same profile type covers two kinds:
- Carrier — a trucking company or driver moving cargo.
- Visitor — a person on site with no asset, for visitor check-in.
Profile Fields
| Field | Required | Notes |
|---|---|---|
| Kind | Yes | carrier or visitor. |
| Name | Yes | Driver or person name. This is what operators search on. |
| Company | No | The carrier company. Worth filling in — it is how you group a fleet's activity. |
| Contact | No | Phone and email. |
Visitor profiles additionally track whether the person is currently on site and, if so, which visit they are on and when they arrived. Those are maintained by check-in and check-out, not edited directly.
Creating Carriers Inline
Operators do not have to leave the gate to add a carrier. The carrier selector on the check-in screen has a create option that captures a name and company, saves the profile, and selects it in one step.
This matters more than it sounds. The alternative — an operator blocked at the gate because a new driver is not in the system — is how yards end up with every unknown truck logged against one "MISC" profile, which destroys the reporting the field exists for.
Inline creation is available to Gate and Dispatch roles as well as Admin. Editing and deleting profiles stays with Admin.
Keeping the List Usable
The carrier list is a working list, not a CRM.
- Prefer company-level profiles unless you genuinely need per-driver records. A hundred drivers from one carrier is harder to report on than one carrier.
- Expect duplicates and merge them. Inline creation at a busy gate will produce "ABC Trucking" and "ABC Trucking Inc". Reviewing the list periodically is normal housekeeping.
- Do not delete a carrier with history. Past visits reference the profile; removing it loses the ability to resolve who brought an asset in.
Visitors
Visitor check-in records a person entering and leaving without any asset, location, capacity check,
or billing. It uses the visitorIn and visitorOut capture forms, which
typically ask for the person's purpose, who they are visiting, and a badge or licence number.
Use it where you need a site-safety record of who was on the property. It deliberately shares nothing with the cargo billing path — a visitor produces no line items.