Building and Running a Reputational-Risk Register

The reputational-risk register is where good intentions become an operational discipline. Without it, community risk lives as vague unease in a few people's heads; with it, every specific exposure is written down, owned, and tracked to a mitigation. The register borrows directly from the risk-management practice operators already use for construction and supply chain, and applies it to the political and reputational domain. Here is how to build one that earns its keep.

Each entry begins with a specific, concrete risk statement, not a category. 'Community concern' is useless; 'During a declared drought, our peak water draw becomes a symbol of unfairness while residents face restrictions, triggering organized opposition and a possible council reversal of our water-service agreement' is a risk you can actually manage. The discipline of writing the risk this specifically forces you to think through the scenario, and it surfaces exposures the team would rather leave unspoken. The best registers are uncomfortable to read precisely because they name the things nobody wants to say aloud: the abatement will look bad if the school levy fails, the swing seat is up for reelection, the shell entity concealing the tenant will read as deception when revealed.

Each entry then gets the standard fields: likelihood, impact, an owner, a mitigation, and a trigger or early-warning signal. Likelihood and impact let you rank, so scarce engagement effort goes to the high-likelihood, high-impact rows rather than being spread evenly. The owner is non-negotiable; a risk without a named person responsible is a risk nobody is actually watching. The mitigation must be a concrete action, not a hope, funding your own grid upgrades to defuse the rate-shift fear, pre-committing a drought-contingency water plan, structuring the abatement with a community-benefit tie so the fiscal story is defensible. The trigger is the signal that the risk is materializing, a drought declaration, a hostile letter to the editor, a challenger announcing against a friendly incumbent, so mitigation activates early rather than after the story has hardened.

A well-run register also distinguishes between risks you can mitigate by changing the project and risks you can only mitigate by changing the narrative or the relationships. Choosing air-cooling over evaporative cooling reduces the water risk substantively, at real cost. That is a project change. Explaining your water safeguards credibly is a narrative change. Both are valid, but conflating them is dangerous: some risks cannot be talked away and require an actual design or commitment change, while others are genuinely matters of transparency and framing. The register should be honest about which lever each risk requires, because a substantive risk papered over with messaging is the exact configuration that blows up when a reporter finds the underlying reality.

The register must be reviewed on a cadence, not filed and forgotten. Reputational risk is dynamic in the same way the stakeholder map is; a row that was low-likelihood in a wet year becomes urgent when the drought monitor turns red. A standing review, monthly during active permitting, weekly as a key vote approaches, keeps the register live and keeps ownership honest. In that review you update likelihoods, close mitigated risks, and add new ones as the political situation shifts. The register becomes the shared operating picture that keeps the whole team, legal, government affairs, engineering, communications, working from the same list rather than each holding a private and partial sense of what could go wrong.

Finally, the register is only as valuable as the honesty that goes into it, and honesty is a cultural choice. A register sanitized to reassure leadership is worse than no register, because it creates false confidence. The teams that use this tool well create room to name ugly risks without being punished for pessimism, because the person willing to write down 'our incentive deal will not survive contact with a fiscally conservative new majority' is doing the organization a service. The register's whole purpose is to let you see the hit coming while there is still time to move. That only works if people are allowed to write down what they actually see.