Immutable booking context
Keep the accepted quote assumptions available for comparison after the load is created.
Rate confirmation management
Catch the booking-to-RateCon difference before it becomes a dispatch problem.
CarrierOS gives a small carrier a controlled RateCon review workflow that keeps the original booking assumptions, extracted or entered terms, identified differences, and human approval together.
For carrier owners, dispatchers, and operations teams that want a repeatable review between accepting a broker offer and releasing the load.
The accepted offer and the signed confirmation need an intentional comparison.
Rates, miles, stops, dates, equipment, accessorials, and instructions can change between a negotiation and the final document. CarrierOS preserves the booking snapshot and supports a field-level review before dispatch approval.
What you can manage
Keep the operating math attached to the work.
Document review
Upload a supported RateCon when secure document storage is configured, or use the controlled manual review path.
Difference classification
Separate financial, operational, and informational differences for human review.
Approval control
Keep dispatch blocked until required review and safety-sensitive decisions are complete.
A clearer workflow
A reviewable path from document to dispatch
CarrierOS connects the record, the assumptions, and the result so the next decision starts with better context.
- 01
Receive the confirmation
Associate the RateCon with the intended load and validate the supported file.
- 02
Compare the terms
Review the confirmed values and their source against the preserved booking snapshot.
- 03
Resolve and approve
Document material differences, confirm the authorized terms, and continue to dispatch.
A closer look
What this workflow means in practice.
Use CarrierOS for the operating record and review, while keeping authoritative safety, financial, legal, and regulatory systems in their proper roles.
Human review remains the control
Where configured providers assist with text or field extraction, their output is evidence for review rather than an automatic contract change. The carrier remains responsible for reading the document and approving the terms.
- Review field source, confidence, and document-page context when available.
- Do not silently overwrite the booked load from extracted text.
- Require explicit approval for material financial or operational differences.
Document security depends on production configuration
CarrierOS uses provider boundaries for private storage and malware screening. Production uploads should remain unavailable unless the required secure services and operational controls are configured.
- Validate file signature, size, and supported document type.
- Keep private documents out of public pages and search indexes.
- Follow the carrier's retention and access-control procedures.
Common questions
What small carriers ask before starting.
What RateCon fields can be reviewed?
The workflow is designed to review important financial and operational terms such as rate, miles, dates, stops, equipment, and instructions, with the exact review depending on the document and configured provider.
Does CarrierOS automatically change a load from a RateCon?
No. Extracted or entered values are review evidence. Material changes require an authorized human decision.
Can a RateCon be uploaded on every deployment?
Private uploads depend on secure storage and malware-screening configuration. CarrierOS keeps uploads disabled when required production controls are not ready.
Does RateCon review replace reading the contract?
No. The carrier must read and verify the governing document and resolve questions with the broker or qualified adviser.
Explore CarrierOS with a fictional sample fleet.
Try dispatch, driver pay, load profitability, and pricing without creating an account.