+1
New

HTML5 AV: Provide two unique sections to differentiate between review and reference materials

Diane Kifer 3 weeks ago • updated by Eric Teitsma 5 days ago 3

Provide two unique sections to differenate between review and reference materials

Description

• When reviewers open review tasks where there are multiple documents, it is not possible to discern which documents are for review and which are reference only, unless the submitter has put an identifier in the document title.
• Relying on file naming convention to discern reference documents is impractical.
• That information is visible on the Attachments screen, which they have to navigate to outside of the review task, and then manually reconcile document names to determine which are reference. There is room for error in this process and it is inefficient.

Examples: 

The Communications and Legal reviewers see a list of Review Materials when they open their review tasks that does not discdifferentiateern documents for review from reference.

Example 1:
One  of the seven documents listed below are reference, but you cannot tell which ones:




Example 2:
In this test project, there are 5 attachments. Two were uploaded as reference documents. One is easily identifiable, because I included the word REFERENCE in the document title. The other is not discernible to the Comms and Legal reviewers:



Impacts of Enhancement: 

• Will help reviewers in Communications and Legal to work much more efficiently
• Will reduce errors
• Will reduce instances of Resubmits, where a reviewer rejects a project with instructions for the submitter to include ‘REFERENCE’ in the file name
• Will be a better user experience


Risk of not implementing:

• Reviewers may inadvertently not review a document if they mistake it for reference
• Reviewers may waste time reviewing a document that is reference only

New

Can the reference documents you are using be added into the supporting documents section on tasks instead of being added just a normal attachments?  This would create the separation you are looking for and it one of the intended use cases for supporting documents.

Adding screenshots on behalf of Diane

Example 1 Screenshot:

One  of the seven documents listed below are reference, but you cannot tell which ones:

Example 2 Screenshot: 

In this test project, there are 5 attachments. Two were uploaded as reference documents. One is easily identifiable, because I included the word REFERENCE in the document title. The other is not discernible to the Comms and Legal reviewers:

Note that this is what the Compliance reviewer sees (with the Type), because their task is built differently to accommodate a Fair Lending loop:

For reference, the scenario applies to Task Inbox in addition to the legacy completion page.