Carriers

Carrier records manage qualification, contact details, payment setup, documents, compliance, and dispatch readiness.

Carrier record areas

• Legal name and DBA
• MC and DOT identifiers
• Address and contact details
• Operating status and compliance details
• Insurance and authority information
• Payment method and terms
• Factoring details when applicable
• Drivers and dispatchers
• Documents and packet status
• Internal notes and inactive or blocked status
• Carrier safety badges, checks, exceptions, and evidence when enabled
• Carrier reviews and service history
• File history and synced documents

Carrier profile

Carrier profiles are organized into Overview, Activity, Compliance, Onboarding, Documents, Contacts, and Settlement. Use the profile when you need the full carrier record instead of the list row.

Overview and Contacts show primary phone and email, dispatch contacts, carrier identifiers, billing address, or factoring remit-to details. Compliance shows insurance, provider monitoring, carrier safety, and FMCSA broker, common, and contract authority when available.

Use Settlement to confirm the non-sensitive payment destination before payment review. Factored carriers show the factoring remit address, email, phone, terms, method, and currency; direct carriers show billing address contact details with payment method, terms, and currency.

When MyCarrierPortal, RMIS, or Highway is enabled, carrier rows and profiles may show provider sync actions. Sync by provider when you need the latest monitoring, packet, document, contact, payment, or factoring details before approval, dispatch, or payment review.

When Carrier Safety is enabled, carrier rows and profiles may show safety badges and check summaries. Open Carrier Safety for enforcement settings, exceptions, and evidence packets.

Carrier identity

ARK TMS matches carrier records by normalized DOT and MC/MX/FF identifiers. DOT numbers are stored as digits without leading zeroes. MC, MX, and FF docket numbers are stored with their prefix and without leading zeroes.

Keep one non-deleted carrier record for each DOT or docket number. If adding, importing, inviting, or syncing a carrier reports a duplicate identity, archive or resolve the duplicate carrier record before retrying.

Carrier workflow

1. Add or import the carrier.
2. Complete authority, contact, and payment details.
3. Collect submitted or provider-synced carrier packet documents.
4. Review compliance and insurance readiness.
5. Approve, reject, block, or keep the carrier inactive based on review results.
6. Keep monitoring details, documents, and contacts current.

Provider data

Provider data is evidence for review, not an automatic approval. Compare ARK TMS values with the provider when authority, insurance, packet, payment, factoring, or status details conflict.

Approval, rejection, and blocking

Approved carriers can be considered for dispatch when their compliance, documents, contacts, and payment details are ready. Rejected carriers should show a clear reason, such as missing paperwork, failed compliance review, duplicate records, or payment concerns. Blocked carriers require extra attention and should only be unblocked after the reason has been reviewed.

Carrier Safety can also block dispatch or rate confirmation based on the active workspace policy.

Carrier reviews

Carrier ratings and reviews help users understand past service experience. Review rating history, notes, lane history, and recent issues before choosing between similar carriers.

Documents and files

Carrier files may include packets, insurance documents, agreements, tax forms, payment forms, and other support files. Keep documents organized so compliance, dispatch, and payment review are easier.

Drivers and dispatchers

Driver and dispatcher records should be linked to the correct carrier and kept current. Confirm names, phone numbers, emails, and assignment details before dispatch or tracking begins.