← University
Risk Identification and the Risk Register
0 of 4

A governance review conducted by an external consultant delivered findings that surprised the leadership of a mid-sized community services organization operating across 3 urban centres in central Canada. The organization, which had grown from a volunteer-run neighbourhood initiative 15 years earlier into an operation with 47 full-time staff and an annual budget of $4.2 million, had never formalized its approach to organizational risk. The board of directors received the consultant's report in late autumn, and among its observations was a pointed note: the organization maintained no risk register, conducted no systematic risk identification process, and relied entirely on the institutional memory of its executive director and 2 long-serving program managers to anticipate and respond to threats.

The observation landed differently depending on who read it. The executive director, who had been with the organization for 11 years, initially dismissed the concern as consultant-speak disconnected from how community organizations actually function. The board chair, a retired healthcare administrator with experience in accreditation processes, recognized the gap as significant. The finance committee chair, a professional accountant, noted that the organization's liability insurer had twice requested documentation of risk management practices in the previous 18 months, requests that had been answered with general assurances rather than evidence.

The organization's operational landscape had changed substantially over the preceding 5 years. It had expanded from 1 service location to 3, added a transportation program serving elderly clients, begun accepting referrals from child welfare authorities for supervised family visits, and hired its first information technology coordinator to manage client databases containing sensitive personal information. Each expansion had proceeded without a structured assessment of associated risks, and each had introduced exposures that no one had formally documented or assigned for monitoring.

The board passed a motion directing the executive director to develop a risk register within 90 days. The motion came with no budget allocation, no template, no training resources, and no clear guidance on what the board expected the document to contain or how it should be maintained once created. The executive director now faced the task of building a risk identification and documentation system from nothing, with limited time, competing operational demands, and uncertainty about whether the resulting document would be a genuine management tool or another compliance exercise destined for a forgotten folder on the shared drive.

Ownership, Review Cycles, and Keeping the Register Alive

A risk register that sits untouched in a shared drive, accumulating digital dust while the organization it was meant to protect evolves and changes, serves no protective function whatsoever. The document becomes a historical artifact rather than a living instrument of governance. This final lesson addresses what separates functional risk management from performative compliance: the establishment of clear ownership, the discipline of regular review cycles, and the organizational commitment required to keep a risk register responsive to emerging threats and opportunities. Without these elements, the considerable effort invested in identifying risks and constructing a register yields diminishing returns with each passing month.

The concept of risk ownership emerges from a fundamental truth about organizational behaviour: risks that belong to everyone effectively belong to no one. When a risk register lists hazards without assigning specific individuals the responsibility to monitor, mitigate, and report on those risks, the document becomes an exercise in collective avoidance. Each person who encounters an unowned risk reasonably assumes that someone else must be handling it. This diffusion of responsibility creates dangerous gaps in organizational awareness, allowing known risks to materialize into incidents while multiple people assume the situation is under control. The Canadian Standards Association's risk management framework, known as CSA Z1600 as of the date of authorship, explicitly addresses this concern by emphasizing that risk management requires defined roles, responsibilities, and authorities at appropriate organizational levels.

That’s the free preview

You’ve reached the end of what’s open to read. The rest of this lesson is part of a $79 course — purchasing unlocks it, or sign in if you already have access.