Compliance
Guides

You finally have authority, the truck is moving, freight is being booked, and then another federal acronym lands on the desk: New Entrant Safety Audit.

The useful response is not panic and it is not a giant folder built the night before documents are due. FMCSA’s New Entrant Program is designed to determine whether a new motor carrier has basic safety management controls in place and can support those controls with records.

FMCSA monitors a new entrant during its initial 18-month New Entrant period. A Safety Audit is conducted within the first 12 months after operations begin. The audit may be conducted at the carrier’s place of business or offsite through an electronic document-review process, depending on how FMCSA assigns the audit.

What the audit is actually looking for

A Safety Audit reviews records and operating practices to determine whether the carrier has basic safety management controls that support compliance with applicable Federal Motor Carrier Safety Regulations and, where relevant, Hazardous Materials Regulations.

That word applicable matters. Not every carrier has the same drivers, freight, equipment, authority, testing obligations, or record set. Do not copy another carrier’s binder and assume every tab belongs in yours.

For the records that do apply, an auditor may review material related to drivers, vehicles, hours of service, drug and alcohol requirements, maintenance, crashes, operating credentials, and other safety-management controls.

Build the driver record before the audit letter

Driver qualification questions are a common source of confusion because a one-truck owner-operator may be both the motor carrier and the driver. That does not mean the carrier-side record disappears. Where Part 391 applies, the carrier still needs to identify the records required for the driver and maintain the file according to the current rule.

A useful review starts with the actual driver and operation. Determine which qualification requirements apply, then identify the evidence: applications or inquiries where required, driving-record information, qualification documentation, medical qualification where applicable, road-test documentation or permitted equivalents, and recurring reviews required by the current rule.

If you cannot establish whether a record exists or is current, mark it Unknown. Do not create completion by memory.

Hours of service need supporting records, not confidence

Where hours-of-service and ELD requirements apply, the carrier should be able to retrieve the relevant records of duty status and explain the supporting record system around them.

Fuel receipts, toll information, shipping documents, dispatch records, repair records, or other time-and-location evidence may help establish whether the record tells a coherent story. The important point is not to collect every receipt in North America. It is to retain and organize the records the current requirements and your operation call for.

An ELD dashboard that says everything looks fine is useful operational information. It is not a substitute for knowing where the underlying records are and how they are produced when requested.

Drug and alcohol obligations depend on who is actually in scope

Do not treat “drug consortium” as a universal New Entrant checkbox. First determine whether the driver and operation are subject to the applicable Part 382 drug-and-alcohol requirements.

For an owner-operator who is subject to those requirements, FMCSA requires participation in a consortium/random testing pool and requires a C/TPA to perform certain Clearinghouse functions on the owner-operator’s behalf. A service invoice alone does not prove every required program action is current. The carrier should understand the program scope, driver population, record location, and service arrangement.

Vehicle maintenance has to leave a record trail

A clean truck at the time of an audit does not by itself establish a maintenance system. Where the requirements apply, the carrier should be able to show how vehicles are inspected, maintained, repaired, and reviewed.

That may include annual inspection records, maintenance history, repair records, reported defects and correction records, and the identifying information needed to connect the paperwork to the actual vehicle.

The record should answer a practical question: if a component needed attention, can the carrier show how the condition was identified and what happened next?

Crash records are another specific system

Federal crash-record requirements apply to crashes that meet the regulatory definition. Do not turn every parking-lot scratch into a federal accident-register event, and do not assume a qualifying crash can be handled through an ordinary insurance folder alone.

Where an accident register is required, the carrier should maintain the required information and retention record under the current rule.

What happens if the audit identifies serious problems?

Passing the audit does not end the New Entrant period. FMCSA continues to monitor safety performance through the remainder of the 18-month period.

If a carrier fails the Safety Audit, FMCSA provides written information identifying the violations and the corrective-action requirements. A corrective action plan must follow the instructions and deadline in the actual FMCSA notice. Failure to submit an acceptable corrective response or implement required corrective action can lead to loss of the carrier’s New Entrant registration.

Do not guess at a CAP deadline from an old article, forum post, or someone else’s audit. The actual notice and current FMCSA instructions control the response.

A practical pre-audit record

1. Confirm the current operating facts: drivers, vehicles, authority, freight, and jurisdictions.
2. Identify which requirement groups actually apply.
3. List the record that proves each applicable requirement.
4. Verify the record location and current status.
5. Separate Current, Unknown, stale, and missing evidence instead of calling all four “done” or “bad.”
6. Assign a real owner to each unresolved item.
7. Keep the official audit notice and submission instructions with the audit record.

The objective is not a binder thick enough to impress somebody from across the room. It is a carrier that can answer a simple question without scrambling through five inboxes:

What requirement applies, and where is the proof?

A roadside inspection usually becomes stressful before anything has actually gone wrong. The scale is open. The truck is directed in. An inspector approaches the window, and suddenly every document in the cab feels as though it has learned how to hide.

The better operating question is not “How do I talk my way through an inspection?” It is: Can the driver and vehicle produce the applicable proof without improvising?

