Start Here: A Quick Snapshot of Your Team

• Please tell us your name, role, and the best way to reach you for follow-ups.
• Which functions are involved in hiring decisions for drivers at your company? Options: Recruiting/Talent Acquisition, Safety/Compliance, Operations/Dispatch, HR/People Ops, Finance/Procurement, IT/Integrations, Executive Leadership, Other
• How many people are dedicated to recruiting, safety, and operations at your largest terminal or region? Options: 1–2, 3–5, 6–10, 11–25, 25+
• Which terminals, regions, or business units are in scope for this initiative?
• Who will act as the day‑to‑day point of contact for implementation and when are they typically available?

Who's Really Calling the Shots?

• If a solution cut your time‑to‑hire in half tomorrow, whose approval would still be required to move forward? Options: Head of Recruiting, VP/Director of Operations, Head of Safety/Compliance, CFO/Head of Finance, Chief People Officer/HR Director, IT Director, CEO/President, Other
• What does that decision‑maker care about most when choosing a platform? Options: Cost savings, Regulatory risk reduction, Speed to hire, Candidate experience, Ease of integration, Vendor stability, Data & reporting, Other
• Who else needs to be engaged or signed off (e.g., legal, procurement, union reps)? List roles and any known stakeholders.
• How do final decisions typically get made at your company? Options: Single budget owner, Executive committee, Cross‑functional steering committee, Pilot then roll‑out, Formal RFP process, Other
• Have you chosen or rejected vendors in the past 18 months? What reasons drove those outcomes?

What Happens If You Wait?

• Imagine we pause this change for six months—what will be worse about your recruiting or compliance picture then?
• Do you have a target go‑live window or hard deadline we should be aware of? Options: Within 30 days, 30–60 days, 2–3 months, 3–6 months, 6+ months, No fixed date / exploratory
• Are there seasonal hiring peaks, contract renewals, or regulatory audits that drive your timeline? Options: Seasonal hiring window, Upcoming DOT/FMCSA audit, Union negotiation period, Budget cycle/quarter close, Large client onboarding, None of the above, Other
• What’s the earliest minimal scope (terminals, features, integrations) that would be valuable to launch first?
• If timeline slips happen, what internal tradeoffs are acceptable (reduced scope, phased rollouts, pilot only)? Options: Phased rollout, Pilot at one terminal, Delay integrations, Reduce feature set, Increase internal resources, Not acceptable / must meet deadline

Which Metrics Keep You Up at Night?

• If you had to pick one metric that would justify this investment to leadership, which would it be? Options: Time‑to‑first‑dispatch, Application‑to‑hire conversion, 90‑day driver retention, Cost‑per‑hire, DOT compliance pass rate, Turnover rate by terminal, Other
• Select up to three KPIs you want this project to move measurably. Options: Time‑to‑hire, Time‑to‑first‑dispatch, Application‑to‑hire conversion, Cost‑per‑hire, 90‑day retention, Drug/alcohol test turnaround, MVR turnaround time, Compliance file completeness
• For each KPI you selected, what is your current baseline and your targeted improvement?
• How are these KPIs currently tracked and reported? Options: Manual spreadsheets, ATS reports, Payroll/HRIS, TMS/Dispatch analytics, Safety management system, Ad hoc reports, Other
• How frequently do stakeholders review these KPIs (and who attends those reviews)? Options: Daily, Weekly, Monthly, Quarterly, Ad hoc

What's Missing From Your Tech Stack?

• Which single integration gap causes the most manual work today?
• Which systems must our platform integrate with to be considered production‑ready? Options: ATS (name), Payroll / ADP / Paycom, TMS/Dispatch, ELD provider, HRIS (Workday/UKG), Background check/MVR provider, Drug testing lab, FMCSA Clearinghouse, Other
• Do the systems above offer APIs or will we need scheduled file transfers (SFTP) or manual exports? Options: APIs available, SFTP/flat file only, Vendor portal/manual only, Unknown / need to check
• Who on your side owns integrations and vendor technical coordination? Options: IT/Engineering, Operations, Safety/Compliance, Vendor Management, External MSP/Consultant, Other
• Estimate applicant and hire volumes we should plan for (monthly averages). Options: 0–50 applicants, 51–150, 151–500, 501–1,000, 1,000+

