Challenge Summary
Welcome to Insurance iPad Application Design Challenge.
We need the crowd help to come up with an UX solution for an insurance application that will help inspectors to collect sensitive loss data (FNOL) customers suffer on their properties. We are looking forward to capture the incident information, such as photos and causes of losses through a pre-defined template document, in a very easy way.
Best of luck.
2. Register
4. Claims
6. Task Allocation
7. Loss Information Capture
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
1. Login
2. Register
3. Forgot Password
4. Claims
5. Insured Details
6. Task Allocation
7. Loss Information Capture
8. Notifications/Alerts
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
The goal of this challenge is to design the look and feel of an iPad application. We are providing the workflow, user stories and requirements for you to think of an efficient way to deliver and capture information.
Concept Design Goals
We are an insurance company. We want to automate our claims process to make it easier to adjust a large scale amount of claims. In a typical quarter we might get approximately 5,000 claims per quarter. However, when a catastrophe hits, we have approximately 25,000 to 30,000 claims occur in a month. The problem is that all insurance companies are experiencing an uptick in claims so getting claims adjusters to a house is a huge challenge. We want to create an app that allows us to send a home inspector to a house and take required photos and measurements.
The most important and valuable features of this application should cover:
- Registration.
- Task Allocation.
- Photo and scanned Document saving.
Workflow
There are four users who participate in the flow: Insured, Inspector, Desk Adjuster and Manager. We are focusing on Inspector only for this design exercise.
1. The property loser insured person will call the helpline of the insurance company to log the complaint of the loss.
2. This info will be fed by helpline desk or IVR into the system of records.
3. Claims are assigned to inspectors by the desk adjuster.
4. The in house desk adjuster fills out a work assignment based on estimated damage and noted rooms damaged.
5. Claims are run through Google Maps to make a route map for the inspector that is based on the most effective route planning.
6. The prospective travel is made 72 hours in advance and the inspector will call the insured to set appointments. If a cancellation occurs the app tries to fill the spot with a close target
7. The inspector goes to the location and has the claim information in the app. The information gives him the named insured, policy number, etc.
8. The inspector photographs the damaged rooms and asks the insured scripted questions about the claim.
9. The app makes the photos into a stream and uploads them into our claims database.
10. The app saves/exports all collected data to complete the estimate.
11. The claim closes within the app.
Screens Requirements
Overall
- Show hover/active states for buttons, dropdowns, breadcrumbs, errors/success states, elements with interaction, etc.
- All mentions to user below is meant to be the inspector, other user roles are out of scope.
- Please suggest how to organize this content and group them into screens, we are looking forward to see your unique proposals, be bold. The following screens orders are just initial suggestions but we think content could be organized in a different way, go for it!
1. Login
User can enter credentials using email and password. There should be a forgot password link.
DO NOT add a “Register” link.
2. Register
User arrives to registration page through an email invite. Registration process/form should cover the following information: First Name, Last Name, Address, City, State, Zipcode, Email, Mobile, Password, Re-Enter password.
3. Forgot Password
User enters Email or Mobile number for password reset request initiation.
A PIN (6 digit random PIN) is sent to the registered email address to change password. PIN is valid for 10 minutes. User enters PIN, New Password, Re-Type password.
Design three screens, one to capture the email/phone; another one with success or error message (email/phone found or not found); and the another one to enter the PIN with new password.
4. Claims
User can see a set of claims. Eight claims per day maximum.
User can see status indicator of each claim such as done, pending, in progress, etc.
User should be able to see the all details of the claim request. Create a screen for this scenario (could be a popup).
Data to be included: Task ID (number), Status, Customer Info (Name, Policy Number), Customer Location (Zipcode), Address
5. Insured Details
User has access to insured personal information. All data includes: name, policy number, property address, phone number, email.
User can initiate a call or send message to the insured contact.
User should have access to a search feature: customer ID.
6. Task Allocation
User should be able to see the property location map based on Zipcode and HouseNumber. User has access to a guided itinerary, a routemap screen from Inspector location to property visit location.
Map/Schedule
FYI: Schedule is made for the Home Inspector to do 8 inspections per day. Each inspection should last 1 hour. Drive time needs to be accounted for by Google Maps. App should help make schedules by finding the next closest claim to the current loss that has not been scheduled. Target is to have all schedules made within 3 days of the FNOL being taken.
Create a map view and workflow to assign close claims or inspection opportunities for the user. Think of apps like uber to assign the next available resource to the closest available inspector. This in theory should be a very important view, this is where the task allocation takes place.
Itinerary
User should be able to see a guided route through the map that takes him/her to the location. Design the screen to showcase this itinerary from current or custom location to assigned property address.
7. Loss Information Capture
Home Inspector goes to the house and fills out the application. User should be able to collect the conditions of the house and rooms. User can take photos and associate them to the claim, as well as filling a form with questions.
Photo Capture
User can take photos, store them related to the claim. There should be a save option to keep the photo stored.
Loss Information Capture/Scan Doc
Inspector will collect loss information manually using a standard template. Once he/she finishes filling the document the application should allow to perform a scan, with options to:
- Save.
- Export.
8. Notifications/Alerts
System Notifications
System should notify the user about new claim opportunities. User should be able to access claim details from the notification items.
Alerts
Create alerts/popups to express these messages (add dummy text):
- Error.
- Success.
- Warning.
Branding Guidelines
- Extract branding colors and typography from the customer website. During checkpoint feedback we will provide a refined version of the branding, but in the meantime work with the website colors.
- You can use the provided logo.
- Consider the iOS Design Guidelines and Philosophy in your design.
- Keep things consistent. This means all graphic styles should work together.
Screen Specifications
- Tablet Portrait: 1536 x 2048 pixels.
- Make sure your work is in a vector format, for retina scaling and high fidelity.
MarvelApp Presentation
- Request a MarvelApp prototype from me (mahestro@copilots.topcoder.com). Do not use the forums to request for MarvelApp.
- Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.
- Provide the MarvelApp shareable link in your notes during submission upload.
Stock Artwork (Illustrations, Icons, Photography)
- Stock artwork is allowed for this challenge.
- Make sure to declare all your assets properly or you might fail screening.
Target User
18+ persons who own an FNOL insurance. Market is US only.
Judging Criteria
- Interpretation of the user experience.
- Is the application visually appealing?
- Is the application easy to use?
- Cleanliness of your graphics and design.
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, Illustrator or Sketch. Layers should be named and well organized.
Final Fixes
As part of the final fixes phase you may 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.
We need the crowd help to come up with an UX solution for an insurance application that will help inspectors to collect sensitive loss data (FNOL) customers suffer on their properties. We are looking forward to capture the incident information, such as photos and causes of losses through a pre-defined template document, in a very easy way.
Best of luck.
Round 1
Submit your design for a checkpoint feedback.2. Register
4. Claims
6. Task Allocation
7. Loss Information Capture
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03)
Round 2
Submit your final design plus checkpoint feedback.1. Login
2. Register
3. Forgot Password
4. Claims
5. Insured Details
6. Task Allocation
7. Loss Information Capture
8. Notifications/Alerts
- Please provide a MarvelApp Presentation (see details below).
- Make sure all pages have correct flow! Use correct file numbering. (00, 01, 02, 03).
The goal of this challenge is to design the look and feel of an iPad application. We are providing the workflow, user stories and requirements for you to think of an efficient way to deliver and capture information.
Concept Design Goals
We are an insurance company. We want to automate our claims process to make it easier to adjust a large scale amount of claims. In a typical quarter we might get approximately 5,000 claims per quarter. However, when a catastrophe hits, we have approximately 25,000 to 30,000 claims occur in a month. The problem is that all insurance companies are experiencing an uptick in claims so getting claims adjusters to a house is a huge challenge. We want to create an app that allows us to send a home inspector to a house and take required photos and measurements.
The most important and valuable features of this application should cover:
- Registration.
- Task Allocation.
- Photo and scanned Document saving.
Workflow
There are four users who participate in the flow: Insured, Inspector, Desk Adjuster and Manager. We are focusing on Inspector only for this design exercise.
1. The property loser insured person will call the helpline of the insurance company to log the complaint of the loss.
2. This info will be fed by helpline desk or IVR into the system of records.
3. Claims are assigned to inspectors by the desk adjuster.
4. The in house desk adjuster fills out a work assignment based on estimated damage and noted rooms damaged.
5. Claims are run through Google Maps to make a route map for the inspector that is based on the most effective route planning.
6. The prospective travel is made 72 hours in advance and the inspector will call the insured to set appointments. If a cancellation occurs the app tries to fill the spot with a close target
7. The inspector goes to the location and has the claim information in the app. The information gives him the named insured, policy number, etc.
8. The inspector photographs the damaged rooms and asks the insured scripted questions about the claim.
9. The app makes the photos into a stream and uploads them into our claims database.
10. The app saves/exports all collected data to complete the estimate.
11. The claim closes within the app.
Screens Requirements
Overall
- Show hover/active states for buttons, dropdowns, breadcrumbs, errors/success states, elements with interaction, etc.
- All mentions to user below is meant to be the inspector, other user roles are out of scope.
- Please suggest how to organize this content and group them into screens, we are looking forward to see your unique proposals, be bold. The following screens orders are just initial suggestions but we think content could be organized in a different way, go for it!
1. Login
User can enter credentials using email and password. There should be a forgot password link.
DO NOT add a “Register” link.
2. Register
User arrives to registration page through an email invite. Registration process/form should cover the following information: First Name, Last Name, Address, City, State, Zipcode, Email, Mobile, Password, Re-Enter password.
3. Forgot Password
User enters Email or Mobile number for password reset request initiation.
A PIN (6 digit random PIN) is sent to the registered email address to change password. PIN is valid for 10 minutes. User enters PIN, New Password, Re-Type password.
Design three screens, one to capture the email/phone; another one with success or error message (email/phone found or not found); and the another one to enter the PIN with new password.
4. Claims
User can see a set of claims. Eight claims per day maximum.
User can see status indicator of each claim such as done, pending, in progress, etc.
User should be able to see the all details of the claim request. Create a screen for this scenario (could be a popup).
Data to be included: Task ID (number), Status, Customer Info (Name, Policy Number), Customer Location (Zipcode), Address
5. Insured Details
User has access to insured personal information. All data includes: name, policy number, property address, phone number, email.
User can initiate a call or send message to the insured contact.
User should have access to a search feature: customer ID.
6. Task Allocation
User should be able to see the property location map based on Zipcode and HouseNumber. User has access to a guided itinerary, a routemap screen from Inspector location to property visit location.
Map/Schedule
FYI: Schedule is made for the Home Inspector to do 8 inspections per day. Each inspection should last 1 hour. Drive time needs to be accounted for by Google Maps. App should help make schedules by finding the next closest claim to the current loss that has not been scheduled. Target is to have all schedules made within 3 days of the FNOL being taken.
Create a map view and workflow to assign close claims or inspection opportunities for the user. Think of apps like uber to assign the next available resource to the closest available inspector. This in theory should be a very important view, this is where the task allocation takes place.
Itinerary
User should be able to see a guided route through the map that takes him/her to the location. Design the screen to showcase this itinerary from current or custom location to assigned property address.
7. Loss Information Capture
Home Inspector goes to the house and fills out the application. User should be able to collect the conditions of the house and rooms. User can take photos and associate them to the claim, as well as filling a form with questions.
Photo Capture
User can take photos, store them related to the claim. There should be a save option to keep the photo stored.
Loss Information Capture/Scan Doc
Inspector will collect loss information manually using a standard template. Once he/she finishes filling the document the application should allow to perform a scan, with options to:
- Save.
- Export.
8. Notifications/Alerts
System Notifications
System should notify the user about new claim opportunities. User should be able to access claim details from the notification items.
Alerts
Create alerts/popups to express these messages (add dummy text):
- Error.
- Success.
- Warning.
Branding Guidelines
- Extract branding colors and typography from the customer website. During checkpoint feedback we will provide a refined version of the branding, but in the meantime work with the website colors.
- You can use the provided logo.
- Consider the iOS Design Guidelines and Philosophy in your design.
- Keep things consistent. This means all graphic styles should work together.
Screen Specifications
- Tablet Portrait: 1536 x 2048 pixels.
- Make sure your work is in a vector format, for retina scaling and high fidelity.
MarvelApp Presentation
- Request a MarvelApp prototype from me (mahestro@copilots.topcoder.com). Do not use the forums to request for MarvelApp.
- Provide clickable spots (hotzones) to link your screens and showcase the flow of the solution.
- Provide the MarvelApp shareable link in your notes during submission upload.
Stock Artwork (Illustrations, Icons, Photography)
- Stock artwork is allowed for this challenge.
- Make sure to declare all your assets properly or you might fail screening.
Target User
18+ persons who own an FNOL insurance. Market is US only.
Judging Criteria
- Interpretation of the user experience.
- Is the application visually appealing?
- Is the application easy to use?
- Cleanliness of your graphics and design.
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, Illustrator or Sketch. Layers should be named and well organized.
Final Fixes
As part of the final fixes phase you may 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.
Please read the challenge specification 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.