Litigation Support Evidence Collection System Design Challenge

Welcome to the “Litigation Support Evidence Tracking System” Challenge. In this challenge, we would like to design a web-based application running on a desktop browser. This will support the evidence collection status tracking and updates for a litigation support team.

We would like you to define the initial design direction for these dashboards with a focus on usability, simplicity, and a user-centric approach.

Good luck!  We’re looking forward to your designs!

Please read the challenge specifications carefully and watch the forums for any questions or feedback concerning this challenge.  It is important that you monitor any updates provided by the client or Studio Admins in the forums.  Please post any questions you might have for the client in the forums.

Round 1

Please design the following screens:
01. Dashboard
02. Search with scoping and filters (could be integrated into the Dashboard)

Instructions:
1. Readme document: Provide notes about your submission
2. Make sure all sample screens have the correct numbering so we can understand the proposed screenflow. Use file numbering like this: 00, 01, 02, 03

Round 2

1. All remaining screens (see Required Screens)
2. Readme document: Provide notes about your submission
3. Make sure all sample screens have the correct numbering so we can understand the proposed screenflow. Use file numbering like this to show progression through screens: 01, 02, 03, 04

Challenge Description:
The purpose of this challenge is to design a custom dashboard for a litigation support team. Legal teams make collection requests, and the receiving support team collects and organizes evidence. Once evidence collection is completed, a confirmation is sent back to the legal team notifying them that the evidence is available for use.

Of primary importance is the “search” functionality. The legal teams frequently make requests of the support team to locate evidence. This requires the support team to find specific information about collections and evidence and return the information to the legal team.

We are looking for you to create a GREAT design that allows efficient and visually attractive data entry and data presentation.  

User Interface Guidelines:
- All user interface elements should be simple and easy to understand.
- Focus on consistent design patterns, a clear contrast between actions and information, and a clear visual hierarchy.
- When using motion or animation, pay close attention to choreography and authentic motion.
- Make liberal use of white space to create contrast and define interface and data elements clearly.

- Keep interface elements consistent. All interface elements should reflect predictable placement, style, and behavior across all environments. This is especially important when styling actionable items.

- Priority should be given to recognition rather than forcing users to recall paths to tasks. 

Branding Guidelines:
- There is no company logo or style guide available. A temporary logo can be created using #d71921 (primary) and #edf0f5 (secondary).
- Please use hex colors #d71921 (Crimson) and #edf0f5 (Whitesmoke) as the primary colors for decorative elements.
- Background can be #fff (White) with actionable items as  #edf0f5 (#d71921 on hover).
- Secondary action items (i.e. secondary buttons) can be #3b3b3b (darklategray).
- Body text can be #252525 Helvetica Neue.

Required Design Sizes:
- This is a responsive web design which should include sizing for desktop and mobile phone (no tablet).
- Desktop resolution max 1920px.
   1. Design for 1280px wide
       - User screens are 1920 x 1080
       - Does not need to be full screen width
- Mobile Resolution: max 640px

Definitions:
There are several components which should be combined in a dashboard environment.

1. Collection Request
- Collection requests to collect evidence for a legal case.
    - This is similar to a work order where someone is making a request to collect information (in this case evidence).
- Each request contains a group of evidence items to be collected.
- Once evidence collection is complete, a “manifest” file is sent to the legal team that lists all items collected.

2. Evidence
- Data collected based on a todo list in a collection request.
- Each piece of evidence is one or more files, electronic only (not physical objects)
- A support team member can locate a file, files, or directory from a local or remote location and “add” it to the collection request. All file properties (file size, date, created, etc.) are stored in the app and displayed in the evidence detail. No files are actually transferred, but all other file properties are retained and displayed.

3. Search
- The search functionality is central to this website.
- An example would be to search for evidence or collection information by date range to satisfy requests from the legal team.
- It will be used to search items by status to gauge progress or identify problem areas.
- Use a standard text input for search keyword entry
- Include the ability to scope and filter search results

Required Screens:

We need the following screens to be created for this website:

01. Dashboard/Home
- A “personalized” list of “Collection Requests”. Collection Requests should be presented as a list of items which can be chosen by the user.
- The username should be present on the screen to indicate authentication and a “Collection Request” list that is assigned to a specific user.
- Selecting a collection will expose the collection detail screen.
- Required Content:
    1. Collection request list
    2. Search
    3. User information (who logged in)
    
02. Search
- A robust search that allows the support team to find more detailed information about collections and evidence.
    1. Search functions should be easily scannable and highlighted/obvious when chosen.
