Implementing a risk management information system

Context

A risk advisory practice depends on claims, incident, and exposure data from its clients. When that data lives in spreadsheets and inboxes, reporting is slow and inconsistent. The practice adopted a risk management information system (RMIS) to centralize it. I led the implementation and have administered the platform since.

Approach

The project was run end to end, through each phase:

1. Requirements. Worked with the advisory team to define what data had to be captured, who needed to see it, and what reports clients expected.
2. Vendor coordination. Acted as the single point of contact with the platform vendor through configuration and launch.
3. Configuration. Built forms and fields, users and roles, workflows, and reports and dashboards to match how the team actually works.
4. Data migration. Prepared, cleaned, and imported historical data so reporting would be continuous from day one.
5. Testing and training. Validated the workflows with real scenarios, then trained users through group sessions and one-on-one help.
6. Post-launch support. Handled issues, change requests, and improvements as usage grew.

Key decisions

• Configure around the workflow, not the other way around. Forms and approvals mirror how the team already works, which made adoption much easier.
• Role-based access from the start. Client data is sensitive, so who can see what was designed up front instead of locked down later.

Outcome

A centralized system of record for the practice’s risk data, with consistent reporting. More than five years of administration since launch have kept it aligned with how the practice works as needs change.