Freight Brokerage
Edge Logistics lawsuit alleges customer diversion and freight-charge kickbacks
· Source: FreightWaves
Chicago-based Edge Logistics sued rival Freight Tec Management Group, four former employees and three related companies, alleging that they diverted expedited-freight customers and used kickbacks funded by inflated freight charges. Lawyers for the former employees disputed the allegations.
Summary and practical context by RoadHouse Recruiting · Reviewed

The complaint describes an alleged coordinated transfer
The federal complaint, filed September 30 in the Northern District of Illinois, alleges that employees formed competing businesses while still working for Edge and arranged to move customer accounts before resigning.
Edge reports a sharp decline in one division
Edge alleges its expedited division declined 66.4% within weeks of the departures while the rest of its business grew 8.5%. The complaint does not identify whether the decline refers to revenue, shipments or another measure.
The claims have not been adjudicated
Counsel for the former employees and related companies told FreightWaves that the clients dispute the allegations and their legal sufficiency. The lawsuit is pending, and the claims should not be treated as established facts.
Understanding the update
This is a report about disputed allegations in a pending federal civil case, not a finding of liability or criminal charge.
What it means for drivers and carriers
Brokerages should review access controls, customer-data permissions, employee exit procedures and audit trails for pricing changes and agent payments.
Questions to consider
- Who can export customer and pricing data?
- Are unusual margin changes and agent payments independently reviewed?
- Do employment and agency agreements clearly address confidential information?
Read the original reporting
This page provides an original summary and practical commentary. The linked source contains the full reporting. Older stories reflect information available on their published dates.
Read the source at FreightWaves ↗ (opens in a new tab)