Schedules and submissions

My schedule shows your approved working days and absence. Propose a new seven-day schedule from a date, or an absence period. No reason for absence is requested or stored. A proposal counts only after a planner approves it. You can withdraw a pending proposal. The latest twenty decisions are shown.

Team schedule lets planners choose an employee, set the seven weekdays with hours and breaks, and add or remove absence periods. Unknown availability remains unavailable. Review submissions shows pending proposals with the full week or period. Approve or reject; the employee receives an in-app notification. New submissions notify planners in the app. These notifications never send email, SMS or WhatsApp.

A bureau may assign the Field service role. It grants access to the employee's own day route, schedule and notifications. It does not grant access to colleagues or customer administration. A planner first links the user to an active calendar employee.

Via MCP and the director

• Own request: planning_opgave_indienen submits your own working days or absence and planning_opgave_intrekken withdraws an open request of your own (right planning.rooster_eigen). It is a proposal that a planner reviews. Absence has no reason and no type: that is health data and there is no field for it.
• Proposing a schedule: planning_rooster_voorstellen (planning.beheren) proposes a new schedule for an employee from a date. The current schedule does not change; the proposal waits under Requests until a person reviews it.
• Reviewing: planning_opgaven_lezen shows what is waiting. planning_opgave_beslissen is a proposal that a person signs: the director never decides about a person by itself.
• Reading: planning_werktijden_lezen and planning_bezetting_lezen. Someone who does not work is absent and never free; unknown stays unknown.