Where Does Risk Live?

• When an auditor opens your driver qualification files, where are you most likely to fail?
• Which compliance elements are currently inconsistent or paper‑based? Options: MVRs, Drug & alcohol results, Medical certificates (DOT cards), Employment verifications, PSP reports, Clearinghouse records, Policy acknowledgements, None / fully digitized
• How many DOT/FMSCA findings, notices, or fines have you received in the last 24 months? Options: None, 1–2, 3–5, 6–10, 10+
• What would a single significant compliance failure cost you in operational terms (lost routes, fines, contract penalties)?
• Who leads corrective actions and audits internally (role and availability)?

Who Owns Success After Launch?

• If the solution doesn’t hit agreed outcomes in the first 90 days, who is accountable and what does accountability look like?
• Who will be the executive sponsor we should align with for approvals and escalation? Options: Head of Recruiting, VP Operations, Head of Safety, CFO, CHRO, Other
• Who will act as the operational owner day‑to‑day (product owner, implementation lead)? Please provide name/role if known.
• Which teams will handle training, adoption, and ongoing operations after go‑live? Options: Recruiting, Safety/Compliance, Operations/Dispatch, HR, IT, Third‑party trainer, Other
• What governance rhythm would you prefer for the first 90 days (check‑ins, reporting cadence, steering committee)? Options: Weekly stand‑ups, Bi‑weekly status, Monthly executive review, Ad hoc as needed, Formal steering committee

Decision Criteria & Commercial Red Flags

• What three non‑negotiable things must be true for you to sign a vendor agreement?
• Which contract terms would be immediate deal‑breakers? Options: Long auto‑renewals, Uncapped liability, No termination for convenience, Data ownership concerns, Lack of audit rights, Poor SLA commitments, Other
• What budget range has been allocated (or is realistic) for this project this fiscal year? Options: No budget yet / exploratory, Under $50k, $50k–$150k, $150k–$500k, $500k+
• Are there procurement or legal milestones we should plan for (RFP, security questionnaires, insurance certificates)? Options: RFP required, Security/pen test required, Insurance certificate required, Vendor risk assessment, No formal procurement steps
• What would a successful vendor onboarding look like at 30, 60, and 90 days? Briefly describe tangible outcomes.

Start with a Quick Snapshot

• In one sentence, how would you describe your current driver recruiting, qualification, and compliance workflow?
• How many drivers do you typically hire per month (average)? Options: 0–5, 6–20, 21–50, 51–200, 200+
• Which teams or roles are directly responsible for recruiting, safety compliance, and onboarding today? Options: Recruiting/TA, Safety/Compliance, Operations/Dispatch, HR/Payroll, Third-party recruiter, Other
• Which terminals, regions, or business units does this process cover (list primary locations)?
• Which of these metrics do you actively track today? Options: Application-to-hire conversion, Time-to-first-dispatch, 90-day retention, Cost-per-hire, DOT qualification completeness, Source-of-hire, Other
• If you had to name one single metric that would represent success for your hiring process, what would it be?

Where the Wheels Really Come Off

• Which recurring failure do you accept as 'just how trucking works'—the thing you suspect could be fixed but haven’t solved?
• At which stage do most applicants fall out of your funnel? Options: Sourcing/Attracting, Initial application, Qualification checks (MVR/Medical/Drug), Background/employment verifications, Onboarding/orientation, After first dispatch
• What are the most common failure modes you encounter (pick all that apply)? Options: Incomplete DOT files, Slow background checks, Failed drug/screens, No-shows to orientation, Missing integrations with ATS/payroll, Manual data entry errors, Other
• Can you share a recent example where a hiring failure caused operational impact (lost revenue, empty routes, fines)? Tell us briefly what happened.
• How frequently do these failures lead to measurable business costs (choose the best fit)? Options: Weekly, Monthly, Quarterly, Rarely
• When something goes wrong, who typically discovers it and how long before it’s escalated? Options: Recruiter, Safety manager, Dispatch/operations, Payroll/HR, Automated alert, Other