North American Standard inspections are conducted under the Commercial Vehicle Safety Alliance inspection program by trained enforcement personnel. CVSA currently recognizes eight inspection levels, not six.

The eight inspection levels

Level I — North American Standard Inspection. A comprehensive driver-and-vehicle inspection covering driver requirements and vehicle components, including an examination of safety-critical components.

Level II — Walk-Around Driver/Vehicle Inspection. A driver and vehicle review that includes items that can be inspected without physically getting underneath the vehicle.

Level III — Driver/Credential/Administrative Inspection. Focuses on driver credentials and applicable driver or administrative requirements rather than a full vehicle inspection.

Level IV — Special Inspection. An examination of a particular item or set of items, often conducted for a specific enforcement, study, or tracking purpose.

Level V — Vehicle-Only Inspection. A vehicle inspection conducted without the driver present.

Level VI — North American Standard Inspection for Transuranic Waste and Highway Route Controlled Quantities of Radioactive Material. A specialized inspection for covered radioactive-material shipments.

Level VII — Jurisdictional Mandated Commercial Vehicle Inspection. An inspection program established for certain vehicles or operations under jurisdiction-specific requirements. The scope and training standards depend on the jurisdiction.

Level VIII — North American Standard Electronic Inspection. An electronic or wireless inspection concept conducted without direct interaction with an enforcement officer. CVSA and FMCSA are currently evaluating Level VIII through an operational test, so drivers should not assume every carrier is already participating in a nationwide Level VIII program.

The point of knowing the levels is not to memorize Roman numerals for truck-stop trivia. It is to understand that not every inspection checks the same things.

Driver-side records: “where applicable” matters

A generic list of “documents every truck must carry” can be misleading. Required documentation varies with the driver, operation, vehicle, cargo, jurisdiction, and regulatory scope.

Depending on what applies, roadside review can involve items such as:

• driver license class and applicable endorsements;
• driver qualification or medical status where required;
• current record of duty status and hours-of-service information;
• vehicle registration;
• operating authority information;
• Unified Carrier Registration status;
• shipping papers or hazardous-material documentation where applicable;
• other credentials required for the specific operation.

Do not solve this by stuffing every document you have ever received into the door pocket. Build a current list for your operation and know where the applicable proof lives.

Know how your ELD works before roadside

If an ELD is required for the driver, the driver needs to understand how to display and transfer the required information using the actual device or application in service.

The roadside is not the ideal place to discover that the instruction card is missing, the driver does not know the transfer sequence, or yesterday’s unresolved unidentified driving is still sitting in the system.

That does not mean every ELD irregularity equals a violation. It means the carrier should have a process for certification, edits, annotations, unidentified driving, malfunctions, and record retrieval before an inspector asks questions about them.

The vehicle tells its own story

A Level I or other vehicle inspection can involve brakes, tires, lighting, steering, suspension, coupling devices, frame, securement, and other safety-related components within that inspection’s scope.

The practical lesson is simple: roadside preparation starts with ordinary maintenance and inspection discipline.

• Do the required pre-trip and post-trip work that applies to the operation.
• Do not normalize defects because the truck “still drives fine.”
• Repair known safety defects through a documented process.
• Keep required inspection and maintenance records retrievable.

An inspector is not grading the truck on how recently it was washed. Chrome has many talents. Fixing an air leak is not one of them.

When a violation is recorded

Not every violation produces the same consequence. The result depends on the condition, applicable rule, inspection procedure, and out-of-service criteria.

A driver or vehicle may be placed out of service when a condition meets the applicable out-of-service criteria. Other violations may be recorded without an immediate out-of-service order.

A roadside violation can also become part of the carrier’s safety data. Avoid casual language such as “the driver got CSA points.” Drivers do not have a personal CSA score in the way that phrase is often used. FMCSA’s Safety Measurement System uses inspection and crash data in evaluating motor-carrier safety performance.

If you disagree with a finding

Roadside is usually not the place to turn a disagreement into a shouting contest.

Preserve the inspection report, note the facts while they are fresh, retain supporting records, and determine the correct review or challenge process after the stop. A later disagreement does not justify altering the original record or pretending the inspection never happened.

Formal data-review processes such as DataQs belong to their own specialized procedure guidance. This Guide is about being ready for the inspection and preserving the record afterward.

A practical roadside-readiness check

1. Know which driver credentials and documents apply to the trip.
2. Know where current vehicle registration and other required operating records are kept.
3. Know how to display or transfer required ELD information.
4. Resolve unidentified or unexplained ELD events through the proper process.
5. Perform a real pre-trip inspection.
6. Correct known defects instead of assuming roadside will miss them.
7. Keep shipping and hazardous-material documents ready when applicable.
8. Preserve the inspection report and any later correction records.

Inspection readiness is not about predicting which scale will pull you in. It is about making the same truck, driver, and records defensible whether the bypass light is green or the officer waves you toward the inspection lane.

