MasterControl Quality Excellence vs Risk Hawk: Which is a better fit?

Deanna V.: I'm Deanna. I'm a quality system program manager. With the implementation of the MasterControl Quality Excellence tool, I would give it a five out of five. For more reviews like this, please click below. We were a new company that opened up, and we actually had no tools; we only had a paper tool. Prior to us opening up, I actually worked at the same site for a large organization that used another quality tool called TrackWise; however, the TrackWise tool wasn't integrated with other tools such as document control, which was Agile, and training, which was a [inaudible 00:00:37] administration system training. When we went to look for implementation, we wanted one tool where it was all connected, instead of being separate tools. When we went to look for implementation of selecting a software, we looked at multiple companies, and we were really looking for something that was fairly easy to implement and that was integrated between document controls, change controls, training, and other QMS tools we would be implementing. This tool seemed to be the most in line with the regulatory requirements we needed to comply with, and it seemed to be fairly simple in the implementation. During the implementation planning phase, we had to do a lot of cleanup of our own data, so most of our time was spent organizing our master data, and then being able to populate it into the spreadsheets for the upload, so the actual upload was fairly quick. We spent about 12 months cleaning up our data, and we spent about eight weeks from the point of being able to upload our data to completing the entire validation and go live, and we did this between Thanksgiving and Christmas, and it worked out fantastic. One of the recommendations I would have is to make sure your terminology is aligned between what MasterControl gives us for terminology and what you use in your business. For example, the use of deviations; that means something different to different organizations, so take the time to really make sure you understand those concepts and those words they're using so that, when you go to structure your data, it aligns with how they are planning on using that module and using that data. That will save you a great amount of difficulties you may experience after implementation, and we had a few of those because of the terminology issues. Always able to work through them, but we could have been more effective in implementation if we would have made sure we understand the terminology.