← Back to Insights

InsightRisk Assessment

What Makes a Risk Assessment Useful?

A risk assessment is most useful when it changes how leaders understand exposure, set priorities, allocate attention, or decide what happens next.

Key takeaways

  1. Start with what changed since the last assessment, not with last year’s risk register.
  2. A rating is not a decision. Leaders need to know what is driving it and what would move it.
  3. A useful assessment leaves evidence in the decisions that follow: the audit plan, resourcing, monitoring, or a deliberate choice to accept.

A risk assessment meeting can reach a strange point where everyone has done the work and nobody is quite sure what changed.

The familiar moment

The interviews are complete. Ratings have been debated. Comments have been incorporated. Someone puts the final risk register on the screen.

Then a business leader says, “Honestly, this looks almost exactly like last year.”

That does not necessarily mean the assessment was poorly done. The risks may still be valid and the ratings may be supportable. But if leadership already knew everything the assessment is telling them, it is reasonable to ask what the exercise added.

For someone responsible for the business, the useful part is usually not being reminded that cybersecurity, regulatory compliance, fraud, or financial reporting matter. It is understanding where exposure is moving, what is driving the change, and whether something deserves different attention than it is receiving today.

What Has Changed Since the Last Assessment?

Start by asking what is different from the last assessment.

Sometimes the answer is obvious.

  • The company acquired another business.
  • A new system went live.
  • Transaction volume doubled.
  • A regulation changed.
  • A key process moved to a third party.

Other changes are easier to miss.

  • A process that once depended on two experienced employees now depends on one.
  • A manual review still works, but volume has grown enough that the reviewer is struggling to keep up.
  • Several audit issues point back to the same underlying process.
  • A business unit has added products or customers without changing the controls around them.

None of those changes automatically makes the risk high. They do tell you where another conversation may be warranted.

That context is easy to lose when the assessment starts with last year’s risk register. The prior assessment is useful, but it can also anchor the discussion. People see the same risk names, adjust a few scores, update the wording, and move on.

The document is current. The thinking behind it may not be.

Some of the better questions come before anyone looks at the prior score.

Better questions to start with

  • What has become harder to manage?
  • Where are people spending more time than they used to?
  • What are you worried about now that you were not worried about a year ago?

The answers do not always fit neatly into an existing risk category. That is often where the useful information starts.

A High Rating Does Not Tell You What to Do Next

Leadership already knows that some risks are significant.

A public company does not need an annual risk assessment to discover that financial reporting matters. A financial institution already knows that fraud and regulatory compliance require attention. Those risks may remain high year after year for good reason.

The question is what the current assessment adds.

Risk A: high and stable

One risk may remain high even after mature controls are considered because the potential impact of failure is still significant. The exposure is well understood, management receives regular reporting, and conditions have been relatively stable. That does not make the risk unimportant or eliminate the need for assurance.

Risk B: moderate and moving

Another risk may be rated moderate, but something underneath it has started to move. Volume is increasing. A process is becoming more manual. A key manager left. An upcoming system change will alter responsibilities.

That second risk may deserve a different kind of attention now, even if its overall rating remains lower.

This is also why a stale rating can be misleading. If the facts underneath a moderate risk have changed materially but the score has not, the problem may be the assessment itself rather than prioritization.

If the facts underneath a moderate risk have changed but the score has not, the problem may be the assessment itself.

What Is Driving the Rating?

Risk discussions often get stuck on whether something should be a 3 or a 4.

That argument is not always trivial.

In some organizations, moving from a 3 to a 4 changes what happens next. The risk may require committee reporting, additional audit coverage, an action plan, more frequent monitoring, or a formal management response.

Eventually someone says, “If we call this high, it goes to the committee.”

That does not mean the rating should be negotiated down to avoid scrutiny. It does mean the conversation should be honest about why people care so much about the number.

Leadership should also be able to understand what is driving the score without working backward through the methodology.

A risk may have increased because the business grew faster than the process supporting it. Another may have moved because a key control failed repeatedly. In another case, management may have deliberately accepted more exposure as part of a business decision.

Those situations can produce the same rating while requiring very different responses.

