We are looking for a design for the five key pages of our Web Application.
General notes for all mock-ups:
• We have provided a rough guide of how we imagined the mock-ups could look but we are open to suggestions and these are simply a starting point.
• The top banner to remain quite minimal and clean but also open to suggestions or design concepts.
• Blue was chosen as is clean and professional but again open to alternatives
The feed page is the page that users will be immediately presented with when they login.
This is a live feed of all activity that has been happening within the system (Think like any social media feed) We are looking to make this quite visual with use of icons for different activities and perhaps even photo of user who completed the action (or perhaps circle with initials if no photo uploaded)
This is the first page people will see so we need to set the tone.
Crisp, clean and not too busy.
Clear identification between each line item.
Key data that will be captured for each record in the feed will be:
• Detail of activity completed (ie. New Incident Reported)
• Record Reference (Ie. INC202 Injury to Employee – Welshpool)
• Activity completed by (Ie. Fred Smith)
• Date and Time activity completed (Ie. 10/July/2018 11:22:00am)
Need to be able to filter this page easily.
Order and layout is not locked down, so open to suggestions.
2. ACCOUNT SETTINGS
Account Settings section is where admin users will be able to amend and update account information.
This section will also act as the set-up wizard, which new users will be taken through on their first login to set up their account.
Therefore we are looking for clear flow between each tab on the left hand side, as well as clear identification of which tab they are on.
3. INCIDENT REPORT
This page is the online version of the incident report form that all employees will be presented with when they wish to submit a report. Employees accessing this page will not be common users of the system and they may have never have seen this page before.
Therefore key requirements for this page include making it clean, easy to follow and easy to understand.
Field types may include date/time pickers, dropdowns, free text and image upload.
Considerations include visuals for identifying mandatory fields that need completing, as well as very clear save or cancel buttons.
4. INCIDENTS HOMEPAGE
This page is the page under the Incidents Menu item, working title Incidents Homepage. This acts as an overview of all current open incidents.
Main design element is the table.
Users will be able to click on a record to go to the incident summary page for that record to view more detail or add activity.
Search, filter and export buttons/icons also important. Ability to add new incidents also important and needs to be an obvious feature on this page.
We would also like to see consideration of a progress/timeline icon on the left of each line item. This will show the progress of the incident.
There are essentially 5/6 stages that an incident can be in, so something depicting this would be ideal. Alternatively we would consider an icon depicting the stage (more information could be shown on hover) or colour coding but will leave to interpretation.
5. INCIDENT SUMMARY
Perhaps the most crucial design page of the system, this is the incident summary page for each individual incident, which you will see when you click into a record from the Incidents Homepage.
This page holds all the information about a particular Incident.
Current visuals show the following:
o This depicts the different stages that an incident will go through in order to close the record. This aligns with the “stage” of the incident on incident homepage.
o If a form, such as Incident Investigation, needs completing then users will be able to click on the button to add instantly (or choose from the add information dropdown)
o Dates will be added as forms completed
o Consideration for colour coding as progress through the stages or instant visual depiction of where incident is at.
• Add Information
o This will be where users can add any information against this record.
o Such as Incident Review, Incident Investigation, Photo, Document, Action, Alert
o Depending on what option is chosen to be added then relevant questions will appear for adding that bit of information
o Automatic alerts will be generated from the system for tasks that need completing. These need to be visual on the incident summary page with perhaps determination of overdue alerts or those not yet required.
o Similar to the main feed, this will include only activity for this incident. May include additional information or activities that the main feed.