Are We Blind to Our Bottlenecks?

• If we removed one step in your current workflow tomorrow, which step would cause everything to grind to a halt?
• Please map the main end-to-end recruiting and qualification steps you follow (list in order, short phrases):
• Which three steps routinely have the longest cycle time or highest variability? Options: Sourcing applicants, Pre-screen/qualification, Background & MVR, Drug testing & medical, Orientation scheduling, Payroll/HR setup, Other
• For the slowest step you selected, roughly how long does it take on average? Options: <24 hours, 1–3 days, 4–7 days, 8–30 days, >30 days
• What do you believe is the root cause of that delay (pick all that apply)? Options: Vendor turnaround time, Manual handoffs, Lack of applicant responsiveness, Incomplete data from applicants, Integration gaps, Staffing capacity, Other
• How does variability in that step show up in operations—late dispatches, sudden compliance risks, increased churn, or something else? Options: Late dispatches, Compliance gaps/audit risk, Higher early turnover, Increased recruiting spend, No clear operational signal, Other

The Tools on Your Dash — and the Gaps They Hide

• How many distinct systems do you use across sourcing, ATS, background/MVR, drug labs, payroll, and safety monitoring? Options: Single platform, 2 systems, 3–4 systems, 5–7 systems, 8 or more
• Which specific systems or vendors do you currently use? (select all that apply, then name the top two in the free field below) Options: Applicant Tracking System (ATS), Payroll/HRIS, Background check vendor, MVR provider, Drug testing lab, FMCSA Clearinghouse, Safety/compliance system, Other
• Please list the top two systems/vendors from your previous answer (company and product name):
• Where do manual workarounds happen most often (pick up to three)? Options: Data re-entry between systems, Email or spreadsheet coordination, Phone calls to vendors, Manual file assembly for audits, Manual scheduling with applicants, Other
• How often do integrations fail or require manual reconciliation? Options: Constantly, Frequently, Occasionally, Rarely, Never
• When manual reconciliation occurs, what kinds of errors are most common? Options: Missing documents, Incorrect hire dates, Mismatched applicant IDs, Expired credentials not flagged, Payroll onboarding mistakes, Other

What Data Tells (or Hides) the Truth

• What useful hiring story do your reports consistently fail to tell?
• Which sources feed your recruiting and compliance reporting (select all that apply)? Options: ATS data, Payroll/HRIS, Background/MVR vendor feeds, Drug lab results, Manual spreadsheets, Driver mobile app uploads, Other
• Who owns the accuracy and distribution of compliance and hiring reports? Options: Recruiting/TA leader, Safety director, HR/payroll manager, Operations manager, No single owner, Other
• How confident are you that a randomly selected driver's DOT qualification file is audit-ready today? Options: Very confident (>95%), Mostly confident (80–95%), Somewhat confident (50–80%), Not confident (<50%)
• Give one example of a recurring data discrepancy you've found and how you discovered it.
• How quickly can you produce a complete driver file (all DOT required docs) when asked by an auditor? Options: <24 hours, 1–3 days, 4–7 days, >7 days

If Compliance Could Be Less Painful

• When was the last time a compliance issue felt like a surprise rather than a preventable event?
• Do you use automated alerts or workflows to manage expirations and recurring DOT checks? Options: Yes—fully automated, Partially automated, Mostly manual, No system
• How do you currently handle license, medical card, and MVR expirations (choose all that apply)? Options: Automated alerts to drivers, Alerts to safety team, Manual calendar reminders, Vendor-managed tracking, No formal process, Other
• Have you had compliance audits or fines in the last 24 months? If yes, what were the primary findings? Options: No audits/fines, Minor documentation gaps, Missing verification records, Late rechecks/expirations, Major noncompliance
• What single change would make compliance feel predictable and low-risk for your team?
• How comfortable are your managers with the current system for proving compliance during an audit? Options: Very comfortable, Comfortable, Somewhat uncomfortable, Not comfortable

