Figma Design of a Productivity Mobile App
Budget: $30 – $250 USD
Client Area:
- Dashboard with a calendar showing their scheduled shifts.
- Create events - Client should see immediately what is the approximate cost for this event.
- Event creation:
- Client
- Name
- Location (which could be created beforehand)
- Manage events (updates, see how many spots are filled)
- Download or get timesheets by email (only after the SYSTEM ADM approves it)
- See history of events
- After an event, they can come and upload staff hours into the system
- When that happens, SYSTEM ADM has to confirm it and then the system sends an invoice to the client
- There will be different levels of client users, and the user can see one or more clients. For example, the same client could have 3 or 4 contracts. One user will be created for each contract, and another user will be able to see, create and manage info for all 4 of them.
- Client has an option to make payments through the app.
- Rating employees and request for that employee for shifts (when they request, the request will not go directly to the employee, but to SYSTEM ADM to decide if this employee will work that shift or not.
Employee Area:
- Accept or decline shifts
- See history of accepted and declined shifts
- Manage it's own information like address, photo, phone number or email, etc. (whenever they change the phone number or email, the new info has to be confirmed by code sent by text or email).
- Enter availability
Admin Area:
- Create and manage employees
- Create and manage clients
- Create and manage client's users
- Create and manage events
- Send shift requests to specific employees or publish shifts to employees of our choice, to all employees or to groups of employees (using tags to separate employees - for example "publish shift only for employees who are tagged as 'TIPS Certified'")
- Approve timesheets entered by client
- Enter timesheets into the system
- Send announcements to workers (for example send an announcement to all workers in a shift, or choose which workers to receive the announcement, or send to all employees).
Other info:
- Every time an event is created, the system should also create a Job Order for this shift. The Job Order is basically a document with info from the shift that should be available to the employees at any time. ( I can explain about that later ).
- Dashboard with a calendar showing their scheduled shifts.
- Create events - Client should see immediately what is the approximate cost for this event.
- Event creation:
- Client
- Name
- Location (which could be created beforehand)
- Manage events (updates, see how many spots are filled)
- Download or get timesheets by email (only after the SYSTEM ADM approves it)
- See history of events
- After an event, they can come and upload staff hours into the system
- When that happens, SYSTEM ADM has to confirm it and then the system sends an invoice to the client
- There will be different levels of client users, and the user can see one or more clients. For example, the same client could have 3 or 4 contracts. One user will be created for each contract, and another user will be able to see, create and manage info for all 4 of them.
- Client has an option to make payments through the app.
- Rating employees and request for that employee for shifts (when they request, the request will not go directly to the employee, but to SYSTEM ADM to decide if this employee will work that shift or not.
Employee Area:
- Accept or decline shifts
- See history of accepted and declined shifts
- Manage it's own information like address, photo, phone number or email, etc. (whenever they change the phone number or email, the new info has to be confirmed by code sent by text or email).
- Enter availability
Admin Area:
- Create and manage employees
- Create and manage clients
- Create and manage client's users
- Create and manage events
- Send shift requests to specific employees or publish shifts to employees of our choice, to all employees or to groups of employees (using tags to separate employees - for example "publish shift only for employees who are tagged as 'TIPS Certified'")
- Approve timesheets entered by client
- Enter timesheets into the system
- Send announcements to workers (for example send an announcement to all workers in a shift, or choose which workers to receive the announcement, or send to all employees).
Other info:
- Every time an event is created, the system should also create a Job Order for this shift. The Job Order is basically a document with info from the shift that should be available to the employees at any time. ( I can explain about that later ).