Weekly offs that are not Saturday and Sunday

A weekly off is a rostered rest day on the attendance calendar. It is not leave, and it is not a public holiday. For many Indian offices it is Saturday and Sunday. For many others it is not: rotating offs, a weekday off, first-and-third Saturday, or a split weekend (Saturday off this week, Sunday off next). If the rest day lives only in a supervisor’s head, sandwich-leave, attendance, and payroll will each invent a different weekend.

This page owns how to record nonstandard rest days so every process sees the same calendar. Sandwich-leave mechanics — which days get sandwiched, and how balances move — stay on sandwich leave explained. Do not copy that engine here. Feed it honest weekly offs.

Weekly off versus leave versus holiday

Three different day types get collapsed in SME chat:

• Weekly off: rest built into the roster. No leave balance is spent. The person was not expected to punch as a working day.
• Leave: time away from a day that was a working day under the roster, using a leave type and (usually) a balance. See leave management for applications, balances, and approvals.
• Public / company holiday: a dated holiday on the holiday calendar, which may apply to a location, a unit, or everyone. Holidays are not weekly offs. How holidays, offs, and balances interact is the sibling holidays, weekly offs, and leave balances.

If someone “takes Saturday off” on a Tuesday–Saturday working week, that Saturday might already be a weekly off — in which case there is nothing to apply — or it might be a working Saturday, in which case it is leave or an attendance exception. The roster decides. The leave form cannot decide first.

Rest days belong on the person or roster before you argue about leave. A sandwich engine that assumes Sat–Sun will punish (or gift) the wrong people on a rotating-off floor.

Patterns you actually see

Weekday weekly off

Retail, clinics, hospitality, and some plants rest on a weekday because the weekend is the trade. The attendance day for that person is off on, say, Wednesday. Monday–Tuesday and Thursday–Sunday are working unless a holiday or leave says otherwise. Late-mark and missing-punch jobs must not treat Wednesday as absent.

Rotating offs

The rest day moves: this week Thursday, next week Friday, following week Thursday. Rotation only works if the next week’s off is published before the week starts, on a roster people can see. A rotation announced on Thursday afternoon for Thursday rest is not a roster; it is an after-the-fact waiver. Record the dated off on the calendar, not only a pattern name (“rotating”) with no dates.

First-and-third Saturday (and similar)

Many offices work second and fourth Saturdays, or the reverse. The rule is a calendar rule: named Saturdays are working, named Saturdays are weekly offs (sometimes called “off Saturdays” rather than full weekly offs — still rest, still not leave). Publish the year’s Saturday map, or a clear formula plus exceptions (when a fifth Saturday exists). Do not leave HR to reconstruct it from last month’s punches.

Split or staggered weekends

Two people in the same team can have different rest pairs so coverage remains. Person A: Sunday–Monday. Person B: Friday–Saturday. The team still has “a weekend,” but attendance cannot use a company-wide Sat–Sun flag. Rest is per person (or per roster group), not per company default alone.

Pattern	What must exist in the record	What breaks if it is only verbal
Fixed weekday off	Weekday (and timezone/site) on the person’s schedule	Absent marks every off day; false LOP
Rotating off	Dated rest days for the published horizon (at least the current month)	Leave overlapping “maybe off” days
Nth Saturday	Which Saturdays are working versus rest, including fifth Saturdays	Two versions of “this Saturday”
Split weekend	Per-person or per-crew rest pair	Company holiday calendar used as a fake weekend

Recordkeeping that attendance and leave can share

Attendance management should show weekly offs on the same monthly calendar as punches, leave, and holidays. If offs live in a separate Excel that payroll cannot see, you will regularise “false absents” every month and still compute sandwich leave on the wrong days.

Minimum record:

1. Who (employee identity payroll uses).
2. Which dates are weekly offs in this period (not only a pattern label).
3. When the roster was published, and who may change it after publication.
4. How mid-period changes are written (transfer to a new crew, festival coverage, compensatory swap — the swap itself is a different policy; the dated rest still must land on the calendar).

