Freight quote requests often arrive as a mixture of email text, PDF documents, spreadsheets and follow-up messages. The first operational problem is usually not rate calculation. It is establishing what has been requested, which information is missing and who should review the case.
Define the Minimum Shipment Record
The required fields depend on mode, trade lane, customer and company policy. Start with the information the pricing team needs to decide whether it can begin, not with every field that might exist in a TMS.
Common Intake Groups
- Requester, customer and contact references
- Origin, destination and transport mode
- Commodity, package count, weight and dimensions
- Ready date, delivery constraints and validity requirements
- Incoterm and known charge responsibilities
- Dangerous goods, temperature or special handling indicators
- Supporting documents and customer instructions
Keep Every Captured Value Linked to Its Source
A reviewer should be able to see whether a value came from the email body, a PDF, a spreadsheet cell or a later correction. Source references make the record easier to verify and make disagreements easier to resolve.
Separate Missing, Uncertain and Conflicting Information
These states require different actions. A missing ready date may require a question. An uncertain commodity description may require review. Two different weights across attachments create a conflict that should remain visible until a person resolves it.
Use Rules to Prepare the Work, Not Make the Rate Decision
An intake layer can check required fields, identify risk indicators, detect likely duplicates and route a review-ready task. Commercial rate selection, carrier choice, booking and customer communication should remain outside an initial intake pilot unless they are separately scoped and controlled.
Design the Reviewer Queue
- Show the structured shipment record beside its source references
- Highlight missing, conflicting and low-confidence fields
- Allow the reviewer to correct values without losing the original
- Record who approved the request and when
- Send only the approved output to one agreed task or sandbox
Test With Historical Requests First
A representative set of anonymised historical requests reveals the true variation in attachments, terminology and missing information. Testing in shadow mode allows the team to compare structured output with known cases before any live connection is considered.
