Leave Planning Without Excel: Practical Guide for 2026

Every year the same story: in January everyone applies for summer leave, by March nobody remembers who approved what, and in July you're two people short on a Saturday. Leave is not an administrative detail — it is the biggest predictable disruption to your staff planning. And that is exactly what makes it so frustrating when it goes wrong.

In this guide you'll read how to structure leave requests without scattered mailboxes and Excel files, which Belgian ground rules you need to respect as a minimum, and how to link leave to your work schedule instead of bolting it on afterwards.

Why Excel breaks down when it comes to leave

A leave file in Excel works fine with five employees. From about twenty onwards, four things invariably go wrong:

• Two versions of the truth. The request sits in an email, the approval in WhatsApp, the actual day in the work schedule. Three sources, three versions.
• No staffing check. Excel won't tell you that on 14 August you'll be left with just one qualified nurse.
• Balances that don't add up. Part-time employees, variable work schedules, half days, public holidays falling on a leave day — recalculating by hand is asking for arguments in December.
• No audit trail. If a refused day is disputed, you have no date, no reason, no history.

The cost isn't in the file itself, but in the hours your manager or planner pours into it and in the gaps that only become visible on the shop floor.

What Belgian rules require of you as a minimum

You don't need to know employment law by heart, but this basis has to be built into your system.

Four weeks of statutory holiday. A full-time employee is in principle entitled to four weeks of annual holiday, built up on the basis of the work performed during the holiday qualifying year (the year before the holiday year). Someone who didn't work, or worked part-time, in 2025 builds up less for 2026. Starters and people returning to work can top this up through so-called European or supplementary holiday.

Blue-collar and white-collar workers are treated differently. For white-collar staff you pay the holiday pay yourself; for blue-collar staff it runs through the holiday funds (see the National Annual Holidays Office). That changes nothing about the planning, but it does affect your wage budget and how you communicate with the employee.

Holiday is agreed jointly. Individual days are agreed between employer and employee; a collective shutdown is set at sector level, in the works council or by agreement, and belongs in the work rules. Employees with school-age children should preferably be given holiday during the school holidays.

Holiday must be taken within the holiday year. So don't push everything to December: a backlog of leave in the fourth quarter is both a planning problem and a risk.

Falling ill during holiday doesn't count as holiday. Since the 2023 change in the law, an employee who becomes unfit for work during their holiday keeps those holiday days, provided they notify you and supply a medical certificate. The FPS Employment has set out the obligations. In practice: your system has to be able to return those days to the balance — and your planner still has to organise the cover.

Step 1: set your leave framework before January

Most leave disputes arise because the ground rules only surface once someone has already booked a flight. So once a year, preferably in November or December, put the framework on paper:

• Which periods are collective shutdown (construction holiday, the Christmas period, the restaurant's closing week)?
• Which periods are low-leave: the year-end rush in retail, the summer peak in hospitality, the major maintenance shutdown in manufacturing?
• What is the request deadline for summer leave? For example: all requests for July and August submitted before 31 March.
• How do you settle conflicts: seniority, rotation, school-age children, or simply order of request? Pick one rule and write it down.

A one-page framework prevents more arguments than ten individual conversations.

Step 2: one channel, one status

Leave doesn't belong in the manager's inbox. What you need is a single flow with four statuses: requested → approved or refused → scheduled → taken. Every employee sees their own balance and the status of their request; the supervisor sees the impact on staffing at the moment of approval, not three weeks later.

That last point is the real difference with Excel. If a request for 12 May immediately shows that only two of your four drivers are available that day, you'll make a different decision than if you were just looking at a calendar.

Step 3: link leave to the work schedule, not the calendar day

For full-time employees on a fixed schedule, a leave day is simple. For part-time contracts and variable work schedules — the reality in care, cleaning and logistics — it isn't.

An employee who works 10 hours on Monday and 4 hours on Wednesday doesn't lose a "day" but a number of scheduled hours. So account for leave in hours against the planned schedule, not in days on a calendar. That way you avoid someone systematically taking their long days off and ending the year with more hours off than they were entitled to.

Also watch out for overlap with public holidays: a statutory public holiday falling within a leave period may not be charged as a holiday day. You can read more about that puzzle in scheduling public holidays in care without an overtime peak.

Step 4: set minimum staffing instead of going on gut feeling

Approving becomes straightforward as soon as you know the minimum per day or shift. Think concretely:

• Restaurant with 60 covers on a Friday evening: at least 2 in the kitchen, 3 front of house, one of whom is responsible for the till.
• Cleaning team on an office site: every shift needs at least 1 team leader with an access badge.
• Warehouse: at least 2 forklift drivers with a valid certificate per shift.

Once those rules are fixed, "no" is no longer arbitrary but an outcome. And you immediately see where flexible work — flexi-jobs, students or extras — can plug a gap instead of making colleagues work overtime.

Step 5: monitor balances, carry-over and the fourth quarter

Block out a moment in September to go through all outstanding balances. Who still has ten days left? Schedule them together, spread across October to December, taking your peak period into account. Without that check you'll get a wave of requests in the final weeks of the year that you can no longer spread out.

Keep the special cases visible separately too: youth holiday for school leavers, senior holiday for older employees, and the days restored to people who fell ill during their holiday.

Leave planning checklist

• Leave framework and collective shutdown set out and included in the work rules
• Request deadline for summer leave communicated
• One digital channel with visible status and balance per employee
• Minimum staffing defined per shift, including required certificates
• Leave accounted for in hours against the planned schedule
• Public holidays correctly excluded from leave deductions
• Quarterly check on outstanding balances
• Procedure for illness during holiday known to supervisors

From scattered files to a single plan

Leave management only becomes calm once requests, approvals, schedules and HR administration sit in the same system. Then every approval immediately shows you the effect on your staffing, balances stay correct automatically, and on 1 July you don't have to hunt for which email came last.

In Forganiser you process leave requests directly in the planning: the day disappears from the schedule, the gap becomes visible, and you fill it with whoever is actually available — including the right employee records and the formalities that go with them. If you then also want to handle changes to your schedules correctly, read changing a work schedule: what Belgian law says.