Small Changes That Could Move the Needle

• What would have to stop today for hiring outcomes to noticeably improve within 30 days?
• Which pilot would you be most open to trying first to fix that problem? Options: Automated DOT file assembly, Integrated ATS-to-payroll onboarding, Text-to-apply + mobile app, Faster background/MVR integrations, Centralized compliance dashboard, Other
• Who are the decision-makers and approvers we would need to involve in a short pilot (list roles)? Options: Recruiting leader, Safety director, Operations manager, HR/payroll lead, IT/Integrations, CFO/Finance
• What would you consider a successful pilot outcome after 60–90 days (pick up to three)? Options: Reduced time-to-hire, Higher application-to-hire conversion, Improved DOT file completeness, Fewer manual reconciliations, Clear ROI on cost-per-hire, Other
• What constraints (budget, people, vendor contracts) would most limit your ability to run a pilot? Options: Budget, Staff bandwidth, Existing vendor contracts, IT/API capacity, Regulatory approvals, Other
• Realistically, when could your team start a focused pilot to address one of these areas? Options: Immediately, Within 30 days, 1–3 months, 3–6 months, Unsure

Quick Check — Who’s in the Room and Why Now?

• Who are the core stakeholders we should expect to engage for deployment (names, titles, and roles)?
• What’s driving the urgency to deploy now—regulatory pressure, driver shortage, a major contract, or something else? Options: Regulatory deadline, Driver attrition/coverage gap, New contract or account, Cost reduction mandate, Operational inefficiency, Other
• Which outcomes are highest priority in the first 90 days post-deployment (pick up to three)? Options: Application-to-hire conversion, Time-to-first-dispatch, DOT file completeness, 90-day retention, Reduced cost-per-hire, Reporting accuracy
• Who will be the single point of contact for daily decisions and who has final sign-off on compliance?
• How confident are you that internal stakeholders will make timely decisions during deployment? Options: Very confident, Somewhat confident, Concerned about delays, Significant risk of delay

If Go‑Live Breaks, What Breaks First?

• If one critical thing fails at go‑live, what would have the largest operational or compliance impact?
• How often in the last 12 months have you had compliance-related go‑live or deployment issues? Options: Never, Once, 2–3 times, More than 3 times
• When those incidents occurred, what was the root cause most frequently—data, integrations, people, vendor timing, or unclear processes? Options: Data quality, Integration failures, Insufficient training, Vendor delays, Process gaps, Other
• What would a compliance failure look like in practical terms (e.g., missing MVRs, lost drug test results, Clearinghouse mismatch)?
• How do you typically detect these failures—manual audits, periodic reporting, driver complaints, or external audits? Options: Manual audits, Automated reports, Driver feedback, DOT/auditor notification, Other

Can We Actually Reach All Your Data?

• What systems currently hold driver / applicant data we’ll need access to (ATS, payroll, safety, background checks)? Select all that apply. Options: Greenhouse, iCIMS, SmartRecruiters, Workday, ADP, Paylocity, Samsara, Geotab, Custom/Proprietary, Other
• For each system you listed, can you provide the access method we should expect (API, SFTP, CSV exports, database read-only, manual uploads)? Options: API (REST/GraphQL), SFTP file drop, Scheduled CSV export, Direct DB read-only, Manual upload only, Unknown
• Do you have technical contacts and test accounts for those systems available now? If not, which ones will need lead time and why? Options: All test accounts ready, Most ready with one exception, Several need provisioning, No test accounts available yet
• Are there data retention, PII, or encryption requirements we must follow when moving or storing data? Options: HIPAA-like/PII restrictions, Company-specific encryption policies, No special requirements, Unsure—need to check
• Can you share a small, de-identified sample file from each source for early mapping and validation? Options: Yes—available now, Yes—available with lead time, Requires approval, No, cannot share

How Tight Are Your System Connections Today?

