Staff rotas with Zoho Shifts: building, publishing and filling shifts across sites

Staff rotas with Zoho Shifts: how the setup works

You build staff rotas with Zoho Shifts in five steps. Create the week's shifts as open shifts and let auto-schedule fill them from staff availability. Review the draft, publish it, and leave any gaps open for eligible staff to pick up. Each step depends on two choices you make early: the schedule and the position each person belongs to.

A staff rota in Zoho Shifts is the set of published shifts that tells each employee where and when they work. Until you publish, employees see nothing. Zoho's publishing guide says employees "can view and take action on shifts only when they are published". That gives you a safe space to build and correct the week before anyone is notified.

The sections below follow the order a manager works in. They start with the terms and the structure for several sites. Building, auto-scheduling, publishing and filling gaps come next. The post closes with a worked example, a table of setup decisions, a note for UK employers and practical next steps. Every product fact comes from Zoho's own help pages, listed at the end.

Key Zoho Shifts terms: schedule, position, open shift, draft and auto-schedule

Five terms decide how Zoho Shifts behaves, and Zoho's help pages use them precisely. Here is what each one means in practice:

• Schedule: a group of shifts that staff and managers are assigned to. Managers can create, publish and auto-schedule shifts only for schedules they are assigned to.
• Position: the role a shift needs. An employee qualifies for an open shift only if they hold the same schedule and position as that shift.
• Open shift: a shift with no named employee. Zoho describes open shifts as shifts "created without assigning them to a specific employee". Eligible staff can request them once the schedule is published.
• Draft shift: a shift saved without being published. Draft shifts are not visible to employees.
• Auto-scheduling: a feature that fills open shifts from staffing needs, employee availability and schedule constraints. It produces a read-only draft schedule that you review, apply or discard.

Most rota problems trace back to the first two terms. An employee who is missing from a schedule, or who holds the wrong position, never receives a notification for an open shift. Auto-schedule will not place that person either, however available they are. Getting schedules and positions right first saves hours of manual fixing later.

Zoho Shifts or Zoho People shift setup for rotas that change by day

If your rotas change from day to day, look at Zoho Shifts before forcing them into the shift setup in Zoho People. A user on Zoho's community forum describes the limits they hit in People's shift setup:

• A day off could only be set up as a weekend setting.
• Only one shift could be assigned per employee per week.
• Shift days configured as OFF days did not show on the desktop calendar.

The poster explains that with hybrid workers "shifts vary by DAY not week". They also point out that Zoho already has an application called Shifts. These are one user's report, not Zoho documentation, so test the behaviour in your own account before deciding. You can read the full Zoho community thread on shift management.

For a business on Zoho One, the bigger risk is a second, standalone staff list. Before you build anything, agree the names for your sites and roles. Then use the same names for schedules and positions in Shifts as for teams and locations elsewhere in your Zoho One setup. Consistent names make rota data much easier to compare with HR, finance or project figures later. If you schedule customer appointments rather than staff, Zoho Bookings for appointment scheduling is the tool to look at instead.

Multi-site rotas: one schedule per site and permissions to match

For teams across several sites, a clear structure is one schedule per site, with positions for the roles that work there. The rule that makes this work is scope. Managers can create open shifts, publish and run auto-schedule only for schedules they are assigned to. A site manager assigned to one schedule therefore cannot publish another site's week by mistake.

Staff who work at more than one site should be assigned to every schedule they can cover. Zoho checks clashes across sites for you. An employee is notified about an open shift only if they have no overlapping assigned shifts "across any schedule". Auto-schedule also skips anyone whose approved time off or existing shifts overlap the open shift.

Each task in Zoho Shifts needs its own access level or permission. Give site managers only the permissions their job needs:

Task	Access needed	Scope
Create open shifts	Administrator, or Add, edit shifts	Assigned schedules only
Run auto-schedule	Administrator, or Publish shifts	Assigned schedules only
Publish or unpublish shifts	Administrator, or Publish schedule	Assigned schedules only
Manage open shift pick-up behaviour	Administrator, or Manage account and other settings	Account-wide setting

Keep the pick-up settings with an administrator. They change how every site fills its gaps.

Building the weekly rota as open shifts

