Skip to content
FitRank

Shift scheduling

Employee availability form: the four questions that actually build a schedule

By Yaseen Khatib, , 5 min read

Employee availability form: the four questions that actually build a schedule

Short answer. An employee availability form needs four answers: which days the person cannot work, the most shifts they can take in a week, any dates that change either, and a way to reach them. Add up the totals before you build the schedule. Capacity equal to demand is not enough; you need a margin.

When I built the free schedule generator for this site, I had to decide what it would ask about each person. I did not start from a form. I started from what the fill needs to know, and it came down to two facts: the days a person cannot work and the most shifts they will take this week.

Those two facts are the core of every availability form I have seen since, and the order matters: what a person cannot do is a more useful answer than what they can.

Why I ask for days off, not days available

In the generator the field is called Unavailable on. Each person has a list of days they cannot work, and everything else counts as open. The code stores exactly that, a list of unavailable days, and the total capacity shown at the top is the smaller of two numbers for each person: their weekly maximum, or seven minus their days off.

There is a practical reason. People answer faster when they list the exceptions. Ask someone for their available days and you get a long list that is half habit. Ask what they cannot do and you get a short one that is mostly true.

The test: capacity equal to demand

The example team in the generator has six people and 22 slots to fill in a week, with 27 shifts of capacity. I wanted to know how much margin is enough, so I took one person, Dev, out of the example. Dev has no days off and a maximum of five, so removing him takes the capacity from 27 to 22, which is exactly the demand.

The generator then left one slot unfilled: Friday evening. Everyone who could work Friday evening had already hit their limit or was already on Friday morning. Ben, Farid, Chen and Elena had reached their weekly maximums, and Asha was on the Friday morning shift, so she could not take a second one that day.

Two things came out of this. The first is the point of this post: capacity is a total, but shifts happen on particular days, so a total that matches demand can still leave a gap. The second is a flaw in my own tool. The banner under the form only warns when capacity is below demand. With capacity equal to demand it says nothing, and the week still has a hole. I know because I tested it for this post. A better warning would fire when the margin is thin.

The four questions

  1. Which days of the week can you not work? Tick boxes beat free text, and a list of exceptions beats a list of availability.
  2. What is the most number of shifts you can take in a week? This is different from the days off. Elena in the example can work five days, but her maximum is three.
  3. Are there dates that change your answer, such as leave, a course or an exam? Ask for dates, not for a description.
  4. How should I reach you if a shift changes? One channel, not three.

Leave out the questions that sound useful and are not: preferred shift times usually become hard constraints in people's heads and in yours, and a form that asks for them promises something a rota cannot keep. If you want to track preferences, keep them in a separate column and use them only to break ties.

What to do with the answers

  1. Add up capacity for each person: the smaller of their maximum or the number of days they are free.
  2. Add up demand: every slot, times the number of people it needs.
  3. Aim for capacity at least a fifth above demand. That is my own rule of thumb from one test, not a standard. It is a place to start, and 27 against 22 in the example is about 23 percent over.
  4. For the day with the fewest free people, count them by hand. If it is close to the number needed, fix that day first.
  5. Keep the form answers with the schedule you publish, so you can say afterwards why somebody was or was not on a shift.

You can run the numbers in the free automatic schedule generator, which asks for exactly these fields and prints the capacity and demand line. If you would rather keep it in a spreadsheet, the Excel employee schedule template has the grid and the hours.

What the form cannot tell you

A form records what people say. It does not know whether they have the skill for a shift, how much rest they had between two shifts, or whether the same person has had every weekend this month. If your problem is who is the right person for a piece of work rather than who is free, that is the part FitRank is built for. It is in pilot, and the pricing page explains how it is licensed.

What should an employee availability form include?

The days the person cannot work, the most shifts they can take in a week, any dates that change those answers, and how to contact them. Keep it to those four.

Should the form ask for available days or unavailable days?

Unavailable days. People list exceptions faster and more accurately than they list every day they could work.

Is there a free employee availability form template?

You can build one from the four questions in this post in any spreadsheet or form tool. The free schedule generator on this site asks for the same two core fields, days off and a weekly maximum.

How much spare capacity do I need?

In my test, a week with capacity exactly equal to demand still left one slot empty. I would start with about a fifth more capacity than demand and check the hardest day by hand.

More from the blog

Be one of the first teams to staff with FitRank

We're taking on a small number of pilot companies. Pre-register for early access, or talk to us about an annual licence.