# Why Planned Schedules and Actual Attendance Belong Together

- Canonical: https://qrgate.az/en/blog/schedule-and-actual-attendance-together
- Markdown: https://qrgate.az/en/blog/schedule-and-actual-attendance-together.md
- Language: en
- Date: 2026-06-05

A report line reads "09:17". On its own that number is neither good nor bad. If the person's day starts at 09:00, it is seventeen minutes late. If their shift begins at 10:00, they arrived forty-three minutes early. If it was not a working day for them at all, the record means something else entirely. When **schedule and actual attendance** are stored in different places, a report fills up with numbers that carry no meaning - because there is nothing to compare them against.

## Why actual times are not enough on their own

An attendance system knows one thing precisely: when the record was created. That is a fact and it is not disputable. But a management decision does not rest on the fact - it rests on *the gap between the fact and what was expected*.

In practice that gap shows up in three questions: did this person arrive on time, how long did they work, and was the planned cover achieved? None of them can be answered without knowing the schedule.

Without one, companies typically fall into one of two errors. Either a single 09:00 rule is applied to everybody - and every shift worker appears late every day. Or the concept of lateness is dropped entirely - and no trend is ever visible.

## Plan and fact are two different records

The core idea of a combined system is simple: two layers are kept for every day.

- **Plan** - what was expected that day: is it a working day, which shift, how many hours.
- **Fact** - what happened: whether a record exists, and at what time.

When the two sit side by side, the report explains itself. A "no record" line read together with the plan immediately shows whether it was a rest day or a genuine absence.

The important consequence is that the comparison happens for every day automatically. In a manual process that comparison is made at month-end, by hand and selectively - which in practice means it is barely made at all.

## Lateness only exists in context

Lateness is not an absolute concept but a relative one. It exists only in relation to an expected start time.

This matters in three situations in particular. First, in **shift teams**: a morning shift starts at 07:00 and an evening shift at 15:00, and the same threshold cannot serve both. Second, in **flexible patterns**: if the arrival window runs from 08:00 to 11:00, then 10:20 is not late. Third, in **part-time roles**, where the working day does not follow the general rule at all.