This is one reason a risk description such as “failure to comply with applicable regulatory requirements” gives leadership very little to work with. It names a category of exposure. It does not explain what is happening inside the organization that makes the risk worth discussing now.

Heat maps have a place here. They are useful for seeing a broad risk universe quickly, but they compress context. Two risks in the same part of the heat map may be moving in different directions for completely different reasons.

The level of detail should depend on the decision someone is trying to make, not on how much information the methodology can produce.

Not Every Risk Needs the Same Response

Risk assessments sometimes create an expectation that every elevated risk needs an action plan.

That can produce a lot of activity without much change in exposure.

Some risks require investment. Others need management to make a process decision that has been delayed, clarify ownership, or monitor conditions more closely for a period of time. Management may also decide to accept an exposure because additional mitigation would cost more or create more disruption than the risk warrants.

The important part is whether someone actually made that decision.

A known risk with a target date that has been moved three times can quietly become accepted without anyone ever saying so. The same thing happens when everyone knows an exposure exists, nobody disputes it, and no one decides whether it should be mitigated, monitored, or accepted.

From a distance, all of those situations can look like “no action.”

Formal acceptance should sit with someone who has the authority to accept the exposure at that level, and it should be considered against the organization’s appetite or tolerance. It also has to be revisited when conditions change. For Internal Audit, there is an additional escalation question when management appears to be accepting exposure beyond the organization’s established tolerance.

Not every exposure can simply be accepted because management prefers not to address it. Legal and regulatory requirements still set boundaries.

The response also has to be realistic about capacity.

In practice

Five individual action plans may each look reasonable. If all five depend on the same technology team during the same quarter, leadership has to decide what gets done first rather than accept five promises that cannot all be delivered.

Disagreement Can Be Useful, but Not All Disagreement Is

Risk scoring often creates pressure to reach consensus.

Some of that pressure is healthy. If one person is rating inherent risk and another is rating residual risk, or two teams are using different time horizons, the disagreement needs to be resolved. Leadership should not have to sort out inconsistent definitions that the assessment process should have calibrated beforehand.

Other disagreements are more informative.

Two views of the same risk

A business leader may rate a risk moderate because the team has never experienced a significant loss. Internal Audit may see it differently because several key controls are manual and recent testing identified recurring exceptions.

The business leader may know about compensating activity that was never documented. Audit may know the same exception has appeared in more than one review.

There may also be incentives in the room.

A higher rating can attract more scrutiny, create reporting obligations, or trigger additional work, so a risk owner may push the score down. In other situations, a higher rating may help a leader make the case for funding or resources.

The person facilitating the assessment still needs to understand what is behind the disagreement.

In an enterprise risk process, management owns its risk decisions and the second line may challenge and calibrate them. Internal Audit’s own risk assessment has a different purpose. Audit should form an independent view informed by management rather than simply inherit management’s rating.

It is usually more useful to understand why two experienced people see the exposure differently than to receive a risk register where every difference has been smoothed out before leadership sees it.

What Happens After the Assessment?

A useful risk assessment should leave some evidence in the decisions that follow.

For enterprise or management risk assessments, timing matters. If the assessment is completed after budgets and annual priorities are already set, there are fewer opportunities for it to influence those decisions.

What it can look like

Maybe the audit plan changes because a moderate risk is moving faster than expected. Management may shift resources after recognizing that several risk responses depend on the same team. A previously accepted exposure may need another look because the underlying conditions changed.

Sometimes the decision is that no additional action is warranted. That can be a perfectly reasonable outcome when it is deliberate and supported by the facts.

The point is not that every assessment should create a new project, issue, or action plan.

But if the assessment changes no priorities, alters no monitoring, and gives nobody firmer ground for the decisions they are already making, it is worth asking what it accomplished.

Have a Specific Problem to Work Through?

An aging finding, control issue, documentation gap, or workstream short on capacity is enough of a starting point. Tell us what is happening and what you need to be true at the end.

Tell us what is stuck, what changed, or what deadline is driving the need. We can determine whether BPS Advisory Group is the right fit and what a sensible scope would look like.