Skip to content

Driver Compliance Monitor · Healthcare & NEMT

Never send a driver out on a lapsed credential

Every weekday morning it checks each driver's license, medical card, drug tests, insurance and certifications, and proposes holds for a manager to confirm.

Available now $99 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Runs on a schedule
  • 1 AI step
  • A person approves before it acts
  • About 20 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “We found out a driver's medical card had expired after he'd worked a week.”
  • “Tracking renewal dates across the fleet is a spreadsheet nobody opens.”
  • “Dispatch doesn't know who shouldn't be on the road today.”

What you get with the agent

  • A weekday check of every driver's credentials against today's date and the requirements you set
  • Lapsed, missing and expiring credentials (30, 14 and 7 days out) posted to your compliance channel
  • Proposed dispatch holds for drivers with a lapsed or missing required credential
  • Holds confirmed by a manager, then posted to your dispatch channel
  • A dated record of each day's check in the run history

Before

Credential dates live in a spreadsheet someone checks before an audit, and expirations are discovered after the fact.

After

Each morning, compliance sees what's expiring this month, and dispatch has a manager-confirmed list of who's on hold today.

How it works

The whole workflow, step by step.

Every weekday morning the agent reads your driver credentials sheet in Google Sheets and AI checks each credential against today's date and the requirements you set: driver's license, medical card, drug-test cadence, insurance, training and state NEMT certifications. Lapsed, missing and expiring credentials (30, 14 and 7 days out) are posted to your compliance channel in Slack. Drivers with a lapsed or missing required credential are proposed for a dispatch hold; once a manager confirms the list, it's posted to your dispatch channel. It reads the dates in your sheet; it doesn't verify credentials with outside agencies or block drivers in other software.

  1. TriggerWeekdays at 6 am
  2. App callRead the driver credentials sheet
  3. LogicCheck the credential dates
  4. AI stepCheck every driver's credentials
  5. LogicAnything to act on?
    • Issues found:Post the compliance report in Slack
    • Issues found:Manager confirms the dispatch holds
    • All clear:All clear
  6. App callPost the compliance report in Slack
  7. Human approvalManager confirms the dispatch holds
    • Confirmed:Tell dispatch who is on hold
  8. App callTell dispatch who is on hold
  9. OutputAll clear

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1Weekdays at 6 amRuns each weekday morning before dispatch starts. Change the time and time zone on the trigger.
  2. Step 2Read the driver credentials sheetReads your driver credentials sheet in Google Sheets: one row per driver with each credential's expiry or last-done date.
  3. Step 3Check the credential datesIn code, not AI: for each driver works out every credential's days left and tier — lapsed, 7, 14 or 30 days, or ok — from the expiry dates, and from the last-done date plus its renewal interval (drug test every 365 days, PASS every 1,095 days). Every driver stays in the list. Change the columns, intervals and tiers here (fields and buckets).
  4. Step 4Check every driver's credentialsAI reads each credential's tier worked out in code (lapsed, expiring in 30 / 14 / 7 days, or missing) against your requirements and proposes which drivers to hold from dispatch.
  5. Step 5Anything to act on?Lapsed, missing or expiring credentials go to your compliance channel and the hold list goes to a manager for confirmation; an all-clear day is just logged.
  6. Step 6Post the compliance report in SlackPosts lapsed, missing and expiring credentials (30 / 14 / 7 days) to your compliance channel.
  7. Step 7Manager confirms the dispatch holdsYour compliance or operations manager checks the proposed holds in Reviews (a renewal may not be in the sheet yet), edits the list and approves it to tell dispatch.
  8. Step 8Tell dispatch who is on holdPosts the confirmed hold list to your dispatch channel so those drivers aren't given trips.
  9. Step 9All clearDays with nothing to act on are kept in the run history as a dated record of the check.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

A fictional driver row: medical card expires in 8 days, last drug test over a year ago, everything else current.

The agent produces

Compliance post lists the medical card in the 14-day group and the drug test as overdue under your annual cadence. The driver is proposed for a hold; once a manager confirms, dispatch is told.

What you need

Everything it takes to run it.

About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $99 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets and Slack, connected in Settings → Integrations.
  • A Google Sheet with one row per driver and a date for each credential, kept up to date.

Setup, about 20 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open your driver credentials sheet (Settings → Integrations → Google Sheets).
  3. Connect Slack. Connect the Slack workspace your compliance and dispatch teams use (Settings → Integrations → Slack).
  4. Pick your driver credentials sheet. Open “Read the driver credentials sheet”, pick your Google account, paste the spreadsheet link and pick the tab.
  5. List your credential requirements. Open “Check every driver's credentials” and replace the placeholder with each credential and whether it's required to drive. Check the date columns and renewal intervals on “Check the credential dates”.
  6. Pick the compliance and dispatch channels. Open the two Slack steps and pick your account and channel in each. Invite the app to private channels first (/invite @Fluxo Flow).
  7. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  8. Switch the trigger on. Open the trigger, check the time and time zone, and switch the schedule on. Assign the review step to your compliance manager.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • NEMT and paratransit operators
  • Fleet and safety managers at transportation companies
  • Compliance coordinators tracking driver files

What it doesn't do

  • It doesn't block drivers in your dispatch or scheduling software; a manager confirms holds and dispatch applies them.
  • It doesn't verify credentials with the DMV, testing labs or insurers; it reads the dates in your sheet.
  • It doesn't message drivers directly or collect documents.
  • It doesn't produce an audit binder; the run history keeps each day's report.

We list the limits up front so you can decide before you buy.

Price

$99 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Driver Compliance Monitor.

Does it block drivers in our dispatch software?

No. It proposes holds, a manager confirms them, and the confirmed list is posted to your dispatch channel for dispatchers to apply.

Does it verify credentials with the DMV or labs?

No. It reads the dates in your sheet, so keep it updated when a driver renews. It doesn't message drivers or collect documents.

What does setup involve?

About 20 minutes: a Google Sheet with one row per driver and a date for each credential, your requirements in plain text, and Slack channels for compliance and dispatch.

Is it worth the price?

It's a one-time purchase that never renews that checks every driver, every weekday, without anyone remembering to. Live runs need a paid plan and your own AI key; Dry Run is free.

Does it block drivers in my dispatch software?

No. It proposes holds, a manager confirms them, and the confirmed list is posted to your dispatch channel. Your dispatchers apply it.

Where does the credential data come from?

From your Google Sheet. Keep it updated when a driver renews; the agent reads it fresh every morning.

Which columns are checked?

“Check the credential dates” reads License expires, Medical card expires, Insurance expires, CPR expires, Last drug test (every 365 days), PASS completed and Defensive driving completed (every 1,095 days). Column names can vary a little. A credential you require that isn't on that step is reported as missing until you add its column there.

Is this a subscription?

No. Driver Compliance Monitor is a one-time purchase of $99 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Driver Compliance Monitor to work.

Free account, no credit card. Your Agents page opens with Driver Compliance Monitor ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works