Belgium is moving toward a general obligation to record employees’ working time from 1 January 2027. The driver isn’t a sudden love for administration—it’s legal and enforcement pressure: working-time rules can’t be applied consistently if working time is not measured in an objective and accessible way.
What’s important for employers in 2026 is not to panic—but also not to wait. If a broad obligation lands as announced, the lead time to choose an approach, align stakeholders, and roll out tooling and processes will be longer than it looks.
Note: This is an operational briefing, not legal advice. Confirm the final scope and requirements with legal counsel, your payroll provider, and your social secretariat once draft legislation is published.
What’s the latest development (as of January 2026)?
The most concrete signal so far is the Belgian federal budget agreement (announced in late November 2025), which references a general time-registration obligation from 1 January 2027. At the time of writing, the practical details are not yet set out in a published draft law.
That means: direction is clear, but implementation details (scope, specifics of what must be recorded, enforcement mechanics) are still to be confirmed.
Why now?
Across the EU, working-time enforcement has increasingly emphasized that employers need a system that is objective, reliable, and accessible to measure daily working time. Without measurable time, compliance becomes theoretical—and disputes become harder to resolve fairly.
Belgium’s move can be understood as aligning domestic practice with those EU expectations.
What seems clear already
Even without a draft law, several points look consistent with how this requirement has been described publicly so far:
- Start date: 1 January 2027 is the announced target.
- Scope direction: intended to be broad (public + private sector) and general—not limited to special regimes only.
- System characteristics: “objective, reliable, accessible” (and in practice likely flexible enough to fit different working patterns).
- Technology choice: reporting suggests employers will retain discretion on the method/technology rather than being forced into one prescribed tool.
What’s still unclear (and will matter a lot)
Until draft legislation appears, these questions remain open—and they drive real design choices:
- Coverage: will all employee groups be included, including roles currently treated as more autonomous?
- What must be recorded: start/end only, or also breaks, on-call, travel time, etc.?
- Retention and access: how long must records be retained, who must be able to access them, and in what format?
- Enforcement: what will inspections look for (process, tooling, audit trail, employee access)?
What “objective, reliable and accessible” means in practice
You can think of this as three design constraints:
- Objective: not purely “trust me,” and not dependent on informal memory. The system should reflect what happened, not what someone wishes happened.
- Reliable: consistent over time; protected against casual manipulation; with an audit trail for changes.
- Accessible: employees and relevant stakeholders can access records in a usable way (not locked in a payroll export nobody sees).
This doesn’t automatically imply one type of technology. It does imply your method must stand up in real-world use.
What employers should do in 2026 (low-regret moves)
You don’t need final legislation to start preparing in a way that won’t be wasted.
1) Segment your workforce and working patterns
Map groups with different realities:
- Fixed schedule
- Flex schedule
- Remote/hybrid
- Field/mobile roles
- Shift work
- Part-time with frequent deviations
- Management/autonomous roles (depending on how your organization treats them today)
2) Audit what you already track
Many organizations already have “time signals,” but they are fragmented:
- Badge access / building logs
- Shift planning tools
- Payroll inputs and overtime approvals
- Project timesheets
- Fleet/field scheduling
Identify what can be reused and what cannot (especially for auditability and employee access).
3) Define your future operating model
Common models:
- One core tool for all (simpler governance, harder to fit every edge case)
- A core tool + add-ons (better fit, higher integration and governance cost)
Decide where “system of record” lives (HRIS, dedicated time tool, WFM).
4) Plan communications early
Time tracking touches trust and culture. Successful rollouts make the purpose explicit:
- Compliance and fairness
- Payroll accuracy
- Protection for both employer and employee
Avoid “productivity surveillance” optics by design.
5) Bake privacy in from day one
Time registration data is personal data. Build:
- Retention rules
- Access control
- Vendor governance (processor agreements, security, subprocessors)
- Transparency (policy and employee notice)
Key dates to highlight
- 24 November 2025: federal budget agreement announced (policy signal)
- 1 January 2027: planned start of the general working-time registration obligation
The first step is workforce segmentation. Many employers have different time-tracking realities across:
- Office staff with flexible schedules
- Field staff / mobile workers
- Shift-based operations
- Project-based teams (billable hours)
- Management / exempt roles (if applicable)
Even if the end requirement is broad, implementation often needs segmentation because the “right” capture method differs.
What data should you be ready to capture?
A conservative operational baseline for time registration includes:
- Start time
- End time
- Breaks (where applicable)
- Total daily working time
- Exceptions (leave, sickness, travel time rules, on-call)
- Edits (who changed what, when, and why — audit trail)
If your organization also needs project costing or client billing, you may additionally capture:
- Project/cost center
- Activity type
But be careful: mixing compliance time registration with detailed productivity tracking can create trust and privacy issues unless governed carefully.
Policies and process: the hidden work
Time registration is not “install an app.” You’ll need clear policies covering:
- What counts as working time (travel, training, on-call)
- Break rules and how they are recorded
- Handling of missed punches / late entries
- Approval workflow (manager validation, frequency)
- Dispute handling process
- Data retention and access controls
If policies are unclear, your system will collect inconsistent data and you’ll fail the auditability test.
System requirements: what to demand from a solution
When selecting or configuring a tool (HRIS module, dedicated time system, or workforce management platform), focus on these requirements:
1) Reliable capture methods for your workforce
Examples:
- Web and mobile entry
- Clock-in/out (kiosk, badge) for on-site work
- Offline mode for field staff
- Geofencing or location logging (only if justified and lawful)
2) Auditability
- Immutable logs of edits and approvals
- Exportable reports
- Role-based access control
3) Integration
- Payroll and HRIS integration (avoid double entry)
- SSO (Azure AD/Okta)
- Reporting exports for finance/compliance
4) Operational controls
- Reminders and nudges (e.g., end-of-day prompts)
- Exception workflows (missed punch)
- Approval SLAs and escalations
5) Privacy-by-design
- Minimize data collection
- Configurable retention
- Data access logging
GDPR and privacy considerations (don’t leave this to the end)
Time registration is personal data processing. Common risk areas include:
- Over-collection (tracking location when not necessary)
- Excessive retention
- Broad access (too many admins/managers)
- Using time data for performance surveillance without appropriate governance
Operational best practices:
- Define the purpose clearly (compliance, payroll accuracy)
- Document the legal basis and data processing activities
- Apply least privilege access
- Set retention aligned with legal obligations
- Train managers on appropriate use
In many organizations, the success of time registration hinges on trust. Privacy mistakes can create resistance and reputational risk.
Social dialogue and change management
Even if the requirement is legal, adoption is human. Plan for:
- Works council / employee representation communication (where applicable)
- Clear employee-facing guidance (what to do, why, how)
- Training for managers on approvals and exceptions
- A pilot period to identify friction and edge cases
A practical roadmap to 2027
Phase 1: Discovery (now)
- Segment workforce and working patterns
- Document current processes and pain points
- Identify systems of record (HRIS, payroll, scheduling)
- Define requirements (audit, privacy, integration)
Phase 2: Selection and design
- Shortlist solutions (HRIS module vs specialized tool)
- Define workflows (entry, approval, correction)
- Define data model and reporting requirements
- Define privacy controls and governance
Phase 3: Pilot
- Pilot with one department and one operational group (e.g., office + field)
- Measure completion rates and correction rates
- Gather feedback; refine policies and UX
Phase 4: Rollout
- Train managers and employees
- Set clear deadlines and support channels
- Monitor adoption and exceptions
Phase 5: Stabilize and evidence
- Ensure audit reports are reliable
- Run internal “inspection drills” (can you export evidence quickly?)
- Review privacy controls and access logs
Risks to plan for
- Low adoption: solved by UX, nudges, and manager accountability.
- Manager overload: solved by sensible approval frequency and exception-based approval.
- Privacy pushback: solved by minimization, transparency, and governance.
- Integration failures: solved by early technical validation and clear data ownership.
Final thought
Time registration compliance is ultimately an operational capability: accurate data capture, consistent processes, and trustworthy governance. Start early, segment intelligently, and build a system that’s defensible in an audit and usable every day.