The Real Cost of a Regulation Change
A few years back, a charity I was working with commissioned a new safeguarding course. They did everything right. Found a good instructional designer, engaged their subject matter experts, and spent a little over £15k on a first-rate piece of learning. It was clear, engaging, and everyone who took it knew exactly what was expected of them.
Two years later, the government issued new statutory guidance. Nothing seismic, but enough – a few shifted definitions, a new reporting requirement. Their course, the one they’d been rightly proud of, was now technically non-compliant. A liability, sitting on their LMS.
They went back to the original agency. The quote to update it came in at £8k, with an eight-week lead time. Meanwhile, the Director of L&D was looking at her total training budget for the quarter: £12k to cover everything. Management training, the new induction programme, software skills for the finance team. Everything.
So what happens?
You know what happens. The update doesn't get signed off. The eight thousand pounds isn't spent, because spending it would mean gutting the entire quarter's plan. And so the organisation, a charity dedicated to vulnerable people, continues to run a safeguarding course it knows is out of date. Maybe they add a note to the introduction, or send a follow-up email with a link to the new guidance. A sticking plaster over a structural wound.
Everyone involved feels a bit sick about it. The training manager worries quietly. The senior team hopes nothing goes wrong. The gap between ‘what we are teaching’ and ‘what is actually true’ becomes a known, accepted, and unmanaged risk.
This isn't a failure of diligence. It’s a failure of the model. It's the moment the traditional, project-based approach to commissioning and creating learning collides with the reality of a world that refuses to stand still.
The half-life of professional knowledge
We talk about content having a shelf life, but we rarely apply the same thinking rigorously to the courses we build. A course isn't a static asset like a book. It’s a live statement about how things are. And its value degrades over time.
For some topics, the decay rate is slow. The principles of giving feedback or managing a project budget are reasonably stable. But for a huge swathe of professional learning – compliance, regulation, clinical practice, financial advice, environmental standards, technology guides – the half-life is brutally short.
A course on medical device regulation from 2019 is now an antique. A guide to ESG reporting from last year is already missing key taxonomies. This isn't an occasional problem; it is the defining condition of professional learning in the 21st century.
Yet we continue to build and buy training as if it were a one-off capital project. We spend months and significant budget creating a perfect artefact, a snapshot in time. We launch it, track completions, and consider the job done. We budget for creation, but we rarely budget for the continuous, ongoing cost of currency. When the world moves on, the artefact we built becomes a risk. And because the original process was so expensive and slow, the activation energy required to update it is impossibly high.
The result is a kind of organisational hypocrisy. We declare our commitment to standards, to safety, to excellence, whilst knowingly propagating information that is no longer quite right. The £15k course becomes an £8k problem, which becomes a quiet, persistent source of anxiety.
Version control is the wrong answer to the wrong question
The logistical friction of an update is where the real cost lies. It's not just the designer's day rate. It’s the cascade of painful, manual steps that follow.
Someone has to brief the change. An expert has to validate the text. The designer makes the change in their authoring tool. A new version is exported. It’s probably a SCORM package, a locked, opaque file named something like Safeguarding_v2.1_FINAL_updated.zip.
That file then needs to be uploaded to the learning management system, replacing the old one. You hope the transition is seamless, that learner records don't get lost. You test it. You find a typo the expert missed. The entire loop begins again. Get the designer back, make the tiny fix, re-export, re-upload, re-test. Each cycle adds days, cost, and another layer of human frustration.
It’s no wonder people don't do it. The entire workflow is designed for creation, not maintenance. It treats a course like a PDF to be replaced, not a living document to be tended.
When we were first thinking about the architecture of CourseAgent, this was the problem that I wanted to solve more than any other. Not the initial act of creation – but the long, difficult life of a course after it goes live.
It seemed obvious to me that the problem wasn't the SCORM package itself, but the act of exporting anything at all. The moment you export, you create a static copy. You break the link with the living source. You create a future maintenance problem, by design.
What if you never had to export? What if the course URL, the Academy portal, and even the SCORM file in your LMS weren't copies, but were all just windows looking at the same, single, central version?
That was the thought behind Live Publish. You make a change – fix that typo, add the new regulatory paragraph, swap an image – and hit save. Instantly, everywhere the course is deployed, it updates. No re-exporting. No uploading. No version v2.1 versus v2.2. The eight-week, eight-thousand-pound headache evaporates. It becomes a ten-minute job for one person.
This isn't just about efficiency. It's about restoring integrity to the process. It allows an organisation to stand behind the training it provides, not just on the day it's launched, but every day after. It closes that awful, unnerving gap between what people need to know and what we can afford to tell them.
It lets the training be as current as the world it’s trying to explain.