How to Set Up DVSA Trigger Point Alerts and Self-Audit Workflows in FleetForge

Most operators don't lose their licence in one dramatic moment. It's a slow accumulation: a missed PMI window here, a tachograph download that slipped past the 28-day deadline there, a defect that sat open for too long. By the time DVSA issues a formal notice, the pattern is already established.

The good news is that DVSA's own trigger point system gives you a warning before it escalates. The better news is that FleetForge is built to surface those warnings automatically, so you're not relying on memory or spreadsheets to stay on top of them.

This post walks through exactly how to configure alerts and self-audit workflows inside FleetForge to keep your operation in the green.

What we'll cover:

• What DVSA trigger points actually are (and when they fire)

• Which compliance areas FleetForge monitors automatically

• How to configure your alert thresholds and notification settings

• How to run a self-audit workflow before DVSA does it for you

What Are DVSA Trigger Points?

Trigger points are the thresholds built into the DVSA Earned Recognition scheme that determine when your compliance performance is poor enough to warrant automatic notification to DVSA. They sit above your KPIs as an escalation layer.

Under Earned Recognition, KPIs are measured over rolling four-week periods. When you miss a KPI, the system issues an internal alert. Miss it badly enough, or repeatedly enough, and the system fires a trigger directly to DVSA.

The three alert levels

Alert level	When it fires	Who sees it
Yellow (Minor)	Missing a KPI by less than 1 percentage point	You only
Amber (Moderate)	Missing a KPI by 1 percentage point or more	You only
Grey (Major)	Missing a KPI by 2 percentage points or more	You and DVSA automatically

Grey alerts are reported to DVSA at the end of the measurement period. There is no grace window once a grey fires.

What triggers an automatic DVSA notification

According to GOV.UK's Earned Recognition guidance, DVSA is alerted automatically when any of the following occur:

• Any single KPI is missed by 2 percentage points or more in one measurement period

• Any KPI is missed three times by less than 1 percentage point over three rolling periods

• Any KPI is missed twice by 1 percentage point or more over three rolling periods

• Any KPI is exceeded more than four times over 13 rolling measurement periods

• A driver infringes in three consecutive measurement periods

The practical implication: you do not need a catastrophic failure for DVSA to be alerted. A persistent, low-level drift in maintenance compliance or driver hours is enough. That's exactly the kind of slow bleed that FleetForge's alert system is designed to catch before it reaches that threshold.

What FleetForge Monitors Automatically

Before configuring alerts, it helps to know which compliance areas FleetForge tracks in the background. The platform monitors the core areas DVSA focuses on during desk-based assessments and roadside checks.

Vehicle and maintenance compliance

• PMI scheduling: FleetForge tracks each vehicle's safety inspection frequency against your stated schedule. Approaching deadlines appear on the management dashboard before they breach.

• MOT and annual test dates: Expiry dates are stored against each vehicle record. The system flags vehicles approaching their MOT date so you're never caught with an out-of-date test.

• Defect status: Every defect logged through a walkaround check carries an open/closed status. FleetForge highlights defects that remain open past a defined period, which is one of the most common findings during DVSA assessments.

Driver records and hours

• Licence and CPC expiry: Driver records include licence check dates and Driver CPC expiry. Alerts fire ahead of the expiry window so renewals don't get missed.

• Tachograph download compliance: FleetForge tracks download dates against the statutory deadlines: 28 days for driver cards, 90 days for vehicle units. Overdue downloads are flagged on the dashboard.

• Driver hours infringements: When infringement data is recorded, FleetForge logs it against the driver record and tracks frequency across measurement periods.

Walkaround checks

Daily check completion is recorded in real time as drivers submit via the mobile app. The dashboard shows which vehicles have a completed check for the current day and which don't, giving you an immediate view of gaps before a vehicle leaves the yard.

Why this matters in 2026: DVSA confirmed that electronic records are fully acceptable for documenting walkaround checks, safety inspections, and defect records. Digital, timestamped records are now the standard DVSA expects to see, not a folder of paper forms.

Configuring Your Alert Thresholds

FleetForge's alert system is designed to give you early warning before a compliance issue reaches the level where DVSA would be notified. Here's how to set it up properly.

Step 1: Set your advance warning windows

Navigate to Settings > Alerts & Notifications in your FleetForge account. For each compliance area, you can define how far in advance an alert fires. We recommend the following as a baseline:

