Freight RFP Visibility Questions: Answers a Small Broker Can Prove

You already send shareable tracking links instead of status emails to the customers you have. An RFP is a different reader: a shipper that has never worked with you, comparing your reply with brokers that have a visibility team and an EDI department. This guide covers what the visibility questions usually ask, which ones a one to five desk shop can answer today, and what to attach so the answer counts.

What does the visibility section of a freight RFP ask?

Shipper templates group it in roughly the same way. WARP’s freight RFP template for shippers puts “Real-time tracking (GPS + scan events)”, EDI, a REST API, webhooks, portal access for the shipper’s team and per shipment SLA reporting under technology requirements, and introduces that list with a blunt line: “In 2026 these are baseline, not differentiators.” Its SLA table carries “Tracking / visibility compliance” as a metric with a target. Nuvocargo’s freight RFP checklist tells shippers to specify real-time tracking and visibility systems next to TMS integration, EDI standards and escalation procedures, and gives the reason: “Carriers without adequate technology capabilities create manual work and visibility gaps that increase operational costs.”

Read across a few templates and the questions fall into four groups:

1. How you track. Method, coverage, when tracking starts and stops, how you handle a carrier that will not run it.
2. How the shipper sees it. Portal or link, EDI status messages, API or webhooks, who on their side gets access.
3. Exceptions. How a delay is detected, who tells the shipper, how fast, and who they call when it is serious.
4. Measurement. How on-time is calculated, what tracking compliance means, and what you report and how often.

The WARP template weights “Service capability” at 30 to 40% of the score and puts technology, visibility, claim handling and integration inside it. That share is decided by what you write, not by your rate.

Which questions can a small brokerage answer honestly?

Most of them, if you separate what you do on every load from what you would have to build. The last column matters as much as the second.

Scroll sideways on a phone to see all four columns.

The EDI row is where small brokers lose points by being vague. WARP’s bidder question on it comes with a note for the shipper: “On the roadmap” means 6 to 12 weeks of your implementation timeline. Expect “coming soon” to be read as no, so it costs you the point without buying you anything.

What counts as proof in a visibility answer?

The WARP template tells shippers to send the same questions to every bidder and compare the answers side by side, and then adds a sentence worth printing above your desk: “Vague answers are answers.” On API questions it tells shippers to “Ask for the API docs URL, not a slide about innovation.” A shipper cannot audit your process during a bid, so it scores what it can open.

Four attachments do most of the work:

• A sample tracking link or a screenshot of one. It shows what their team will see on day one. Take customer names, addresses and reference numbers out before you send it.
• The event timeline of a delivered load. Pickup, arrival and departure at each stop, delivery, each with a time. This answers “how do you track” better than a paragraph.
• A POD with its upload time. It shows how soon after delivery the document reaches you, and it is the document billing and claims both depend on.
• Your exception log. A short list of late loads from the last few months: what was flagged, when the customer was told, what the outcome was. A broker who wrote down the bad loads is more believable than one who claims none.

No history on the lane? Say so and attach proof from similar freight. That reads better than a claim the shipper can test in week one.

What tracking commitment should you put in writing?

If the RFP asks you to commit to update points without naming them, look at what a large broker asks of its own carriers. C.H. Robinson’s tracking expectations for its contract carriers list updates 4 hours and 2 hours before appointment close, arrival and departure updates within 30 minutes of the driver arriving or leaving, and an in-transit update at least every 4 hours. It also says how a window is read: “If pickup appointment contains a window of time, requirements are based off of close time.”

Use that as a benchmark, not a promise. Write the points your carriers already meet, and tie them to something your desk controls:

• tracking connected before arrival at the shipper, checked by your desk;
• arrival and departure recorded at every stop;
• the shipper told about a predicted late delivery before the appointment, not after it;
• POD sent within a stated time after delivery.

Your commitment to the shipper is the tracking line in your rate confirmation seen from the other side; how to get carriers to accept it is in setting tracking expectations with carriers. Expect the target to carry a consequence. WARP’s SLA section opens with “SLAs without consequences are aspirations.”

How do you answer the escalation question?

