How is a work schedule prepared?
06.09.2026
How is a work schedule prepared looks like a simple question, but in practice it requires satisfying several constraints at once: workload, headcount, labour norms, leave and the expectations of the team. This guide sets out the preparation sequence, the constraints to account for, and the mistakes made most often.
Preparation: what must be known
Four pieces of information are needed before writing a schedule:
- The workload - how many people are needed at which hours.
- The available staff - who, with which skills, under which constraints.
- The norms - daily and weekly hour limits, rest requirements.
- The exceptions - leave, training and business trip plans.
The first item is the one most often skipped. Schedules are usually written on the principle of "how it was last month", whereas the real question is how the workload is distributed across the hours.
Step by step
- The demand curve is derived. How many people are needed by day and hour.
- The shift structure is chosen. How many shifts, at which hours.
- The staff are allocated. Skills and roles are taken into account.
- Rest days and leave are placed.
- Compliance with norms is checked. Weekly hours, consecutive days.
- The schedule is published - in advance, together with the rules for changes.
The timing of the sixth step matters: the later a schedule is published, the higher the dissatisfaction in the team.
Shift structures
| Structure | Suits | Watch out for |
|---|---|---|
| Standard 5/2 | Office, administrative staff | The simplest |
| Two shifts | Retail, services | Shift handover |
| Three shifts | Manufacturing, security | Night shift rules |
| 2/2, 3/3 | Security, healthcare | Monthly hour balance |
| Flexible | IT, marketing | The daily norm is the basis |
A practical example
At a café chain the schedule was written by hand every week by the manager, on a simple principle: the same number of people every day.
Comparison with sales data showed the demand was far from even: on Thursday and Saturday evenings the load was twice as high, while Wednesday mornings were the opposite.
When the schedule was rebuilt around demand, two results followed: waiting time at peak hours fell, and total employee hours dropped by 8% - because staff were no longer held during quiet periods.
The lesson is that a schedule is a plan of the workload, not a plan of the headcount.
The most common mistakes
- The schedule is published late. Employees cannot plan their own lives.
- There is no rule for changes. Who can change what, and by when?
- Skill distribution is ignored. A shift lacks the required expertise.
- Norms are not checked. The weekly hour limit is exceeded.
- It is never compared with actual hours. The schedule is written but never checked against reality.
The last mistake loses the most valuable information: a schedule is a planning tool, but it only teaches you something when compared with the facts.
The link between schedule and attendance
The schedule is the basis of the attendance calculation. Without a plan, lateness, overtime and shortfall cannot be calculated. Writing the schedule down and keeping it in the system is therefore the first condition of recording - covered on the schedules and attendance page.
Publication and changes
The rule that works in practice: the schedule is published at least a week in advance, and changes are made with the agreement of both parties and in writing. This rule stabilises expectations in the team and removes most schedule disputes.
Deriving the demand curve
The quality of a schedule depends on how accurately demand is measured, and in practice this is the step most often skipped.
The sources of demand vary by sector: sales data and customer footfall in retail, order volumes in services, production plans in manufacturing, call statistics in a contact centre.
The data is collected by hour and averaged across the days of the week. The result shows that the load is not evenly distributed at all - twice as high in some hours, low in others.
Without this curve the schedule is written on the "how it was last month" principle, and resource is short at peak hours and idle in quiet ones.
Reconciling the constraints
Several constraints must be satisfied at once when writing a schedule, and their priority must be set in advance.
Mandatory constraints cannot be broken: the weekly hour limit, minimum rest between shifts, the maximum number of consecutive working days, and the presence of the required skills in each shift.
Desirable constraints are accommodated where possible: employees' personal requests, an even distribution of night shifts, stability of team composition.
The practical mistake is mixing the two groups. Treating personal requests as mandatory makes the schedule impossible; treating mandatory norms as preferences creates legal risk.
When the priority list is written down, the decisions of the person writing the schedule can also be justified.
Comparing the schedule with actual hours
A schedule is only a planning tool; to become instructive it must be compared with the facts.
The monthly comparison asks three questions: on which days does the plan systematically differ from the fact, which shifts always end in overtime, and in which hours is resource left idle.
The answers feed directly into next month's schedule. If a shift ends with forty minutes of overtime every time, that is not chance - the shift length does not reflect the real workload.
Without this comparison the same mistakes repeat every month and overtime becomes a permanent cost.
Publishing the schedule
When and how a schedule is published matters as much as its quality, because employees plan their lives around it.
The practical norm: the monthly schedule is published at least a week before the month begins. In shift patterns that period should be longer - two weeks is considered optimal.
The method of publication matters too. A printed table stays at the post and goes stale when a change is made; a digital view always stays current.
The third element is the change rule: under what conditions can the schedule be changed after publication, and how is the employee informed?
When these three elements are turned into a written policy, most schedule disputes disappear - because expectations become clear to both sides.
In summary
A work schedule is a plan of the workload rather than a plan of the headcount. Preparation should therefore start from the demand curve, not from repeating the existing pattern.
A quality schedule satisfies three conditions: alignment with demand, compliance with norms and timely publication. When all three are met, resource is used efficiently and dissatisfaction in the team falls.
The final step is comparison with the facts: a schedule only improves when it is measured against real outcomes.
The next step
A practical way to test the quality of a schedule: compare last month's plan with the actual hours. A systematic difference means the schedule does not reflect the real workload.
QRGate stores schedules and reconciles them automatically with actual records. See what QRGate can do or calculate the price.