An envelope says DOT. An email has an FMCSA logo. The subject line says ACTION REQUIRED, and somewhere below that is a deadline, a penalty, a phone number, and a payment request.

That is not enough to tell you what you are looking at.

Motor-carrier information is publicly available, which means legitimate private businesses can contact carriers and offer paid services. At the same time, FMCSA actively warns carriers about phishing, government impersonation, fake audit messages, bogus registration portals, misleading carrier-status notices, and aggressive telemarketing.

The result is a messy real-world problem: a real regulatory subject can appear inside an optional private solicitation or an outright fraudulent message.

Put the message into the correct bucket

Before paying, clicking, signing, or sending documents, classify what you actually have.

Official agency communication is correspondence or an action that can be independently confirmed through an official government source or account.

Private service solicitation is a business offering to perform or help with a compliance task for a fee. The underlying requirement may be real while use of that company is optional.

Unverified or suspicious communication is a message whose sender, link, claimed requirement, payment request, or data request has not cleared independent verification.

Do not collapse all three into “official-looking” and “scam.” A private vendor does not become FMCSA because it offers help with an FMCSA filing. And a private vendor charging for real administrative work is not automatically fraudulent.

First check: who actually sent it?

Do not use the questionable message to verify itself.

If an unexpected email gives you a telephone number, QR code, login link, or payment portal, do not assume that destination is independent simply because it appears under a government-looking logo.

Navigate separately to the responsible agency’s official website, official account, or published contact information. FMCSA currently directs carriers who are targets of suspicious practices to the FMCSA Contact Center at 1-800-832-5660.

FMCSA’s current fraud guidance states that the agency will not contact regulated entities through telemarketers or automated robocall solicitations and will not request a credit-card number or charge a fee for downloadable FMCSA forms.

Second check: what requirement is the message claiming?

Write the claimed obligation in plain language.

For example:

Claim: My MCS-150 biennial update is due and I must pay this sender to complete it.

Now separate the two questions:

1. Is an MCS-150 biennial update actually required for this carrier at this time?
2. Is this particular company or payment required to satisfy it?

FMCSA requires entities under its jurisdiction to update their information every two years, even when information has not changed. FMCSA currently states that updating USDOT information through the official biennial-update process is free.

Failure to complete the required biennial update can result in deactivation of the USDOT number and may result in civil penalties of up to $1,000 per day, not to exceed $10,000.

Those are real consequences. They do not prove that the company demanding $149, $299, or $399 is the government or that the carrier must purchase that company’s service.

Third check: what information are they asking for?

Sensitive information deserves a higher verification standard.

An official process may legitimately require identifying information. That does not mean you should send a Social Security number, EIN, driver-license image, USDOT PIN, bank information, insurance documentation, or account credentials to an unexpected sender because the email looks official.

Use the official process to determine what information is actually required and where it must be submitted.

HaulSmarterHQ does not need your SSN or driver-license number to help organize a Compliance working record. Proof status, dates, applicability, source, and record ownership usually tell us far more about the problem without creating another sensitive-data exposure.

Fourth check: whose fee is it?

A fee needs a label.

Some government transactions have official fees. Some do not. A private company can also charge for its own administrative labor even when the government filing itself is free.

Ask:

• Who receives the money?
• What exact service am I purchasing?
• Is this an official government fee or a private service fee?
• Can I perform the official task directly?
• What written scope explains what the vendor will actually do?

If the sender cannot distinguish the government obligation from the private service being sold, stop and verify independently.

Why new authorities get flooded

New carriers are especially vulnerable because public registration information makes them easy to find, while their internal compliance system may still be new.

The result is familiar: the authority goes active and suddenly the phone behaves as though the carrier accidentally registered for every mailing list on Earth.

A caller knowing your USDOT number, company name, address, or authority status does not establish that the caller works for FMCSA. Public information is not a government badge.

A five-line verification record

When a message feels important enough that you are afraid to ignore it, document it instead.

1. Sender claimed: Who does the message say it represents?
2. Requirement claimed: What exact filing, audit, renewal, registration, or record does it say is required?
3. Deadline claimed: What date does it give?
4. Official verification: What does the responsible government source or official account actually show?
5. Money or information requested: Government fee, private service fee, credentials, payment information, documents, or sensitive identifiers?

That turns “Is this thing real?” into a record that can be checked.

If you already clicked, paid, or shared information

Stop using the questionable communication as your source of instructions.

Contact the relevant financial institution or payment provider promptly if money was sent. Change compromised credentials and enable stronger authentication where available. Use official agency and federal fraud-reporting resources for the type of information or loss involved.

Keep copies of the communication, payment record, sender information, and any report or confirmation number. Do not delete the evidence because the message was embarrassing. Convincing people is what fraudulent messages are designed to do.

The operating rule

An official-looking notice can contain a real requirement and still send you to the wrong place.

Verify five things independently:

Sender. Requirement. Deadline. Filing channel. Fee.

If the requirement is real, handle the requirement through a verified path.

If a legitimate private company is offering optional help, decide whether the service is worth purchasing.

If the sender or request does not clear verification, do not give it money, credentials, or sensitive documents.

