Carrier Safety
Carrier Safety checks carrier records, provider evidence, insurance, authority, and internal status before dispatch or rate confirmation.
Where it appears
- Carrier list and carrier profiles may show safety badges when enabled.
- Load details show carrier safety status for the assigned carrier.
- Dispatch can be blocked when the workspace mode enforces dispatch checks.
- Rate confirmation sending can be blocked when the workspace mode enforces dispatch and rate confirmation checks.
- Audit Reports show carrier safety policy, gate, exception, and evidence activity when permitted.
Safety modes
Admins configure Carrier safety mode in Settings.
- Off: no carrier safety checks are shown or enforced.
- Block dispatch + Send Ratecon: dispatch and rate confirmation sending are blocked when active safety checks fail.
Turning the mode off also disables safety badges, exception workflow, evidence exports, dispatch or rate confirmation safety gate calls, and new carrier-safety gate or evaluation entries in Audit Reports.
Policy checks
Carrier safety policies decide which checks are active. Locked system checks for Do not use, inactive, and deleted carrier records are always included. Policy checks can also cover authority, insurance, safety rating, provider compliance, missing evidence, stale evidence, or internal review status.
Review the active policy before changing enforcement. A saved policy must be activated before it controls new checks. If safety is enabled without an active policy, ARK TMS creates the default system-check policy before enforcement.
Blocked dispatch
- Open the load.
- Review the carrier safety panel.
- Open the carrier profile and resolve the blocker when possible.
- Refresh provider data if the evidence looks stale.
- Choose another carrier or request an exception when your permissions and policy allow it.
Changing the carrier on an active dispatch uses a fresh safety snapshot for the new carrier. If a safety panel shows unchecked or stale evidence after a carrier change, refresh provider data and run the check again before sending the rate confirmation.
Blocked rate confirmation
When rate confirmation sending is blocked, ARK TMS does not send the email. Review the safety approval panel, then resolve the carrier issue, choose another carrier, or request approval when the blocker allows exceptions.
Approved rate confirmation exceptions are consumed after a successful send.
Exceptions
Exceptions are available only when the workflow is enabled and every blocking rule allows an admin exception.
- Request approval from the load or rate confirmation block.
- A user with review permission approves or denies the request.
- Approved exceptions apply to their action scope: dispatch, rate confirmation, or both.
- Expired, denied, revoked, or already consumed exceptions do not allow the action.
Evidence packets
Evidence exports must be enabled and require permission. Packets summarize the carrier, load, policy, decision, rule results, and source evidence with redaction based on the user's access.
Use evidence packets for vetting records, governance review, insurance review, or support escalation.
Permissions
Carrier safety uses separate permissions for viewing safety details, editing policies, requesting exceptions, reviewing exceptions, generating evidence packets, and viewing restricted safety evidence.