Join our next workshop: Risk Transfer 101 coming up on Nov 18th

Compliance Coffee Talk · November 2026

Risk registers and risk appetite

Greenwich risk manager Megan Damato on building risk registers with department heads, working through disagreements about risk appetite, and keeping registers current.

Guest expert

  • Megan Damato

    Megan Damato

    Director of Risk Management, Town of Greenwich, Connecticut

  • John Rote

    John Rote

    Host

The session

Building her registers one conversation, one department at a time

[Megan Damato](https://www.linkedin.com/in/megan-damato-095b4613b/) has been Director of Risk Management for the Town of Greenwich, Connecticut, and Greenwich Public Schools for almost ten years, after working in private practice as an attorney. Greenwich has about 60,000 residents, and Megan now runs a formal enterprise risk management program for the town.

The topic came from a PRIMA webinar where Megan and Sara Lowenthal named a simple risk register as one of the best tools any organization can start with. This was the third and final session of our [Coffee Talk series on brokers, carriers and risk registers](/resources/brokers-carriers-and-risk-registers-series/), after sessions on [working with your broker](/resources/october-compliance-coffee-talk-working-with-your-broker/) and [working with your underwriter](/resources/november-compliance-coffee-talk-working-with-your-underwriter/). Megan walked through how she builds registers with department heads, works through disagreements about risk appetite, and keeps the registers in use.

Watch the conversation, or read the takeaways below.

Session RecordingOpen in a new tab

Key takeaways

15 takeaways from the session

Megan's advice in five themes, from a first spreadsheet to keeping registers current.

01–03

Start simple, at any budget

A register can begin as a spreadsheet and grow into a formal program.

  1. 01

    Start with the tools you have

    When Megan started in Greenwich, she had no risk management software and kept her registers in Excel. Now she runs a formal enterprise risk management program. She says you can build a register at any budget, from a consultant-built database to one person working in a spreadsheet or Word document.

    The takeaway: Start your first register in a spreadsheet if that's what you have.

  2. 02

    Rate frequency and impact on a short scale

    A register lists the risks around your organization by category and rates how often each might happen and how big the impact would be. A rare event can have a huge impact, and a frequent one can be minor. Greenwich uses low, medium and high. Megan finds that more levels get chaotic, though some organizations use five or six.

    The takeaway: Pick a scale your stakeholders can apply the same way every time.

  3. 03

    Use AI for a sample, not your data

    Megan suggests asking ChatGPT for a sample risk register for, say, a municipal Department of Public Works, adding your state if you like. It gives you a structure and may surface risks you hadn't thought of. Keep confidential or organization-specific information out of it.

    The takeaway: Generate a generic sample to get started, then fill in the real details yourself.

04–06

Build it with the people who own the risk

Megan goes to each department with a sample register and keeps the meeting to an hour.

  1. 04

    Start at the top, then go to the field

    Megan began with the first selectman, the board of selectmen, boards and committees, and department heads. As the registers get more detailed, she meets with division leaders and with crews out in the field.

    The takeaway: Start with leadership, then add detail with the people doing the work.

  2. 05

    Ask for one hour and send a sample first

    Megan schedules an hour, because longer meetings lose people's focus and are harder to get on the calendar. She sends a sample register ahead of time, with nothing specific to the town or schools, and finds out whether each person prefers it on paper or on a laptop. Anything left over gets finished offline or in a follow-up meeting.

    The takeaway: Send a generic sample ahead and keep the first meeting to an hour.

  3. 06

    Meet people where they work

    Megan went to the sewer plant, a plow crew's shed, the fleet department and the police department instead of having everyone come to town hall. Seeing each environment helped her understand the risks. She also learns about mitigation departments already have in place, which she passes to insurance carriers and raises at budget time, especially for safety items.

    The takeaway: Visit each site, and share the mitigation you find with your carriers.

“We're not trying to stop things from happening. We're just trying to make them happen more safely.”
Megan DamatoDirector of Risk Management, Town of Greenwich, Connecticut

07–09

When you and a department don't agree

Relationships, evidence and patience do more than putting your foot down.

  1. 07

    Bring evidence to the conversation

    When a department rates a risk lower than she does, Megan gathers as much information as she can: benchmarking, examples from colleagues in other cities and states, and what a carrier paid out on a similar loss. If she doesn't win the point right away, she keeps building the relationship and tries again.

    The takeaway: Come to disagreements with examples and loss data.

  2. 08

    Let the experts drive in their own areas

    For risks outside her wheelhouse, Megan lets the department take the lead on risk appetite, then adjusts as she learns more. On cloud and AI vendors, IT and the town's outsourced chief information security officer review documentation such as SOC 2 reports and explain it to her, so she can make an informed call on what goes in the register.

    The takeaway: Collaborate on ratings where others know the risk better than you do.

  3. 09

    Be the department of K-N-O-W

    Megan borrows a line from PRIMA National speakers: risk management is the department of know, as opposed to no. With new department heads and board members, she explains that the goal is to help things happen safely and protect people and the organization. She doesn't have perfect relationships with everyone, and says putting her foot down got easier the longer she was in the role.

    The takeaway: Frame your role around helping projects happen safely.

10–12

Keep the register in use

Treat it as a living document, not a one-time report.

  1. 10

    Update as risks come in, and review once a year

    A listener's consultant-built register made a splash, then went stale. Megan reviews each register with its stakeholders once a year and refers to them at least monthly. When someone brings her a new risk, she adds it right away instead of waiting for the annual meeting, which often gets pushed.

    The takeaway: Add new risks when you hear about them, and hold an annual review.

  2. 11

    Registers and assessments do different jobs

    Megan keeps a register for each department, plus one for the whole town. A risk assessment covers a specific project or topic, and she often uses one to brief the audit committee or another board on specific risks. What an assessment turns up then feeds back into the register.

    The takeaway: Use assessments for specific questions and fold what you learn into the register.

  3. 12

    Give it time

    Even with some registers already in place, it took Megan close to a year to meet with everyone and get detail she was comfortable with. Greenwich is now building a register for AI, starting from an inventory of AI technologies the audit committee asked for, then rating risk with each department that owns a platform.

    The takeaway: Plan for months, not weeks, and expect the register never to be finished.

“They're a fluid document. They're never going to be completely done.”
Megan DamatoDirector of Risk Management, Town of Greenwich, Connecticut

13–15

Vendors, contracts and big events

Some risks cut across departments and need their own process.

  1. 13

    Track vendor risk across departments

    Greenwich's formal registers are organized by department, but vendor management is its own category. Megan's office looks at insurance levels, contract language and certificates of insurance, and now runs cybersecurity reviews of cloud vendors with the town's cybersecurity task force, with added questions about AI. The town's financial system tracks every vendor, so finance can run reports across departments.

    The takeaway: Keep a vendor view that spans departments, even if your registers don't.

  2. 14

    Give insurance terms a clear path to risk management

    In Greenwich, the law department reviews every contract, and procurement works with both law and risk management. Law brings insurance questions to Megan. As a former attorney she talks through other contract language with law informally, though she doesn't give formal legal opinions for the town. She learned the insurance side through online courses, PRIMA events, more experienced colleagues and her broker.

    The takeaway: Make sure insurance questions in contracts reach risk management.

  3. 15

    Start on big events six months out

    Greenwich's large summer concert, the Greenwich Town Party, usually happens in June or July. Planning starts in January or February with a kickoff meeting that spells out what's needed, the deadlines for getting information in, and the permits required. For larger special events, Megan plans at least six months ahead. As John put it, it's easier to push back on a project six months out than on one that starts tomorrow.

    The takeaway: Start risk reviews for large events at least six months ahead.

Join the next session

Bring your questions to the next Coffee Talk

Each month, experienced risk leaders answer questions from public sector and enterprise risk teams in a 30-minute conversation.

RSVP for Coffee Talk