Can you prove who is asking? Start there.

The phrase “driver file” sounds like a cabinet problem. It is really a qualification and record-timing problem. A file can look tidy and still fail to answer the current question if it contains old documents, missing inquiries, or no clear record of what was reviewed and when.

The recurring forum confusion is especially important for a solo owner-operator: “I own the company, so do I really need a driver qualification file on myself?” Where the rules apply, being both the motor carrier and the driver does not make one side of the requirement disappear. It means the same person must understand both roles and keep the required evidence accordingly.

Start with scope and the current rule

Part 391 establishes driver qualifications and motor-carrier duties for covered drivers, while also containing exceptions. That is why a generic online DQ checklist is not the governing document. Confirm the carrier’s operation and the rule’s scope first. Then use the current rule to identify the required records and the applicable retention or review duties.

For a driver in scope, the core practical question is simple: can the carrier produce the required qualification record and explain its current status? That is different from asking whether the driver is a good person, experienced, or known to the owner. A familiar driver does not create an auditable record by proximity.

Do not mix initial qualification with continuing review

Some records arise at or before a driver begins operating. Other duties require later review, updated information, or a response to a triggering event. Put them on separate lines. A one-time qualification item and a recurring annual review should not share one vague checkbox labeled “complete.”

Use a record register with the driver name, record type, source/location, date obtained, expiration or next review date where applicable, person responsible, and evidence state. Evidence state matters. An actual motor vehicle record is not the same as an owner’s recollection that it was pulled. A documented good-faith effort is not the same as a response that was never requested.

The current Part 391 text specifically recognizes duties for a person who is both a motor carrier and a driver, and contains requirements about driver qualification and investigations. That makes the solo-carrier question a place for verification, not assumption.

Illustrative file review

Illustrative example: A one-truck carrier keeps a folder labelled “DQ.” Inside are a copy of the owner-driver’s CDL, an old medical document, and a blank annual review form. The folder establishes that some material exists. It does not establish which current Part 391 obligations apply, whether the documents satisfy them, whether an applicable review occurred, or whether the carrier can locate the supporting evidence. The appropriate first action is a scoped review of the applicable rule and the file contents—not a signature added to a blank form to make the folder look finished.

That last shortcut deserves a dry warning: blank paper is wonderfully compliant with nobody. It does not prove a review happened.

A practical review order

1. Confirm whether Part 391 applies to the carrier and driver in question, including any relevant exception.
2. Build the required-item list from the current rule, not from memory.
3. For every item, record the actual document or official source, location, date, and status.
4. Separate items that are missing from items that are present but whose currency cannot be established.
5. Create a recurring review calendar only for obligations the current rule and operation actually support.

Keep personal data minimized and protected. A file may legitimately contain sensitive information; that is a reason to control access and retain only what is necessary, not a reason to leave ownership and storage undefined. When a provider holds records, confirm retrieval and export before you need them.

The guide cannot decide an individual driver’s qualification or provide legal advice. It can establish the working discipline: first determine scope, then locate the evidence, then track the review date. A DQ file is a living proof record, not a drawer where last year’s documents go to wait for confidence.

The phrase “our consortium handles that” is often the beginning of a useful answer and the end of an incomplete one. A consortium or third-party administrator can perform important work. It can manage enrollment, random selections, testing coordination, collection-site logistics, and parts of record administration. It cannot make the carrier’s own role disappear.

That distinction is not an argument against using a C/TPA. It is a way to prevent a familiar service relationship from being mistaken for a complete proof trail. The carrier still needs to know which drivers are covered, what policies and contacts exist, where the records are held, how a result or event is handled, and how the records are recovered if the provider changes.

Name the two systems

There is a DOT-wide testing process under Part 40 and motor-carrier-specific controlled-substances and alcohol rules in Part 382. They are related, but they are not a single subscription product. The current rules define responsibilities and procedures. A provider agreement defines the administrative work the provider has agreed to perform. A carrier needs both records, and it should not let one substitute for the other.

The practical error is to treat a payment receipt or a welcome email as proof that every required carrier-side action is current. It may prove that an account exists. It may prove that a particular service was purchased. It does not establish which drivers are enrolled, whether the current operation is within the service scope, whether a required record is retrievable, or whether a required action has been completed.

Build an ownership map

For the actual program in use, write down the carrier owner, the C/TPA contact, the medical review officer contact if relevant to the arrangement, the collection or testing path, the record location, and the process for an event that needs carrier action. Keep the service agreement with that map.

Then list the records and tasks in plain language. Who supplies driver changes? Who receives a notification? Who documents a decision? Who can retrieve historical records? Who confirms an employee or driver is in the correct population? The answer may be different by provider, which is why a generic “the consortium takes care of it” is not a complete operating procedure.

Illustrative example

Illustrative example: A carrier has paid an annual consortium fee for years. A driver is added after a busy period, but no one can show the date the provider was notified, the enrollment status, or the record path. The carrier may not have a proven program gap yet; the scope and evidence have not been reviewed. The first result is Unknown with a verification task: compare the current driver population to the provider’s written records and service terms. If a covered driver was not handled under the applicable program, the evidence may then support a correction task.

