Blue Bird Buyers Ran 38% More RFQs Without Adding Headcount

A sourcing file does not fail because the buyer lacks a spreadsheet. It fails because the quote, the supplier document and the rule for running the bid sit in different inboxes, and an audit has nowhere to look. That was the break at Blue Bird, which has built school buses in Fort Valley, Georgia, for nearly 100 years.

The Bid Had No System of Record

Until the change, requests for quote went out by email, spreadsheets moved back and forth, and each site followed its own process. With no system of record, quote history and supplier documents sat in individual inboxes. Buyers had no standard way to build or run an RFQ. The compliance team had no central repository for an audit. In a case submitted to The Supply Chainer, Blue Bird moved sourcing onto LightSource, which the submission says now holds item data, supplier quotes and communication. The purchasing team built a library of bid templates, trained every buyer to run projects the same way, and onboarded 398 supplier companies. Nearly all, 99.7%, activated their accounts. Every project now leaves a documented trail.

Blue Bird moved sourcing onto LightSource, now holds item data, supplier quotes and communication

Throughput Moved Without More Buyers

The submission puts the result in throughput. RFQs per buyer rose 38%, from 34.9 to 48.3, with no added headcount. Average sourcing cycle time fell from 16 days to 14. Buyers launch a project in under 20 minutes on average. The team has run 291 projects through the platform so far in 2026. With less time on administration, the file says, buyers can focus on supplier relationships.

The limit on what a record can do is already on the file from another operator. In The Supply Chainer's piece on procurement data, Kristian O'Meara, chief commercial officer at Pairsoft, said: "Visibility does not automatically translate into action. The biggest disconnect between insight and execution occurs when organizations treat data as something to analyze rather than something that can actively drive business processes. Many companies have dashboards that identify issues, but they still rely on people to interpret findings, coordinate across functions, and manually execute next steps."

A documented sourcing record does not, by itself, keep approvals moving. Michael Petter, Director at Eyvo, told The Supply Chainer that the next bottleneck often appears when a request changes hands: “An urgent operational purchase is most likely to stall at the handoff from the manager who understands the immediate need to the next budget owner or policy approver.” Important context can disappear at that point, he said, leaving the request in a queue, particularly when the designated approver is unavailable. That is a separate challenge from organizing bids: the file may be complete while the decision still waits.

Petter recommends a visible, time-bound exception process that identifies the approval owner, shows how long the request has been waiting and notifies the appropriate person. Once an agreed time limit is reached, a pre-authorized delegate or escalation path can keep the purchase moving. The process should preserve budget checks, spending limits, required sign-offs and the audit trail. As Petter put it: “It removes idle time, not control.”

The Trail Is the Compliance Change

The two-day cut is the cycle. The operational change that matches the complaint is the trail: one record, one template, 398 suppliers on the system, and a project that can be launched in under 20 minutes. The submission does not give a savings figure or a part-price change. It does show a buyer running more bids, on the same headcount, with a file an audit can open.