Published: September 18, 2026.
A carrier signs more authorization documents than it realizes. A permitting service registers overweight loads. A registration agent handles apportioned plates. A factor receives an assignment of receivables. A tax preparer files quarterly returns. Each of those relationships usually rests on a signed letter, a power of attorney, or an appointment. When the relationship ends, the paper often lingers, and so does the authority it grants.
List every authorization the carrier has granted
Start with a full inventory. Pull the current file for registration, permitting, tax, insurance, factoring, and any third party that files or signs on the carrier's behalf. List each authorization with the recipient, the document title, the date signed, the scope, and any expiration date.
Include authorizations that are easy to overlook: state-specific permits, IRP and IFTA agent appointments, UCR service agreements, and any letter naming a person to act for the carrier in a portal. If a service uses the carrier's credentials rather than a signed letter, record that as an access relationship and note who holds the login.
State the scope in plain language
An authorization that says "to act on the carrier's behalf" is too broad to manage. Write a short scope note for each document: what the recipient may do, for which period, and for which jurisdictions or accounts. That note makes it possible to spot an authorization being used outside its intended purpose.
The scope note is not a legal interpretation. It is a summary of what the document says, written so an office can compare activity to authority. When the wording is unclear, flag it for the carrier's owner or counsel rather than guessing.
Track expiry and renewal
Many authorizations expire, and some agencies require renewal filings. Put the expiration date on the register and on the office calendar. Set an alert well before the date so renewal decisions are not made in a panic.
When a renewal is due, confirm the carrier still wants the arrangement. A registration agent that was useful two years ago may no longer be needed. Renewing by default keeps paying for access the carrier has outgrown.
Control and document revocation
The highest-risk moment is a separation. A service is fired, an agent's contract ends, or an employee who held a portal login leaves. The register should drive a short, dated revocation checklist: send written notice to the recipient, revoke portal credentials, confirm the counterparty acknowledged the revocation, and update the register.
Keep proof of each step. A revocation that was sent but never acknowledged can leave the carrier exposed if the former agent files something later. Record the date the authority truly ended, not just the date the carrier decided to end it.
Reconcile activity against authority
Quarterly, compare what each authorized party actually did to what it was permitted to do. Look for filings, registrations, or correspondence that appear outside the stated scope or after an expiration date. Flag anything unusual for the carrier's owner.
This reconciliation catches quiet problems. For example, an agent that continues to renew a service the carrier cancelled, or a former factor that still receives an assignment instruction.
Keep credentials and documents in restricted storage
Authorization letters and portal credentials are sensitive. Store them in a restricted location with limited access, not in a shared inbox or an open drive. Limit who can request a new authorization, and require the carrier owner's approval before anything is signed or filed.
For electronic signatures, confirm the carrier's policy on who may sign and how signatures are recorded. An assistant should never sign a filing on the carrier's behalf unless the carrier has explicitly authorized it and the process permits it.
Keep a current copy for every counterparty
The register is only as good as the documents behind it. Store a legible copy of the signed authorization, not just a note that one exists. When a counterparty asks for proof of authority, the office should be able to produce the exact document the carrier signed, with the correct date and scope. If a copy is missing, mark the register entry incomplete and request it before the next renewal.
Version control matters here too. When an authorization is renewed with different terms, add the new version and mark the old one superseded. A single summary line that overwrites the prior terms erases the history a dispute may depend on.
Questions teams usually ask
Who can approve a new authorization?
The carrier's owner or an officer with authority under the company's policy. The office prepares the document and routes it for signature; it does not grant authority on its own.
What if a document has no expiration date?
Treat it as indefinite for tracking but review it at least annually. Indefinite authority is exactly the kind that becomes stale and dangerous.
Should the register include portal logins?
Yes, as an access relationship separate from signed letters. Track who holds the login, what it can do, and when it was last reviewed, and revoke access promptly when the relationship ends.
How does this help a virtual assistant relationship?
A clear register lets a carrier grant a virtual assistant defined, documented access for specific tasks, and revoke it cleanly if the scope changes. That protects both parties.
An authorization letter register is a simple list that prevents a serious problem: someone acting in the carrier's name after the carrier stopped wanting them to. In document control, the quiet lists do the most work.
Want help building and maintaining this register? Contact our team to discuss how a trucking virtual assistant can support your document control.