2.3Working time, leave & absences
The essentials in 30 seconds
- Time must be proven: reference hours, overtime with counts and compensation, reliable tracking (clocking, HRIS).
- Leave planned early: known rules, written requests and validations, fair arbitration.
- Reflex: handle each absence fast and methodically — absenteeism is first a signal before it is misconduct.
Threaded mini-case — Amira prepares summer without conflict
After the hires, Amira inherits the summer leave schedule: last year, everything was decided orally at the last minute, with conflicts and untracked overtime. This time, she publishes the rules early, requires written requests and makes time counts reliable. Continued from case 2.2 — Amira moves from files to working time.
Continued from case 2.2 — Amira organizes time, leave and absences.
1. Count fairly: time must be proven
Applicable hours (statutory or agreed), overtime (counts, premiums, time off in lieu), day-based packages (with workload monitoring) and on-call duty (working time only when called in) require reliable counts: clocking, HRIS, validated records.
Without a reliable count, every dispute over hours is lost: Amira has time validated weekly instead of reconstructing it afterwards.
2. Leave: plan it, don't suffer it
Paid leave and time-off-in-lieu are earned then taken under rules: periods, departure order, written validation, reasoned deferrals and refusals. Rules published early (calendar, arbitration criteria) prevent conflicts; decided late and orally, they manufacture them.
Amira posts the calendar and criteria, centralizes written requests and arbitrates transparently and fairly.
3. Absences: handle fast and fairly
Each absence is qualified (leave, illness, family event, unpaid, unjustified): evidence requested quickly, treatment adapted to local law, systematic return interview (listening, not punishment first), tracked reasons to detect a collective cause.
Absenteeism is a signal (workload, management, conditions) before it is misconduct: Amira analyzes reasons instead of punishing blindly, and links each absence to payroll.
🔎 Concrete example — 🔎 Hands-on example — A summer schedule without conflict
Early rules + writing = workplace peace.
Upstream: rules published (arbitration criteria known to all).
Then: written requests, transparent arbitration, posted schedule.
Before summer: reminder and cover planned ahead.
→ zero conflict, replacements ready.Reading: a summer covered with no emergency arbitration.
Lesson: last-minute oral deals manufacture conflicts.
Section vocabulary
- Working time
- Working time framed by statute and agreement: reference hours, maximums, mandatory rest.
Simple example: Amira applies the agreement's reference hours to each rota.
What it is not: hours decided day by day with no reference or rest.
Reflex: always place hours within their reference duration.
- Overtime
- Hours worked beyond reference hours, earning a premium or time off.
Simple example: Peak hours validated by Amira, counted then compensated.
What it is not: hours “on trust”, neither counted nor compensated.
Reflex: no hour without a count or compensation.
- Paid leave
- Paid rest days earned through work, with regulated scheduling and planning.
Simple example: Amira's summer leave, requested in writing and arbitrated early.
What it is not: departures decided orally the day before.
Reflex: early rules, written requests, fair arbitration.
- RTT (time-off-in-lieu)
- Working-time reduction days (France), under agreements, compensating hours above a threshold.
Simple example: Reduction days under the applicable agreement, planned like leave.
What it is not: days taken at random with no accrual or scheduling rule.
Reflex: check the applicable agreement before planning.
- Absence
- Periods when employees do not work (leave, illness, family events, unjustified absence), possibly affecting pay.
Simple example: Each absence qualified by Amira, then correctly translated into payroll.
What it is not: treating all absences alike, with no qualification.
Reflex: qualify first, pay fairly after.
In practice — Hands on — Manage working time and absences
- Spot the applicable reference hours (law, agreement), overtime rules and mandatory rest.
- Set up reliable tracking of time and attendance (ideally via the HRIS).
- Manage leave: accrual, scheduling rules, fair planning that accounts for team needs.
- Handle absences with clear rules and translate them correctly into payroll.
Ready-to-say script — announcing leave rules (1 min)
“For summer, here are the rules: written requests before the posted deadline, arbitration on criteria known to all, schedule published after. Time is validated weekly: no hour is lost, none invented. Questions now, not in July.”
To say in a meeting: rules, written records, calendar — before requests.
Copy-paste template — time and leave tracking
WEEK: _______________ | COUNT VALIDATED (yes / no): _______________
OVERTIME (counted + compensated): _______________
LEAVE (written request + arbitration + schedule): _______________
ABSENCES (reason + evidence + payroll qualification): _______________
RETURN INTERVIEWS DONE: _______________SME / small budget
A weekly spreadsheet validated in writing is enough: time, leave, absences — reviewed every Friday.
Seasonal-peak team
Anticipate cover and rest: plan leave outside peaks and count every peak hour from day one.
Remote work
Declared, written-validated time: trust does not exclude counting, it requires it.
Rising absenteeism
Analyze reasons by department before any punishment: workload, organization, conditions — then act on the cause.
✓ Best practices
- Make time counts reliable and have them validated regularly.
- Publish written, fair leave rules early.
- Hold a return interview after each absence.
✗ Common pitfalls
- Paying hours “on trust”, with no count.
- Managing leave orally and at the last minute.
- Calling every absence misconduct without hearing the reason.
Key takeaways
- The law governs working hours, overtime (premium or time off) and mandatory rest.
- Paid leave and time-off-in-lieu are earned and taken under rules to be planned fairly.
- Absences (illness, family events, unexpected events) affect pay.
- Stakes: compliance, team planning, pay accuracy and workplace climate.
48h Challenge — apply tomorrow
Publish the leave rules for the next period and make the week's count reliable (written validation). Note one gap fixed thanks to the count.
- I can explain why time must be counted.
- I can organize fair leave (early rules + written records).
- I have made one count reliable and handled one absence methodically.
Frequently asked questions
Can an employee take leave whenever they want?
No: taking leave follows rules balancing the right to rest with the organization's needs. Employees request, employers validate considering service requirements. Neither arbitrary refusal nor unilaterally imposed dates: terms depend on local law and the agreement. The key: clear rules, known to all, applied fairly.
How do absences affect pay?
Depending on their nature: some are paid (paid leave), others partly compensated by social protection (illness, maternity, under conditions), others unpaid (unpaid leave, unjustified). Each absence must therefore be qualified correctly with the right treatment, with reliable tracking linked to local rules. An error here directly produces a wrong payslip.
Amira pays overtime with no time count. What is the main risk?