• Which system is your single source of truth for driver status and payroll eligibility (ATS, HRIS, safety telematics, or payroll)? Options: ATS, HRIS/Payroll, Safety/Telematics, No single source (multiple)
• Do you currently have any automated integrations between these systems, or are hand-offs manual? Options: Fully automated APIs, Partial automation + manual tasks, Mostly manual file hand-offs, None
• Have you previously used middleware or iPaaS (Workato, Mulesoft, Boomi) for integrations? If yes, which? Options: Workato, MuleSoft, Dell Boomi, Zapier, Custom middleware, None
• Are there custom fields, non-standard IDs, or legacy codes we must map to our platform? Options: Yes—many custom fields, Some custom fields, Standard fields only, Unsure
• Do any partners or third-party vendors sit between systems (e.g., drug testing vendor feeds) that require separate credentials or approvals? Options: Yes—multiple vendors, One or two vendors, No third parties, Unsure

DOT Compliance — Where Are the Landmines?

• What DOT checks are required today and how are they currently performed (MVR, PSP, Clearinghouse, drug/alcohol, DOT physicals)? Select all that apply. Options: MVR, PSP, FMCSA Clearinghouse, Drug & Alcohol testing, DOT Medical Certificate, Employment verification, Other
• Which vendors handle those checks today, and do they offer automation/APIs we can connect to? Options: OneDrive/Manual vendor, Vendor offers API, Vendor offers SFTP only, Vendor has no electronic feed, We use internal processes
• What percentage of new hires today arrive with complete compliance files versus missing items? Options: >90% complete, 70–90% complete, 50–70% complete, <50% complete, Unknown
• How are Clearinghouse queries and violations currently tracked and escalated? Options: Automated tracking and alerts, Manual checks, Vendor-managed, Not consistently tracked, Unsure
• Tell us about a recent DOT audit or near-miss: what was uncovered, and how long to remediate?
• What risk controls must be in place before we execute DOT-related actions (two-person review, encrypted storage, audit logs, role-based access)? Options: Two-person review, Encrypted at rest & transit, Immutable audit logs, Role-based access controls, Automated expiration alerts, Other

Who Will Touch This System Every Day — And Who Will Rescue It at 2AM?

• Who will be the daily operator(s) for applicant flows, compliance checks, and exception handling? List roles and primary responsibilities.
• Who are the escalation contacts for integration outages, DOT compliance disputes, or urgent payroll blocks?
• What are your typical support hours and SLA expectations for critical incidents? Options: Business hours only (M–F), Extended hours, 24/7 on-call, Business hours with on-call escalation
• Do you have internal change control or security approval processes that could block deployment artifacts (IP whitelisting, security review, legal data agreements)? Options: Yes—formal security review, Lightweight approvals only, No formal process, Unsure
• Would you prefer a single operator console or role-specific dashboards for recruiting, safety, and payroll teams? Options: Single operator console, Role-specific dashboards, Both

Show Me How You’ll Test This — What ‘Pass’ Actually Means

• What absolute acceptance criteria must be met before we move a live driver into production (e.g., 100% file completeness for pilot cohort)?
• Which test scenarios are non-negotiable during validation (applicant flows, MVR ingestion, Clearinghouse match, payroll feed, reporting accuracy)? Select all required. Options: Applicant mobile apply & doc upload, MVR ingestion & mapping, Clearinghouse query/response, Payroll eligibility sync, Safety telematics sync, Reporting reconciliation
• Do you have a pilot cohort or test group we can use for live validation? If yes, how many drivers/operators? Options: Yes—small pilot (1–10), Yes—medium (11–50), Yes—large (>50), No pilot group available
• What data reconciliation tolerances do you accept (e.g., <1% mismatch between systems)? Options: 0% tolerance (exact), <1% mismatch, 1–3% mismatch, >3% mismatch
• Who signs off on each validation area (integration, compliance, operations, payroll)? List names/roles.

Migrations & Order of Operations — What Must Land First?

