Skip to main content
New Idea

Risk Register - any solutions?

Related products:Freshservice
  • June 15, 2026
  • 2 replies
  • 47 views
M
Apprentice
Forum|alt.badge.img

Was wondering if anyone ever established a Risk Register function? I have seen sporadic discussions elsewhere in the community, and a very limited plugin that doesn't really serve the function fully.

 

In short, ITIL4 says Risk Management is a fundamental and should be treated as a first class citizen (similar to how change records and problem records have their own dedicated sidebar areas and full lifecycle and integration across the platform)

 

I have added this as a feature request in the non-community freshworks pages, but really wondering if anyone has come up with a workaround or solution? I feel it should really be fundamental given the above relation in ITIL.

 

I also saw this post with a few asking the same thing but the post is now closed Risk Register | Freshworks Community

2 replies

S
Contributor
Forum|alt.badge.img+2
  • SteveDewSWR
  • Contributor
  • June 15, 2026

I second this, it would be good if you could associate incidents, problems and changes in relation to the risks too.

Thank you for submitting mgunn; this has prompted me to request CIR functionality which maybe able to bundled in with this, to create a ‘Registers’ module.

 

    muqqadasali
    Community Debut
    Forum|alt.badge.img
    • muqqadasali
    • Community Debut
    • June 18, 2026

    That’s a valid point—Risk Register really should be treated as a core ITIL4 component with proper lifecycle integration, similar to change/problem records.

    In many cases, teams end up building custom objects, ticket-based workarounds, or using marketplace apps to simulate a risk register, but it still feels fragmented without native support.

    Even across different digital service ecosystems like Atlas Pro ONTV Streaming, we often see how centralized management improves visibility—same principle applies here for risk tracking.

    Terms of UseAccessibility statement