Which version of your SharePoint document is being read the most?
DocRead for SharePoint is an extension to SharePoint that allows you to request that a group of SharePoint users read and confirm that they have read a document and agree with the terms and conditions you set. DocSurvey for SharePoint takes this one step further and allows you set an exam for a user to pass at the point of confirmation. This ensures that they not only read it but also understood. This process is vital when you have important policies and procedures that must be adhered to by staff.
By using DocRead and DocSurvey Reporting it’s very easy to answer questions such as:
- How many people read the SOX Compliance Policy?
- How many people were overdue on the Health and Safety Policy?
This remainder of this post will discuss how DocRead will let you scrutinise the performance of 2 different versions of an important document.
How to distribute a SharePoint document to a group of users
Before we dive into main reason for this post, for those that don’t know, it’s probably a good idea to illustrate how to assign a document stored in a SharePoint document library to a group of users. Here’s how.
Upload the document to SharePoint
If your document isn’t already in SharePoint upload it.
Edit the document properties
Process Reading Tasks
Now that the document is configured to be assigned to the ‘SP24 – Management’ group DocRead needs to be instructed to create a task for each person. This can be achieved by either waiting for a Timer Job to run, or by manually kicking it off via a menu option available at the site level!
How to confirm a document
Obviously the next step is for an end-user (who is a member of the ‘SP24 – Management’ group). This can be done easily with DocRead by using the screen below:
How to compare the performance of your documents across 2 versions or a document
Now to the point of the post! So now we know how to publish with DocRead and how and an end-user would confirm (sign-off) it, it’s time to put our administrators cap on! At this point we need to mention document versions in SharePoint.
SharePoint Document Versions
In the old file share world, you would have created a document called “Document ABC v1.doc” and then “Document ABC v2.doc” and so on. SharePoint improves this story vastly! A SharePoint document library (the container for your documents) can be configured to support multiple versions of a document.
This offers several advantages, namely:
- you can revert back to a previous a version.
- you don’t have a file structure littered with documents all having very similar names.
When we built DocRead we built it so that we fully supported document versions. After all a document can change greatly between 2 versions, so it’s really essential that you can record what version a user accepted! Here’s a few facts about how DocRead handles SharePoint document versions :
- DocRead will not touch any documents in draft stage. Documents will only be processed by DocRead once they are published and approved.When DocRead generates reading tasks for Documents the task will always point to the latest version of a document
- When the task gets completed DocRead will register the version of the document at the point that the task was marked as completed. DocRead will also register the document version on the reading receipt that is automatically generated when the reading task gets completed.
- When a new version of a document is published DocRead will not automatically re-issue reading tasks to users that have already acknowledged that they have read the document. If you want to force those users to read the document again then you need to select “Reset tasks” on the document properties. This will clear all tasks (even the ones that have already been completed) and re-issue new tasks to everyone (regardless of whether they have already read the previous version of the document).
When you ‘Reset Tasks’ for a document configured with DocRead this performs the following steps :
- Delete all ‘assigned’ and ‘overdue’ tasks and also create a ‘Negative Receipt’ stating that the user did not read that particular version of the document.
- Delete all ‘completed’ tasks. In this case no receipt is created as a ‘Positive Receipt’ will have already been created at the time of confirmation.
- Once all tasks are deleted – DocRead will then create a new set of tasks for every user in the assigned audiences.
How to analyse the Receipts with DocRead Reports
DocRead also ships with a set of filterable and sortable reports that help you track the progress of a particular user, task, audience, team member or document. On the whole, Receipts are used so that each user can access a printable receipt proving that they did (or didn’t) read a document.
However, as the receipts are all generated from the DocRead database and can easily be reported upon, you can also use them to discover a lot of information about the performance and history of your documents.
For example, using the Site Receipts Report you can view the following information about each receipt :
- User that the Receipt was generated for.
- Reason for creating the Receipt.
- Type of receipt
- Document that the user was required to read.
- Document Id of the document. (Generated by the Document ID Service).
- The Version of the document that the user was required to read.
- Dates relating to the task.
Receipt information can also be exported to Excel, but please be aware that this can be a fairly intensive operation so always try to filter the results as much as possible before exporting the data.
Once in Excel the data can be manipulated with pivot tables (for example) to summarise as required.
It is therefore possible to use the data available from the receipts table to compare and contrast the confirmation rates across documents and versions. If you also use DocSurvey, it’s also possible to do the same with the test results, to ascertain the comprehension levels of your staff after reading your documentation.