Keeping Up With Regulatory Change

Regulatory requirements move, and they move quietly. A clause is revised, a transition period ends, a new requirement takes effect, and an organisation that was fully compliant last year can be out of step without anyone having made a decision to change anything.

Why Requirements Change

Regulations and standards change because technology, clinical practice and evidence all change. A requirement written for an earlier generation of devices may no longer address the risks that matter most today.

They also change because of events. A serious incident or a newly recognised hazard can prompt a revision that would otherwise have taken years, and organisations that were comfortable can find themselves with work to do at short notice.

Membership of the relevant professional bodies is often the cheapest way to hear about change early. The information arrives as a summary rather than raw text, which makes it much easier to judge whether a revision affects you at all.

The Shapes of Change

Change does not arrive in one form. A new requirement may be introduced, an existing one tightened, a transitional period brought to a close or an old rule withdrawn because it has been superseded.

Each has a different consequence. A closed transition period demands action by a date, while a withdrawn rule may simply mean that practice which was previously required is now optional, which is itself a decision to make.

It is worth assigning the watching role to a named person rather than to a department. Work distributed across a team has a habit of being done by everyone and owned by nobody, and regulatory change is exactly that kind of task.

A Workable Watching Routine

• List the bodies and publications whose requirements affect you.
• Check them on a regular cycle rather than only when prompted.
• Record which edition or version each of your practices relies on.
• Assess whether each change applies to your devices and settings.
• Plan any necessary work across the whole transition period available.

Building a Watching Routine

The practical answer is a routine rather than a heroic effort. Identifying which bodies and publications matter for your devices and activities, and checking them on a predictable cycle, is enough to catch most changes while there is still time to respond.

It helps to record the source of each requirement you rely on. When a document is revised, a list of what you depend on lets you see quickly which of your practices are now affected.

Where a change affects several teams, a short briefing is more effective than a circulated document. People act on what they have heard explained, and the explanation also surfaces the practical obstacles that a written notice tends to conceal.

Assessing the Local Impact

Not every change applies to you. The first question is whether the requirement covers the devices, activities or settings you are actually responsible for, and the second is what would have to change in practice if it does.

Answering both honestly prevents two opposite errors: doing unnecessary work on requirements that do not apply, and assuming that a change is irrelevant without having checked.

Some requirements change in ways that remove obligations rather than add them. These are easy to miss because nobody is chasing them, and they are worth catching, since dropping work that is no longer required frees effort for the requirements that do apply.

Types of Change and What They Demand

Planning the Transition

Where action is needed, the transition period is the resource to use. Work planned across the available time is far cheaper than the same work compressed into the weeks before a deadline.

The plan should be specific about what changes, who owns it and how completion will be demonstrated. A general intention to comply is not a plan, and it is what turns a manageable change into a last-minute scramble.

Aligning the review with existing planning cycles helps it survive. A regulatory check attached to a meeting that already happens is far more likely to be repeated than one which depends on a separate occasion being arranged each time.

Recording and Reviewing

Recording what you concluded about each change, including the decision that a requirement did not apply to you, is part of good practice. The reasoning is the evidence if the judgement is ever questioned.

Reviewing that record periodically closes the loop. Requirements that were irrelevant last year may apply this year as devices or services change, and the review is what catches the difference.

Finally, the record of decisions is the thing most often skipped and most often needed. Two lines explaining why a change was judged not to apply can save a great deal of reconstruction the next time the same question is asked.

Keeping up with regulatory change is mostly a matter of routine attention rather than expertise. Watch the sources that affect you, assess the local impact honestly, plan across the transition period and record the reasoning behind every decision you reach.