Shift planning guide: night shifts, flexible shifts and tolerance rules

On paper, a shift plan looks simple: who works which day, from when to when. The trouble starts in week three — someone goes on leave, someone swaps a shift, the night shift spills into the next day, a holiday falls in the week, and the plan ends up being run through WhatsApp messages. On the administrative side, this is one of the biggest time sinks: not building the plan, but keeping it alive.

In this guide, I walk step by step through how we set up a shift structure in the system: definitions, assignments, exceptions and how they flow into the timesheet.

First, the vocabulary: shift, flexible shift, tolerance

• Shift: a definition stating the hours of the day to be worked and when and how long breaks will be. For example, "08:00–17:00, lunch break 12:30–13:30."
• Night shift / overnight clock-out: a shift that starts at 22:00 and ends at 06:00. The clock-out falls on the next calendar day; the system should count it as a single working day.
• Flexible shift: an arrangement where the start time is free within a set window ("arrive between 08:00 and 10:00, complete 9 hours").
• Tolerance: the number of minutes overlooked for late arrival, early departure and overtime. Deviations within the tolerance are not reported; deviations beyond it count as lateness, undertime or overtime.
• Weekly rest day: the employee's weekly day off; in shift-based operations, it doesn't have to be Sunday for everyone.

Step 1: Set up your shift definitions

Create one definition for each distinct working pattern — for the pattern, not for the person. In a typical production facility, three definitions are enough: morning (08–16), evening (16–24), night (24–08). An office may need just one, and security may have two 12-hour definitions. Each definition includes:

• Clock-in and clock-out times by day (differences such as a half day on Saturday are set here)
• Breaks: start time and duration, and all of them if there is more than one
• A single checkbox if the shift carries over to the next day

Keep the legal framework in mind: under Turkish Labour Act No. 4857, the normal weekly working time is 45 hours, daily work may not exceed 11 hours, and night work as a rule may not exceed 7.5 hours. If your shift definition exceeds these limits, it is the plan that's wrong, not the system.

Step 2: Write down your tolerance and break rules

Define tolerance in minutes and spell it out: for example, "10 minutes for late arrival, 5 minutes for early departure, overtime counts only once it reaches at least 30 minutes." Watch out for three things:

• Tolerance should not be hidden; employees should know the rule. Unknown tolerance breeds disputes.
• Define a "minimum duration" for overtime; otherwise 4-minute late clock-outs add up into an overtime balance.
• Track break overruns separately: a 30-minute lunch break that lasts 50 minutes isn't lateness, but it is a notable deviation. The "employees exceeding break time" report exists for exactly this.

Step 3: Assign people and days from the calendar

Don't make assignments one person at a time; in the calendar view, select people and days and assign a shift, a flexible shift or a weekly rest day in bulk. In a rotating pattern (one week mornings, one week nights), this takes a few minutes. When a new hire is added to a group or site, they should inherit that unit's default shift; the plan shouldn't be rebuilt from scratch with every new hire.

Step 4: Turn exceptions into rules

The things that break a plan are predictable; each one should have a counterpart in the system:

• Shift swap: the person is assigned a different shift for that day; past records are re-evaluated against the new definition.
• Leave: approved leave is entered on the calendar and no shift is expected that day; no absence appears on the timesheet.
• Public holiday: if a holiday calendar is defined, anyone working that day is reported separately as "holiday work."
• Clock-in at another branch: a person who clocks in at a different site appears in a separate report; if policy allows it, that's normal, and if not, it warrants a review.

When is a flexible shift the right choice?

Flexible shifts work for office and software teams whose work doesn't need to start at a fixed time. A start window and a total daily duration are defined; the employee can arrive at 08:40 or 09:50, and if the daily total falls short, undertime is recorded. In jobs like a production line, security with shift handovers or store openings, flexible shifts disrupt operations; there, classic shifts with tolerance are the right tool.

How does the plan flow into the timesheet?

Once shift definitions, tolerance and breaks are set up, every clock-in/out record is evaluated against them: with a 10-minute tolerance, an 08:12 clock-in counts as late; a 17:35 clock-out is a normal departure because it stays below the 30-minute minimum overtime threshold; and the 06:00 clock-out of a night shift is recorded on the previous day. The timesheet that emerges at month-end is correct according to the plan, because the plan was in the system from the start.

Shifts in NetKurum

In NetKurum, shift and flexible shift definitions, break and tolerance settings, and individual and bulk assignments are all handled in the same section; overnight shifts that carry into the next day are supported. Mobile, card and turnstile entries are evaluated by the same rules; late arrivals, early departures, overtime and undertime appear in daily reports, and monthly totals appear on the timesheet. For details, see the Shift Management page.

A good shift plan isn't one that never changes; it's one where change follows a rule.

Move your shift plan into the system

We can migrate your current plan into the system together and set up your tolerance and break rules. Start your free trial or contact us.