Firefly Subpoena App Design Challenge

Welcome to the "Firefly Subpoena App Design Challenge". In this challenge, we are looking for your help to create the best possible UI/UX for an application for the Documents and Subpoena teams at an insurance company.

Read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. Let us know if you have any questions in the challenge forum

Round 1

You don’t have to deliver all 10 pages for the checkpoint.  Show as much as you can so we can provide as much feedback as possible.  There is no minimum or maximum amount of pages required for the checkpoint.

01) Landing Page/Dashboard
02) User Admin
03) Manage User Hierarchy Admin
04) New Entry NDC
05) All Subpoena Search
06) Subpoena Details
07) Invoicing
08) Overflow Assignment
09) Fee Table Matrix
10) Audit Trai

Round 2

01) Landing Page/Dashboard
02) User Admin
03) Manage User Hierarchy Admin
04) New Entry NDC
05) All Subpoena Search
06) Subpoena Details
07) Invoicing
08) Overflow Assignment
09) Fee Table Matrix
10) Audit Trai
BACKGROUND OVERVIEW
Firefly is an insurance company and currently they are utilizing 2 separate systems for processing Subpoenas.  The Documents Team has one system and the Subpoena Team has another.  A Subpoena is a legal document from the court stating that some particular documentation is required for a legal case.  The Documents team receives the request and enters the necessary data into the system.  They then create an assignment for the Subpoena team.  The Subpoena team then goes in and sees that some of the fields have been filled out by the Documents team.  They can see what the request is, for example, a person’s medical records might be needed by a certain due date.  The problem is that once the Documents Team sends the request over to the Subpoena Team, they have limited visibility.  They can see the documentation and information that they entered, but they can’t see who it’s been assigned to or what the status is.  We would like to create 1 cohesive system.

CHALLENGE GOAL
The goal of this challenge is to develop a more satisfying user experience for an application that utilizes data entry and data retrieval. 

DESIGN CONSIDERATION

• User Friendly
• Figure out ways to create clean simple designs for filling out forms and viewing data

Documentation - Interactive Excel Spreadsheet (assets)

• We are providing a spreadsheet which contains the fields needed for each screen of the app.  Each tab in the spreadsheet is numbered and represents a different page.
• The text in the spreadsheet is clickable, and will take you to another tab called Lawsuit and Subpoena UI which gives information on each of the fields, like if it’s a text box, dropdown box, radio button, etc.  It also tells the desired behavior of the field
• In the Lawsuit and Subpoena UI tab Column H, is labeled Type, which states if a field is a text box, dropdown box, radio button, etc.  Keep in mind these are suggestions, if you have a better solution, it is okay to not follow it.  These are only suggestions.
• Column N shows the List of Values for the dropdown boxes
• Column O shows the field’s Behavior Rules

CHALLENGE FORUM
If you have any doubts or questions regarding challenge requirements, please ask in our challenge forum:
https://apps.topcoder.com/forums/?module=ThreadList&forumID=704619

SCREEN REQUIREMENTS
For this challenge, we are looking for the below pages to be designed/considered in your concepts. The screen functionality details listed below are suggested functionality for consideration. Do not allow the suggestions below to impact the creativity of design. If there is a better way to accomplish the same goal, then feel free to take creative liberties.

Roles:

• Documents Team - the initial team who receives the subpoena request and enters the necessary data and documentation for the process to get started
• Subpoena Team - receives the assignment from the Documents team and processes the subpoena request and ensures it gets carried out.  They also handle invoicing.
• Managers - oversees both teams and needs to have insight on statuses and who to assign work to.
• Administrator - Provides permissions and enables, edits & creates new accounts.

01) Landing Page/Dashboard (refer to tab: “1. Landing Page CSU” in the provided spreadsheet)
This is the landing page after someone from the Documents Team logs into the app.  It should be some sort of grid view or table showing a summary of claims.  There are 2 different views My Inventory and Department Inventory.