The bad shortcut would be to print the invoice, put it on top of the folder, and declare victory. Invoices are excellent at proving that money has travelled. They are less chatty about what happened afterward.

What to review periodically

Review the population in scope, carrier contacts, provider scope, record retrieval path, the policy and educational material applicable to the carrier, and current rules that affect the task. Review changes in drivers, operating status, or provider terms when they occur rather than waiting for an annual renewal to discover that the working process and the written agreement have separated.

Do not add more personal or medical information to a general compliance folder than the program and law require. The carrier needs a controlled, retrievable record system with a clear owner. Sensitive information is not a reason to make the record unknowable; it is a reason to minimize access and document the correct custodian.

What this guide does not decide

This guide does not determine whether a particular person is subject to testing, interpret a test result, or replace a medical review officer, agency, or qualified legal advice. It does establish the question every small carrier can ask: what does our provider actually administer, and what proof remains ours to maintain?

When that answer is written down, outside administration can be genuinely useful. When it is not, a carrier has bought a cloud of reassurance and may still be unable to produce a clear record on the day it matters.

An ELD is not a compliance conclusion mounted on the dashboard. It is a recordkeeping system with ordinary days, corrections, exceptions, roadside use, and failure paths. A carrier that only asks, “Is the device installed?” has skipped the harder question: can the driver and carrier explain the record the device produces?

This is why roadside questions make drivers anxious even when they believe they are doing the right thing. The stress is not always the normal log. It is the unassigned segment, a requested edit, a device problem, a driver change, a certification question, or the moment an officer asks for the information in a form the driver must be able to provide.

Review the working record, not the sales page

The ELD vendor may show a dashboard, a compliance score, or a helpful alert. Those can be useful operating tools. They are not a substitute for checking the applicable HOS and ELD requirements or the carrier’s actual records. The carrier needs to know which drivers and operations are in scope, what supporting documents and retention duties apply, how records are certified and corrected, and what the process is when the device malfunctions.

Start with one normal day. Open a record of duty status and walk through it with the driver’s actual work. Then look at the events that generate explanations: edits, annotations, personal-conveyance use where applicable, unassigned driving, and a malfunction. A process that works only when nothing unusual happens is not a process. It is a lucky day wearing a procedure’s name tag.

Edits and annotations

An edit is not automatically bad. The practical question is whether the record reflects what happened, whether the edit is handled through the required system process, and whether the record can be explained. A carrier should not use edits to cosmetically improve a log, and a driver should not be left to guess what a carrier expects when an annotation is needed.

Keep an internal instruction that states who reviews records, when an issue is escalated, what documentation belongs with a correction, and how the carrier preserves the original event history where the system does so. Do not write a generic rule such as “fix all errors.” A real instruction describes the path for a driver who sees a record problem.

Unidentified driving is a carrier work queue

Unassigned or unidentified driving should not become background noise. It is an event that needs review through the current system and rule process. The carrier should know who reviews it, what information is compared, what action is taken, and how the resolution is recorded. A growing queue is not proof that the company has a bad intent. It is proof that an unresolved record process needs an owner.

Malfunctions deserve a written path

The failure path is where a casual setup becomes expensive. The driver needs to know what to do if the device is not functioning as required, what backup records or instructions are applicable, who to contact, and how the carrier documents the event. The carrier needs to verify those instructions against current Part 395 requirements and the device documentation. Do not rely on a vague memory that “the app has a malfunction mode.”

Illustrative example: A driver reports a device issue at night. The dispatcher says, “Just keep rolling and we will sort it out in the morning.” That statement is not a procedure. A useful response identifies the current event, retrieves the carrier’s written malfunction path, follows the applicable recordkeeping requirements, and documents what was done. If the carrier cannot locate the path or establish the device status, the honest finding is Unknown pending verification.

A short recurring review

Review a sample of normal records and exception records. Confirm that drivers know the roadside display or transfer procedure applicable to the system. Reconcile unidentified driving. Check that carrier contacts and device instructions are current. Preserve supporting records in the manner and period the current rule requires. When an operating fact changes, verify whether the existing procedure still fits.

The guide does not decide a particular HOS question or determine whether an exception applies to an individual trip. It gives a better starting point than “the ELD is on”: the record must be explainable, the exception path must be usable, and the current rule must be checked before a conclusion is stated.

A compliance finding is not useful because it sounds serious. It is useful because it tells the operator what should happen next.

The Compliance Toolkit stops at the finding. It establishes which requirements apply, what evidence exists, whether the evidence is current enough for the requirement, and what remains Unknown or unresolved.

The Compliance Decision Center then has a narrower job. It converts that record into one of four operating outcomes:

NOT READY
KEEP CURRENT SETUP
FIX INTERNAL RECORD
COMPARE OUTSIDE HELP

Those are HaulSmarterHQ decision classifications. They are not FMCSA enforcement labels, regulatory statuses, or substitutes for an official agency finding.

