Shift Swap Policy Template for Small Restaurants

At 3:10 p.m. on Friday, one server posts in the team chat: "Jordan is taking my close tonight." Jordan replies with a thumbs-up. The floor looks covered, but the message does not answer four manager questions: Can Jordan close that section? Who approves the trade? What happens to Jordan's weekly hours? Has the posted schedule changed?

A restaurant shift swap policy turns that message into a request, a review, and one approved record. Employees get a fair way to trade shifts, while managers protect skill coverage, hours, access, and payroll handoff.

This template is operational guidance, not legal advice. Check current employment standards, union agreements, contracts, and internal HR requirements before relying on any policy language.

Route the request before applying the swap policy

The word swap is often used for five different events. Classify the request first. A recurring school or second-job conflict belongs in the availability record. A one-time planned absence belongs in the restaurant's time-off process. An illness reported before the shift belongs in the call-out workflow. An employee missing after the shift begins belongs in the no-show evidence workflow.

Use the shift-swap policy when one employee proposes another current employee for one specific published shift and both can participate in the approval. This boundary matters because a manager should not force an emergency or protected issue through a routine trading deadline, and should not turn a recurring availability conflict into a new swap every week.

The request can be concise: original employee, proposed replacement, date, start, end, role, station, opening or closing responsibility, time submitted, and each employee's acknowledgement. Private reasons are not necessary in the shared schedule record.

Copy the policy, then set the local decisions

Choose the request deadline, approval roles, emergency channel, and contact method before publishing the policy. A 24-hour deadline may work for routine swaps, while an illness two hours before service belongs in the call-out process. Do not force both situations through the same rule.

State how employees know a request was approved. A manager reaction emoji is ambiguous. Use a clear status such as approved and schedule updated, then notify both employees.

Use an approve, decline, or escalate decision tree

An escalation is not a rejection. It means the shift cannot be decided safely from the schedule alone. For example, a manager may need payroll to review a holiday week or HR to handle an accommodation-related change.

Two swaps that look alike but need different answers

The difference is visible only when the request includes the full shift and the manager can see the replacement's week. "Jordan can take it" is not enough data for either decision.

Keep a swap log that payroll can reconstruct

The approved schedule should show the replacement, but keep the change record as well. At minimum, record the original employee, replacement, shift, request time, approval time, approving manager, reason if declined, and whether an hour or payroll review flag was added.

Do not collect sensitive personal explanations in a public team channel. The schedule needs the operating fact, such as unavailable or manager review required. Accommodation, health, family, or disciplinary details belong in the restricted process your business uses for that information.

At payroll cutoff, compare approved swaps with the worked week. A swap may have been approved correctly and still differ from actual hours because someone arrived late, stayed through cleanup, or was sent home early. Preserve the schedule change and the actual-hour correction as separate facts.

Test the policy against three failure modes

Before giving the policy to employees, run three tabletop tests. First, a same-role swap submitted three days early. Second, a closing shift offered to an employee without close training. Third, a last-minute illness when no full-shift replacement is available.

For each test, ask who receives the request, what information they see, how they decide, how the employee receives the answer, and where the final change is recorded. If two managers can reach different statuses from the same facts, clarify the policy.

Also define the fallback. A late call-out may require a shorter rush cover, a manager to move stations, a reduced section plan, or a documented no-show process. The shift swap policy should point to that process instead of pretending every absence can be traded.

Attach the approved trade to the week it changed

Maxuod Shift gives the manager a weekly record where employees, roles, shifts, hour totals, and later review stay connected. The topic-specific value is not another chat channel. It is the ability to update the approved schedule and carry that change into the same review and export path.

The manager still owns approval, training judgment, private employee issues, and the correct payroll or legal review. Maxuod Shift makes the operating evidence easier to inspect; it does not approve a trade automatically or promise compliance.

Test the policy with one upcoming week in the free scheduler. Add a routine swap and a failed closing swap, then confirm another manager can explain both decisions from the record. Pair it with the call-out guide and no-show policy so the emergency path is not left blank.

FAQ