Rules

Secret ingredients to quality software

Edit
Info

Do you know where your staff are (and where they’re supposed to be)?

Last updated by Tiago Araujo on 04 Jan 2021 06:37 pm (7 months ago) See History

It's been said that in order to succeed you have to show up – nowhere is that more true than the workplace. Knowing where your staff are is paramount.

At the beginning of each day you should:

  1. Review a staffing report – consider a report in Power BI or a similar tool that shows which of your staff are booked for what activities on any given day

BookedInDays
Figure: Green is booked, Black is booked for internal work, and Red is leave

  1. Make updates to staff bookings as required in the source calendars so that the booked in days report is an accurate representation of what clients staff are assigned to. Ensure that any other staffing or service calendars are also updated to accurately reflect the day's planned activities.

Service Calendar
Figure: See 4 blue bars. This means they are booked. Not easy eh!

  1. Review your absence calendar. Each business should have a calendar where employees can note any upcoming absences or leave so that it's easy for other team members to know where folks are at any given time.

absences
Figure: Here are the 2 people on leave

  1. Check who's in the office. Have a look at who's currently in the office and if someone's not present or doesn't have an absence or booking, find out where they are. You can use a tool like SophieBot or other tools to find out who's physically in your office at any time

SophieBot
Figure: You can use SophieBot to provide a staffing report of who is physically in the office today

SophieBot booked
Figure: SSW SophieBot to answer “Who is booked? [ANSWER: 6 people]

SophieBot free
Figure: SSW SophieBot to answer “Who is free? [ANSWER: 4 people]

SophieBot leave
Figure: SSW SophieBot to answer “Who is on leave? [ANSWER: 2 people]

  1. If staff are missing or otherwise unaccounted for, make sure to take appropriate action to find out where they are and why they haven't been in communication
Matthew SampiasMatthew Sampias
Adam CoganAdam Cogan

We open source. This page is on GitHub