NOT READY

Use NOT READY when the evidence is not strong enough to support a decision.

A requirement may still have an unresolved applicability fact. A document may be unavailable. The current date or scope may not be established. Two pieces of evidence may conflict. Or an operator may not yet know whether a private notice describes a real obligation.

NOT READY is not a failure state. It means the record does not support pretending.

The next job is usually verification: identify the missing fact, source, record, or contradiction and close that question before routing into KEEP, FIX, or COMPARE.

KEEP CURRENT SETUP

KEEP CURRENT SETUP is a successful result.

Use it when the applicable requirement and supporting evidence show that the current process is working well enough and no material correction or outside-service need has been established.

This is where a compliance system proves it is not a sales funnel. A provider being available is not evidence that the operator needs a provider.

If your numbers are good, keep them. If your record is good, keep that too.

FIX INTERNAL RECORD

Use FIX INTERNAL RECORD when the evidence establishes a carrier-controlled record or process problem that can be corrected internally.

The correction should be specific:

• what condition was found;
• which applicable requirement or record is involved;
• what work must be performed;
• who owns the correction;
• what proof will establish completion;
• when the correction will be checked.

“Get compliant” is not a work order. “Retrieve the missing record, verify its current status, file it in the correct driver record, and record the review date” is much closer.

COMPARE OUTSIDE HELP

Use COMPARE OUTSIDE HELP only when the record has established an actual job worth comparing.

The issue may be recurring administration, provider-held records, program management, software, structured review work, or another defined service function that the carrier does not want to perform internally.

The outcome does not mean “buy a vendor.” It means the carrier now has enough evidence to define the work and compare options on the same spec.

The correct Page 4 question becomes:

What exactly do we need someone else to do?

Where does escalation fit?

Some findings do not belong inside an ordinary DIY-versus-provider comparison.

An official enforcement action, a disputed agency determination, a formal data challenge, a New Entrant corrective-action response, a safety-rating process, a legal dispute, or another time-sensitive official proceeding can require a specialized procedure or qualified professional.

Those formal agency-response workflows are deliberately outside the core Decision Center. The Decision Center should identify that the ordinary four-state decision path is insufficient; it should not quietly become an appeal engine.

Specialized DataQs, New Entrant CAP, safety-rating, and similar procedure guidance belongs in a separate Compliance procedure layer.

Example: the missing document

Illustrative example: The Toolkit finds that an applicable driver record cannot currently be produced.

If the operator does not yet know whether the record exists somewhere else, the result may be NOT READY.

If the record is found and verified current, the result may become KEEP CURRENT SETUP.

If the record is confirmed absent and the carrier can correct the process internally, the result may become FIX INTERNAL RECORD.

If the carrier has several drivers, repeated administration failures, no stable record owner, and wants ongoing outside administration, the result may become COMPARE OUTSIDE HELP.

One original condition. Four very different conclusions. The evidence determines which one is earned.

Do not strengthen the evidence to make the outcome easier

An old document does not become current because the carrier wants to move past NOT READY.

An operator declaration does not become an independently verified record because a provider comparison needs a clean input.

A blank is not zero. Unknown is not failure. Not Applicable is not deficiency.

That discipline is what keeps the Decision Center from manufacturing a problem simply to give the next page something to sell.

“I need compliance help” can mean several very different things.

It can mean the carrier does not know which requirements apply. It can mean the carrier understands the work but does not have time to maintain recurring records. It can mean a specific regulated function appropriately uses an outside administrator. It can mean a formal matter needs professional interpretation. Or it can mean a sales call successfully turned ordinary uncertainty into the feeling that somebody else must take over immediately.

Those are different problems.

Buying a general package before naming which one is present often produces a vague service, a vague bill, and a carrier that still cannot locate its own records later.

First identify what kind of problem you have

Knowledge problem: You do not yet know what requirement applies or what proof it requires.

Record problem: The requirement is understood, but the supporting record is missing, stale, contradictory, or difficult to retrieve.

Capacity problem: The work is known and repeatable, but the carrier does not have enough time, staffing, or process discipline to manage it reliably.

Specialized administration problem: A particular program function is appropriately handled through or with an outside service provider under the applicable rules.

Professional-interpretation problem: The question involves a disputed official action, legal issue, contract interpretation, or another matter beyond ordinary administrative support.

The answer determines whether you need the Toolkit, an internal correction, a provider comparison, or escalation to a qualified professional.

Doing work yourself is not automatically better

There is no prize for personally performing every administrative task in the business.

A small carrier can sensibly use outside help for program administration, driver-record systems, registration support, audit-preparation work, software, reminders, or other recurring functions.

But outsourcing administration does not automatically outsource the carrier’s duties, the truth of the carrier’s records, or the need to understand where evidence lives.

For some regulated functions, outside participation is part of the actual compliance structure. For example, an owner-operator who is subject to Part 382 drug-and-alcohol testing requirements must participate in a consortium/random testing pool and must designate a C/TPA for certain Clearinghouse functions.

