Prepare my trucking company for a DOT compliance audit
A gap checklist and document plan covering driver files, hours of service, maintenance, drug and alcohol testing, and insurance before an audit.
The prompt
Help me get my fleet ready for a safety compliance audit.
Regulator and audit type: [e.g. "US FMCSA compliance review", "new entrant safety audit", "state DOT audit", or my country's equivalent]
Operation: [interstate / intrastate, property / passenger, hazmat yes/no]
Fleet size: [NUMBER OF POWER UNITS, NUMBER OF DRIVERS]
How we keep records today: [ELD provider, paper files, maintenance software, testing consortium]
Known weak spots: [e.g. "missing annual reviews", "late DVIR repairs", "no clearinghouse queries"]
Audit date or trigger: [DATE, or what prompted it - crash, complaint, high scores]
Build the review around the areas auditors sample:
1. Driver qualification files: application, MVRs, road test or equivalent, medical certificate, annual review, previous employer checks.
2. Hours of service: ELD records, supporting documents, unassigned driving, edits and annotations.
3. Drug and alcohol program: pre-employment tests, random rates, clearinghouse queries, supervisor training.
4. Vehicle maintenance: inspection records, DVIRs and repair sign-offs, annual inspections.
5. Crash register, insurance filings, and operating authority.
Return:
- A checklist table: Area | Requirement | What to pull | Status (OK / Gap / Unknown) | Fix owner | Deadline.
- The top 5 gaps most likely to cause a violation, in priority order.
- A 2-week remediation plan.
- How to organize files so an auditor can sample them quickly.
Mark any regulation reference you are not sure applies to my operation as [CONFIRM]. Do not invent rule numbers or thresholds. This is general information; verify requirements with the regulator's current guidance or a transportation compliance specialist.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Legal & Compliance prompts
What to fill in
- interstate / intrastate, property / passenger, hazmat yes/no
- NUMBER OF POWER UNITS, NUMBER OF DRIVERS
- DATE, or what prompted it - crash, complaint, high scores
- CONFIRM
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Check my AI workflow for privacy and data-protection risksMaps the personal and confidential data in an AI-assisted process and flags privacy and compliance risks to fix before launch.
- Write a suspicious activity report (SAR) narrativeA clear, chronological SAR narrative that answers who, what, when, where, why, and how, ready for compliance review.
- Assess subrecipient risk and plan grant monitoringA risk assessment and monitoring plan for organizations you pass grant funds to, scaled to their risk and aligned to your award terms.
- Run a HIPAA security risk assessment for a small practiceA structured security risk analysis covering where ePHI lives, threats, likelihood and impact ratings, and a documented remediation plan.