• Which migrations or integrations are blockers for pilot or production (historical driver files, active applicant backlog, payroll PII sync)? Options: Historical driver records, Active applicants backlog, Payroll sync, Safety telematics, Background check history, Other
• Which of the following must be completed before operations accepts live drivers from the platform? Options: Payroll integration, Clearinghouse automation, Applicant-to-hire workflow validated, DOT file audit trail established, Reporting dashboards live
• Are there seasonal or operational blackout windows where migrations cannot occur (e.g., peak hiring weeks, busy seasons)? Options: Yes—specific blackout windows, No restrictions, Unsure / need to check
• How much lead time do your vendors typically need to provision API access or test environments? Options: <1 week, 1–2 weeks, 2–4 weeks, >4 weeks
• What’s your preferred cutover strategy—phased, pilot-first, parallel run, or big bang? Options: Phased by terminal/region, Pilot then roll, Parallel run with fallbacks, Big bang

Operational Readiness — Will People Actually Use It?

• How would you describe front-line operator comfort with new tech (digital-native, willing learners, reluctant, strongly resistant)? Options: Digital-native, Willing learners, Reluctant adopters, Strong resistance
• What training model do you prefer: train-the-trainer, role-based cohort training, on-demand micro-learning, or shadowing during pilot? Options: Train-the-trainer, Role-based cohorts, On-demand micro-learning, Shadowing/pairing
• What KPIs will you use to measure adoption in the first 60–90 days (use rate, time-to-complete, error rate, helpdesk tickets)? Options: Use rate, Time-to-complete, Error rate/exceptions, Helpdesk tickets, Compliance pass-rate
• Are incentives or process changes planned to encourage operators to use the new workflows? Options: Yes—financial incentives, Yes—process enforcement, Yes—recognition programs, No incentives planned, Unsure
• What resources would increase your confidence in operator adoption (cheat-sheets, in-app guidance, dedicated support line)? Options: Cheat-sheets, In-app guidance, Dedicated support line, Office hours, Other

Security, Legal & Audit — What Approvals Are Waiting?

• Does your security or legal team require specific artifacts (SOC2, data processing agreement, encryption specs) before prod access? Options: SOC2 required, DPA required, Encryption spec required, No specific artifacts, Unsure
• Are there corporate policies about vendor onboarding, background checks for vendor personnel, or on-site audits we should prepare for? Options: Yes—formal vendor onboarding, Yes—background checks required, Occasional audits only, No special policies
• Who owns the audit trail for DOT-related documents after migration—operations, safety, or compliance team? Options: Operations, Safety/Compliance, Shared responsibility, Vendor-managed
• Are there contractual penalties or regulatory fines we should be aware of if files are incomplete or late? Options: Yes—contractual penalties, Yes—regulatory fines, Both, None known, Unsure
• What timeline do you need to complete any internal reviews or approvals for security and legal? Options: <1 week, 1–2 weeks, 2–4 weeks, >4 weeks

Acceptance, Rollback & Ongoing Governance

• What is your formal acceptance process—who signs off, which artifacts (test reports, reconciliations) are required, and what’s the timeline for sign-off?
• What are your rollback criteria and who must authorize a rollback in the event of a critical failure? Options: Rollback authorized by Operations, Rollback requires Exec approval, Rollback not planned (patch in prod), Other
• How often will we meet in the first 90 days to review incidents, backlog, and enhancement requests? Options: Weekly, Bi-weekly, Monthly, Ad-hoc as needed
• Who will own the shared backlog for post-deployment issues and enhancements? Options: Customer product owner, Customer operations owner, Joint governance team, Vendor/Host owner
• What cadence and format do you prefer for status updates during deployment (dashboard, email summary, standing meeting)? Options: Live dashboard, Weekly email, Standing meeting, Combination

Final Readiness Checklist — The Things We Cannot Skip

• Please mark which of the following are confirmed and available prior to pilot: API credentials, test accounts, sample data, vendor approvals, security sign-off. Options: API credentials, Test accounts, Sample data, Vendor approvals, Security sign-off
• Which risk controls must be demonstrably working before we run DOT-related actions in production (audit logs, encrypted storage, dual-approval for changes)? Options: Audit logs, Encrypted storage, Dual-approval, Automated alerts, Role-based access
• What’s the last missing dependency that, if unresolved, should delay go-live? Options: Data access, Vendor integration, Security approval, Operator training, Other
• Realistically, when can you provide the earliest complete set of credentials, test accounts, and sample data we requested? Options: Immediately, Within 1 week, 1–2 weeks, 2–4 weeks, >4 weeks

