The 10 visibility questions in every 2026 freight RFP

75% of European shipper RFPs in 2026 score visibility before they go into rate negotiations. 80% require Scope 3 emissions data. This comes directly from CO3’s shipper survey. Most road freight forwarders are still addressing these questions only indirectly. Here are the ten most frequent questions shippers ask, the answers that win, and the four most forwarders fail.

Why this matters?

The RFP has changed. Until 2022, "visibility" was a bonus line. Today it is a default requirement of every serious European road freight tender, and the answer often decides who gets shortlisted before rates are even discussed. The two drivers are well documented: shippers now publish their own CO2 emission / Scope 3 reports under CSRD, and their auditors flag carriers that cannot produce primary data. At the same time, shipper TMS estates have matured — most large shippers expect ETAs to land inside their own systems, not on a separate carrier portal.

What this means for a forwarder: the visibility section of the RFP response is no longer a tick-box. It is the default, and on most lanes it is decided in the first two pages of the answer.

The 10 questions to expect — and the answers that win

1. "Do you provide live ETAs into our TMS via API?" Strong answer: name the integration pattern (REST + webhook), the update cadence, and the SLA on missed pings. Avoid "yes, we offer integration" without specifics.
2. "How do you calculate per-leg CO2, and is the methodology aligned with ISO 14083?" Strong answer: state ISO 14083 alignment, mention GLEC v3.2 as the practical interpretation, declare your primary-vs-default-data split, and offer a sample report.
3. "What proportion of your carriers can you reach via primary telematics data?" Strong answer: a single number ("82% of lane volume, 71% of shipment count") and the integration mechanism behind it. Hand-waving here is what kills shortlists.
4. "What is your named exception process and what is the SLA on it?" Strong answer: name the alert source (geofence + ETA-deviation), the routing rule (which exceptions reach an truck operator, which auto-resolve), and the response-time SLA in business hours.
5. "Show us your data-quality methodology — how do you handle missing pings, late telematics, and source disagreement?" Strong answer: declare your reconciliation logic (e.g. "most-recent-source-of-truth with a 15-minute fallback window"), provide a sample data-quality dashboard, and name the version-control policy on restatements.
6. "What audit trail can you produce if our reviewer asks for evidence on a single shipment?" Strong answer: a single-screen pack containing raw GPS, fuel proxy, lane segment, methodology version, and exception log — packaged inside two business days. This is the question that separates serious data infrastructure from a dashboard.
7. "How do you handle subcontractor visibility — both pinging and emissions?" Strong answer: spell out the consent model (subcontractor opts in via their existing telematics provider), the data-sharing scope (event-level for visibility, aggregate-level for emissions), and the GDPR position. Most forwarders have no answer here.
8. "What dashboard SLA do we get — uptime, refresh, role-based access?" Strong answer: state uptime (99.5%+), refresh cadence (≤5 min), and role-based access (shipper-side ops can see lane-level; CFO can see emissions aggregate; auditor can see the audit trail).
9. "What's your restatement policy if telematics data is corrected after the fact?" Strong answer: declare the immutable record + signed restatement model. Auditors love this answer; few forwarders give it.
10. "What does our 30-day pilot look like, and what's the kill switch?" Strong answer: a four-week onboarding plan (week 1: lane inventory; week 2: connect 80% of volume; week 3: parallel-run vs current system; week 4: shipper-side validation), with a stated exit clause. Forwarders that lead with a 12-month rollout lose to forwarders that lead with a four-week pilot.

The four most forwarders fail

Looking across 2025–26 RFPs we have seen the same four weak answers repeatedly:

• Question 3 (telematics reach). Most answers cite the number of carriers, not the share of lane volume reached by primary data. Shippers care about the latter.
• Question 6 (audit trail). Most answers describe a dashboard; auditors want a per-shipment evidence pack.
• Question 7 (subcontractors). Most answers stop at the owned-carrier layer. This is where Scope 3 reporting falls over.
• Question 9 (restatement policy). Most answers have not been thought about. This is a one-paragraph fix.

If a forwarder closes those four gaps before the next tender, the response moves from average to top-quartile without changing any operational capability — only the way it is described.

A 30-day plan to close the gaps

• Days 1–5: Inventory the lanes that account for 80% of shipper volume. Map each lane to the carrier and the carrier's telematics provider. This produces the number that answers question 3.
• Days 6–15: Connect the top-20 carriers via API or via a telematics aggregator. CO3's 500+ integration library means most of them are already wired; the work is consent and ID-matching, not engineering.
• Days 16–25: Build the audit-pack template (question 6) and the subcontractor consent flow (question 7). Both are documents and one workflow, not a system rebuild.
• Days 26–30: Run a parallel-week with the current dashboard to confirm coverage and exception SLAs. Use the parallel-week numbers in the next RFP response.

A forwarder that does this can answer all ten questions credibly in the next tender. CO3 runs this onboarding with most clients in under four weeks because the integration plumbing is already built.

What to watch over the next 12 months

• Shipper RFPs are starting to weight primary-data share explicitly (rather than asking only "do you provide CO2?"). Expect this to be standard by Q4 2026.
• The new CountEmissionsEU methodology, built on ISO 14083, might be referenced in shipper RFPs from late 2026 onward.
• Limited assurance is the current CSRD bar; reasonable assurance is scheduled from October 2028. Forwarders that build the audit trail now will be ready when shippers' auditors raise the bar.

Closing thought

The RFP visibility section is no longer a marketing exercise. It is a data-infrastructure question with a marketing wrapper. A forwarder that answers all ten questions with specifics — not slogans — moves up the shortlist before the rate column is even opened. Talk to CO3 if you want to run the 30-day plan above against your next tender.

Glossary

• RFP — Request for Proposal. Shipper-issued tender; the document a forwarder responds to.
• TMS — Transport Management System. The shipper's operational software estate.
• ETA — Estimated Time of Arrival; in a visibility context, recomputed continuously.
• ISO 14083 — international standard (2023) for quantifying transport-chain greenhouse-gas emissions.
• GLEC Framework — Global Logistics Emissions Council. Industry practical guide that maps onto ISO 14083; v3.2 was published October 2025.
• Primary data — measured fuel, distance, and load from the actual shipment (vs. industry defaults).
• Scope 3 — emissions outside a company's own operations; for shippers, road freight sits in Scope 3 Category 4.
• CSRD — Corporate Sustainability Reporting Directive (EU 2022/2464). Drives shipper emissions reporting.
• Audit trail — the per-shipment evidence pack a reviewer can request.