• My Inventory view is the user’s personal list of subpoenas that they have worked on.  See Rows 3 - 14 in the “1. Landing Page CSU” tab in the spreadsheet, for the necessary fields in the grid.
• Department Inventory view is only visible to supervisors.  See Rows 16 - 26 in the “1. Landing Page CSU” tab in the spreadsheet, for the necessary fields in the grid.
  • For this view include a total of “Open and Pending” claims that are Due each day - this should be some type of graph showing the number due each day, or this week, or this month, can be drilled into or maybe a link to a reporting screen.
• Search/Filter/Sort: For both views there should be the ability to search, filter, and sort against any of the fields. 
• On the page provide a link to the NDC Entry View (check more details below about NDC Entry)

02) User Admin (refer to tab: “2. User Admin” in the provided spreadsheet, for necessary fields and example screenshot)

• This screen will be accessible only by Admin users (technical team).
• This is a general permissions screen, and is geared towards setting the permissions within the application.
• They should be able to change permissions and Enable/Disable/Remove an account.

03) Manage User Hierarchy Admin (refer to tab: “3. Manage User Hierarchy Admin” in the provided spreadsheet, for necessary fields and example screenshot)
The admin would be able to assign users to a manager thereby creating a hierarchical structure.  These are the functions of this feature:

• Assignment of users to a specific manager
• Create Team Members List

04) New Entry NDC (National Document Center) (refer to tab: “4. New Entry NDC” in the provided spreadsheet)

• This is the area where new Subpoena records are created.  Someone from the documents team first does a Search.  If no record exists, they create a brand new one.  If the record already exists, they can update and edit it as needed. 
• This is basically a form that needs to be filled out and is then assigned to someone on the Subpoena Team.  See Rows 4 - 39 in the “4. New Entry NDC” tab in the spreadsheet, for the necessary fields and actions on this page
• Include these buttons on the page (See Rows 4 - 39 in the “4. New Entry NDC” tab):
  • Convert to Subpoena
  • Save
  • Search
  • New Record
  • Cancel
  • Exit
  • Document Upload
  • Document View/Edit
• Last 25 Records: in a grid or table view, show the last 25 Records accessed by the team.  The fields for the grid are shown in Rows 51 - 59 in the “4. New Entry NDC” tab. 

05) All Subpoena Search (refer to tab: “5. All Subpoena Search” in the provided spreadsheet)

• This is a dedicated search page to allow someone from the Subpoena team to run a search.  The list of fields that they are running a search against is shown in the spreadsheet, refer to tab: “5. All Subpoena Search” 
• The user needs to be able to filter/sort results
• Results should be shown in a table or grid format containing the list in the spreadsheet, refer to tab: “5. All Subpoena Search”
• Any of the results should be clickable and take the user to the Subpoena Details view (check more details below about the Subpoena Details)

06) Subpoena Details (refer to tab: “6. Subpoena Details” in the provided spreadsheet)

• After clicking on a record in the Subpoena Search, the person from the Subpoena team is taken here.  This page shows a detailed view of a single Subpoena claim. 
• Please check all of the fields required in tab “6. Subpoena Details”
• A person from the Subpoena team should be able to update and edit any of the details in this view.
• Include these buttons:
  • Preview Invoice (Will open Invoicing screen, check details bellow)
  • Save
  • Search
  • New Record
  • Cancel
  • Exit
  • Document View/Edit
  • Document Upload

07) Invoicing (refer to tab: “7. Invoicing” in the provided spreadsheet)

