> For the complete documentation index, see [llms.txt](https://docs.foodcore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/staff-rota.md).

# Staff rota

{% hint style="info" %}
📦 Available on the **Core** plan, or as the **Staff rota** bolt-on (£6 a month) on Essentials and Growth.
{% endhint %}

The Staff Rota is where you build your team's working week — shifts, who's on them, and when the schedule is confirmed and visible to everyone.

## Opening the rota

Go to **Staff Rota** in the main menu. The rota shows your team's shifts laid out across the week, with tools to move between weeks and build the schedule ahead of time.

## Build a shift

1. **Go to Staff Rota** in the main menu.
2. **Choose the week** you're scheduling, using the week navigation.
3. **Add a shift** on the day you need cover — set the start and end time.
4. **Add any notes** the shift needs — an early prep start, a delivery to expect, anything the person on shift should know before they arrive.

## Your team

Your team list lives on the **Staff** tab. Everyone with a login is already there, and you can add people by name only, with no email or login. See [The Staff tab](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/staff-tab.md).

On Essentials and Growth, the Staff rota bolt-on works for staff without logins. To let staff sign in, see their own shifts and request holidays, add **Team logins** (£10 a month). Both together are £16 a month.

## Assign staff

**Assign a team member to each shift** from your team list. The picker groups people into **With a login** and **Without a login**. If someone isn't listed, add them on the Staff tab first. A shift can sit unassigned while you're still working out the week, or you can assign it straight away if you already know who's covering it.

If your account has multiple sites, a shift is tied to the site it was created for, so each location keeps its own schedule.

## Publish the rota

Shifts you're still arranging stay in draft, so you can move things around without confusing anyone. **When the week is settled, publish the rota** — this is what makes the schedule visible to your team. Publish once you're confident the week won't change, rather than shift by shift, so everyone sees a complete, settled picture rather than a rota that's still being rearranged underneath them.

## Keeping the week visible everywhere

Once shifts are on the rota, your team doesn't have to keep FoodCore open to know when they're working — shifts can appear in Google Calendar or Apple Calendar alongside production and collections. See [Calendar sync](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/calendar-sync.md) for how to set that up.

## What's next

* [The Staff tab](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/staff-tab.md)
* [Set a kitchen PIN](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/kitchen-pin.md)
* [Give them a login](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/give-them-a-login.md)
* [Calendar sync](https://docs.foodcore.io/staff-rota-core-or-staff-rota-bolt-on/calendar-sync.md)
* [Production planning](https://docs.foodcore.io/production-growth-and-core/production.md)
* [Production calendar](https://docs.foodcore.io/production-growth-and-core/calendar.md)
* [Team & Users](https://docs.foodcore.io/team-and-users-core/users.md)
