Small teams do not have scheduling departments. The person writing the rota also manages operations, handles supplier calls, and covers shifts when someone is sick. Complexity is the enemy. A good rota process for a team of 2-9 people needs to be fast to build, clear to read, and easy to update.

What Small Teams Actually Need

Before looking at tools or software, define what your scheduling process must do:

  • Show who works which hours on which day
  • Track time off and leave
  • Handle the occasional swap or cover request
  • Give staff enough notice to plan their lives
  • Take less than 30 minutes per week to update

That is the list. A team of 6 people does not need demand forecasting, AI-driven scheduling, or a 14-step approval workflow. They need clarity.

The Weekly Rhythm

Build a consistent cadence for rota creation:

  • Wednesday or Thursday - Collect availability for the following week from anyone with variable hours
  • Friday - Publish the rota for the coming week (Monday to Sunday)
  • Monday - Confirm coverage is in place; address any last-minute changes

This gives staff a weekend to plan around next week's schedule. It gives you a buffer day on Monday if something needs adjusting. The schedule is not a surprise that arrives Sunday night.

Handling Leave Requests in a Small Team

With 6 people, two on leave simultaneously might reduce your floor coverage by 33%. That is not a statistic - it is a real operational constraint. Manage leave by:

  1. Keeping a shared annual leave calendar that everyone can see
  2. Setting a clear maximum for overlapping leave (for most small teams, that is 1 person at a time)
  3. Processing requests in the order received - "first come, first served" is transparent and defensible
  4. Flagging known busy periods in advance (Christmas week, summer peak, trade show season) and restricting leave during those times

Do not approve leave verbally. Confirm it in writing - a message, an email, a calendar update. Verbal agreements cause disputes.

Shift Swaps in Small Teams

Swaps are simpler when the team is small. The rule that works:

  • Staff arrange the swap directly between themselves
  • Both parties confirm to the manager in writing
  • Manager approves before it takes effect
  • The swap is recorded in the rota

The key word is "recorded." A swap that exists only in two employees' memories is not a swap - it is an assumption waiting to fail.

When Someone Calls In Sick

Your cover process for a team under 10 should name a specific person or sequence before the sick day happens. "We'll figure it out" is not a plan. "If [Name A] calls in sick, we call [Name B] first, then [Name C]" is a plan.

Maintain a short cover list:

  • Who can be called in on short notice
  • Whether part-time staff have agreed to take occasional extra shifts
  • Whether any staff live close enough to come in quickly

If your cover list is empty, you need to either hire someone to fill that gap or accept that sick days will sometimes go uncovered. That is a staffing model decision, not a scheduling one.

Tracking Hours Without Overcomplicating It

For a 6-person team, hours tracking can be simple:

  • Record scheduled hours per person per week
  • Track actual clock-in/out if you need precision (important for hourly paid staff)
  • Flag anyone approaching their contracted weekly maximum before you assign more shifts
  • Note overtime separately so it is visible at the end of the month

You do not need a time-and-motion study. You need to know that Jane is contracted for 24 hours and this week she is already at 22 before Friday.

The Common Mistakes

Small teams tend to make predictable scheduling errors:

  • No published rota at all - Manager tells each person their hours verbally or by text. No written record, inevitable disputes.
  • Schedule changes with no notice - "Can you come in two hours early tomorrow?" sent at 21:00. Convenient for the manager, disruptive for staff.
  • Rota built around one person's preferences - The manager's favourite gets all the good shifts. Everyone else notices.
  • No overtime tracking - A small team member quietly accumulates 12-15 hours of untracked overtime over a month. Either they expect payment and you do not know, or they burn out without anyone connecting it to the hours.

A simple, consistent, fair process solves all four.

Rezano keeps your rota, leave, and time tracking in one place without extra complexity. Try it at rezano.lv.