# How is attendance managed with flexible working hours? - Canonical: https://qrgate.az/en/attendance-with-flexible-working-hours - Markdown: https://qrgate.az/en/attendance-with-flexible-working-hours.md - Language: en **A flexible schedule** does not abolish attendance recording - it changes what is measured. Under a fixed pattern the main question is "when did they arrive?"; under a flexible one it becomes "how much did they work?". Companies that miss that distinction either leave flexible work unrecorded or mark employees as "late" for no reason. This guide explains how a flexible pattern is managed correctly. ## What a flexible schedule means Three different models are called "flexible" in practice: - **Sliding start** - arrival is free within a window (08:00–11:00) and the daily norm is fixed. - **Core hours** - everyone must be present during a defined period; the rest is free. - **Fully flexible** - only a weekly or monthly norm is defined. The recording approach differs for each, so the first step is naming the model precisely. ## What is measured | Model | Main indicator | Concept of lateness | | --- | --- | --- | | Sliding start | Daily norm | After the window | | Core hours | Presence in the core plus the norm | Lateness to the core | | Fully flexible | Weekly or monthly norm | None | The third row matters: under a fully flexible pattern the lateness indicator is meaningless and should be removed from the report. ## Why recording is still needed Abandoning recording under a flexible pattern is a frequent mistake. Recording remains necessary for three reasons: 1. **Overtime.** If the norm is exceeded, that must be visible. 2. **Workload distribution.** Balance across the team. 3. **Project accounting.** Which work the time went into. In practice the greatest risk under a flexible pattern is not lateness - it is **unpaid overtime**. Without recording that stays entirely invisible. ## A practical example A software company had adopted a flexible pattern and kept no attendance record at all, on the principle that "we work by results". A year later signs of burnout appeared in the team. To investigate, management proposed three months of voluntary time recording. The result was unexpected: a third of the team worked on average six hours a week beyond the norm, and this came from unrealistic project deadlines. The recording brought no penalties for anyone - instead the planning methodology was changed. It is an example of recording as a management tool rather than a means of supervision. ## How to set it up - **Write down the model** - sliding, core hours or fully flexible. - **Define the norm** - daily, weekly or monthly. - **Set the window** - the arrival window in the sliding model. - **Remove lateness** - if it does not fit the model, take it out of the indicators. - **Track overtime** - time above the norm must be visible. ## Remote work A flexible schedule often comes together with remote work. In that case the recording point may not be a physical location - time is recorded by the start and end of work. The essential rule is that the concepts of norm and overtime must remain for remote employees too; otherwise the working day becomes unbounded. ## The question of trust Under a flexible pattern recording is frequently read as "distrust". There is a practical way to change that perception: state the purpose of the recording openly and share the first results with the team. When recording reveals overtime and works in the employee's favour, attitudes change quickly. ## What to measure 1. The difference between the weekly norm and actual hours. 2. The distribution of overtime across the team. 3. Presence during core hours (if that is the model). 4. The number of consecutive long days. ## Defining the core hours The most used variant of the flexible pattern is the core hours model, and setting it up requires attention. Core hours are the period during which the whole team must be present - for meetings, contact and joint work. A window of four to five hours is usually chosen (11:00–16:00, for example). Two factors guide the choice. The first is the team's real need for interaction: in which hours is joint work required. The second is alignment with other departments - a team on a flexible pattern still has to interact with departments on fixed hours. Core hours set too wide destroy the flexibility; set too narrow, the team is practically never together. ## Combining with remote work A flexible schedule is often applied together with remote and hybrid work, and that brings additional questions to the recording. The first is the recording method: without a physical point, how is the start of the working day recorded? Two options exist in practice - a start and end record through the app, or task-based accounting. The second is separating the days spent in the office: if a hybrid arrangement requires a number of office days per week, that has to be measured too. The third and most important is the boundary of the working day. When the concept of a norm is not preserved in remote work the day lengthens, and that leads to burnout - the most documented problem of remote work. Under flexible and remote patterns, therefore, the purpose of recording is not supervision but protecting the boundary. ## Presenting the recording to the team Teams working under a flexible pattern are usually more sensitive to recording, because flexibility is associated with trust. The way it is introduced therefore affects the outcome directly. The approach that works in practice has three steps. The first is stating the purpose openly: the measurement exists to reveal overtime and balance the workload. The second is starting with an observation period - three months of measuring with no measures taken. The third is reading the results together with the team. Following that order, the recording is understood as a management tool. Conversely, when measurement starts abruptly and without explanation it is read as tightened supervision and meets resistance. Practical experience shows that attitudes change quickly once the first results reveal overtime. ## The limits of flexibility A flexible pattern does not mean unlimited freedom, and writing down the limits protects both the company and the employee. Four boundaries should be defined in practice. **The arrival window** - how late at the latest, in the sliding model. **Core hours** - the period in which everyone must be reachable. **A daily maximum** - beyond how many hours in a day is not recommended. **Response time** - how quickly a reply to messages is expected in remote work. The last boundary is the one that causes most trouble under flexible and remote patterns: when no response time is defined, the expectation forms as "always available". When these four boundaries are announced in writing, flexibility genuinely delivers; when they are not, it gradually turns into a working day without limits. ## In summary A flexible schedule does not abolish attendance recording - it changes the measure. Instead of the arrival time the norm becomes the key indicator, and instead of lateness the focus moves to overtime. The real risk under a flexible pattern is not lateness but unpaid overtime and an unbounded working day. Recording exists precisely to prevent that. The introduction should be gradual: write down the model, define the boundaries, run a three-month observation period and read the results together with the team. ## The next step The gentlest way to start recording under a flexible pattern is a three-month observation: measure only, take no action, and read the results with the team. QRGate supports a separate schedule template for the flexible pattern. [See what QRGate can do](https://qrgate.az/en/advantages) or [calculate the price](https://qrgate.az/en). ### Related pages - [Employees with different working hours](https://qrgate.az/en/attendance-for-different-working-hours) - [Determining actual working time](https://qrgate.az/en/determining-actual-working-time) - [Schedules and attendance together](https://qrgate.az/en/managing-schedules-and-attendance-together) ## FAQ ### What is measured under a flexible schedule? The norm rather than the arrival time. With a sliding start the daily norm is the key figure, with core hours it is presence during that window plus the norm, and under full flexibility only the weekly or monthly norm applies - lateness has no meaning there. ### Why is recording still necessary? Because the real risk under flexible work is not lateness but unpaid overtime and a working day without boundaries. Recording exists to protect the boundary, not to supervise arrival times. ### How should recording be introduced to a flexible team? Gradually and openly: state the purpose, run a three-month observation period with no measures taken, then read the results together with the team. Attitudes change quickly once the numbers reveal unpaid overtime. ### How should the report be built under a flexible schedule? Instead of a daily lateness column, show the weekly and monthly norm fulfilment, the share of overtime and the length of the working day. Applying a lateness metric to flexible work produces artefacts and undermines trust in the report. ### Can flexible and standard schedules live in one system? Yes, provided the schedule types are configured separately. Each person is then calculated against their own norm while the reporting stays unified - no separate ledger is needed. The condition is that the template is updated when a role or pattern changes. ## Related pages - Tracking clock-in times - [Markdown](https://qrgate.az/en/tracking-clock-in-clock-out-times.md) | [HTML](https://qrgate.az/en/tracking-clock-in-clock-out-times) - Biometric attendance - [Markdown](https://qrgate.az/en/biometric-attendance-system.md) | [HTML](https://qrgate.az/en/biometric-attendance-system) - Time recording systems - [Markdown](https://qrgate.az/en/working-hours-recording-systems.md) | [HTML](https://qrgate.az/en/working-hours-recording-systems) - Shift worker attendance - [Markdown](https://qrgate.az/en/attendance-tracking-for-shift-workers.md) | [HTML](https://qrgate.az/en/attendance-tracking-for-shift-workers) - GPS employee oversight - [Markdown](https://qrgate.az/en/gps-employee-oversight.md) | [HTML](https://qrgate.az/en/gps-employee-oversight) - Tracking attendance with QR - [Markdown](https://qrgate.az/en/tracking-attendance-with-qr-codes.md) | [HTML](https://qrgate.az/en/tracking-attendance-with-qr-codes)