Employee productivity

What is employee productivity?

Employee productivity is the output an employee or a team produces per hour worked: revenue, covers, rooms cleaned, or order lines picked. It is a ratio, so it rises when the same hours produce more, or when the same output takes fewer hours.

Hours worked is the part that matters most in shift work. A server on the floor for eight hours on a quiet Tuesday is paid for eight hours, but what those hours produce depends on whether the schedule put the right number of people on that day. Productivity in a shift business is as much a property of the schedule as of the person.

Two other words get used next to it. Efficiency is about waste: how much input one unit of output takes, such as minutes per order. Performance is wider and includes quality, behaviour, and goals, which is why it is judged in a review rather than calculated. Productivity is the one you can put a number on every week.

How to measure employee productivity

The formula is output divided by input:

Employee productivity = output ÷ hours worked

Both halves need a decision. Output should be something the team on that shift can influence and that you already record, usually in the till or your operations system. Hours should be hours worked, taken from clock-in data or approved timesheets, not contracted hours and not headcount. Revenue per employee looks tidy in an annual report, but it counts a student who works Saturdays the same as a full-timer, so it says little about a shift team.

Measure per department and per day before you measure per person. On most shifts the output belongs to the team: the kitchen and the floor sell the same meal, and splitting the till between them gives numbers nobody trusts.

A worked example from one restaurant week

A restaurant sets a target of £45 revenue per labour hour for front of house. Two days from the same week:

Saturday beats the target. Tuesday misses it by a third, and the people working that day did nothing wrong: the schedule gave them 60 hours for a day that needed about 40 (£1,800 ÷ £45). Cutting 20 hours would put the day on target, but only if the remaining crew can still open, serve, and close. If a Tuesday needs at least 48 hours to run safely, the realistic ceiling is £37.50 per hour, and the target for quiet weekdays should say so.

Then compare planned with actual. Say the Tuesday schedule had 60 hours, timesheets show 66 because two people stayed late, and the till took £1,650 instead of the £1,800 forecast. Actual productivity was £25 per hour (£1,650 ÷ 66). The drop from £30 planned to £25 actual holds two separate problems, a forecast that was too high and hours that ran over, and each has its own fix.

Productivity metrics that mislead

Most productivity figures go wrong in one of a handful of predictable ways, and each one makes the team look better or worse than it is.

Hours present instead of hours worked

Scheduled or contracted hours flatter the result when people leave early and punish it when a shift overruns. Use the hours from clock-in data, the same hours that go to payroll. Time tracking that records breaks gives you that figure without a separate list.

Output without quality

A kitchen that sends out more plates per hour by cutting corners looks more productive until the remakes and complaints arrive. Pair the output figure with one quality signal you already collect, such as returns, remakes, or review scores.

One average for the whole week

A week at £44 per hour can be two strong weekend days and three overstaffed weekdays. Look at productivity per day and per department: the weak days are where hours can move.

Activity instead of output

Monitoring software that counts keystrokes, mouse movement, or app use measures activity, and activity is not output. For frontline staff it captures almost nothing, since a server carrying plates touches no keyboard. A shift business already holds the two numbers it needs: output from the till and hours from the clock.

Blaming people for the schedule

When productivity drops on the same days every week, the cause is usually staffing rather than effort. Overstaffing lowers revenue per hour on quiet days. Understaffing does the opposite on busy days, and a figure that looks excellent can hide skipped breaks and slow service.

KPIs for employee productivity in a shift business

One number rarely explains itself. These are the measures that sit around productivity and tell you why it moved:

• Revenue or output per labour hour, per department and per day

• Labour cost as a percentage of revenue, which adds wage levels to the picture

• Scheduled hours against worked hours, which shows the size of the overrun

• Overtime as a share of all hours worked

• Absenteeism rate, because a sick call on a busy shift lowers output and raises cost at the same time

• Staff turnover, since a new starter needs weeks before they work at full pace

What affects employee productivity on a shift

The biggest factor is whether the number of people on the floor matches demand. That is a planning question before it is a management one: labour forecasting from past sales, bookings, and local events puts the hours where the revenue is.

Next is the mix of skills. Five people on a shift where nobody can work the grill produce less than four people who can cover every station, and cross-training one extra person per station gives the schedule room to move.

Schedule stability counts for more than most managers expect. A rota that changes at short notice brings late arrivals, swaps arranged in group chats, and people working a shift they did not plan their week around. Publishing early and handling swaps in one place takes that friction out.

Fatigue shows up in the last hours of a long shift and after a late close followed by an early start. Those patterns are easier to spot in the schedule than in the results.

Then the people themselves. Staff who know what a good shift looks like, and who see that their work is noticed, put more into it. Employee engagement moves slowly and is hard to measure directly, but it shows up in absence and turnover.

How to improve employee productivity

Start with the days and departments furthest from target. That is where hours can move without anyone having to work harder.

1. Set a target per department that the team can reach on a normal day, with a separate floor for quiet days that need a minimum crew.

2. Schedule against the forecast, and shift hours from quiet slots to the peaks instead of adding hours on top.

3. Check planned against worked hours every week. An overrun that repeats on the same shift usually points to a closing or handover routine that takes longer than the schedule allows.

4. Put the people with the right skills on the busiest shifts, and train a second person for every critical station.

5. Ask the team which task slows the evening down. The answer is often a slow till, a missing prep list, or a delivery that arrives at the worst moment.

Raising the number by squeezing breaks or stretching shifts works for a few weeks. After that, absence and turnover tend to take the gain back.

If you want one figure that combines several of these measures, a productivity score weighs them into a single number per team.

Employee productivity in Shiftbase

In Shiftbase you can set a productivity target per department, calculated as forecast turnover divided by scheduled hours. With targets shown in the schedule, each department gets a colour per day, so an overstaffed Tuesday is visible while the week is still a draft. The schedule versus timesheet report then puts scheduled hours next to approved worked hours, which is the planned-against-actual gap from the example above.