A coercion complaint needs the request and the response

An unsafe assignment can become a difficult story to reconstruct after the messages disappear. What was the driver asked to do, what rule did the driver say would be violated, and what happened after the objection? Those are different facts, and a complaint needs their sequence. This resource explains existing federal coercion reporting requirements and offers an editorial method for keeping that account usable. It reports no new enforcement case and makes no finding about any driver, carrier, broker, shipper, or receiver. The nationally useful task is to preserve the actual exchange while keeping an internal safety discussion separate from a government filing.

The federal definition is more specific than an unpleasant dispatch conversation. In 49 CFR 390.5T, coercion includes a threat involving work, business, employment, or adverse employment action intended to induce prohibited operation after the driver has stated, at least generally, the regulation that would be violated. It also includes actual punishment for refusing such operation. Section 390.6 prohibits covered conduct by carriers, shippers, receivers, transportation intermediaries, and their representatives; an additional set of commercial regulations applies to coercion by carriers. Editorial inference: a disagreement over a rate or an inconvenient appointment, standing alone, does not establish those elements. Record the regulatory concern rather than replacing the facts with a label.

FMCSA's April 2026 FAQs organize the account around the request, the driver's objection, and a direct or implied threat or negative action. The objection can be verbal or written. The driver need not commit the underlying violation, and a threat need not be carried out for coercion to occur. The agency gives examples involving denied loads, reduced miles, or threatened pay penalties. It recommends keeping ELD communications, emails, and texts, and writing a prompt account of a conversation while memory is fresh. These FAQs explain the agency's approach; FMCSA expressly identifies them as guidance rather than an independent binding requirement.

Make a chronology that another person can follow. Editorial inference: identify the assignment and who made it; record when, where, and through which channel the instruction arrived; preserve the driver's reply explaining the anticipated violation; and retain the subsequent threat or action. Keep the surrounding messages, not only an isolated sentence, along with available assignment records and relevant duty-status or equipment information. Separate words remembered from words preserved in a message, and identify witnesses without guessing what they heard. Keep lawful copies of records already available to you, retain originals, and describe missing material honestly. The objective is a faithful account, not a more dramatic one. Gather it only when safely stopped, away from driving or an active work hazard.

A formal complaint has its own clock and required contents. Under 49 CFR 386.12(c), the driver must file a written coercion complaint no later than 90 days after the event through the National Consumer Complaint Database or the FMCSA Division Administrator for the state where the driver is employed. The driver must sign it and include the driver's name, address, and telephone number; the alleged coercer's name and address; the regulations allegedly involved; and a concise, complete factual statement with each alleged violation's date. FMCSA determines whether the complaint meets the requirements and is non-frivolous, then investigates qualifying complaints. For filing information, the published contact is 1-888-368-7238. A company incident number or an unsent draft does not demonstrate that the agency received a complaint.

Protect the filing trail as carefully as the incident trail. Editorial inference: put the event date and filing deadline beside the chronology, check the signature and required fields, retain a copy of the submitted complaint and attachments, and save the submission acknowledgement or delivery evidence. Do not assume a supervisor's investigation changes the federal deadline. If several incidents occurred, list their dates individually instead of collapsing them into the last conversation. Be realistic about confidentiality: section 386.12(c)(3) says prosecution of coercion requires disclosure of the driver's identity and describes protections the agency will pursue. That is not a promise that an accused party can never learn who complained.

Employer retaliation raises a separate route. OSHA administers Surface Transportation Assistance Act retaliation complaints for covered employees. Under 29 CFR 1978.103, a person who believes an employer retaliated in violation of STAA may file, or have someone file on their behalf, within 180 days after the alleged violation. OSHA accepts oral or written complaints; no particular form is required, and a complaint need not be in English. Those procedures differ from FMCSA's signed written coercion complaint. Editorial inference: preserve the date and nature of any later employment action and evaluate the appropriate channel promptly; do not treat one agency's deadline or submission receipt as proof that a different claim was filed. Whether a particular worker, refusal, or action qualifies depends on the applicable law and facts.

A fleet can make this process easier to understand before a dispute arises. Editorial inference: brief dispatch and customer-facing staff on how to receive a specific regulatory objection, provide an accessible safety escalation contact, preserve relevant communications when an allegation is raised, and avoid threatening work opportunities to obtain unsafe operation. An internal review should hear the account and address the operating concern without demanding that the driver withdraw an external complaint. For drivers, the practical record is a sequence: request, stated objection, response, event date, and filing evidence. That sequence helps an investigator assess the allegation and helps a carrier examine its decisions without confusing a claim with a proven finding.