Build the week as open shifts when you want auto-schedule to fill it. Zoho's guide states that auto-scheduling "uses the unpublished open shifts to create a schedule". Shifts you assign by hand stay as they are. Open shifts are the demand that auto-schedule tries to meet.

Create each open shift on the right schedule and position, then set the details:

• Employees needed: enter the count of people the shift requires, such as two counter staff for a busy Saturday.
• Hide end time: select this to show staff only the start time. It suits shifts that finish when the work is done, not at a fixed hour.
• Save, do not publish: shifts saved without publishing stay as drafts. Zoho says draft shifts let you "create and review all required shifts, make adjustments, and publish them together".

Managers away from a desk can create open shifts in the Zoho Shifts mobile app. Tap Schedules at the bottom of the screen, then the + icon at the top right. The same permission and schedule rules apply as on the web.

Build the whole week before you publish anything. Draft open shifts let you see the full demand for each site in one view. You can spot an understaffed day before auto-schedule runs, rather than after staff have been notified.

Auto-schedule in Zoho Shifts: eligibility rules, settings and the draft

Auto-schedule assigns an open shift to an employee only when every eligibility rule and every condition you select is met. Zoho's auto-schedule help article lists the base rules. The employee must be assigned to the open shift's schedule and position. The shift must not overlap their approved time off or existing assigned shifts.

Three settings shape the result:

• Low labor cost: assigns shifts to employees with lower hourly rates first. This setting is only as good as the hourly rates you hold for each person.
• Do not schedule employees when unavailable: on by default. If you untick it, staff may be scheduled in time slots they have marked as unavailable.
• Maximum repeated days: a schedule constraint for the most days in a row an employee can be scheduled.

Generating an auto-schedule typically takes a few minutes. The result is a read-only draft schedule, which you review, then apply or discard. Some shifts may stay unassigned. Zoho explains that this means no employee met the conditions, and you can assign those shifts manually.

At Svennis we run the first auto-schedule on a test week and read every unassigned shift before applying the draft. An unassigned shift often traces back to a person missing from a schedule or position, not to a real shortage of staff.

Publishing the rota and choosing who is notified

Publishing makes the rota visible: until then, employees cannot view or act on their shifts. Publishing needs Administrator access or the Publish schedule permission. It works only for schedules you are assigned to. You can publish a single shift or a whole schedule.

On the web, publishing applies to the shifts visible in your current day, week, bi-week or month view. Set the calendar to the week you mean before you publish. A month view will publish more than one week's rota. When you publish several shifts, Zoho offers three notification options:

• Notify employees with changes: only staff whose shifts were created, updated or changed since the last publish.
• Notify all employees: everyone on the published shifts.
• Don't notify, just mark as published: publishes without sending notifications.

Use Notify all employees for a new weekly rota. Use Notify employees with changes for mid-week corrections, so unaffected staff are not disturbed. Publishing a single shift notifies the employees associated with or eligible for it.

Unpublishing hides a shift from the employee's view. Once unpublished, staff cannot view or take the shift until it is published again. On the web, unpublish several shifts from the Schedule Editor through Tools > Unpublish Shifts. The mobile app unpublishes individual shifts only. The steps are in Zoho's guide to publishing shifts.

Filling a gap when someone cannot work

When someone cannot work, create an open shift for the hours that need cover and publish it. Eligible employees are notified and can pick it up from the web or the mobile app. Eligible means assigned to the same schedule and position, with no overlapping shift on any schedule.

How the pick-up is decided depends on settings that an administrator controls. Zoho's open shifts help article describes two:

• Manager approval: when enabled, open shift requests are assigned only after a manager approves them. When disabled, the shift goes to whoever picks it first.
• Restrict pickups when employees' schedule constraints are exceeded: adds constraint checks on top of schedule and position. This stops a pick-up that would break a limit you have set.

The choice is speed against control. First come, first served fills a gap quickly, which helps when cover is needed the same day. Manager approval lets a site manager weigh experience, cost or fairness before confirming. For several sites, many teams combine approval with the constraint restriction. Shared staff then cannot take a shift that breaks their limits just because they saw the notification first.

If nobody picks up the shift, it stays open. The manager can then assign it by hand.

Worked example: a weekly rota for two sites

This example follows a fictional bakery with shops in Leeds and York. It uses the settings named in Zoho's help pages. Some counter staff work at both sites.

