Sep 16, 2026
.webp)
Most safety coordinators who have heard of the coercion rule assume it applies to them the way most regulations do: if you did not threaten anyone, you are fine. That assumption is correct for coercion under 49 CFR 390.6. It is wrong for the narrower, ELD-specific rule sitting one section away. Under 49 CFR 390.36, a carrier can be found to have committed harassment without ever threatening a driver, without taking any adverse action, and without intending to pressure anyone at all. If the driver complied with an instruction and an hours-of-service violation resulted, and the ELD data connects the two, that alone can meet the standard. For anyone building the dispatch habits and alert workflows that touch this exposure daily, eld support can walk through how your specific setup handles the record-keeping side of it.
The distinction between these two rules gets flattened constantly in casual conversation, and the flattening is where carriers get exposed without realizing it.
Coercion under 390.6 prohibits a motor carrier, shipper, receiver, or transportation intermediary from coercing a driver to operate in violation of the federal safety regulations. It requires an actual mechanism of pressure: a threat to withhold business, employment, or work opportunities, a threat of adverse employment action, or actually taking either of those actions, done specifically to induce the driver to violate the rules or to punish them for refusing. FMCSA describes the sequence as three steps. A carrier, shipper, or broker requests something that would violate a regulation. The driver objects, in writing or verbally, explaining they cannot comply without violating the rule. If the requesting party proceeds anyway with a threat or an adverse action, that is coercion.
Harassment under 390.36 is different, and it applies specifically where ELD data is involved. FMCSA's own guidance states the distinction plainly: a carrier can be found to have committed harassment if the driver commits a specified underlying hours-of-service violation based on the carrier's actions, and there is a connection to the electronic logging device, and critically, adverse action is not required, because the driver complied with the carrier's instructions. Coercion needs a threat and a refusal. Harassment needs compliance and a resulting violation, with the ELD as the evidentiary link between the instruction and the outcome.
This means a dispatcher who never threatens anyone can still generate carrier exposure under 390.36 simply by pushing a driver toward a delivery window that the driver's remaining hours cannot legally support, if the driver goes ahead and the ELD confirms the violation.
The scenario that creates this exposure rarely looks like coercion in the moment. It looks like ordinary dispatch communication under ordinary time pressure.
A driver is running short on hours. A load is behind schedule. A dispatcher sends a message, by text, by the carrier's messaging system, or through the ELD platform itself, asking the driver to push to the delivery point rather than take the required break. No threat is made. No one says the driver will lose the load or face discipline for refusing. The driver, wanting to be seen as reliable, complies. The ELD records the resulting hours-of-service violation automatically, exactly as it is designed to. At that point, the elements of 390.36 harassment are arguably present: an instruction connected to an ELD-recorded violation, and compliance rather than refusal.
The dispatcher in this scenario likely believes they did nothing wrong, because in their understanding of the rule, that would be true, if the applicable rule were 390.6. It is not. The absence of a threat protects against coercion. It does not protect against harassment, because harassment was built specifically to cover the situation where pressure is implicit rather than stated outright, and where the driver's compliance, not their refusal, is what generates the violation.
The same record that exposes a carrier in this scenario is also the carrier's best protection when the underlying decision was legitimate. This is the part of the ELD relationship to compliance risk that gets discussed the least, because most ELD content treats the device purely as a recording tool for HOS accuracy, not as evidence in a dispute that has not happened yet.
Consider the same scenario with one difference: the dispatcher's message includes the driver's actual remaining hours, states clearly that the driver should stop and take the required break if the delivery window cannot be met safely, and the resulting decision to continue was the driver's own choice made against that instruction. The ELD data plus the message record together show a carrier that gave the driver an out. That is a materially different position than a message that only conveys urgency with no acknowledgment of the hours constraint.
This is the same principle already covered from the litigation side in the guide on ELD data retention and spoliation after a crash: the record you keep, and how completely you keep it, determines whether you are defended by your own data or condemned by it. A 390.36 complaint runs on the same logic. FMCSA's complaint guidance explicitly encourages drivers to submit documentation including text messages, emails, and ELD records. A carrier whose dispatch communications are undocumented, inconsistent, or deleted is not protected by the absence of a paper trail. It is exposed by having nothing to show the instruction was reasonable.
The practical fix here is not a policy document nobody reads. It is a small number of specific habits built into how dispatch actually communicates under time pressure, which is exactly the condition under which this exposure occurs.
Any message pushing a driver toward a tight delivery window should reference the driver's actual remaining hours rather than assume them, and should explicitly state that the driver's legal limits take priority over the schedule. This is not a legal formality. It is the difference between a message that could later be read as pressure and one that plainly is not. Dispatch communications connected to load timing should happen through a channel that is retained, not a personal phone that gets wiped or a call that leaves no record. And the alert configuration that already governs how your operation catches an approaching HOS limit, covered in the guide on ELD compliance dashboard alerts, is the same infrastructure that determines whether dispatch even knows a driver is close to a violation before sending the next message. A dispatcher who cannot see a driver's remaining hours at a glance is a dispatcher more likely to push blind and create exactly the pattern 390.36 was written to catch.
None of this requires treating every dispatch conversation as a legal risk. It requires treating the ELD record as something that will be read after the fact, by an investigator or by FMCSA reviewing a complaint, and building communication habits that hold up under that reading.
A driver alleging a violation of 390.6 or 390.36 has 90 calendar days from the incident to file a written complaint with FMCSA, submitted to the National Consumer Complaint Database or the Division Administrator for the state where the driver is employed. The complaint is expected to include the driver's contact information, the identifying details of the carrier or party involved, the specific regulation alleged to have been violated, and documentation of the act, which FMCSA explicitly lists as including text messages, emails, and ELD records.
The reason this matters to a carrier is not the filing mechanics themselves, which belong to the driver's side of the process and are well covered elsewhere. It is the 90-day window. A carrier's own retention and communication records need to survive at least that long intact, ideally longer, because a complaint can surface weeks after the underlying event, well after the pressure of the moment has been forgotten by everyone involved except the record.
The coercion and harassment rules are not new, the underlying framework dates to 2016, but 2026 has brought renewed attention to them, tied directly to the same enforcement environment driving the current wave of ELD device revocations. Industry commentary has described this period as a return to the rule's original purpose: preventing chameleon carriers, pressuring brokers, and unprincipled shippers from pushing drivers into violations, at the same time FMCSA is aggressively removing non-compliant devices from its registered list. The pattern of providers operating under former names, documented in the analysis of the FMCSA revoked ELD list, and the broader question of what happens when an ELD provider disappears entirely, sit inside the same enforcement climate as the renewed coercion and harassment guidance. FMCSA is treating the bad-actor problem across several fronts at once, and a legitimate carrier operating in that environment benefits from understanding all of them rather than assuming coercion enforcement is a separate concern from device compliance.
The useful version of this is short. Confirm that dispatch messages involving tight delivery windows reference actual remaining hours rather than generic urgency, and are sent through a channel your operation retains rather than one that disappears. Confirm that your safety coordinator, not just your dispatch team, understands the difference between coercion and harassment, since the absence of a threat is not a defense to the rule that actually applies most often to ELD-connected situations. And confirm that your platform's reporting can produce a clean, dated record of both the HOS data and the relevant communications if either is ever requested, since a 90-day complaint window means the record you need may already be a month old by the time you learn a complaint exists.
The compliance reporting tools that already generate your HOS violation summaries are the same infrastructure that supports this kind of after-the-fact review, provided the underlying communication habits give them something worth reviewing.
If you want to see how a platform's reporting and retention would actually hold up if a dispatch decision were ever questioned, start a free 14-day trial of AI ELD and run it against your real dispatch workflow rather than a hypothetical one.
eCFR. "49 CFR 390.6: Coercion Prohibited." Primary regulatory source for the coercion rule, its applicability to motor carriers, shippers, receivers, and transportation intermediaries, and the requirement that coercion involve a threat or an actual adverse action. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-390/subpart-A/section-390.6
eCFR. "49 CFR Part 386: Rules of Practice for FMCSA Proceedings." Primary regulatory source for the separate complaint procedures governing 390.6 coercion complaints and 390.36 harassment complaints, including the 90-day filing window and the confidentiality protections for complainants. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-386
FMCSA. "FAQs: Prohibited Coercion of CMV Drivers." Primary source for the definition of coercion, the three-element sequence of a coercive action, and the 90-day complaint filing requirement to the National Consumer Complaint Database or the Division Administrator. https://www.fmcsa.dot.gov/regulations/faqs-prohibited-coercion-cmv-drivers
FMCSA. "FMCSA-HOS-ELD-395-FAQ66: Differences Between Harassment and Coercion." Primary source for the specific regulatory distinction this article is built on: that a 390.36 harassment finding requires a specified underlying HOS violation connected to the ELD, and does not require adverse action, because the driver complied. https://www.fmcsa.dot.gov/sites/fmcsa.dot.gov/files/2022-03/FMCSA-HOS-ELD-395-FAQ66%282017-04-06%29-CORR1.docx
Overdrive. "How to File a Coercion or Harassment Complaint." Source for the practical documentation FMCSA expects in a complaint, including text messages, emails, log screenshots, and ELD records, and the distinction drivers are advised to make between citing 390.6 and 390.36 depending on the circumstances. https://www.overdriveonline.com/business/article/14897215/how-to-file-a-coercion-or-harassment-complaint
FleetOwner. "Trucking Industry Revisits Coercion Rule as FMCSA Ramps Up ELD Enforcement Actions." Source for the 2026 enforcement context connecting renewed coercion rule attention to the broader ELD compliance crackdown and chameleon carrier enforcement. https://www.fleetowner.com/safety/blog/55377897/trucking-industry-revisits-coercion-rule-as-fmcsa-ramps-up-eld-enforcement-actions
CDLLife. "FMCSA's New Guidance Tells Truck Drivers What to Do If They're Pressured to Violate Safety Rules." Source for FMCSA's 2026 coercion FAQ guidance update and the agency's stated purpose in reissuing driver-facing guidance on the rule. https://cdllife.com/2026/fmcsas-new-guidance-tells-truck-drivers-what-to-do-if-theyre-pressured-to-violate-safety-rules/
AI ELD. "ELD Records Retention and Spoliation After a Crash." Source for the underlying principle that the completeness of a carrier's own records determines whether they are defended or exposed by that data in a later dispute. https://ai-eld.com/insights/eld-retention-spoliation-after-crash
AI ELD. "ELD Compliance Dashboard Alerts." Source for the alert configuration that determines whether dispatch has visibility into a driver's remaining hours before communicating about a delivery window. https://ai-eld.com/insights/eld-compliance-dashboard-alerts
AI ELD. "The FMCSA Revoked ELD List: What the Record Actually Shows." Source for the current enforcement environment and provider naming patterns referenced in the discussion of why coercion enforcement is resurfacing alongside device revocation activity. https://ai-eld.com/insights/fmcsa-revoked-eld-list-record