A staff extranet is a secure web portal, accessible from any browser, that allows employees to view and modify their schedules without going through a manager. Its primary function is not to replace a complete HR software, but to centralize scheduling information in a single point, shared between the company and its teams.
Availability windows and right to disconnect in the scheduling extranet
Competitors talk about planning, workload distribution, and software. None address the legal framework that directly constrains how a schedule must be constructed: the right to disconnect.
Since 2017, Article L2242-17 of the Labor Code requires companies with 50 or more employees to negotiate the concrete terms of this right as part of the annual negotiation on quality of life and working conditions (QVCT). Specifically, the employer must define contact time slots, specify the handling of messages outside of hours, and qualify what constitutes an emergency.
An effective staff extranet translates these obligations into the interface itself. Availability slots appear on the schedule, notifications are blocked outside the defined time frames, and on-call duties are visually identified. Without this layer, the schedule remains a simple time table that ignores regulations.
Case law has clarified one point: the employer is not responsible if an employee connects on their own initiative outside of working hours, but any active solicitation during a break engages the company’s liability. Therefore, the extranet must record who initiated a schedule change and at what time.
For organizations in the personal services sector, it is possible to access the A2micile employee extranet to directly manage their availability and interventions from a dedicated portal.
Staff extranet and remote work: accounting for actual working time
Remote work has created a blind spot in schedule management. When an employee works from home, the company must still account for their actual working time. An extranet that only manages on-site presence becomes obsolete as soon as part of the team is working remotely.
An adapted portal offers a declarative accounting of working time in remote work, with timestamps for the start and end of sessions. This is not surveillance: the legal framework requires hours to be accounted for without resorting to a disproportionate control mechanism.
The difficulty lies in the articulation between on-site days and remote days. The schedule must clearly display the planned workplace for each slot, and the employee must be able to report a change (switching from on-site to remote, for example) without waiting for hierarchical approval that would come too late.
Perception gap between management and staff on schedule management
A recurring observation in HRIS feedback is that management believes the planning tool works well, while employees on the ground find it inadequate. This perception gap between management and end users explains why some extranets are deployed and then abandoned within a few months.
The problem often stems from three specific points:
- The interface is designed for the HR manager, not for the employee checking their schedule on a phone between two tasks
- The validation times for changes are too long, pushing teams to revert to SMS or messaging exchanges
- The displayed information does not match the reality on the ground (theoretical slots instead of the hours actually practiced)
An effective extranet is tested with end users before deployment. If an employee takes more than three actions to check their weekly schedule, the ergonomics are problematic.
Multi-portal centralization: avoiding the dispersion of planning tools
In many companies, planning is scattered across multiple tools: a spreadsheet for schedules, a messaging system for slot exchanges, one HR software for leave, another for on-call duties. The employee navigates between three or four interfaces to reconstruct their week.
The staff extranet makes sense when it becomes the single entry point. The schedule, leave requests, slot exchanges between colleagues, and related documents (job descriptions, specific instructions) are accessible from a single login.
This centralization has a concrete effect on data reliability. When scheduling information passes through multiple channels, errors in transcription and contradictory versions multiply. A single portal eliminates these duplicates and ensures that the schedule displayed to the employee is the one validated by the manager.
Technical criteria for evaluating a scheduling extranet
Before choosing or migrating to a new tool, several points deserve verification:
- Mobile accessibility without the need for native app installation (a browser is sufficient)
- Real-time synchronization between manager modifications and employee display
- Differentiated rights management: the employee sees their schedule and that of their team, the manager sees the entire department
- Data export to the payroll software, to avoid double entry of hours
The last criterion, often overlooked during selection, becomes the first irritant in use. An extranet that does not communicate with the payroll system generates re-entry work that negates the initial time savings. Checking technical compatibility before deployment remains the most cost-effective precaution in the long run.
