A restaurant duty roster is built section by section, not person by person. You fill the tandoor before you fill the floor, because a missing chef de partie closes a section while a missing server only slows one.
The format itself is simple: names down the left, days across the top, and a shift code in every cell.
What makes it hard is everything that format has to respect at once. A weekly off for each person, a cap on daily hours, a lunch and dinner split, and enough cover on a Saturday to survive both.
This guide gives you the format, the six steps to fill it, and the checks to run before you put it on the noticeboard.
Key Takeaways
- Roster by section first: an empty station closes a menu
- Names down the left, days across, one code per cell
- Assign weekly offs before shifts, or the roster will not hold
- Hour caps and overtime rates are set state by state, so check yours
- Publish a week ahead so swaps happen before the shift
What Goes Into a Restaurant Duty Roster?
A duty roster is the written plan of who works when. For a restaurant, five things belong in it.
- Names, grouped by section. Kitchen sections and floor sections, not one alphabetical list.
- Days across a week. A fortnight if your rota alternates.
- A shift code per cell. Morning, evening, double, weekly off.
- The role being covered, where one person can work more than one.
- A published date, so everyone knows which version is current.
What does not belong is anything that changes daily. Leave the reservation count and the guest notes to the shift briefing.
What Does a Restaurant Duty Roster Format Look Like?
This is a working week for a small outlet in Indiranagar (an example) with two kitchen sections and a four-person floor, covering 14 to 20 September 2026.
| Staff | Section | Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|---|---|
| Ramesh | Tandoor | M | M | OFF | M | M | D | D |
| Suresh | Tandoor | E | E | E | OFF | E | D | D |
| Anil | Curries | M | OFF | M | M | M | D | D |
| Kavita | Commis | E | E | E | E | OFF | E | E |
| Priya | Captain | M | M | M | OFF | E | D | D |
| Farhan | Server | E | E | OFF | E | E | D | D |
| Neha | Server | M | OFF | M | M | M | D | D |
| Imran | Busser | E | E | E | E | OFF | E | E |
M = morning, 11am to 4pm (5 hours). E = evening, 6pm to 11pm (5 hours). D = double, 11am to 3pm and 7pm to 11pm, so 8 hours with a four-hour gap. OFF = weekly off.
Those timings are set to stay inside the caps below: no stretch runs past five hours without a break, and no day exceeds nine hours. The busiest person here works 36 hours in the week.
Four things to read from it.
Tandoor never loses both people at once, because Ramesh and Suresh take different days off. That is the pairing every two-person section needs.
Curries has one person. Anil works mornings, so Tuesday has no curries cover at all, and no weekday evening has any either. A one-person section is the first thing to fix as you grow.
Every name has exactly one OFF, which is the check most rosters fail.
Saturday and Sunday run doubles for the six who cover both services. Kavita and Imran stay on evenings, because a commis and a busser earn their keep at dinner rather than at lunch.
The sample leaves out two things your own version needs: a role column where one person covers more than one job, and the date it was published. Both are in the template below.
A QSR in Whitefield would use the same grid with a flatter shape. Counter service has no captain row and fewer kitchen sections, and it runs straight through rather than splitting lunch and dinner. The five-hour break rule still applies, so the shifts get longer on paper but still break in the middle.
Copy the shape rather than a generic template. Our staff shift schedule template is the same layout in Excel, with the weekly hour total calculating itself.
How Do You Build a Duty Roster in 6 Steps?
The six steps below run in a fixed order. Doing them out of order is what produces a roster with three servers on a Tuesday and nobody on the grill on Friday.
- List the sections, not the people. Tandoor, curries, cold kitchen, bar, floor, host. Every section that must be covered for the menu to be servable is a row that cannot be empty.
- Mark the peak services first. Friday and Saturday dinner for most outlets, plus Sunday lunch if you do brunch. Check that against your POS sales reports rather than assuming, because the hours that actually fill are not always the ones you expect. A festival week in October 2026 will not look like an ordinary one either. Fill those before anything else, because being one person short at full seat covers is where it costs money.
- Assign weekly offs before shifts. Spread them across the week and never let two people from the same section share one. This is the constraint that breaks a roster if you leave it to last.
- Fill the quiet shifts with your thinner cover. A Tuesday lunch can run on a smaller team. That is where a commis learns a section without a full house and a queue of KOTs behind it.
- Check the hours. Add each person’s week. Daily and weekly caps are set by state law, so confirm yours against the labour codes rather than assuming a common figure.
- Publish a week ahead. People swap shifts either way. Published early, they swap with each other before the week starts. Published late, they call in on the day.
While talking to restaurant owners using Petpooja, step 3 is the one we hear is skipped most. A missing weekly off shows up as a tired section on a busy night, with KOTs backing up at the pass, before anyone spots it on the roster.
That is conversation rather than data, but it is consistent enough to be worth passing on. Offs get filled in around the shifts instead of before them, and the roster ends up legal on paper but impossible for one person to actually work.
What Rules Shape a Restaurant Roster in India?
Restaurants come under their state’s Shops and Establishments Act, not the Factories Act. Each state writes its own, so check yours. Delhi’s shows the shape they take.
Under the Delhi Shops and Establishments Act, 1954:
- Nine hours a day, 48 hours a week is the cap for an adult employee under Section 8.
- No more than five hours in a row without a 30-minute break, under Section 10. So a real double shift has a proper gap in the middle. It is not eleven hours straight.
- One paid day off a week. A restaurant that opens on its close day must give that day off within three days either side.
- Overtime at twice the normal hourly rate.
The weekly off is the one that catches restaurants, because most open seven days. The day off does not disappear. It moves, and it has to land inside a three-day window.
A roster that quietly runs someone six days of doubles is not a scheduling decision. It is a payroll liability you have already incurred.
What Happens If the Roster Breaks Those Rules?
Four things follow a breach, and the fine is the least of them. Section 40 of the Delhi Act linked above sets a penalty of not less than ₹25 and up to ₹250 for a contravention. Those figures have not been revised since 1954.
The wage bill is the bigger number. Under the Delhi Act overtime is payable at twice the ordinary rate. A roster that runs someone past the cap accrues that cost whether or not an inspector ever sees it.
Records carry a separate line. Under the same Act, failing to keep the registers and notices it requires is its own offence, charged for each day it continues.
Making a false entry in those records is treated more seriously again. Under Section 41 it can bring imprisonment of up to three months, a fine, or both.
Other states set their own numbers. Treat the Delhi figures as the shape of the thing rather than the amount you would actually pay.
Roster or Attendance Register: What Is the Difference?
This section covers where the two documents part company. The roster is the plan, and the attendance register is what actually happened.
Priya is on the morning shift on Wednesday because the roster says so. Whether she punched in at 11am is a separate record entirely, and the gap between those two documents is where payroll disputes start.
Keeping them apart matters at month end. You pay against attendance, not against the roster, and you investigate the difference. Our comparison of shift management and attendance tracking covers where the two systems meet.
What to Check Before You Publish the Roster
Six checks, listed below, take about five minutes and catch most of what goes wrong.
| Check | What you are looking for |
|---|---|
| Section cover | Every station covered, or a named person crossing over |
| Weekly offs | Exactly one per person, none clashing within a section |
| Hour totals | Every person inside the daily and weekly cap |
| Peak cover | Your busiest two services fully staffed first |
| Skill mix | At least one experienced hand on every shift |
| Publish date | Version marked, out at least a week ahead |
Two of those six are legal rather than operational: the weekly offs and the hour totals. Check them first, because they are the hardest to put right once the week has been worked.
A short-staffed Saturday costs you a bad service. A missed weekly off has to be substituted inside the window the Act allows, and past that it is a breach.
Run the skill-mix check properly as well. A shift can be fully staffed on paper and still fall over if everyone on it joined last month.
Where the Roster Meets the Rest of Your Setup
A roster only works if it reflects the staff structure you actually run, from the front of house roles through to the kitchen sections. You can only schedule roles you have defined, which is why rostering gets easier once the reporting lines are settled.
It also feeds two other things. Attendance is measured against it, and labour cost is calculated from it.
Priced out with the staff cost calculator, a week of doubles looks very different from a week of singles. It lands in your food cost ratio alongside the wage bill.
Set that against the sales the week actually brought in, which your restaurant POS already holds, and you can see whether the cover paid for itself. Worth knowing before you publish the roster, not at month end.
A spreadsheet holds up while one person can keep the whole team in their head. Once shifts start overlapping across outlets, Attendo handles multiple shift creation, overnight timings and alternate week-off assignment, and the hours total themselves instead of being added by hand.
Conclusion
Sections first, peaks next, offs before shifts. That order is most of what separates a roster that holds from one that gets rewritten on Thursday.
The format is the easy half. The discipline is checking the hours and the weekly offs before it goes up, because both are legal obligations rather than preferences.
Build the first one in a spreadsheet using the template linked above. Move it into Attendo when the manual version starts taking a full morning every week.
Frequently Asked Questions
It is the written plan of who works which shift over a week or fortnight, organised by section rather than alphabetically. It records names, days, shift timings and weekly offs. It is a plan, not a record of attendance.
At least a week. Published early, staff arrange swaps between themselves before the week begins. Published late, you find out about a clash on the morning of the shift, which is when it costs you cover.
Occasionally, as a double shift, but not as a routine. Daily hour caps apply and vary by state, and hours beyond the limit usually attract overtime at twice the ordinary rate. Two shifts across a full week is close to double the headcount, not a longer day.
In practice they describe the same document. Roster is the more common term where staff are grouped by section or station, as in a kitchen. Both are the plan, and both sit apart from the attendance register.
Yes. A weekly off is a statutory entitlement, not a scheduling courtesy, and the roster is where it is evidenced. Never schedule two people from the same section off on the same day, or the station has no cover.