Managers swapping offs in a chat without updating the calendar create sandwich and LOP noise. If policy allows a swap, the swap is complete only when the two dates are rest/working on the attendance calendar.

Night shifts add a dating constraint: the weekly off is an attendance day under your night-shift rule, not necessarily “the civil Sunday.” Align with how you date overnight instances; do not rest a crew on Sunday civil date while their rostered night is Saturday’s instance.

What weekly off is not

• Not a leave type named “WO” that deducts a balance. If you historically coded rest as leave in a spreadsheet, stop. Rest should not reduce casual or earned leave.
• Not a public holiday. A national holiday that falls on a weekly off is a holiday-on-off interaction — owned by the holidays sibling article, not by inventing a second rest day unless policy says so.
• Not “the employee didn’t punch, so we will call it off.” That is absence or pending regularisation. Offs are planned.
• Not compensatory off. Comp-off is a grant against extra work, with its own rules. A weekly off is ordinary rostered rest.

If the floor works a weekly off, that is extra work against a rest day, not “the off never existed.” How you compensate (pay, comp-off, or a later rest date) is a separate written rule. The original date should still show as a scheduled off that was then worked, so reports stay honest.

Sandwich leave needs the real rest days — not a recap of sandwich

Sandwich policies look at leave adjacent to rest and holidays. If the rest days in the engine are the company default Saturday–Sunday, a person whose off is Wednesday will be treated wrongly on both sides: sandwiched when they should not be, or not sandwiched when the engine should have seen Wednesday. Fix the calendar feed. Do not rewrite sandwich logic in this article. The owner remains the sandwich-leave guide.

HR close week should include a short check: sample people with nonstandard offs, confirm the month’s rest dates, then let leave and sandwich run. Do not wait for a dispute after payslips.

Joiners, exits, and transfers

A joiner inherits the roster of their assignment, not a generic Sat–Sun, unless you explicitly start them on the company default. An exit should stop generating “absent on weekly off” noise after last working day — offs after exit are not events. A transfer from a five-day office to a rotating-off plant must change dated rest from the effective date, not from the date someone remembered to update Excel.

If two systems exist (a plant roster and an HRMS calendar), name which one is master for paid-day math. Dual masters are how one Saturday is working in attendance and off in leave.

Publishing and reminders

People cannot obey an unpublished rotation. Put the roster where employees already look, with a freeze: changes after a stated weekday need a named exception. Managers who cover a store on a festival weekend should request a roster change, not a pile of regularisations that pretend the off moved.

Month-end reminders to managers should list “offs not matching punches” as a queue: worked-on-off without a compensation path, and absent-on-working-Saturday because the Nth-Saturday map was wrong. Those are attendance exceptions, not leave applications.

Publish at two horizons if rotation is dense. A monthly view is what payroll and leave close against. A weekly view is what the floor actually staffs. If the weekly sheet and the monthly calendar disagree, the monthly one still wins for paid days unless you have a written rule that the shop-floor sheet is master — in which case HR must copy it before freeze, not after payslips. Do not keep a third copy in a group chat that neither system can see.

When a public holiday cluster sits next to a nonstandard off (for example a Wednesday weekly off beside a Thursday holiday), employees will ask whether they “get a long weekend.” Attendance should already show both dates as not-worked. Whether leave on the adjacent working day is treated as sandwich is not decided in this article. Confirm the rest dates are correct first; then the sandwich guide can run on facts instead of on a default weekend.

If contractors and employees share a site, do not assume they share a rest pattern. A contractor roster owned by a vendor still needs dated offs in whatever calendar you use for their presence, or your gate will mark them absent every Wednesday while the vendor insists they were never expected. That is still a weekly-off recording problem, not a leave problem.

---

Record weekly offs as dated rest on the same calendar attendance and leave already use. Rotating, weekday, Nth-Saturday, and split weekends are normal; Sat–Sun is only one pattern. Do not spend leave on rest, and do not treat holidays as weekly offs. Let sandwich-leave read those rest days from the calendar — do not restate sandwich mechanics here. If the roster is late or verbal, every other policy will guess.