Restaurant Check-in and Check-out Policy Template

Last verified: 2026-08-28

Software records time; policy explains what the time means. A clear check-in policy prevents arguments and gives managers a consistent way to handle exceptions.

Define the official shift clock

State how early staff may check in, when a late mark begins and whether changing uniform happens before or after paid time starts.

Document common exceptions

Explain what to do for a missed tap, device problem, emergency leave or approved overtime. Require same-day reporting where practical.

• Employee reports the exception
• Manager verifies the shift
• Correction reason is recorded

Apply rules consistently

The same rule should apply across roles and branches unless a written operational reason says otherwise. Review repeated lateness privately, not on the floor.

Policy purpose and scope

State that the policy creates an accurate record of work time, attendance exceptions and approved corrections for scheduling and payroll review. List the employees, branches and work arrangements it covers. Identify any role or situation that follows a different authorised process, such as approved off-site delivery support or temporary work at another branch.

Make clear that a check-in record is evidence, not the whole employment decision. Leave, overtime eligibility, lateness treatment, deductions and disciplinary action require the restaurant's current written rules and applicable law. This template is an operational starting point, not legal advice for an individual worker.

Clauses to include

Write the clause in plain language and connect it to the real screen or form. A policy that says 'inform management' is incomplete unless staff know which manager, channel and deadline. Avoid promising automatic calculations the configured system and lawful rules do not support.

Individual account and no proxy attendance

Each employee should use the assigned account or approved identity method. Staff must not check in for another person, share a password or leave a session open for the next shift. Managers should not solve access problems by posting a shared credential; they should use the documented recovery or temporary-access process.

The policy should also protect staff from false attribution. If a device or account is compromised, the employee needs a prompt reporting route and the manager should review the events. A technical identifier is useful evidence, but suspected misuse requires investigation rather than an automatic conclusion.

Timing, preparation and closing work

Define whether staff check in before changing, setup or briefing and when check-out occurs after cleaning, cash close or handover. The rule must match the work the restaurant requires. Do not instruct staff to check out and then continue required closing tasks. Schedule and approval should reflect the full operating routine.

Explain early arrival, late arrival, early departure and work beyond schedule without turning every timestamp into an automatic pay outcome. Managers should review the shift, approved changes and current policy. If overtime needs prior approval, include what an employee should do when urgent guest, safety or closing work continues.

Break and split-shift rules

Describe which breaks need a time event, who can approve a missed or interrupted break and how split shifts are represented. A system should not deduct a standard break when the restaurant knows the employee could not take it. Conversely, an unrecorded break should follow correction rather than an invented time.

For two work blocks in one day, preserve each block or an equivalent transparent record so overlaps and total time can be reviewed. A shift crossing midnight needs a consistent business-date rule. Give examples based on the restaurant's actual schedule and current lawful policy.

Missed event and correction form

Set a correction deadline before payroll close and allow an exceptional route for a genuine late discovery. Preserve the original event and decision. Employees should know the result and how to raise a factual disagreement without changing the source record themselves.

Device or internet outage procedure

Name the fallback before an outage: a numbered paper log, approved manager form or another controlled device. Record employee, time, branch, reason and supervising manager. When service returns, enter the event as an outage correction with its reference rather than pretending it was a normal employee tap.

Managers should report repeated failures and keep staff from attempting endless duplicate check-ins. The system owner reviews whether the issue was account access, device clock, browser permission, network, server or training, then documents the fix.

Period review, payroll and employee query

Before payroll, managers review missing checkouts, overlaps, leave conflicts, exceptional shifts, approved overtime and corrections. The reviewed period is locked or otherwise protected from silent change. Payroll receives both totals and enough detail to trace an adjustment to the attendance source.

Give employees a practical way to view or request their records and a deadline for correction. A manager who made the original correction should not be the only route for a dispute where another authorised reviewer is available. Keep the final decision and any later payroll adjustment visible.

Policy rollout checklist

• Review the template with current HR or legal advice where needed
• Translate the final policy for the actual team
• Train managers on corrections and outages
• Test midnight, split shift and branch cover
• Issue individual accounts before enforcement
• Run a pilot before payroll depends on it
• Record employee acknowledgement
• Publish owner, version and effective date
• Review after system or lawful-rule changes

Share the policy during onboarding and keep it accessible. Ask employees to confirm they understand it before attendance affects payroll.

Related guides

• Attendance System Guide
• Attendance to Payroll Automation
• Staff Onboarding Checklist
• Compare Restaurant Management Software

See this workflow in Rosuii: See digital attendance

Start using Rosuii for free