Fake Rate Confirmations: A Broker’s Document Review Workflow

Quick Answer

A revised rate confirmation arrives while the warehouse is loading. The carrier name looks right. The load number is familiar. One small detail has changed: the dispatcher wants your team to use a new phone number.

In this article

That change deserves its own review. Fake rate confirmations can contain correct shipment details while carrying an instruction nobody approved. Brokers need a clear way to separate routine edits from changes that shift control of a load.

The workflow below is a practical operating recommendation. Adapt it to your customer agreements, carrier procedures, and shipment needs.

Review fake rate confirmations against the approved version

Keep the original rate confirmation and each later version. Give every revision a time and a clear status: received, under review, or approved. Avoid saving the newest attachment over the old one.

Compare the changed document with your own shipment record. Review these fields first:

  • Carrier legal name and identifying numbers
  • Dispatcher name, email address, and phone number
  • Driver and equipment assignment
  • Pickup reference and facility details
  • Delivery location and appointment
  • Instructions about who may make further changes

Ask what changed, who requested it, and whether that person had authority to make the change. A new document should not quietly become the approved source for every field it contains.

Handle the file before reviewing its contents

A rate confirmation is supposed to explain a shipment. If a message requires an unfamiliar download, a new program, or a login through a supplied link, stop and use your company's security process.

Do not test a suspicious attachment on a personal phone or forward it to coworkers asking them to try opening it. Preserve the message in the approved way and send it to your IT or security contact. Ask the sender for a safe copy through a previously established channel if appropriate.

The FBI's business email compromise guidance warns that criminals can gain access to real email threads. That means a familiar conversation does not make every new file safe.

Give each changed field an approval owner

A different rate, dispatcher, delivery address, and payment destination raise different questions. Assign the relevant person to each review instead of asking one employee to accept the whole document.

For example, operations may confirm the driver assignment. The customer account owner may confirm a destination change. Finance may review payment instructions. A single reply saying “looks good” should not leave everyone guessing which fields were checked.

For changed contact details, use your separate contact-verification procedure. Do not rely only on a phone number printed in the disputed document. FMCSA's fraud guidance recommends independent phone checks and careful document review.

Record the old value, proposed value, reviewer, and decision for each material change. If only one field is approved, keep the remaining changes pending. A clean logo or professional layout adds no missing authorization.

Control release while the question is open

If pickup has not occurred, tell the facility exactly which approval is pending. Use your agreed release procedure so a warehouse employee does not receive one instruction from dispatch and another from sales.

If the truck is already loaded, involve the operations lead immediately. Establish the actual release status with the facility. Coordinate any next step with the responsible parties and site staff. Never ask warehouse workers to confront a driver or take unsafe action.

CargoGuard's driver verification workflow supports review of license details, selfie checks, and truck registration. Those details can help compare the arriving person and vehicle with the assignment. Your team still needs to confirm who authorized that assignment.

Treat payment edits as a separate decision

A dispatch change may arrive alongside new payment instructions. Do not approve both because one explanation sounds reasonable.

Route bank, factoring, or payment changes to the staff responsible for those checks. Keep the shipment moving only when its own authorization questions are resolved. A dispatch employee should not be pushed into approving a financial change to avoid a missed pickup.

Close the loop with every affected team

Consider this training example: a revised confirmation introduces a new dispatcher, but the established carrier contact says the original dispatcher still controls the load. Your team should preserve both documents, mark the new version unapproved, and investigate the discrepancy. It should not silently delete the attachment and assume the issue is finished.

Once a legitimate change is confirmed, update the shipment record. Tell the facility, account owner, and next dispatch shift which version applies. Remove outdated instructions from active work queues while keeping their history.

Review the CargoGuard platform to see how tracking, pickup photos, and shipment documents can support that shared review.

A useful rule is simple: a revised rate confirmation starts a review. It does not complete one. Book a CargoGuard demo to explore how driver and shipment records fit your approval process.

Add CargoGuard as a preferred source on Google