Key Information

Register
Submit
The challenge is finished.

Challenge Summary

Long & Foster is building a web application that allows their staff to store various sales contracts and other sales related documents in PDF format and allow retrieval of these documents upon request. The goal of this contest is to produce wireframes that accurately capture the application requirments and information flow so the client has a clear understanding of their application and a designer can create UI screens needed to build this application. Please read the contest specification and watch the forums for any questions or feedback concerning this contest. 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.
The Case File Imaging System (CFIS) will be a document storage and retrieval web application. The application will store various sales contracts and other sales related documents in PDF format and retrieve these documents for display when requested by a user. Documents will be submitted to the system either through the use of a document copier or through directly uploading PDF documents. Both methods will utilize a 'coversheet creation page' that will either allow users to print out a coversheet for the hard copy upload or allow users to directly upload previously existing PDF documents. After documents are in the system, users may retrieve documents from the system and view them online, or save them to their local drive as desired. The system shall also provide 4 worklist screens that will be used by accounting department personnel to see the status of a case as it flows through the accounting system. Four main areas of the cycle are covered: 1) Escrow with L&F 2) Received HUD-1 3) Pending Disbursement 4) Money Releases These worklist screens merely show data on the screen; there is no other functionality they are required to perform. Users look at them to see what is pending and go to other external systems to resolve any issues that may hold up a case from processing. Because a document submitted to the system may not find its way to the proper case, a 'Lost and Found' area will be available to IT System Administrators who can look at each orphaned document and attach it to the proper case. Target User - Sales Agents - Accounting Departement Staff - IT System Administrators Requirements Allow user to create a coversheet for adding documents to the system - Case Number - Address - Document Type - Case Name - Number of pages - Comments Allow users to see documents linked to a specific case - Jurisdiction - Case Number - Case Name - Document Type - Date Entered - Entered by - Comment - Select option - Delete option Allow IT System Administrators to assign documents from Lost and Found to existing cases - User ID - Date Received - Fax Number/Scanner ID - Reason Failed Provide a worklist to show various Accounting groups what cases are currently requiring attention. Escrow with L&F - Jurisdiction - Case Number - Case Name - PC Name - Deposit Amount - Escrow Type - Date Entered - Case Side Received HUD-1 - Jurisdiction - Case Number - Case Name - Date Entered - PC Name - Excess Flag - ACE Case status Pending Disbursement - Jurisdiction - Case Number - Case Name - Date Entered - PC Name - Coordinator - ACE Case status Money Releases - Jurisdiction - Case Number - Case Name - ACE Case status Information within the website is display only - not editable. Links will exist to open a document, save a document to a local drive, or delete a document. Site Navigation Administrator Login - Lost & Found (Administrators only) - Recover deleted documents (Administrators only) - Admin Delete documents (Administrators only) Agent and Accounting Department Login - Create Coversheet (All users) - View Documents (All users) - View Worklists (All users) - Escrow with L&F - Received HUD-1 - Pending Disbursement - Money Releases Data and Functionality Elements Please see download (CFIS-Requirments.pdf) additional requirements. Wireframe Resources Wireframes on Wikipedia: http://en.wikipedia.org/wiki/Web_site_wireframe Wireframe software option: www.axure.com Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php Wireframe Requirements Wireframes can should be built in HTML, Axure (listed above), MS Visio or OmniGraffle. The resulting files are not critical in this contest. The most important point is that all the content is listed and the pages are linked together to show page flow. Pages must be linked together as a clickable resource Judging Criteria Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

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.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

CHALLENGE LINKS:

Screening Scorecard

SUBMISSION FORMAT:

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

CHALLENGE LINKS:

Questions? ‌Ask in the Challenge Discussion Forums.

SOURCE FILES:

You must include all source files with your submission.

SUBMISSION LIMIT:

Unlimited

SHARE:

ID: 30021498