That is why “keep everything in-house” cannot be a universal rule either.

Use the burden test

Before deciding to outsource a recurring administrative job, write down:

1. How often the task occurs.
2. How much owner or staff time it consumes.
3. What expertise is actually required.
4. What happens if the task is missed.
5. Whether the carrier can produce a repeatable internal process.
6. Whether a regulated third-party role is required or merely optional.
7. What records must remain accessible to the carrier.

A one-time record cleanup is different from ongoing administration. A one-driver operation is different from a growing fleet with multiple record owners. A filing task is different from interpreting an official enforcement notice.

Keep control of the proof trail

If you use a provider, know what the provider actually owns and what remains carrier-side.

A login to someone else’s portal is not a complete continuity plan.

Ask:

• Which records does the provider create or maintain?
• Which records must the carrier supply?
• Who reviews exceptions?
• What happens when information is missing?
• Can the carrier export its records?
• What happens when the service ends?

The provider may perform excellent work. The carrier still needs a usable route to the proof.

Illustrative comparison

Illustrative example: Carrier A has one driver, a known set of records, a stable folder system, and a short list of recurring review dates. The owner can reasonably maintain most administrative work and use outside services only where the actual program requires or clearly benefits from them.

Carrier B has several drivers, documents spread across email and multiple accounts, no repeatable review schedule, and recurring missed follow-ups. Carrier B may have an administration-capacity problem worth solving with a defined provider scope.

Neither carrier should buy the same “full compliance package” merely because both use the phrase “I need help.”

The Decision Center outcome can still be KEEP

If the current system works, records are retrievable, required outside functions are properly handled, and no material administration gap is established, KEEP CURRENT SETUP is a valid answer.

If an internal record problem is the issue, FIX INTERNAL RECORD may be enough.

If the work is not sufficiently defined, the answer may still be NOT READY.

Only after the work and need are established should the operator move to COMPARE OUTSIDE HELP.

The carrier’s job is not to prove that it can do everything alone. The carrier’s job is to know what applies, know who owns each task, and retain a defensible proof trail whether the work is done in-house or by someone else.

A correction record is not an apology letter and it is not a before-and-after success story. It is the short factual chain that lets a future reader see what was found, why it mattered, what was done, and what evidence supports the result. When the record is built after the fact from memory, it usually becomes smoother and less useful. The point is not to make history tidy. It is to make the work traceable.

Start with the condition. Identify the record, date, source, or notice that created the question. Then identify the basis: the current requirement, written term, official instruction, or actual operating control involved. Do not make a broad claim such as “we were not compliant” when the evidence only shows that one record could not be located. Precision protects the carrier as much as it protects the reviewer.

The five lines that matter

Record the condition, the basis, the action, the proof, and the check. The condition is the factual gap. The basis says why it needs attention. The action says what was actually done and by whom. The proof points to the record that supports completion. The check records who reviewed it, when, and what the correction does not establish.

Illustrative example: A carrier discovers that an applicable record was not available during an internal review. The correction record should not claim that the underlying work “must have happened.” It should state the date discovered, the requirement or record category involved, the retrieval or correction action, the document now obtained or created, and any remaining limitation. If the historical fact cannot be reconstructed honestly, say so. The new record may establish the carrier’s current action; it does not rewrite the earlier period.

That distinction becomes important when someone prints a binder or retains a snapshot. A historical finding should remain immutable: it says what the carrier concluded from what evidence, under what rule basis, on that date. When the record is reopened later, the system should separately check whether the regulatory basis is still current. A changed rule does not erase the old record. It does prevent the carrier from quietly treating the old conclusion as a current regulatory answer.

Do not manufacture clean history

Never backdate a review, alter an original record, or add a signature intended to make a past action look completed. Add a dated correction record instead. If a document was obtained later, record it later. If a verification was not possible, preserve Unknown. The record can be imperfect and still be honest; a polished fiction is a worse operating asset than an explicit gap.

Keep the evidence with the correction: a source copy, document identifier, system export, email confirmation, receipt, or official response where appropriate. A general note that “handled with vendor” is not proof of what the vendor did. If a provider performed a task, retain the service record and carrier-side review that establishes the job was completed.

What the correction does and does not prove

A correction record may prove that the carrier identified a condition and took a documented action. It may show the record now exists. It does not automatically establish that every related requirement is current, that no consequence occurred, or that a prior period is retroactively clean. Keep those boundaries visible.

Donna’s useful version of humor belongs here: a folder does not become a time machine because someone clipped a newer document to the front. That is not a joke about enforcement. It is a warning against paperwork theater.

Use a short final line: current status, owner, date checked, evidence state, and limitation. That is enough for a correction to become a working record rather than a paragraph that gets lost in an email thread.

Provider comparison begins too late when the first task is choosing a company. The first task is defining the work. “Compliance help” can mean registration support, driver-file administration, drug-and-alcohol program support, audit preparation, software, a reminder service, or legal interpretation. Those are not interchangeable deliverables, so they cannot be compared honestly under one vague price.