Getting Oriented — Who We’re Talking With Today

• Which role are you participating as in this conversation? Options: Driver Recruiting Manager, Safety Director, HR Leader/TA, Operations/Dispatch Manager, Director of Fleet, Other
• What is the size and type of fleet you oversee (drivers and business model)? Options: 1–50 drivers (private fleet), 51–200 drivers (regional carrier), 201–1000 drivers (national carrier), 1000+ drivers (enterprise), Owner-operator network/other
• Which single outcome matters most to you right now? Options: Increase applications, Improve application-to-hire conversion, Reduce time-to-first-dispatch, Audit-ready DOT files, Improve 90-day retention, Lower cost-per-hire, Other
• Briefly, what has prompted you to take a closer look at a new driver management approach today?

Are We Settling for “Good Enough”?

• What’s one hiring or compliance problem you’ve been tolerating because solving it felt too painful or expensive?
• How long has this been tolerated—weeks, months, years? Options: <3 months, 3–12 months, 1–3 years, 3+ years
• When that problem shows up, what immediate operational consequences do you see (e.g., missed loads, fines, overtime)? Options: Missed loads/dispatch delays, Regulatory fines/audit exposure, Overtime and coverage gaps, Increased recruiting spend, Driver safety incidents, Other
• Who on your team is most frustrated by this—recruiting, safety, payroll, or operations? Tell a recent example. Options: Recruiting/TA, Safety/Compliance, Payroll/HRIS, Operations/Dispatch, Senior Leadership
• What attempts have you made to fix it and why didn’t they stick?

Where the Pipeline Actually Breaks (and Why You Might Be Missing It)

• If you had to point to one step where most candidates vanish, which is it—awareness, apply, qualification, drug testing, onboarding, or first dispatch? Options: Awareness/sourcing, Apply (mobile/form friction), Qualification (MVR, PSP), Medical/drug testing, Electronic onboarding/orientation, First dispatch
• What is your current baseline for these metrics? (Please include numbers where available: weekly applicants, application-to-hire %, average days-to-hire, days-to-first-dispatch)
• Which candidate sources deliver the most hires today, and which produce the lowest conversion despite volume? Options: Job boards, Text-to-apply/keyword, Social media ads, Referrals, Internal re-hires, Staffing agencies, Other
• How mobile-friendly is your application and document upload experience on a scale of 1–5? Options: 1 - not mobile friendly, 2, 3, 4, 5 - very mobile friendly
• When candidates drop off, what reasons do they give most often (in their words if you have them)?
• Where do you think small changes could move the needle fastest—messaging, form length, screening rules, logistics (tests/appointments), or follow-up cadence? Options: Messaging/ads, Form/application length, Screening criteria, Scheduling logistics (meds/tests), Follow-up/candidate communication, Other

When Compliance Breaks the Business — Truths Many Teams Avoid

• How confident are you, right now, that a random driver file would pass a federal audit without missing documents? Options: Very confident, Somewhat confident, Unsure, Not confident at all
• What DOT elements do you struggle to keep current and complete (select all that apply)? Options: MVRs, PSP queries and results, DOT medical certificates, Drug & alcohol testing records, Employment verifications (previous employers), License expirations, FMCSA Clearinghouse, Other
• Tell us about a time a compliance gap caused real pain (audit, fine, lost contract, or operational interruption). What happened and how did it feel for your team?
• Who currently owns compliance end-to-end in your organization, and where are handoffs causing delays or errors? Options: Safety/Compliance team, Recruiting/TA, HR/Payroll, Operations/Dispatch, Shared/No clear owner
• What tools or manual processes do you rely on today to assemble a driver qualification file? Options: Paper files/scanners, Spreadsheets, Legacy ATS, Separate safety system, Integrated driver platform, Other
• How would reducing audit risk change how leadership feels about investing in tools or headcount?

What Would True 90–Day Retention Actually Change for You?

