Restaurant Staff Attendance Sheet Template Bangladesh: Shift to Payroll
A bilingual, exception-based attendance template that connects restaurant shifts to approved payroll inputs without inventing labour-law calculations.
Last verified: 2026-08-30
A restaurant attendance sheet should show what shift was planned, when the worker actually started and ended, what rest or meal interval occurred, why any exception arose, and who approved the record before payroll. It should not let one late handwritten total silently become a salary deduction or overtime payment.
Bangladesh's Labour Act and Rules create employer record and working-time obligations that must be assessed for the actual establishment and worker. The Act's English text available through ILO NATLEX includes a register-of-workers requirement with work periods, rest and meal intervals and rest days among the listed particulars. Use the template as an operating record, then have HR or a qualified labour professional approve the legal and payroll mapping.
Copyable daily restaurant attendance sheet
Use employee ID as well as name because staff can share similar names or change displayed spelling. Record branch and role because a worker may temporarily support another outlet or station. Never pre-fill actual in/out time from the roster; schedule and actual record serve different purposes.
The status list should be controlled: present, approved leave type, weekly rest, holiday, training, branch transfer, absent pending review or another clearly defined state. Free-text notes can explain an exception, but payroll must use approved status codes.
| Employee ID/name | Role | Branch | Scheduled shift | In | Break out/in | Out | Status | Employee/manager |
|---|---|---|---|---|---|---|---|---|
| ____ | Cook/server/cashier | ____ | ____–____ | ____ | ____ / ____ | ____ | Present/leave/other | ____ / ____ |
| ____ | ____ | ____ | ____–____ | ____ | ____ / ____ | ____ | ____ | ____ / ____ |
| ____ | ____ | ____ | ____–____ | ____ | ____ / ____ | ____ | ____ | ____ / ____ |
Monthly attendance and payroll handoff
The monthly summary should be generated from signed daily or system events, not from memory. Keep a link to every correction. Do not convert late marks, absence or extra time into taka on the attendance sheet; send approved quantities and status to the payroll calculation controlled by HR or finance.
Payroll cut-off and attendance cut-off must match. Shifts crossing midnight need one consistent business rule so hours are not duplicated or lost between two days. Record unsettled attendance disputes as pending and correct payroll under the lawful process rather than hiding a missing approval.
| Employee | Scheduled days | Present records | Approved leave | Rest/holiday | Late/early exceptions | Extra-time review | Payroll status |
|---|---|---|---|---|---|---|---|
| ____ | ____ | ____ | ____ | ____ | ____ | Pending/approved | ____ |
| ____ | ____ | ____ | ____ | ____ | ____ | Pending/approved | ____ |
Scheduled shift versus actual attendance
The roster shows management's plan; attendance shows what occurred. Store both. If a manager asks a worker to arrive early, stay late, cover another branch or skip a scheduled day, the approved change must update the record. Otherwise the worker can appear non-compliant with a schedule that management itself changed.
Capture planned start/end, actual in/out and shift-change approval. Use reason codes such as approved swap, emergency cover, event extension, transport disruption or manager correction. The reason does not automatically determine whether time is payable or overtime; HR applies the lawful rule.
Rest, meal and split-shift records
Record the interval as actual start and end where the restaurant's system and lawful policy require it. A scheduled break is not proof that staff were relieved from work. If service demand interrupted the interval, use an exception route rather than entering the plan as fact.
Split shifts need two work blocks or a clear unpaid interval approved under the applicable rules. Avoid one long presence total that treats every hour on the premises the same. Security, staff meals, travel between branches and on-call periods also need an approved treatment.
Sources for this section: ILO NATLEX: Bangladesh Labour Act English text
Late, early, absent and missed-punch workflow
Never let a supervisor edit time without a visible trail. Preserve original event, requested value, reason, evidence, requester, approver and change time. The employee should be able to see the corrected record and raise a dispute through the restaurant's process.
Repeated missed punches can indicate device placement, network failure, staff training or deliberate misuse. Fix the source rather than treating every event as the same disciplinary problem.
| Exception | Employee submits | Manager verifies | HR/payroll action |
|---|---|---|---|
| Late arrival | Actual time/reason | Time and operational fact | Apply approved lawful rule |
| Early departure | Request/reason | Approval and time | Update payable status |
| Absence | Leave or explanation | Roster/contact evidence | Classify after review |
| Missed punch | Correction request | Witness/system evidence | Approved correction |
| Device outage | Manual time record | Outage and supervisor sign | Bulk reconciliation |
Overtime and extra-time review—not automatic calculation
Calculate raw recorded presence only as a factual duration, then separate scheduled work, approved extra work, rest interval, leave, holiday or other status. Current Bangladesh law, worker category, establishment coverage, agreement and lawful policy determine normal hours, overtime and payment. Do not publish one formula as universal restaurant law.
Require pre-approval where operationally possible, but do not erase time actually worked because approval was missing. Record the event, manager instruction and HR decision. If a dispute exists, preserve the source data and obtain qualified legal or labour advice.
Sources for this section: DIFE: Bangladesh Labour Act 2006 · DIFE: Bangladesh Labour Rules and amendments
Manager approval and separation of duties
Shift supervisors may confirm operational facts, but HR or another authorized role should approve material payroll-impacting corrections under the restaurant's control design. A manager should not create a roster, edit every punch, approve the edit and finalize payroll without any review.
Publish the cut-off, correction deadline and escalation route. Late corrections should create an adjustment trail, not overwrite a closed period. Require reason and supporting evidence proportionate to the issue without collecting unnecessary personal or medical information in an open sheet.
Privacy, access and retention
Attendance data can reveal employee identity, location, work pattern, leave and sometimes health-related information. Limit access by role, protect exports, avoid public messaging groups and remove inactive manager access. Biometric attendance requires additional privacy, security and lawful-use assessment.
The restaurant should adopt a retention schedule based on current legal, tax, payroll and dispute requirements after professional review. Do not invent a universal number of years. Keep the official source and policy version that supports the schedule.
Paper, spreadsheet or attendance system
Move beyond paper when payroll repeatedly waits for sheets, branch data arrives in different formats, missed punches are untraceable or managers recalculate the same hours. Digitization does not fix bad rules: status, cut-off, break, branch transfer and approval must be configured first.
During migration, run a controlled parallel check, sample shifts crossing midnight, approved leave, device outage, branch transfer and correction. Employees and managers need a visible dispute and correction process before the system affects payroll.
| Method | Works when | Main risk | Minimum control |
|---|---|---|---|
| Paper | Small stable team | Loss, pre-fill, unreadable edits | Numbered sheets and signatures |
| Spreadsheet | Controlled branches/users | Version and formula changes | Protected master and change log |
| Attendance system | Multiple shifts/branches | Wrong setup or access | Roster rules, audit trail and review |
| Biometric | Identity assurance is necessary and lawful | Sensitive-data risk | Privacy/security assessment |
Attendance audit checklist
Review a sample from roster to punch, correction, monthly summary and payroll result. Then sample backward from payroll to the source events. Check leavers, new joiners, branch transfers and managers because access errors often remain around employment changes.
Treat patterns as control questions: one device with many missed punches, one manager with many manual edits, or one branch with repeated late closing may indicate process or staffing issues. Investigate fairly and document the resolution.
- Every active worker has a unique ID and correct branch
- Roster and actual events are separate
- No shared attendance credential
- Missed-punch edits retain the original
- Leave and rest status use approved codes
- Cross-midnight shifts follow one rule
- Payroll-impacting changes have approval
- Closed-period changes create an adjustment
- Employee dispute route is visible
- Access and exported files are reviewed
How we calculated and verified this
The template separates planned shift, actual presence, rest or meal interval, approved leave, attendance exception and payroll approval. It does not calculate legal overtime or wages. Total recorded presence is clock-out minus clock-in, while payable work, overtime and deductions follow the employer's lawful policy, current Bangladesh law and professional advice.
DIFE pages are the current official law and rules index; the ILO NATLEX English text is linked for accessible context, including the Act's register-of-workers provisions. No universal shift length, break, overtime threshold, salary deduction or retention period is invented.
A strong restaurant attendance sheet preserves planned and actual time, makes corrections visible, separates raw attendance from legal payroll calculation and gives employees a clear review route. It should help payroll become accurate without turning a supervisor's unchecked edit into a wage decision.
Customize this template only after checking the current Bangladesh Labour Act, Rules, establishment coverage, worker terms and professional advice. This article is an operating-control guide, not a calculation of wages, overtime or lawful deductions.
Related guides
- Restaurant Attendance System Guide
- Attendance to Payroll Automation
- Restaurant Labour Law and Staff Rules
- Restaurant Staff Salary Structure
See this workflow in Rosuii: Manage restaurant attendance, shifts and payroll inputs in Rosuii
Sources checked
Frequently asked questions
What should a restaurant attendance sheet include?
Can attendance automatically calculate restaurant salary?
How should a missed punch be corrected?
Should a scheduled break be deducted automatically?
Is biometric attendance required for restaurants in Bangladesh?
Run your restaurant on Rosuii
POS, menu, inventory, payroll and more — built for Bangladeshi restaurants.
Start free
