Compliance tracking - read and signs

We have recently submitted the below to the support centre as a request for the development team.  Would be interested to see if anyone has similar issues, work arounds or comments.

We are currently in the process of trying to migrate our compliance tracking for manual/document read and acknowledgments from our old system to Web Manuals and are finding limitations, which are outlined below.  This is an important requirement for regulatory and IOSA compliance.

1 – Using the Remind and View permission option

                Problematic in that this sits at a folder level, as opposed to document level.  So, any document added to this folder will default to needing a ‘check out’ or ‘read’.

We have tested some variations of making a separate folder for Read and View that we could duplicate documents into to avoid the above, but permissions to this category would need to be for all users, which would mean they would be required to ‘read’ documents potentially not relevant to their role, creating white noise with unnecessary volume.

                Suggestion – that Read and Acknowledgment requirements – that can be reported on – are set at a document level.

2 – Announcement functionality

We will need to use this to track ‘read and acknowledgement’ requirements for updated documents (due to limitations mentioned above), which is easy to set up, however we have identified issues from the end user perspective that we would like to recommend/request product changes for.

When you link a document to the announcement and the user opens the link, there is no direct way back to the announcement itself to acknowledge it.  You must then navigate back to the Dashboard, re-enter Announcements, open the specific announcement again and then acknowledge it.  7 clicks in total.

                This will result in staff opening the link and reading it, thinking that they have completed what is necessary AND/OR acknowledging the Announcement, without opening the link.

                Suggestion – provide a ‘back’ button or direct link back to the Announcement from the linked document.

We appreciate your consideration in these suggestions, which we believe will enhance your product and the end user efficiencies.