[x] On the event tab, when there are 7 volunteers registered for an event with 10 slots, it should show “3/10 slots available” instead of just showing “3 slots available”. This is to present more clarity for the admin to understand how big this event is without opening the editing event window to review. The same should apply to the event tabs on the events list page.
Events
[x] on an event tab for a private event, there should be a label “Private Event” next to the event’s name indicating that this is a private event.
Manage Volunteers/Admins
[ ] on the new design of this page, the search bar is blended into the list of volunteers/admins. This helps make the “Download to CSV” button more evident and that the features on the page is seperated in a clearer way.
Attendance
The main design goal for this feature is to present a clear and intuitive way for admins to manage attendance, accomplished through controlling the degree of flexibility when interacting with the system. All the design decisions were made based on a careful evaluation to maintain a balance between giving users enough flexibility while not making the system too complicated which leads to confusion.
[x] it should show the number of minors alongside the adult. This is to present more clarity for the system’s current status. It helps reduce the confusion, for example, when an admin created an event with a capacity of 10 volunteers and an adult registered with 2 minors, the number of available slots would change to 7. If the number of volunteers is not shown alongside the adult, the admin will see only 1 adult on the registered list but 3 spots are taken. This will make the user think that there is a bug in the system.
[ ] the “End Event” button should change to a grayed “Event Ended” button, instead of a “Reopen Event” button. This is to reduce the amount of flexibility of the system by limiting the number of possible states it can get.
[ ] there should be pop-up windows for checking in, checking out, and ending an event. This is to prevent users from accidental touch or errors, while also forcing the users to rethink an action when they take it. We selected this type of error prevention instead of error recovery (such as allowing users to change a checked-in volunteer to waiting to be checked in) to keep the interactions simple. The system will guide users to take their actions seriously.
Create a Private Event
[ ] the private event creation window is rearranged to differentiate the organization information and the event information. This rearrangement reduces the possibility of admins inputing the organization’s information in the event information section.
Bits of Good Approval Portal
[ ] there are some spacing issues with this page, which could be improved by following the original design.
Admin Home
Events
Manage Volunteers/Admins
Attendance
The main design goal for this feature is to present a clear and intuitive way for admins to manage attendance, accomplished through controlling the degree of flexibility when interacting with the system. All the design decisions were made based on a careful evaluation to maintain a balance between giving users enough flexibility while not making the system too complicated which leads to confusion.
Create a Private Event
Bits of Good Approval Portal