- Should allow scoping (default is “all”)
    1. Collection request, evidence, manifest, date range
    2. The search scope should be stated at the top of search results so it’s clear what the results represent.
- Should allow filtering of search results
    1. Date added, date modified, status (Open, closed, urgent, response required, pending, ignore), by collector (who collected the evidence).
    
03. Collection Request Detail
- Collection request detail screens should include a request summary at the top including requestor, company, address, contact information, date of the request.
- Collection Requests can be assigned one or more statuses (i.e. Open, closed, urgent, response required, pending, ignore)
- Collection Requests can be “Completed” with a single action. This action notifies the legal team that the evidence is available for use and also transmits a “manifest” file that contains information about the evidence transmitted.
    1. This could be a status dropdown or a separate action item to close the request.
    2. Completing a collection request marks the request and “closed”.
    3. Completing a collection request sends a “manifest” file to the legal team. A confirmation is displayed upon successful transmission.
    4. There should be options to access the manifest other ways.
        - Resend
        - Email (to use a different email address than what was contained in the collection request).
        - Download
- Each collection request is presented as a list of evidence items that need to be collected.
- Evidence items should be presented as a checklist. As each item of evidence is collected, it can be marked as “complete”.
- The collection detail should also show an on-screen activity log at the bottom.
    - Examples
        - “Marvin F added evidence item #1234 4/11/16 8:46am”
        - “James T deleted evidence item #1255 4/10/16 11:25am”
- Required labels and samples for Collection Request details: This should be a separate area from the Evidence list.
    1. Path
        - /TO_PROSEARCH/20160401_Takata/Takata_TEMA_NAMCs/TEMA_Purchasing_Greg_Laskey/
    2. Firm Name
        - Company name
    3. Matter
        - Matter name
    4. Media
        - FTP
    5. Custodian
        - John_Ortiz_T5710
    6. Collection Date
        - 4/1/2016
    7. Collection Type
        - EDOCS
    8. Client Collection Type
        - NETWORK SHARE
    9.File Count
        - 4
    10. Data Size
        - 2.23 MN
    11. Comments
        - Replace TA103547_0000007 with this file "Copy of 340L TRI List from TMQD.xls"; same filename

04. Evidence Detail
- Each piece of evidence (a file or set of files) requires a page to display the details about the evidence collected or to be collected.
- Please avoid using a large table to display all data. A more compact layout is preferred.
- This could be a tabular display but does not have to be.
- To “collect” evidence means to attach file properties. Once a file is attached, the file information should be displayed near the evidence item (file size, file type, date added, date modified)
- Required Fields for each evidence item:
    1. System (where the evidence was collected from)
        - Name
        - Company
        - Dept
        - System Owner Contact
        - System Owner Contact Email
        - System Owner Contact Phone
    2. Custodian (who the evidence was collected from)
        - Name
        - Custodian EmpID
        - Employment status
        - Company
        - Department
        - Email
        - Phone
    3. Collection Details
        - Method
        - Collected By
        - Collection Date
        - Collection Type
        - Client Collection Type
    4. Evidence Properties
        - Source File Name
        - Source File Type
        - Source File Size
        - Source File Path
        - Number of Files
        - Transfer ID
        - Processing ID
        - Comments
        - Sha1 Hash

Workflow:

 

Sample Task Flows:

1. Open collection request → Evidence collected → External confirmation sent
2. Search (for evidence) → Search results → Evidence details
3. Search (for status) → Search results → Collection request details���

Target Audience:

- A litigation support team. They receive requests from a legal team and must collect evidence.

Judging Criteria:

We will be judging on:
- How well your design aligns with the objectives of the challenge.
- Adherence to the Design Guidelines.
- Usability and user-centric approach.
- Consistency of elements across screens.
- Clear, simple, visual hierarchy.
- Ability of your design to support user tasks in a straightforward, pleasant, efficient manner.
- Overall user interface design and layout.

Submissions and Source Files:
Preview Image
Please create your preview images as 1920 x 1080 JPG or PNG file in RGB color mode at 72dpi and place each screenshot of your submission within it.

Submission File
Submit JPG/PNG/PDF for your submission files.

Source Files
All original source files of the submitted design are required. The preferred file format is Sketch, although clean, layered Photoshop PSD’s are also acceptable.

Final Fixes
As part of the final fixes phase, you may be asked to modify your graphic elements (sizes or colors) or modify portions of the color palette. We may ask you to update your design or graphic elements based on checkpoint feedback. See more information about Final Fixes.