Compliance area	Recommended alert window
PMI / safety inspection	14 days before due
MOT expiry	28 days before due
Driver CPC expiry	60 days before due
Licence check due	30 days before due
Tachograph download (driver card)	7 days before 28-day deadline
Tachograph download (vehicle unit)	14 days before 90-day deadline
Open defects	Flag if unresolved after 48 hours

Adjust these to suit your operation. If you're running a larger fleet with more moving parts, tighten the windows. The point is to build in enough lead time to act, not just be informed.

Step 2: Configure notification recipients

Under each alert category, you can assign which users receive the notification. For most operators, this means:

• Transport Manager: receives all alerts across all vehicles and drivers

• Depot or fleet supervisor: receives alerts for their assigned vehicles only

• Driver: receives personal alerts for their own licence, CPC, and tachograph card

Notifications are delivered by email and in-app. If you're an external Transport Manager covering multiple operators, you can configure alerts per client account and receive them all in one place.

Step 3: Set escalation rules for open defects

This is the one most operators miss. Go to Defect Management > Escalation Settings and define what happens when a defect remains open beyond your threshold. FleetForge can:

• Send a reminder notification to the assigned manager at 24 hours

• Escalate to a secondary contact at 48 hours

• Flag the vehicle as requiring attention on the dashboard until the defect is closed with evidence

This matters because open defects without documented rectification are a direct finding during a DVSA assessment. The system creates the audit trail automatically, but only if escalation is configured.

Running a Self-Audit Workflow

Alerts tell you something needs attention. A self-audit workflow tells you whether your operation would pass if DVSA knocked on the door today. The two serve different purposes, and you need both.

We recommend running a structured internal audit at least once per four-week KPI measurement period. Here's the workflow we suggest inside FleetForge.

1. Pull the compliance summary report

Go to Reports > Compliance Overview. This generates a snapshot of your current position across all monitored areas: PMI completion rates, defect open/close rates, walkaround check completion, and document expiry status.

Look specifically for any areas where your rate has dropped compared to the previous period. A single missed PMI is an anomaly. Two in a row is a trend that DVSA's trigger system will start counting.

2. Review open defects and rectification times

Under Defect Management, filter by status: open and in-progress. For each open defect, check:

• Has it been assigned to a responsible person?

• Is there a planned rectification date?

• If it's been rectified, has the evidence (photo, workshop sign-off) been attached and the defect closed?

DVSA expects to see that defects were actioned, not just logged. The closed defect record with supporting evidence is the proof.

3. Check driver record completeness

Run the Driver Records Report and look for:

• Any licence checks overdue or approaching their review date

• Any Driver CPC hours that are behind schedule relative to the five-year cycle

• Any driver with a tachograph card download overdue

This takes about five minutes for a small fleet. For larger operations, the report filters let you sort by status so you're only looking at exceptions.

4. Verify your walkaround check coverage

Under Daily Checks, filter the last 28 days and look for any vehicles that had operational days without a completed check. A gap here is one of the simplest findings DVSA makes during a desk-based assessment.

If you find gaps, check whether the driver submitted a check via the app or whether the vehicle operated without one being logged. The former is a records issue; the latter is a compliance failure that needs addressing with the driver.

5. Generate your DVSA readiness pack

Once you've reviewed the above and addressed any gaps, go to Reports > DVSA Readiness Pack. FleetForge compiles your records into an organised evidence pack covering vehicles, drivers, checks, defects, and maintenance history.

Keep this habit: generating the pack monthly means you always have a current, structured evidence base. If a Desk-Based Assessment letter arrives, you're not scrambling to pull records together under a tight deadline.

This is the step that most operators only think about when DVSA contacts them. By then, the window to fix gaps has already closed.

A Note on Operator Responsibility

FleetForge supports your compliance management. It does not replace your responsibilities as an operator or Transport Manager. The alerts and workflows described here are tools to help you maintain oversight; acting on them is still down to you and your team.

What the system does is remove the "I didn't know" defence. If an alert fires and nothing is done, that's now a documented gap rather than an oversight. That's actually a useful discipline: it forces action rather than allowing issues to drift.

The DVSA's Earned Recognition scheme is built on the principle that operators with robust internal systems need less external intervention. FleetForge is designed to help you build and evidence exactly that kind of system.

If you're not yet using the alert and self-audit features, the configuration steps above are a good place to start. It takes less than an hour to set up properly, and it's the kind of groundwork that makes a material difference when DVSA comes looking.

Explore FleetForge at fleet-forge.com.