Confirmation Tool Wireframe Design Challenge

Welcome to the "Confirmation Tool Wireframe Design Challenge". In this challenge, we are looking for your help to re-design an existing Confirmation Process Tool to be more efficient and user intuitive. We are looking for responsive wireframes (for desktop) that help multiple different users (Reviewer, Target Entity, and Confirming Entity) to perform tasks related to a financial review. The user is able to do this through a few key workflows and through a series of processes and required functionality. We are looking for your expertise related to how to best present the information to the user and create a clean UX for this desktop web app. Good luck and looking forward to seeing your creative ideas!

Round 1

Round 2

Challenge Description:
We have developed a prototype app which contains workflows to manage a set of confirmation processes by task basis. There are 3 key user types involved in the confirmation process; A reviewer, A Target Entity, and a Confirming Entity.  The purpose of the application is not only to improve the efficiency and quality of the process but to transform and digitalize the review confirmation process that is currently paper-based.  We hope we can use your design expertise to bring the UX to the next level!
The balance confirmation workflow can be broken down into six major steps;  

A) A Target Entity (which is a client of the reviewer) needs to be able to upload balance data that needs to be confirmed
B) A reviewer needs to select a confirming entity (Think of the confirming entity as a 3rd party reviewer)
C) The Target Entity then needs to be able to create a system registration letter that they can send to the confirming entity so that they can access the balance data they need to confirm
D) Once the letter is created the reviewer and the Target Entity then needs to be able to request the confirming entity to confirm the balance data
E) The confirming entity then needs to be able to respond to the request to confirm the balance data
F) If the Confirming Entity finds discrepancies in the Balance Data the reviewer and the Target Entity needs to be able to reconcile balance data

(Each task has some sub-tasks, e.g. “Reviewer creates balance confirmation requests” is a sub-task of D), and “the Target Entity checks and attaches necessary reference to the balance confirmation requests” is another sub-task of D). Please see required functionality section for more details regarding subtasks.

We are looking for dynamic wireframes that are simple, intuitive, and which allows users to complete each step/task without talking with the help-desk.

Required Screens / Functionality:
We want you to introduce the idea of a dashboard and an improved tasks list to allow different users to more easily begin and complete the tasks that are required of them. If you think there is a better way to organize the content in different screens or in a different order please show us. We are open to your ideas on what is the best user experience based on the content and required features and functionality.

We want you to focus the design around the following screens:

01. Login Screen
- This should be the default screen every time user open the apps.
- User needs to enter their User ID and password to be able use the application.
- Needs to have error scenario if incorrect credential entered by user.
- Provide "remember me" and "forgot password" feature (Create the feature, not just static link)
- Links to Terms of Use and Privacy Policy.
- Notes section contains some dummy paragraph to explain the apps summary.

02. Dashboard
- The dashboard should have 3 different views: User, Approver, Admin
- The dashboard should allow different user types to easily access the functions they need:
-- User view: Quick access to begin a common task.
-- Approver: Focus on quickly completing assigned tasks / approvals. Ability to filter and search through assigned tasks.
-- Admin: Admin level functions.
-- We want the user to have access to the following menu items, however if you think there is a better way to organize the items or the menus we are open for suggestions: (As long as the location is appropriate from the usability point of view, we do not have specific requirement that all of these links has to be on the main menu)
---- Dashboard
---- Pending Task (Show any task status activity that related and needs to be done by the user or other roles in the apps)
---- Task /Project workflow
---- Confirmation Data List
---- Confirming Entity List
---- Registration Request
---- Balance Confirmation
---- Reconciliation List
---- User Management
---- Project Management
---- User Manual

03. Tasks List / Project list
- A robust list of tasks / projects that a user needs to complete or monitor progress of. Quick access to the items a user is responsible for is important.
- Approvers should use this improved tasks list to complete tasks without leaving the page.

04. Task Completion User Flows
- For the task completion user flow we want you to propose the user flow through the following tasks. We want you to streamline this process by making individual tasks easily accessible through dashboard / tasks list:

The following key workflows needs to be included:
 A. Upload Confirmation data
