Skip to content
RosuiiRosuii

Restaurant Duty Roster Template Bangladesh: Weekly Plan

A copy-ready weekly structure that plans people by station and demand rather than repeating the same shift every day.

By 5 min read
Share
Restaurant Duty Roster Template Bangladesh: Weekly Plan

Last verified: 2026-08-28

A restaurant duty roster should show who works, when they work, where they are assigned, who opens or closes, their break and weekly rest, and who covers a handover. It is a staffing control, not only a list of names.

Build the roster from forecast demand and the current legal limits that apply. DIFE's laws index includes a 2026 labour amendment, so confirm hours, rest and overtime rules before adopting an old template unchanged.

Weekly roster columns

ColumnExample entryPurpose
Employee and roleRahim, waiterIdentifies skill
Day/dateSaturdayPlanning period
Start/endApproved shiftExpected attendance
StationFloor A or cashierCoverage
BreakPlanned windowRest coverage
Open/close dutyNamed task ownerAccountability
Weekly restMarked dayCompliance and recovery
Approver/versionManager and timeChange control

Plan by demand and station

Forecast covers, delivery orders and kitchen volume by hour. Schedule the required skills: cashier, floor server, runner, grill, fryer, prep, packing and shift lead. One extra untrained person does not replace a missing station skill.

Show a short overlap between shifts for cash, stock, pending orders, reservations and equipment handover.

Opening and closing duties

Assign named owners for opening cash, table and device checks, prep verification and online-menu availability. At close, assign cash reconciliation, stock protection, waste, cleaning, equipment shutdown and security.

Do not place every closing task under manager. The roster should distribute work while keeping one accountable reviewer.

Change-control rules

  • Publish at a consistent weekly time
  • Require manager approval for swaps
  • Record the replacement and reason
  • Notify affected stations
  • Preserve the prior version
  • Update attendance, not only the roster
  • Escalate uncovered critical roles

Roster versus attendance

The roster is the authorized plan; attendance records what happened. Payroll must distinguish absence, approved leave, late arrival, early departure, extra work and manager-approved overtime.

Never overwrite the roster after the week to make it match attendance. Keep version history and an exception record.

Four roster checks before publishing

Confirm lawful hours and rest, skill coverage, break coverage and opening or closing accountability. Then ask whether the same person has an unsafe closing-to-opening turnaround or too many consecutive peak shifts.

Share the roster in a format staff can access and provide a clear route for correction. A roster that nobody confirms is not a control.

Build the roster from coverage requirements

Start with service periods, stations and responsibilities—not the previous week's names. Estimate coverage from reservations, order history, event calendar, delivery demand and known constraints, then assign people who are trained and available. Mark opening, peak, handover and closing coverage explicitly.

A roster is a forward plan, not proof of attendance or payable time. Keep scheduled, actual, approved correction, leave and overtime records distinct so payroll does not silently treat a plan as a worked shift.

Recommended roster fields

Add skill or certification requirements only where the operation has a legitimate need. Avoid putting sensitive employee notes in a widely shared roster. Use access controls and a separate HR process for medical, disciplinary or payroll information.

FieldPurposeValidation
Employee and roleIdentify assigned capabilityActive and trained
Branch/stationPlace the workAuthorized location
Start/endDefine scheduled windowValid time sequence
Break planProtect coverage and policyNo uncovered station
DutyOpening, service, close or handoverClear owner
StatusDraft, published, changedPublication history
Change reasonExplain post-publication editApprover and time
Employee acknowledgmentShow receipt, not consent to illegalityTimestamp/channel

Shift-change and absence workflow

Define who may request, approve and finalize a swap. The replacement must be available, qualified for the station and within the restaurant's approved scheduling policy. A peer agreement in a chat should remain pending until the authorized roster owner confirms it and updates the published version.

For an absence, record notification time and coverage action without exposing unnecessary personal detail. Escalate an uncovered critical duty, and preserve the original schedule plus the approved change so later attendance and payroll review has context.

Pre-publication roster checks

Use local legal and organizational review for working time, rest, leave and overtime policy. This operational template does not set universal lawful hours or pay rules.

  • Every opening and closing duty has one owner
  • Peak stations have the planned skill coverage
  • No employee is double-booked across branches
  • Availability and approved leave are respected
  • Breaks do not remove all coverage from a station
  • Handover overlap is visible where needed
  • Changes since the prior version are highlighted
  • The publication channel reaches every employee
  • A correction and escalation route is stated

Weekly roster variance review

Compare scheduled coverage with actual attendance, approved swaps, late changes and station-level service issues. A variance is a question: demand may have changed, the plan may have been unrealistic, or an individual event may need follow-up. Do not turn attendance data into blame without checking corrections and context.

Track repeated uncovered stations, emergency edits and overtime approvals by cause. Improve the demand input, cross-training, publication lead time or change workflow, then measure whether the next roster reduced the specific failure.

Roster publication and acknowledgment

Publish one identifiable roster version through the agreed channel, with branch, week, issue time and contact for corrections. An employee acknowledgment shows that the schedule was received; it should not be used to waive rights or approve an inaccurate attendance record. Provide an accessible alternative for staff who cannot use the primary app or channel.

When a change is approved, notify affected staff and station owners, highlight the difference and supersede the prior version without deleting it. At shift start, the manager should see the current roster and unresolved gaps, while payroll later uses reviewed attendance rather than notification receipts. Record failed notification delivery and follow the backup contact process.

A good weekly roster protects service, staff recovery and payroll evidence at the same time. Plan by hour and station, then preserve every approved change.

Related guides

See this workflow in Rosuii: Plan staff shifts and attendance in Rosuii

Sources checked

Start using Rosuii for free

Updated:

Frequently asked questions

What should a restaurant duty roster include?
Employee, role, date, start and end, station, break, opening or closing duty, weekly rest and approval/version.
How far ahead should it be published?
Use a consistent weekly deadline early enough for staff to review and request lawful changes before the shift.
Can staff swap shifts?
Yes under a written process with manager approval, skill coverage and a recorded replacement.
Is the roster used directly for payroll?
No. It is the plan; verified attendance and approved exceptions determine payroll.
Does Rosuii support shifts?
Rosuii can support shift and attendance records; the restaurant must design a lawful roster and approve changes.
Is a duty roster the same as attendance?
No. The roster is planned work; attendance and approved corrections record what occurred, and payroll applies reviewed policy.
What fields belong in a restaurant roster?
Include employee, role, branch/station, start/end, break plan, duty, status, change reason and approval or acknowledgment evidence.
How should shift swaps be handled?
Require a qualified available replacement and authorized approval, then update the published roster while preserving the original and reason.

Run your restaurant on Rosuii

POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.

Start free