Paper Log Request Denied: Keep Your ELD Plan
The paper log request was denied. Check the official decision before changing your fleet’s ELD procedure.
FMCSA has rejected a request to let professional drivers choose paper logs instead of an electronic logging device. The final-disposition notice for the Federation of Professional Truckers, or FOPT, is scheduled for Federal Register publication on September 30, 2026. The immediate operational consequence is straightforward: this application gives a carrier no new permission to disconnect its ELD or switch its drivers to manual records.
A denied request is not a new operating option
The decision concerns docket FMCSA-2025-1282. FOPT had sought flexibility for its members and other drivers who wanted to participate. FMCSA concluded that the application did not establish safety equivalent to or greater than the existing requirements. The agency also pointed to the congressional ELD mandate and said it could not grant a blanket exemption to any driver or carrier that wished to opt out.
For a small fleet, the useful distinction is between a request, a decision and an existing exception. A request describes what someone wants changed. A final decision states what the agency actually granted or denied. An existing exception has its own eligibility conditions. Those are separate documents with separate purposes; a headline about one cannot establish eligibility under another.
Why the proposed safeguards were not enough
FOPT proposed education on accurate paper-log completion, random internal audits by participating carriers and exclusion of drivers who violated hours-of-service limits. FMCSA said the proposal extended beyond the organization's membership without explaining how those safeguards would reach an unknown population or how violators would be excluded. That gap was part of the agency's explanation, not a finding that every individual paper-log operation is unlawful.
The notice records 901 public comments, including 890 unique comments, with most individual commenters supporting the request. Support in a comment docket is not an authorization. An operator reviewing social posts about the case should check the agency's disposition before changing a compliance procedure, even when a post accurately describes widespread support for the proposal.
What a dispatcher should verify now
The following is an editorial workflow for handling this announcement, not an additional federal reporting requirement. First, identify whether anyone in the fleet changed plans because they expected the application to be approved. A driver, dispatcher and outside service provider may each have heard a different version. Send the same official decision to whoever maintains the company's logging procedures so that a proposed change does not quietly become a dispatch assumption.
Second, separate the method of recording work from the work itself. This denial does not create additional driving hours. Changing a screen, a subscription or a notebook does not by itself change the hours available for a shipment. Review actual driver availability before accepting a delivery window, rather than treating a different recording method as extra capacity.
Third, review any claim that an individual operation already qualifies for an exception on its own terms. The notice cites the existing provision concerning drivers who need records of duty status on no more than eight days in any thirty-day period. That reference is not a blanket exemption for all small fleets. Ask the compliance lead to verify the full applicable rule and the actual operating history before making a change.
A short internal checklist
- Save the final decision. Keep the September notice with the earlier application so the outcome is visible beside the original request.
- Check the proposed action. Is someone planning to remove a device, cancel service or change the logging procedure? Pause a change based only on this denied application.
- Identify the actual authority. If a separate exception is claimed, record which provision applies and who checked eligibility. Do not use an organization's membership as a substitute.
- Align dispatch instructions. Make sure the driver receives the same instructions as the person who accepted the load.
- Keep technical problems separate. A device malfunction needs the applicable malfunction process; it does not turn this rejected request into permission.
For example, a two-truck company could have postponed renewing a service contract while waiting for the decision. The practical next step is to review its actual requirements and contract options with its compliance contact, not to assume that company size settles the question. This is a hypothetical planning example, not a reported case from the docket.
Preventive planning includes checking the paperwork as carefully as the equipment. Find preventive-maintenance resources at The Truck Savers™. Read the official notice before changing a logging procedure.
Illustrative stock photograph: Gustavo Fring / Pexels. The person shown is not identified as an applicant, FOPT member or subject of this decision.