
When compliance training improves but still falls short
A public sector report shows employee compliance jumping from 34% to 93% in a year, yet the 100% target remained unmet. For UK SMEs, the gap reveals a familiar administrative problem that AI automation can close.


A large, well-resourced public sector organisation ran a focused compliance learning initiative last year. Employee compliance rose from 34% to 93% in a single year. That is a genuinely strong result. And yet the KPI target of 100% remained unmet.
The gap between 93% and 100% might look small on paper. In practice it represents a category of problem that most HR Managers, Operations Managers, and Compliance Officers will recognise immediately. The training programme worked. The delivery did not reach everyone. And the difference was almost certainly not knowledge or motivation. It was the administrative chain that sits underneath any compliance programme: the reminders, the evidence capture, and the reporting.
The problem that well-designed training cannot solve on its own
Compliance completion is not a single event. It is a process that runs over weeks or months, involves multiple team members, and depends on consistent follow-up.
When that follow-up is manual, it degrades. Reminders get sent late, or not at all. Evidence of completion is stored inconsistently. Managers receive incomplete data and cannot tell who still needs to act.
The result is a familiar pattern. The majority of staff complete the required training. A small percentage slip through. The organisation records strong progress but falls short of the formal target. This is not a failure of intent. It is a failure of infrastructure.
For SMEs, the infrastructure problem is sharper still. A mid-sized business with 50 to 150 staff rarely has a dedicated compliance team. The responsibility sits with an HR Manager or Operations Manager who is carrying several other priorities. Manual tracking of completion rates is time-consuming and error-prone. The admin overhead of chasing, logging, and reporting can consume hours each week without adding any real value to the compliance outcome. The same chain sits behind competency records for fire engineers, CPD records in membership bodies and regulatory training in law and accountancy firms.
Why the 7% gap is not a training problem
The data from the public sector example tells a clear story. A 59-percentage-point improvement in one year is evidence that the learning content worked. Staff who engaged with the programme completed it successfully.
The World Economic Forum has noted that AI delivers its most consistent business value not through the software itself but through the workflows surrounding it. The same logic applies here. The content of the training is not the constraint. The workflow around delivery, follow-up, and evidence capture is.
For the 7% who did not complete, the most likely causes are straightforward. They did not receive a timely reminder. Their completion was not captured in a way that fed back into the reporting chain. No one flagged to a manager that they were outstanding. Each of these is an administrative failure, not a learning one.
This distinction matters for any Operations Manager or Compliance Officer designing a compliance programme. Investing further in learning content will not close the gap. Fixing the surrounding workflow will.
What the administrative failure costs SMEs
For a business operating under regulatory requirements, an incomplete compliance record carries real risk. Auditors and regulators look for evidence of completion, not effort. A 93% rate with no audit trail is harder to defend than a lower rate with clear documentation of who was chased and when.
Beyond regulatory exposure, there is a cost in management time. HR Managers who track completion manually typically spend significant hours each reporting period compiling records, sending follow-up emails, and assembling evidence for reporting. That time is not recoverable and does not scale as headcount grows.
For SMEs, the calculation is straightforward. The cost of incomplete compliance is measured in regulatory risk and management time. Both are reducible with the right approach.
How AI automation addresses the workflow layer
The compliance workflow that fails under manual load has a clear structure. It involves a trigger, a series of timed follow-ups, a completion capture step, and a reporting output. Each of these steps can be automated.
AI-supported automation in this context works as follows. A trigger, such as a new staff member joining, a policy update, or an annual renewal date, initiates a workflow. The workflow sends a prompt to the relevant team member at a defined interval. If no completion is recorded, a follow-up prompt is sent. After a further interval, a manager is notified. When completion is recorded, the evidence is logged automatically and the record is updated.
This removes the human administrative layer without removing human oversight. Managers receive structured reports. Compliance Officers have an auditable record without building a spreadsheet from scratch each quarter. HR Managers spend time on the cases that genuinely need attention, rather than chasing the majority who would complete with a simple prompt.
The output is consistent follow-up for every team member, not just those whose names surface in a manual review.
Implementation safeguards to consider
Automating compliance workflows requires care in two areas. First, audit trails must be preserved in a format that meets the standards your regulators or insurers expect. A record that shows when a reminder was sent and when completion was logged is more defensible than a record that shows only final status.
Second, any workflow that handles employee or customer data must align with UK data protection obligations. This means understanding what data is captured, where it is stored, how long it is retained, and who has access. For most SMEs, this is a configuration decision made at setup, not an ongoing burden. But it requires deliberate attention at the design stage, not after deployment.
Compliance automation is not a set-and-forget approach. The workflow needs to be reviewed when policies change, when team structures shift, or when regulatory requirements are updated. Treating the automated workflow as infrastructure, rather than a one-off project, is the more durable approach.
Making this work for your business
For Operations Managers and HR Managers looking to reduce the administrative overhead of compliance tracking, the starting point is mapping the current workflow. Where does follow-up currently break down? Where is evidence captured inconsistently? Where does reporting require manual assembly?
Those are the steps that automation addresses most directly. The goal is not to replace the compliance programme. It is to make the surrounding workflow reliable enough that the programme reaches everyone it should.
gecco's Automations service connects 7,000+ platforms using event-triggered, no-code workflows with full audit trails. For compliance use cases, this means automated reminders sent at defined intervals, completion data captured without manual chasing, and structured reports generated for managers, removing the administrative overhead that causes capable programmes to fall short of their targets.
Start with a clearer picture of where you are
If you are an Operations Manager, HR Manager, or Compliance Officer asking whether your current compliance workflow could reach more of your team with less manual effort, that is exactly the question the AI Readiness survey is built to surface.
Take the free AI Readiness survey. You will receive 65+ free resources and a custom AI Readiness report based on your answers. From there you can book a free 30-minute showcase to walk through the results with a gecco adviser.

Cash-flow gaps are costing SMEs real growth
Nearly four in ten UK B2B SMEs missed growth opportunities last year because of cash-flow pressure. Automated forecasting and late-payment detection can change that.

OpenAI's always-on agent used 300k tokens unprompted
OpenAI's dot assistant consumed over 300,000 tokens in 24 hours without a single user prompt, raising real cost and data access risks for UK SMEs. This article explains what happened and what governance boundaries you should have in place before deploying any autonomous agent.

