A clerk equates "risk" with "we might get sued" only. What broader view should replace that definition?
Select an answer to reveal the explanation.
Short Explanation
Lawsuits are one storm cloud, not the whole weather map. Ops breakdowns, data leaks, people issues, environmental hits, and burned relationships all threaten the mission too. Stretch the definition past "we might get sued" and the register starts telling the truth.
Full Explanation
Risk is not limited to lawsuit probability. Operational disruption, information compromise, personnel issues, environmental harm, and relationship damage all threaten civic objectives and belong in a corporate risk view. Equating risk only with "we might get sued" narrows attention to one legal outcome and misses leading operational threats. Counting operational and information threats only after counsel opens a claim file makes identification reactive. Parking personnel and environmental issues solely in HR or facilities with a rule that they are never corporate risk creates silos the enterprise register is meant to overcome. Exam caveat: broad category lists beat litigation-only definitions on CRMC-style foundations items. Operational check: rewrite the intake prompt on the city risk form so reporters select among operational, information, personnel, environmental, relationship, and legal/liability tags, then sample ten recent issues to ensure lawsuit language is not the only path that gets filed. Brief supervisors that early operational flags still count as risk work. In civic practice, keep the same vocabulary in board minutes, toolbox talks, and the live register so department heads do not reintroduce casual synonyms after training. Re-check the concept during the next quarterly risk review against one real municipal example so the distinction stays operational rather than slogan-only.