Broker onboarding questions,
answered straight.

The questions every freight operator asks before going live on HatchOS โ€” carrier vetting, payment terms, load posting, escalation paths, and platform uptime. No sales pitch.

How does HatchOS vet carriers?

Shield, our compliance AI employee, runs FMCSA SAFER lookups at carrier onboarding and continuously thereafter. Authority status, BIPD insurance on file, safety rating, and out-of-service flags are checked; a composite scorecard is recomputed nightly. Carriers failing shield do not appear in your tender list.

What are HatchOS payment terms?

Carrier pay terms default to net-15 from delivery confirmation, configurable per carrier or per contract. Quick-pay (net-7 with a small fee) is supported via ACH through the carrier banking module. Settlement statements export to your accounting system on close.

How do I post a load?

From the dispatch board, click "New shipment" and enter origin/dest, equipment, pickup/delivery windows. HatchOS auto-builds a rate suggestion from your rate agreements and historical lanes. Tenders go out via email + load-board integration; replies land in the shipment inbox automatically.

Who do I escalate to?

Routine ops: your account manager. Platform bugs: bug reports at /bug-report (in-app) or support@hatchos.app. For after-hours incidents affecting live freight, page on-call via /status โ€” operator response is monitored 24/7.

What is the HatchOS uptime record?

Live status, 90-day history, and scheduled maintenance are at /status. We publish incident reports and postmortems for any degradation lasting more than 5 minutes.

Still have questions?

Book a 30-minute call with an operator who runs HatchOS in production. They'll walk you through the platform live.