• The Subpoena team needs to bill for the creation of the Subpoena Documentation.  So when the user clicks on the Preview Invoice button in the Subpoena Details screen, it takes them here to generate a new billing invoice of that particular Subpoena Record. 
• The user needs to be able to start off by entering the information shown in rows 3 - 9 in the tab: “7. Invoicing” in the provided spreadsheet.
• Some data is pre populated from the previous Subpoena Details screen see rows 11 - 21 in tab: “7. Invoicing” in the provided spreadsheet.
• There should also be a section with fields for Payments Made Towards Invoices which is also pre-populated see rows 23 - 31 in tab: “7. Invoicing” in the provided spreadsheet.  The person processing the invoice needs to easily see the Subpoena Number and Invoice Number.
• When in the Subpoena Details screen and the user selects from the list of Invoices Sent, it will take them to this Invoicing Screen, but it will be prepopulated.
• Control buttons should be accessible on the screen see Rows 35 - 40 in tab: “7. Invoicing” in the provided spreadsheet.:
  • Print Invoice
  • New Invoice
  • Edit Invoice
  • Void
  • Delete (only Leadership can delete an invoice)

08) Overflow Assignment (refer to tab “8. Overflow Assignment” in the provided spreadsheet)
The Overflow Assignment screen is where extra subpoena assignments which haven’t been assigned end up, and need to be manually assigned by a manager.  Managers need a way to search/show processed claim numbers or requested party name.   They need a way to search/show for previously assigned subpoenas based on claim number or requested party name.  It would help them to assign to the same person who has/is working on the same claim/party.

• List of unassigned subpoenas.  This should be a grid or table view.  For the list of fields that should be in the grid/table refer to Rows 4 - 12 in tab “8. Overflow Assignment”.
• Option to select more than one subpoena at a time to assign multiple subpoenas to a single employee
• Sorting function for Open Subpoenas should include these fields: 
  • Assigned and unassigned (who assigned to)
  • Due date
  • State
  • Claim number
  • Records of name
  • Record ID
• Link to search for Previously processed indicator-Claim # or requested party name
• Display the total # of all open requests, with a break down:
  • New unassigned
  • New assigned
  • Anything in pending queue

09) Fee Table Matrix (refer to tab “9. Fee Table Matrix” in the provided spreadsheet)
This is a reference table for people on the Subpoena Team that shows the breakdown of fees charged for different types of subpoena documentation.

• This should be some sort of grid or table view.
• Show a grid/table for all 50 US states.
• Use the fields in the “9. Fee Table Matrix” tab for the table
• Please reference the existing fee table: fee.png.  This is an example.
• Each line should have an Edit button which allows the authorized user to edit the fee tables when updates are made.

10) Audit Trail (refer to tab “10. Audit Trail” in the provided spreadsheet)
This screen is a log of all events.  It should capture and display all changes to the entries.  Shows a history of changes.  See the “10. Audit Trail” tab to see the fields for this page.
 

• Keep things consistent. This means all graphics styles should follow a set pattern.
• All of the graphics should have a similar feel and general aesthetic appearance

MARVEL PROTOTYPE

• We need you to upload your screens to Marvel App.
• Please send your marvel app request to contato@luizrrodrigues.com.br (Challenge Copilot) 
• You MUST include your Marvel app URL (in your marvel app prototype, click on share and then copy the link & share it with your notes/comments this link while you upload).

 
BRANDING GUIDELINES
CSS StylesGuide 2019

TARGET DEVICES
Desktop: minimum 1366px Width with Height adjusted accordingly

TARGET AUDIENCES
Data entry employees and managers at an insurance company

JUDGING CRITERIA
Your submission will be judged on the following criteria:

• Overall idea and execution of concepts
• How well does your design align with the objectives of the challenge
• Execution and thoughtfulness put into solving the problem
• The overall design and user experience
• Cleanliness of screen design and user flow
• Ease of use

 
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 image files based on Challenge submission requirements stated above
• MarvelApp link for review and to provide feedback

 
Source Files
All source files of all graphics created in either Adobe Photoshop, Illustrator (Might need to convert it to PSD later), XD, or Sketch and saved as an editable layer

FINAL FIX
As part of the final fixes phase, you may be asked to modify your graphics (sizes or colours) or modify overall color