Reviewer progress report
The Reviewer Progress Report is found in the Report Generation section and provides a detailed reporting of changes made to reviewed documents during the review.
Table contents
The Reviewer Progress Report only records information after a reviewer selects Mark Complete to finish reviewing a document. If a change is made on a document and the Mark Complete button is not selected, then that change will not show on the table until a user completes the document.
The following fields are standard in the Reviewer Progress Report:
| Field Name | Description |
|---|---|
| Document ID | Unique document identifier |
| Reviewer Name | Name of the most recent reviewer |
| Native Extension | File extension of the document |
| Reviewer Role | Role type for the most recent reviewer |
| Review Date | Most recent review date. If a document has been QC’d after being FLR’d, this date will reflect the QC date. |
| First Level Reviewed By | Username of the first level reviewer |
| Reviewer Edits | Number of edits from the reviewers on the document |
| Document Review Status | Reviewed status of the document. Three possible options: FLR reviewed, QC reviewed, or “FLR reviewed; QC reviewed” |
| Cleared Flag | A “Y” or “N” value to capture if a user removed a system flag |
| Added Flag | Any flag added by a user |
| Added Excel Headers Count | Number of headers added |
| Updated Excel Headers Count | Number of headers whose PI type has changed. For example, Name to First Name |
| Deleted Excel Headers Count | Removed headers count |
| Added Excel Headers | Added header values |
| Updated Excel Headers | Updated header values |
| Deleted Excel Headers | Removed header values |
| Created Annotations | Added PI tags in non-spreadsheets, and manual annotations in spreadsheets |
| Deleted Annotations | Removed PI tags in non-spreadsheets, and manual annotations in spreadsheets |
| Updated Annotations | Updated PI tags in non-spreadsheets, and manual annotations in spreadsheets |
| Created Annotation Links | Number of Name to PI linkages created |
| Deleted Annotation Links | Number of linkages removed |
| Clear All Annotations Count | Number of times ‘clear all annotations’ was executed |
| Total PII Count | Total PI count on the document after edits |
| Total Edits on Document | Total number of edits |
| Codings Updated | Count of updated codings |
| Document Category Selected | Document categories added |
| Created Comments | Comments added |
| Personal Information | Personal information coding field |
Refreshing the report
Like all other reports on the Report Generation page, the Reviewer Progress Report does not update automatically. Instead, a user must select Run Report Generation from the Incorporate Feedback page to refresh the contents of the table.
Frequently asked questions
How can I find the average number of documents completed per day? To find the average number of documents completed per day:
-
Download the Reviewer Progress Report.
-
Create a new column called “Review Date Only.”
-
The current review date field has the review Date and Time. Only extract the Date from this field.
-
-
In the new column, input the following formula to extract only the Date from column E (Review Date): ‘=LEFT(E2,10)’
-
Populate the entire column with this formula.
-
Make sure that the cell referenced is in the ‘Review Date’ column.
-
-
Create a pivot table over the entire output.
-
To calculate the average number of documents reviewed per day.
-
Rows
-
Review Date Only
-
Reviewer Name
-
-
Values
-
Document ID
-
-
-
With this information you can write a formula to capture the average number of documents reviewed per day.
Note: The Review Date column acts as a ‘Last Review Date’ field, which means the review date is reflective of the last date the document was reviewed. Therefore, if a document was First Level Reviewed and then QC Reviewed, the original review date will be overwritten. Documents that have been both FLR’d and QC Reviewed are indicated with both status in column H (Document Reviewed Status): FLR review complete; QC review complete. Because of this limitation, save the metrics collected before QC review to make sure an accurate calculation of the average documents reviewed per day.