1. Structure. Create two schedules, Leeds and York, each with the positions Counter and Baker. Assign shared counter staff to both schedules. Assign each site manager only to their own schedule, with Add, edit shifts and Publish schedule.
2. Demand. The Leeds manager creates next week's open shifts. One is a Saturday morning Counter shift with the employees needed set to two. All shifts are saved as drafts.
3. Auto-schedule. The manager runs auto-schedule with Low labor cost selected. The unavailability option stays ticked and maximum repeated days is set to company policy.
4. Review. The read-only draft leaves one Baker shift unassigned. The manager finds that a new baker was never given the Baker position. They correct it and assign the shift manually, then apply the draft.
5. Publish. With the calendar on week view, the manager publishes the Leeds schedule and chooses Notify all employees.
6. Gap. On Tuesday a counter assistant calls in sick for Thursday. The manager creates and publishes an open Counter shift. A shared employee who works in York sees it. Manager approval is on, so the Leeds manager approves the request before it is assigned.

The York schedule is untouched throughout, and nobody at York is disturbed. The shared employee was offered the shift only because they had no clashing York shift on Thursday.

Setup decisions for multi-site rotas, in one table

Most of the Zoho Shifts setup comes down to a handful of decisions. Make each one deliberately before your first live week. The table sets out each decision, the options Zoho offers and when each option fits.

Decision	Options	When each fits
Schedule structure	One schedule per site, or one shared schedule	Per site when managers should publish only their own site; shared when one person runs every rota
Open shift pick-up	Manager approval on, or first to pick	Approval for control over who works; first to pick for fast same-day cover
Constraint check on pick-ups	Restrict pickups on, or off	On when staff work across sites and limits matter
Auto-schedule priority	Low labor cost, or not selected	Low labor cost only when hourly rates are accurate for everyone
Respect unavailability	Ticked by default, or unticked	Keep ticked; untick only for an emergency week
Maximum repeated days	A number you set	Set from your contracts and policy
Notification on publish	Changes only, all employees, or none	All for a new week; changes only for corrections
Hide end time	On or off per open shift	On for shifts that end when the work ends

Write your choices down and share them with every site manager. Rotas drift when each site quietly uses different settings for the same kind of shift.

What this means for UK employers using Zoho Shifts

This post states no working time limits, because those rules belong in GOV.UK guidance and your employment contracts, not in a product guide. Check the current rules on GOV.UK and with your HR adviser. Then put your policy into the settings Zoho Shifts provides.

Three settings carry most of that policy. The maximum repeated days constraint caps how many days in a row auto-schedule will place one person. The option Restrict pickups when employees' schedule constraints are exceeded applies your constraints to open shift pick-ups as well. Keeping the unavailability option ticked means auto-schedule respects the slots staff have marked as unavailable.

Two practical points matter for UK teams with hourly staff. First, the Low labor cost priority sorts staff by hourly rate. Rates must be updated whenever pay changes, or auto-schedule will favour the wrong people. Second, Hide end time shows staff only the start time. Decide how you will tell staff when they can expect to finish, so open-ended shifts do not cause disputes.

Finally, treat the published rota as the record your staff rely on. Use Notify employees with changes for every correction after publishing. Everyone affected then hears about the change through the same channel as the original rota.

Next steps for your first Zoho Shifts rota

Start small, with one site and one test week, before rolling Zoho Shifts out to every location. Work through these steps in order:

1. List your sites, roles and staff, using the same names as the rest of your Zoho apps.
2. Create one schedule per site and the positions for each role. Assign every employee to all the schedules and positions they can cover.
3. Assign each manager to their own schedule with only the permissions in the table above.
4. Build a test week as draft open shifts, run auto-schedule and read every unassigned shift.
5. Have an administrator decide the pick-up settings: manager approval and the constraint restriction.
6. Publish the first live week with Notify all employees, then use changes-only notifications after that.

If you are still deciding which Zoho apps your business needs, start with the Zoho One suite overview. It covers what the suite includes before you add rotas to it. If you would rather have help with the setup, our guide to what a Zoho partner does explains what to expect from one.

Sources

• Zoho Shifts help: Open shifts
• Zoho Shifts help: Publishing shifts
• Zoho Shifts help: Auto-schedule shifts
• Zoho community: Shift management