• If your team doubled 90-day retention, what are three concrete business impacts you’d expect to see within the year?
• What is your current 90-day retention rate and what target feels realistic for you in 12 months? Options: <30%, 30–50%, 51–70%, 71–85%, 86–95%, 95%+
• Which parts of onboarding and early employment tend to correlate with early exits—orientation quality, pay clarity, route/trip expectations, manager touchpoints, or other? Options: Orientation/onboarding, Pay/compensation clarity, Route/schedule mismatch, Manager/mentor support, Benefits administration, Other
• Describe a recent new-hire experience that ended well — what kept that driver on board past 90 days?
• What retention interventions have you tried (mentorship, pay tweaks, targeted training), and which produced measurable improvement? Options: Mentorship/buddy programs, Sign-on/retention bonuses, Early driver pay increases, Improved orientation, Route matching, None yet, Other

If We Could Reimagine Your Hiring Flow Together — What Needs to Be Non-Negotiable?

• Which modules must be part of any solution for you to consider it (pick all that must be included)? Options: Sourcing/job distribution, Mobile text-to-apply, ATS with driver workflows, DOT qualification file management, Onboarding & orientation scheduling, Ongoing compliance monitoring, Analytics & retention dashboards, Integrations (payroll/ATS/safety)
• What integrations are mandatory for a go-live to be meaningful (payroll, ATS, ELD/dispatch, background vendors, Clearinghouse)? Options: ATS, Payroll, Dispatch/ELD, Drug testing lab vendors, Background check vendor, FMCSA Clearinghouse, State MVR vendor, Other
• What reporting or dashboards would give you comfort that the system is delivering (sample KPIs or specific views you need)?
• Who would need to be able to use the platform day-to-day (roles and primary responsibilities)? Options: Recruiters/TA, Safety/Compliance, HR/Payroll, Operations/Dispatch, Site Managers/Terminals, Executives
• What acceptance criteria would you require in a pilot to sign off on a broader rollout? Options: Improved conversion %, Reduced days-to-first-dispatch, Audit-ready files % target, Positive user feedback, Integration stability

What Could Derail a Deal — Let’s Name the Real Risks

• What is the single most likely reason a procurement or pilot would stall between agreement and go-live in your organization? Options: Integration complexity, Executive sponsorship loss, Budget timing, Internal IT capacity, Regulatory concerns, Change resistance from ops
• Who are the decision-makers and blockers we should expect, and what are their biggest concerns?
• What timeline does your leadership expect for pilot to production (weeks/months), and how flexible is that timeline? Options: 2–4 weeks, 1–3 months, 3–6 months, 6+ months, Flexible
• What internal resources can you commit to integrations and change management (IT hours/week, recruiting time, safety team involvement)? Options: <10 hours/week, 10–20 hours/week, 20–40 hours/week, Dedicated project team
• What would be a non-negotiable governance or escalation path to keep a deployment on track? Options: Weekly steering meetings, Executive sponsor reviews, Dedicated program manager, Service-level KPIs, Other

Quick Wins, Pilot Ideas, and What Success Feels Like

• Which quick pilot would you want first—sourcing optimization, mobile apply redesign, automated DOT file assembly, or onboarding automation? Options: Sourcing/job distribution optimization, Mobile text-to-apply & form simplification, Automated DOT file assembly, Onboarding & orientation automation, Compliance monitoring pilot, Analytics dashboard pilot
• Which single metric would make that pilot an obvious success to you? Options: +applications, Higher application-to-hire %, Faster days-to-first-dispatch, Higher audit-ready file %, Improved 90-day retention, Lower cost-per-hire
• What resources would you commit to a 30–90 day pilot (people, data, test accounts, candidate volume)?
• What would keep you from scaling the pilot—even if metrics look good? Options: Integration issues, Leadership buy-in, Budget constraints, Operational resistance, Training/time to adopt, Other
• If we agreed on a pilot, what would the ideal next step look like for your team in the next 7 days? Options: Kickoff meeting, Data/API access granted, Select pilot terminals/sites, Define success metrics, Other