Write a one-page scope before speaking to providers. Name the operation, the records or programs involved, the exact deliverables, the cadence, the carrier-side owner, the information the provider will receive, and what output the carrier must retain. Include what is out of scope. A defined no is as useful as a defined yes.

Make the job comparable

If one provider quotes “full compliance” and another quotes “driver-file management,” the price difference tells you very little. Send the same scope to each provider. Ask which tasks are included, which are add-ons, who performs them, how the provider reports completion, what the carrier must supply, and what remains the carrier’s responsibility.

The real operator grievance behind this is not simply price. It is being sold relief before the underlying question is understood. A new carrier receiving a flood of calls may be told that a package is necessary immediately. The calm answer can be that the carrier does not need anyone yet. If the work is occasional, records are available, and an owner can follow a repeatable process, in-house may be the right outcome.

Illustrative example: A carrier asks three providers for “audit help.” One offers a software login, one offers a document-organizing service, and one offers a review of named records. None has received the same task list. The carrier should not rank them by price yet. It should define whether it needs a records inventory, ongoing maintenance, a particular filing, or help responding to an actual official notice. Only then can each proposal be evaluated on the same spec.

Scope is not a guarantee

A provider’s scope can define administrative work. It cannot guarantee a carrier is compliant, decide an unresolved legal question, or replace the carrier’s actual records. Ask for the boundary in writing. Ask how data is exported, whether the carrier has continuous access, what happens at cancellation, and how the provider handles a record it cannot verify.

The useful next action may be Keep It In-House, Verify a requirement, Compare Help, or Escalate a question that no ordinary service should answer. Do not let a brochure choose the action before the operation has named the job.

The clean comparison is not “which provider has the best website?” It is “which proposal performs the same defined work, under terms the carrier can actually use?” The carrier needs written answers, not a confidence score or a sales promise.

Start with a shared scope. Then compare: included tasks, carrier responsibilities, review cadence, data access, support limits, fees, implementation work, and exit rights. If a material answer is missing, mark it Unknown. Do not turn silence into a favorable assumption.

Compare the operating record

Ask each provider for the deliverable produced after a task is completed. Is it a carrier-owned record, an alert, a report, a filing confirmation, or merely a statement inside the vendor portal? Ask where historical documents live and how the carrier obtains them if it changes providers. The service may be useful even if the answer is “inside our system,” but the carrier must decide whether that access and export path fit the operation.

Use the same questions for every provider:

1. What named work is included, and at what cadence?
2. What facts and documents must the carrier provide?
3. Who reviews or performs each task?
4. What does the carrier receive as proof of work?
5. What costs, add-ons, support limits, and cancellation terms apply?

Illustrative example: Two providers both say they maintain DQ files. One collects documents but leaves review dates and carrier follow-up to the customer. The other performs a documented recurring review and returns an exportable record. Neither is automatically better; they are different scopes. The carrier compares them against its defined need instead of calling both “DQ compliance.”

Do not use forum complaints as proof that a particular company will fail a particular carrier. Use real operator experiences as friction evidence: questions to ask, terms to read, and assumptions to challenge. Use the actual written proposal and current rules for the decision.

The correct conclusion can be Compare, Wait, or Do Nothing. A provider does not earn the job by being available. It earns a comparison only after the carrier knows what it needs done.

A compliance service contract should read like an operating record, not a cloud of comfort. It should state the work, price, data access, responsibilities, support path, and exit process. If a carrier cannot explain those points before signing, it cannot realistically manage the relationship after a record question arrives.

Read five areas before agreeing

Scope: name services, timing, excluded work, and any trigger that changes the fee or task. “Full service” is not a scope.

Fees: identify setup charges, recurring fees, per-driver or per-event costs, renewals, payment timing, and cancellation charges. An inexpensive base price can coexist with expensive add-ons; neither is improper if it is visible and fits the work.

Data: identify what the provider stores, who can access it, how records are exported, how long they are retained, and what happens to access at termination. The carrier needs its own path to the records it must retain.

Support: identify normal contacts, response expectations, after-hours limits, and what the provider will not do. Support for administration is not representation in every official or legal matter.

Exit: identify notice, data-return timing, transition assistance, and the carrier’s final responsibility for retrieving records. The day a provider relationship ends is a poor day to learn that the carrier cannot export a driver record.

Illustrative example: A carrier signs an annual service agreement because the salesperson says the company will “handle compliance.” Six months later, the carrier wants its records for a review but discovers that the contract does not describe export format, turnaround, or historical access. The problem is not that the provider necessarily did no work. The problem is that the carrier did not preserve a usable record-access term. The next move is to read the contract, request the written record path, and decide whether the scope still fits before renewal.

The contract does not remove the carrier’s responsibility for its operation or transform a vendor’s assurance into an official finding. It describes a business relationship. Keep it with the scope, invoices, reports, and any service records that show what was actually delivered.

The right outcome may be sign, revise, compare, or walk away. A clear exit term is not pessimism. It is what allows a carrier to change systems without discovering that its proof trail was rented rather than retained.