WARP’s version of the question is “What is the escalation path when a shipment goes sideways?”, and its note to the shipper describes the two answers it expects to see: “Named humans with response time commitments, or a ticket queue.” This is a question a small brokerage can answer well, because on your desk the shipper reaches a person who knows the load.

Write it as a short ladder: the rep on the load, then the owner or senior broker, each with a name, phone, email and hours. Say who picks up at night and on weekends, and what the shipper will hear from you when a load is going to be late. The late delivery conversation is the script behind that answer.

How do you answer on-time and reporting questions without years of data?

WARP asks bidders “How do you measure on-time delivery, and against what timestamp?” and warns the shipper: “Appointment time, gate time, or POD scan changes the number by several points.” Name the timestamp you use and where it comes from.

For reporting, describe what you will actually send and when: loads, on-time against your stated definition, exceptions and their causes. Ask which format and cadence the shipper wants. Building customer reports and QBRs from tracking data shows what goes into one. The WARP template also puts a 90 day performance review among the implementation milestones, so your first report after award is likely to be read closely.

You will be scored on history you may not have. DAT’s guide to RFP season notes that the shipper’s analysis “goes beyond pricing to consider on-time performance, historical tender acceptance and the ability of transportation providers to match inbound with outbound lanes”. If you have loads on similar lanes, report those numbers with the definition attached. If you do not, say how you will measure from load one.

What should you leave out of the visibility section?

• Update frequencies you have not checked. If you write a number, the shipper will hold you to it on every load, including the ones with a carrier you booked that morning.
• “100% visibility.” Say what you do when tracking drops instead.
• Technology you would buy only if you win. The WARP template warns shippers that bidders without an integration story add 6 to 12 weeks to implementation. A promise you cannot deliver by the start date is the first thing the shipper checks.
• Lanes you cannot cover with tracked carriers. DAT puts it plainly: “Nothing gets brokers in trouble faster than overpromising and under-delivering.” Its advice for small and mid-size brokers is to “Stick to your strengths and fight off the urge to bid on the entire RFP.”

A short bid on lanes you can prove is also easier to defend once you win. The WARP template describes multi-award as a primary plus a backup per lane, so a strong answer on a few lanes can still put you on the award. If you do win, the work moves to onboarding the new shipper in the first 30 days, where every line of this section is tested on real loads.

Where does LBOARD fit?

LBOARD is load tracking built for independent brokers. You enter a shipment and the driver’s phone number, with no TMS needed, and it works standalone or inside your TMS, with an optional API for McLeod, Turvo, Tai, Rose Rocket and Ascend. Shippers follow the load on a shareable tracking link, smart alerts flag risks automatically, delays and route deviations are flagged in real time, and all events are timestamped. PODs appear the moment drivers upload. Tracking is consent-based and encrypted, access is role-controlled, and load data is never sold or shared, which is worth one line in a security question. Drivers use the carrier app, which is free for them.

The first 25 loads are free with all features and no contract, which is enough to run the lanes you plan to bid and attach real proof before the due date.

Frequently asked questions

Can a small brokerage answer a freight RFP without EDI?

Yes, if the shipper does not make EDI a hard requirement. Say plainly that you do not support it today and describe what the shipper gets instead, such as a live tracking link per load and the POD sent as soon as the driver uploads it. If the template lists EDI as mandatory, skip the bid or ask the shipper before the due date whether a link is acceptable.

What should I attach to prove load visibility in an RFP?

A sample tracking link or a screenshot of one, the event timeline of a delivered load, a POD with its upload time, a short exception log and a one page escalation contact sheet. Remove customer names, addresses and reference numbers from anything taken from a real load.

What tracking update schedule should I commit to?

Commit only to points your carriers already meet. As a benchmark, C.H. Robinson asks its contract carriers for updates 4 and 2 hours before appointment close, arrival and departure within 30 minutes, and in-transit updates at least every 4 hours.

How should I answer the on-time measurement question?

Name the timestamp you measure against, such as the appointment time, the arrival event at the stop or the POD time, and where it comes from. Different timestamps can move the on-time number by several points, so a definition is worth more than a percentage.

Should a small broker bid on every lane in a freight RFP?

Usually not. Bid the lanes where you have tracked carriers and history you can show. Overpromising on lanes you cannot cover is the fastest way to lose the account after award.