When a carrier sees an access problem, the strongest first response is a clear record: what happened, when it happened, which account or broker connection was affected, what the platform said, and what business activity can actually be documented. An access restriction, a missed opportunity, and a provable cancelled load are different claims.
This guide is a practical companion to THS's Field Note, “The connection is back. Your backup plan still matters.” That earlier article addresses the public Motive–Highway incident and continuity lessons. Here the focus is the carrier's own documentation and escalation process, whether the problem involves permissions, identity, connection status, or a broker's separate decision.
Start with the current public status, then your own case
Highway's incident record identifies a Motive ELD-data connection issue beginning August 26, 2026 and marks it resolved August 28 at 3:46 p.m. Central Daylight Time. Motive and Highway published a joint statement on August 28 describing restored authorized data access and saying carriers and brokers did not need to take action for that restoration. 1 2 3
Those records support a dated public-service chronology. They do not establish the cause or outcome of every individual carrier's access problem. The companies' two publications carry the same joint statement; they are not two independent investigations confirming private losses.
A carrier reporting a later or continuing problem should therefore open a case-specific record rather than assume the public incident remains unresolved. Identify the exact screen, user, connection, or broker response involved. A broad headline can be outdated while a separate account issue still needs attention.
Describe the problem without jumping to a conclusion
Use the words displayed by the system and distinguish them from your interpretation. “The account displayed Access Disabled at 10:15 a.m.” is an observation. “The platform blacklisted the carrier nationwide” is a much broader conclusion that requires different evidence.
Record whether you could log in, view the account, see particular connections, complete a requested action, or receive a broker's confirmation. Those are separate functions. A problem with one does not prove that all others failed.
Identify the environment: date, time zone, device, browser or app, user role, and the carrier account involved. Note whether the same behavior occurred for another authorized user. Do not share passwords or security codes to demonstrate the issue.
If the platform reports no restriction while the carrier still sees one, preserve both statements. The conflict is a question to investigate, not a reason to omit the response that does not fit the initial interpretation.
Preserve original evidence before annotating it
Keep original screenshots, emails, support messages, and relevant documents in a controlled case folder. Save a working copy for highlighting or redaction, and keep the original separate. Record who captured the item and when if that information is not already clear.
Capture enough context to identify the screen and account function without exposing unnecessary personal information. A cropped warning may be useful for discussion, but the fuller original can help explain what the warning referred to. Avoid altering the underlying content.
For email, retain the original message and attachments through an authorized business process where possible, rather than relying only on a pasted paragraph. Keep the sender, recipient, subject, and timestamp connected to the content.
Do not collect information by bypassing permissions or using someone else's account without authorization. A documentation plan should strengthen the reliability of the record. It should not create a second problem through improper access or public disclosure.
Separate access evidence from load-loss evidence
An access screen can support a claim that a function appeared restricted at a particular time. It usually cannot establish, by itself, that a specific shipment was awarded, cancelled because of that restriction, and worth a stated amount of lost profit.
For a particular load, look for the offer or rate confirmation, the relevant communications, the scheduled dates, the carrier's acceptance status, the reason given for cancellation or rejection, and any subsequent correction. Preserve the broker's actual explanation rather than replacing it with an inference.
If there was only a conversation about possible work, label it a potential opportunity. If a broker says the carrier was ineligible but does not identify why, record the unresolved cause. If the carrier declined for another reason, retain that fact too.
Repeated screenshots also need careful counting. Several cards may refer to the same broker or connection. Count displayed items, unique entities, and separate incidents independently. Do not convert a screen count into a count of lost loads.
Build a chronology that another person can follow
Use one row per event: timestamp and time zone, actor, action or observation, evidence reference, response, and next step. Keep events in sequence even when later information changes the interpretation of an earlier event.
For example, an illustrative chronology might show an access warning Monday morning, a support ticket that afternoon, a broker asking for additional information Tuesday, a platform response Wednesday, and a successful retest Thursday. This is a process example, not a THS client history.
Mark the difference between a sent request and a received response. “Correction requested” is not “correction completed.” Likewise, “platform reports active” and “carrier independently retested the function successfully” are distinct milestones.
Keep an open-questions column. It may ask whether the issue affected one user or the whole account, which broker saw which information, or whether a requested troubleshooting step was performed. An honest chronology can contain unresolved questions and still be useful.
Make a support request easy to act on
State the affected carrier and account through the provider's authorized support channel, describe the specific function, provide the relevant timestamp, and attach appropriate evidence. Ask for the case number and the next action needed from the carrier.
Avoid sending a long accusation when the immediate need is to identify a technical or data issue. A focused request might ask what status is currently recorded, which authorized user can correct it, and how the carrier can confirm the correction afterward.
If a response appears to concern another case, say so precisely and ask the provider to reconcile it with the carrier identifier and evidence supplied. Preserve the incorrect response and the clarification. Do not continue citing the earlier message as if the later correction never occurred.
Record recommended troubleshooting and whether it was completed. If the carrier has not performed a suggested step, say that plainly. A support history is less credible when it attributes continued failure to the provider while omitting an outstanding action required from the carrier.
Quantify business impact carefully
Keep three separate categories: documented out-of-pocket cost, documented disruption to identified work, and estimated opportunity impact. The first may include a specific payment supported by an invoice. The second needs shipment-level evidence. The third is a scenario requiring clearly stated assumptions.
Suppose an illustrative load would have paid $1,800 and would have required $650 of avoidable trip costs. The difference is $1,150 before fixed costs, taxes, and other effects. That arithmetic is a contribution scenario, not proof of legal damages or that the load would have been performed.
Do not add every visible load-board posting to a loss total. The carrier may not have been eligible, available, selected, or able to perform all of them. Also consider replacement work and costs avoided; those facts can materially change the assessment.
If legal action is being considered, provide the complete record to qualified counsel. A demand letter states a position and requests action; it is not an adjudicated finding. Avoid presenting a threatened claim, cease-and-desist demand, or favorable response as a legal victory.
Share a useful public lesson without exposing the case file
A public article can explain the process, the dated public facts, and the questions carriers should ask. It does not need private account identifiers, driver information, unredacted broker messages, or confidential attorney communications to be useful.
Obtain the necessary authorization before using a private case as a named example. Have the appropriate reviewer check factual accuracy, privacy, contractual restrictions, and any active legal issues. Include material responses and corrections rather than publishing only the initial allegation.
For Facebook discussion, ask about process: what evidence helped others understand the issue, which status was unclear, or how the carrier verified restoration. Do not invite members to post private records or accuse named parties without support.
A strong educational case earns attention by helping owners make a better decision. It does not need a claim that THS proved wrongdoing or recovered losses unless those outcomes are documented and approved for public use.
Close the issue with a repeatable verification step
After a reported correction, repeat the affected action through the authorized account and record the result. If the issue involved a broker's view, request confirmation from that broker through an appropriate channel rather than assuming the carrier's screen shows the same information.
Record what changed, who confirmed it, and what remains open. A technical connection may be restored while a billing question, private dispute, or separate onboarding decision remains unresolved. Closing one item should not erase the others.
Review the business's continuity plan. Identify authorized account owners, backup access, provider contacts, permission reviews, and the records needed if another interruption occurs. Do not bypass required verification or misrepresent carrier identity to keep work moving.
The next incident should be easier to describe because the business already knows where its records are and who can act. That is a practical improvement even when the provider, cause, or outcome differs.
A carrier documentation checklist
- Capture the exact status, function, account context, timestamp, and time zone.
- Preserve original evidence separately from annotated or public copies.
- Maintain a chronology of requests, responses, corrections, and outstanding actions.
- Separate displayed restrictions, unique connections, and identified shipments.
- Support any load-impact claim with shipment and communication records.
- Label estimates and assumptions, including avoided costs and replacement work.
- Retest after correction and record what is closed and what remains open.
Questions carriers ask
Does an access-disabled screenshot prove lost loads?
It can support an observation of restricted access, but shipment-level loss requires additional evidence. Identify the load, acceptance status, reason given for the change, timing, and financial assumptions. Do not equate a screen count with cancelled shipments.
Does the public Motive–Highway resolution close my private issue?
Not necessarily. The public record addresses the identified service incident. A carrier with a continuing account-specific issue should document that issue, follow the authorized support process, and verify the result separately.
Can a demand letter be used as proof that a platform acted unlawfully?
No. A demand letter presents claims and requests. Legal conclusions and remedies require appropriate analysis and process. Public content should distinguish allegations, verified facts, responses, and unresolved questions.
What should I send THS initially?
Start with a short description, relevant dates, the affected function, and the decision or documentation problem you need help organizing. Agree on an appropriate channel before sharing sensitive records or attorney communications.
Turn the problem into a clear next action
Ask THS about organizing an administrative issue review, chronology, and evidence index. THS is a transportation consulting, business-development, and administrative-services company, not a motor carrier, platform operator, or law firm.
Any support requires an agreed scope and terms. THS cannot promise broker access, restored accounts, freight, recovered revenue, or a legal result. The useful deliverable is a clearer record that helps the appropriate party understand and act on the actual issue.
Sources
- Highway. Incident: Load Tracking Disruption Affecting Carriers Connected via Motive. 2026-08-26 to 2026-08-28 (incident updates). Verified 2026-09-15.
- Motive. Motive and Highway Reach Agreement. 2026-08-28. Verified 2026-09-15.
- Highway. Highway and Motive reach an agreement to ensure continuity of service for carriers and brokers. 2026-08-28. Verified 2026-09-15.