- Step 1. Request  the upload of Balance Confirmation Data - User: Reviewer
- Step 2. Upload Balance confirmation data - User: Target Entity
- Step 3. Upload Account Master Data -  User: Target Entity
- Step 4. Request Approval of uploaded data -  User: Target Entity
- Step 5. Give approval of uploaded data - User: Reviewer
- Step 6. Data completeness check - User: Reviewer

B. Select the Confirming Entities
- Step 1. Select Confirming Entity - User: Reviewer
- Step 2. Request Approval of selected Confirming Entity - User: Reviewer
- Step 3. Give approval of selected Confirming Entity - User: Reviewer

C. Send system registration request letter* to the confirming entities
- Step 1. Create registration letter - User: Target Entity
- Step 2. Give approval to send registration letter - User: Reviewer
- Step 5. Download registration letter - User: Target Entity

D. Request balance confirmation from the confirming entities
- Step 1. Create the confirmation request - User : Reviewer
- Step 2. Attach reference to confirmation request - User: Target Entity
- Step 3. Notify the Reviewer of the attached file - User: Target Entity
- Step 4. Request approval to send confirmation request - User: Reviewer
- Step 5. Give Approval of confirmation request - User: Reviewer

E: Respond and give approval of confirmation response
- Step 1. Respond to confirmation request - User: Confirming Entity
- Step 2. Give Approval of confirmation response - User: Confirming Entity

F: Reconciliation of confirmation balance
- Step 1. Request for reconciliation - User: Reviewer
- Step 2. Perform Reconciliation  - User: Target Entity
- Step 3. Approve reconciliation result - User: Target Entity
- Step 4. Confirm reconciliation result - User: Reviewer

Normaly there is a different level between the person requesting and approving (Staff vs Manager) a task that is performed by the same user group (for example reviewer)

For more details around the workflows, inputs and some some sample screens please see the attachments. However, we are looking for you to analyze the problem based on the high level workflow mentioned above and propose a solution for what screens are needed and the best way to present the information/ functionality on those screens. 

Key functionality and Required Features:
These features must appear within your wireframes and be as user friendly as possible. How these get worked into your solutions and what screens they belong on is up to you. Again, we are looking for your expert UX skills to make the best experience possible.

The following functionality needs to be included for each user:

Review team functionality:
-- Can request balance confirmation data
-- Can Select Confirming Entity
-- Can request to create registration letter
-- Can create confirmation request
-- Can request reconciliation
-- Perform client data management
- Confirming Entity functionality:
-- Can reply to balance confirmation

Target Entity functionality:
-- Can upload confirmation data
-- Can create registration letter
-- Can perform reconciliation of the account balance
- Webadmin functionality:
-- Can only view balance data, balance confirmation, confirmation request, confirmation responses, and responses / reconciliation balances
-- Can set up E-mail notifications
-- Perform user account management tasks 

Target Devices:
Make sure that your solutions and layout adapt and work on all devices. Think about how inputs, navigation, functionality, etc. will need to change. Make sure you are following responsive design best practices and current designs trends
Desktop - 1280px (height can expand as needed)

Target Users:
The expected users of this application are Reviewers, the Target Entities and the Confirming Entities

Normaly there is a different level between the person requesting  and approving a task (Staff vs Manager).

Learn Axure:
New to Axure? Here are some quick tutorials to help you get started.
http://www.axure.com/learn

Judging Criteria:
- Overall User Experience
- Completeness and accuracy of the wireframe as defined in the challenge spec
- How well your wireframes provide a consistent user flow.
- How well your wireframe captures all the functionality.
- Any suggestions, interactions and user flows you recommend (provide any notes or comments for the client).

Submissions:
Preview Image
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission File
All requested contest requirements as clickable HTML files generated by Axure.  All the content must be listed and the pages are linked together to show page flow.

Source Files
Wireframes should be built in Axure. The resulting source files used to generate the clickable HTML files.
All the content must be listed and the pages are linked together to show page flow.
All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the sidebar should be included in your Source zip file.

Final Fixes:
As part of the final fixes phase you may be asked to modify content or user click paths.

Attached files:
- Mockups of some samples screens of the application

How to use this: The attached screens are not meant to be hard requirement but to visually outline how some of the forms and screens look like in the current application. We want your help to make this application more user intuitive and take it to the next level so please feel free to combine some of the existing screens into a more streamlined UI/UX as long as they capture the key functionality.