Ignore the context and the report inflates systematically. In practice that leaves managers with a false impression - attendance discipline looks poor when in fact the measurement baseline is wrong. We describe how lateness records are formed on the [tracking employee lateness automatically](https://qrgate.az/en/tracking-employee-lateness-automatically) page.

## Several schedules inside one company

Most companies run at least three different patterns at the same time:

| Group | Schedule type | The key measurement question |
| --- | --- | --- |
| Office team | Fixed hours | Did they arrive on time |
| Retail point | Shifts | Was the shift covered |
| Warehouse or production | Shifts including nights | How many night hours |
| Field staff | Flexible | Are total hours within the norm |

Those four cannot be measured against a single rule. The schedule therefore belongs at the base of an attendance system, not as an optional add-on.

The practical implication: when a new group appears - a company opening its first shift-based warehouse, for instance - the system has to accept a new pattern type. Otherwise that team sits outside the reporting from day one.

## Plan-versus-fact reporting at month-end

With both layers in place, the monthly report answers three questions in the same table: how much was planned, how much was worked, and where the difference came from.

That third column carries the most value. The difference usually traces back to one of four causes: lateness, an early finish, unplanned extra work, or a missed day. Once those are separated, the report stops being an accusation and becomes a management instrument.

We go into how actual working time is determined on the [determining actual working time](https://qrgate.az/en/determining-actual-working-time) page.

## What happens when the schedule changes

In a real company the schedule never stays still: shifts change, people swap, patterns are adjusted mid-month. Where those changes are recorded determines how much the report can be trusted.

The most common situation is this: the schedule is distributed once as a file, and every subsequent change lives in a chat thread. At month-end the report is built against the original plan, and ten or fifteen lines look inconsistent.

Keeping a change history removes that problem. It also means that when a disagreement arises, you can show which plan was actually in force on that date - in practice the single most useful document in the whole discussion.

## A practical example

In a 110-person warehouse running three shifts, attendance lived in a system while the schedule lived in a spreadsheet. The monthly report showed around 130 "lateness" lines, and management was discussing disciplinary measures.

Once the schedule was moved into the same context as attendance, the number fell from 130 to 18. No behaviour had changed - previously every employee on the evening and night shifts had been measured against a 09:00 threshold every single day.

The remaining 18 lines were real, and it finally became possible to work with them. This is one of the most repeated outcomes in attendance projects: once the baseline is right, the true size of the problem becomes visible.

## What the transition requires

Bringing schedule and attendance together is less a technical project than a documentation exercise. Four things need to be ready.

First, **a list of the schedule types actually in use**. Many companies have three patterns on paper and five or six in daily life. When that difference surfaces, somebody has to decide which version gets formalised.

Second, **a change rule**: who approves a shift change and by when it is published. Third, **role separation** - who can build a schedule and who only views it. Fourth, **a list of exceptions**: holidays, business trips, training days.

With those four settled the transition takes days. Without them, most of the effort goes into settling them - work that has to happen sooner or later anyway.

## The objection you will hear

"Our schedule changes too much to fit a system" is the most common sentence. In practice the opposite holds: the more variable the schedule, the more valuable it is to keep it written down.

In a fixed nine-to-six routine the schedule is easy to remember, so a system adds little. When shifts change twice a week, memory stops working - and that is precisely where plan-versus-fact comparison becomes indispensable.

## How to test your own process

Three questions will tell you where you stand:

1. How many schedule types does the company run, and are they all kept in one place?
2. When a schedule changes, where is the change recorded?
3. What share of the lateness lines in your monthly report are actually caused by a different pattern?

If you cannot answer the third, that in itself is an answer. We wrote about running schedules and attendance together on the [managing schedules and attendance together](https://qrgate.az/en/managing-schedules-and-attendance-together) page.

## Next step

Take twenty "lateness" lines from last month's report and ask of each: what was that person's planned start time on that day?

QRGate keeps schedules and actual attendance in one context and shows plan and fact side by side. [See what QRGate can do](https://qrgate.az/en/advantages) or [calculate the price](https://qrgate.az/en).

## FAQ

### Can lateness be measured without a schedule?

No. Lateness exists only relative to an expected start time. Apply a single 09:00 rule and every member of a shift team appears late every day.

### How many schedule types does a company usually run?

At least three: fixed hours in the office, shifts at retail points, flexible hours for field teams. Each group has to be measured against its own baseline.

### What happens to the report when a schedule changes?

The change history has to be kept. Otherwise the month-end report is built against the original plan and ten to fifteen lines look inconsistent for no reason.

### Which metric shows how well the schedule is being followed?

One number is not enough. In practice three work together: the share of days started on schedule, the average lateness, and the number of unplanned changes. Read together they show whether the problem sits with the person or with the schedule itself.

## Related pages

- Actual working time - [Markdown](https://qrgate.az/en/determining-actual-working-time.md) | [HTML](https://qrgate.az/en/determining-actual-working-time)
- Automatic time calculation - [Markdown](https://qrgate.az/en/automatic-working-time-calculation.md) | [HTML](https://qrgate.az/en/automatic-working-time-calculation)
- Schedules and attendance - [Markdown](https://qrgate.az/en/managing-schedules-and-attendance-together.md) | [HTML](https://qrgate.az/en/managing-schedules-and-attendance-together)
- Alternatives to a fingerprint system - [Markdown](https://qrgate.az/en/alternatives-to-fingerprint-attendance.md) | [HTML](https://qrgate.az/en/alternatives-to-fingerprint-attendance)
- Attendance for field teams - [Markdown](https://qrgate.az/en/attendance-for-field-teams.md) | [HTML](https://qrgate.az/en/attendance-for-field-teams)
- Tracking lateness - [Markdown](https://qrgate.az/en/tracking-employee-lateness-automatically.md) | [HTML](https://qrgate.az/en/tracking-employee-lateness-automatically)