What Clients Are Often Surprised to Learn About Regulatory Projects

What Clients Learn About Regulatory Projects

Regulatory projects are often viewed as highly technical exercises focused on analysing evidence, reviewing regulatory requirements or assessing potential impacts. While these activities are important, they are often only part of the picture.

Clients are sometimes surprised by the range of issues that arise during a project and the amount of work involved before any analysis or recommendations are produced. In many cases, the most important discussions take place before the detailed work begins.

Based on our experience supporting organisations across a range of regulatory and policy issues, there are several aspects of regulatory projects that clients are often surprised to discover.

Understanding the question is often as important as finding the answer

Most projects begin with a request for analysis, evidence or advice. However, before any meaningful work can take place, there is usually a discussion about the decision that needs to be made, who will make it and what information is likely to be most relevant.

Two organisations may appear to be asking the same question but have very different reasons for asking it. One may be concerned about customer impacts, another about alternatives and a third about future investment decisions.

The analysis required may therefore be very different.

It is often tempting to jump straight into the evidence. However, understanding the question is usually what determines whether the work is ultimately useful and whether the conclusions support decision making.

Technical questions often become business questions

Many projects begin with what appears to be a relatively technical issue.

Questions about alternatives, regulatory requirements, compliance obligations or substance use can often be framed as technical problems requiring technical answers.

However, these discussions frequently expand beyond technical considerations.

Questions around customer acceptance, qualification requirements, investment needs, implementation timelines and supply chain impacts often become equally important. For example, a technically feasible alternative may still require significant customer approvals or changes to existing manufacturing processes before it can be adopted in practice.

As a result, regulatory projects often involve a combination of technical, regulatory and economic considerations rather than a single discipline.

Useful evidence comes from many sources

Published studies and technical data are important components of many regulatory projects. However, some of the most useful evidence may come from other sources.

Operational experience, customer requirements, implementation experience and supply chain information can all contribute to a better understanding of how a substance, technology or regulatory proposal may affect organisations in practice.

For example, technical data may demonstrate that an alternative performs effectively under certain conditions. Organisations may still need to understand whether customers will accept it, whether specifications need to change and how long implementation might take.

These questions are often informed by practical experience rather than scientific literature alone.

This is one reason why stakeholder engagement and evidence gathering are often important parts of regulatory projects.

The conclusion is not always the one expected at the start

Many projects begin with assumptions. Some prove correct. Others become weaker as additional evidence is reviewed. Occasionally, entirely new questions emerge during the course of the work.

For example, a project may begin with a focus on alternatives and ultimately identify implementation as the more significant issue. A project focused initially on compliance costs may uncover broader supply chain or customer impacts. A project focused on technical feasibility may reveal evidence gaps requiring further investigation.

This does not mean the project has failed. In many cases it means the project has achieved its purpose.

The objective of a regulatory project is not to support a predetermined conclusion. It is to understand what the available evidence supports, identify uncertainties and provide a robust basis for decision making.

Independent analysis can often add value by testing assumptions, identifying evidence gaps and helping organisations understand the implications of different options.

Supporting informed decision making

While regulatory projects are often associated with technical analysis, they frequently involve a much broader range of considerations. Understanding the question, gathering relevant evidence, assessing practical implications and challenging assumptions can all be important parts of the process.

Ultimately, the purpose of a regulatory project is not simply to produce a report. It is to provide decision makers with the information they need to understand issues, assess options and make informed decisions.