Dinnaco - Request List Tool Design Concepts Challenge

Welcome to "Dinnaco - Request List Tool Design Concepts Challenge". We need your help in planning out our new request list tool application, which will become an app used by our employees and clients to manage all documentation lists within their project. The main purpose of this app is to create a tool that can provide the best method to manage all documentation for our project with our clients using sharepoint enterprise app (This tool will be run in Sharepoint). 

We want you create a 'Non traditional' Sharepoint design, focus on the UI/UX interactions and bringing clean and modern (creative) solutions to how this application should work. Looking forward to see your design concept ideas!

Round 1

Dinnaco users (setup, administration, checking information uploaded from the Client)
01. Homepage/Dashboard Screen
02. Create New List Screen
03. Search and Search Result Screen

Client users (uploading documentation)
07. Homepage/Dashboard Screen

Round 2

Dinnaco users (setup, administration, checking information uploaded from the Client)
01. Homepage/Dashboard Screen
02. Create New List Screen
03. Search and Search Result Screen
04. Settings Screen
05. List Details Screen
06. FAQ Screen

Client users (uploading documentation)
07. Homepage/Dashboard Screen

Project Overview
Dinnaco employees are spending a significant amount of time managing the flow of information from their clients during multiple projects. Lists of required information (e.g. Word, Excel, PDFs, etc) are currently created by Dinnaco teams in Excel spreadsheets and the process of administering what information has been received, when, and by whom is performed manually.

This is primarily a workflow task based application where Dinnaco users and Client team users share and collaborate on project documentation. The main area we are looking for you to explore revolves around a dashboard experience for our two different types of users (Dinnaco/ Client). From this dashboard, our users should be able to see the projects that they are working on and the associated lists contained within each project. Dinnaco users and client users will be working with a request list and specific tasks may be assigned to either user group in order to complete the status of a request list. Project information that should be represented on the project list should include Client Name, Project Name, Audit Period, Project Status, and Request Status. 

At a high level, there should be an overview of total requests and task status with indicators for Overdue, Not Started, Client Submitted, and Dinnaco Accepted. And then at a project level there should be the same metrics of total requests and tasks associated with that project. 

High Level Project information should include:
Client Name
Project Name
Project Start/Project End
Audit Period
Project Status
Request Status Metrics

The dashboard should also contain an activity list alerting users to tasks/ requests that are overdue, or when new documentation has been uploaded. Also consider what other types of user experience solutions can help with the general workflow for our target users through a dashboard. 

After clicking into a project off of the dashboard, the user will be brought to a project detail landing page. Here the user will be presented with the overview metrics for the project as well as the ability to drill down into detail for the requests and tasks for that project. In addition, the user will have the ability to add (upload) documents to the project. Other project details that need to be represented include the team members that are part of the project as well as an a activity feed for alerts and notifications associated with project requests and tasks. 

Drilling down into detail for the request list, the user will be presented with a table outlining the request information and status of each line item. From this table, the user has the ability to comment, export to excel, and upload and/or download list items.

Fields to include:
Request Number
Request Category
Request Description
Status
Due Date
Client Contact Name
Dinnaco Concact name
Upload/ Download
Comments 

Dinnaco uses SharePoint 2013 Enterprise throughout their business already and wishes to push the boundaries beyond the traditional SharePoint user experience; this shouldn’t be a 'traditional' SharePoint design and Dinnaco are expecting user experience orientated dashboards, functionality and a clean, fresh interface. 

Challenge Goals
To develop a 'request list tool' that can track, organize and approve/reject project documentation required to be obtained from a client during Dinnaco's projects. The request list tool will be setup and administered by Dinnaco users and made available to Dinnaco clients for them to access and upload information.

Screen Requirements 
Dinnaco users (setup, administration, checking information uploaded from the Client)
01. Homepage/Dashboard Screen
- The primary homepage view will display a dashboard to show an overview of the Dinnaco user's current request lists that allow the Dinnaco user to identify overdue items as well as the status of items in the workflow (see details later in client dashboard ‘status’ below regarding workflow stages) 
- Information to be included on the dashboard:
-- Client name
-- Project name
-- Request list name
-- Live/not live status
-- Summary of items by workflow stage, flagging those that are overdue
- Differentiate between request lists that the Dinnaco user owns (i.e. has created and is managing) and those that the Dinnaco user has been assigned to as part of being on an associated team (i.e. able to view perform actions)
- Needs A "New List" feature that will enable the Dinnaco user to create a new request list chosen from a selection of templates (for this challenge the example request list used should be titled "Standard Request List 1"). 
- Tool tip style help icons (or similar) should be used to explain the features & functionality of the site features. It is expected that the design and user interface should be sufficiently intuitive that a full user guide is not required. 

02. Create New List Screen
- The Dinnaco user should be able to setup the request list detail using a 'wizard' style form with the following functionality:
-- Pre-populated details: Client name; Project name; Request list name
-- Details entered by the Dinnaco user:
–--- Dinnaco users
–--- Client users
–--- A default 'Due date' for each category so it does not have to be manually entered against each individual line
–--- A default 'Client contact' and 'Dinnaco contact' for each category which will auto-populate all of these fields
–--- Tailoring of the lines items to be included from the template (tick-box to keep / discard – suggest that all removed items turn grey and will not appear in the ‘final’ list when created but will be available to add back at a later stage if required).
–--- Ability to add in a new custom row with drop down options for column content where necessary (e.g. categories)
–--- Ability to add in a custom column with drop down options for column type (e.g. date, free text, numeric, user etc)
–--- A 'make live / take offline' toggle button which will make the list appear for all Client users only when live, and be included in the dashboards of the Dinnaco users, thus initiating the workflow 

03. Search and Search Result Screen
- A "Search" function with results grouped into sections (Client name; Project name; Request list name; User name).

04. Settings Screen
- A "Settings" page allowing Dinnaco users to customise alert settings for Dinnaco users and for the Client users :
-- Notification trigger – a range of options (e.g. summary, overdue, changes etc.)
-- Notification frequency 
-- Notification content (i.e. which column information to include for items)
-- Notification custom text (i.e. custom introductions / messages)
- Once a request list is made 'Live' automated email reminders should be sent to the relevant “Client Contact”
 
05. List Details Screen
- Within a request list, Dinnaco users should have the ability to download multiple attachments from the list at a single time (i.e. not clicking each line and downloading individually one-by-one) and browse to the local location to save attachments.
- A "Roll Forward List" function that will give the Dinnaco user the ability to create a "copy" of an existing list with pre-populated fields including content to make it easier when setting up a similar list the following year
- The new list that is created will be purged of all uploads and all statuses reset to "Not received". Due dates to be rolled forward by one year for every line entry.

06. FAQ Screen
- A FAQs page to allow user to get help regarding the application.

Client users (uploading documentation)
07. Homepage/Dashboard Screen
- Client users have a similar user experience within the platform as described above. They are able to login, view their dashboards, see specific items relating to them and upload documents against individual items

- Each line of the list should have an upload function that allows Client users to:
-- Upload a files against line items quickly, including a fast and intuitive way to upload many files against their respective line items without having to repeat similar steps for each line (e.g. a drag and drop functionality perhaps)
-- Add comments to a line item (i.e. a message from the Client user to the Dinnaco user responsible for checking that item)

- The "Status" field of the line should have the following workflow:
-- "Not received" – file not yet uploaded by the Client user
-- "Received and being checked" – file uploaded by the Client user but not yet checked by the Dinnaco user responsible for that item
-- "Not accepted – replacement required" – Dinnaco user rejects the uploaded document as not suitable and this is flagged to the Client user. A comment field is required to allow the Dinnaco user to write a note to the Client user as to the reasons why the document was not accepted
-- "Checked and accepted" – the uploaded file has been checked by the Dinnaco user responsible and is acceptable

- "Date Received" field to be auto-populated with the date the file was attached

IMPORTANT
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.

Design Considerations:
- The interface needs to be clean, fresh interface and intuitive to navigate.
- It is expected that the design will show the potential for several different request lists for the same single client. Multiple client instances are not required as a separate SharePoint site instance will be used for each individual client project.
- Ideally the focus should be a fluid user experience.
- Focus on the design being a great user experience, think simple but effective solutions!
- Give importance to the overall layout and think on how a user would interact with the content on the page.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application 
- How quickly could you find information?

Create it as responsive design :
Desktop will be the primary target device, but please consider this app will be responsive in the future and design elements should be easily translate to working on different device sizes (i.e. mobile) in the future.
- Desktop : 1280px width with height adjusting accordingly

Branding Guidelines :
- Please follow the Dinnaco Branding guidelines: https://projects.invisionapp.com/boards/3N1FFO2T5K42Z/

Documentation :
- No wireframes are being provided for this challenge.  We want to see your creative takes on solving the problem at hand! 

Target Audience
- Dinnaco Employees
- Dinnaco Client

Judging Criteria
- The overall functionality of your concepts - how well do your ideas work as a request list tools apps. We are looking for an app that is easy-to-use
- Your ideas and concepts!
- How well does your design align with the objectives of the challenge
- Cleanliness of your graphics and design.
- Overall Design and User Experience.

Submission & Source Files
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
Submit JPG/PNG for your submission files.

Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.

Final Fixes
As part of the final fixes phase you will be asked to update the style tile to reflect any new elements that you have added to the design. You may also be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.