Planning

Who works where and when: assignments to publish, absences to decide, and alerts before chaining two shifts without rest.

In preparation Create an account

Planning keeps an organization's staff planning: resources (the people being planned), sites, assignments to a post or a mission between two times, with their break, and absences. An assignment starts as a draft, seen only by planners, then is published so the person sees it, or is cancelled; nothing is deleted.

Rules point out what is wrong before publication. An overlap with another assignment or with an approved absence blocks saving. A rest period that is too short between two assignments, a day or a week that is too long, a missing break are saved with a warning. The rules are replayed at publication.

The starting thresholds (11 h of rest, 10 h per day, 48 h per week, a 20-minute break beyond 6 h) are indicative values, adjustable per organization, to be validated against your collective agreement and the applicable law. A planning without alerts is not thereby validated with regard to labour law: Planning helps to spot issues, the responsibility remains the employer's.

A member sees their published assignments and requests their absences; a planner manages the planning and decides on absences, never their own; an administrator sets the thresholds and the roles. AI agents and Workflows go through nine MCP tools subject to the same rights and the same rules, and each change to an assignment or an absence can be sent as an event to Workflows.

Planning is a web application, in preparation: not online yet, with no desktop application and no Android application. Everything is in UTC, absences are counted in whole days, and neither public holidays nor night work are taken into account.

Planning is in preparation. It will join the Etrebil subscription catalogue when it is released.

Every feature of Planning

64 features in 10 areas

The week grid

Displays a week from Monday to Sunday: one row per resource, one column per day, with the current day highlighted.
Moves to the previous or next week, or back to the current week.
Shows each assignment as a card: times, post or mission, site, status, and the mention +1 d when it runs past midnight.
Places requested and approved absences in the cells of the days they cover, with their type and status.
Totals each resource's week, net of breaks, against its contract hours.
Shows the rule alerts on each card; a planner publishes or cancels the assignment from its card.
For a member, it becomes My planning: only their published assignments appear.

Assignments

An assignment places a resource on a post or a mission, at a site or not, between two times, with its break in minutes.
It starts as a draft, seen only by planners, then is published so the person sees it, or is cancelled.
A cancelled assignment no longer counts for the rules or the totals; nothing is deleted.
The Check the rules button shows the alerts for an entry before creating it.
An end time before the start time carries the assignment over to the next day; an assignment lasts 24 h at most.
The database itself refuses an end that is not after the start, a break longer than the slot, and any change to a published or cancelled assignment.
An assignment created by a workflow carries its origin, for example a Field Service intervention, visible on its card.

Rest and duration rules

Blocks saving an assignment that overlaps another assignment of the same resource: nothing is written.
Likewise blocks an assignment that covers an approved absence.
Warns of a rest period that is too short before or after the nearest assignment, including between two back-to-back shifts.
Warns of a day or a week that is too long, in durations net of breaks.
Warns of a missing or too short break beyond a given assignment duration.
Saves the warnings with the assignment and displays them; they do not prevent publication.
Replays the rules at publication: an absence approved since creation blocks the publication of the draft.
At the exact threshold, no alert. The day is the UTC day of the start, the week the ISO week, Monday to Sunday.

Absences

Absence request: first and last day included, type (leave, sickness, other), optional reason.
A member requests for themselves; a planner, for any resource.
Refuses a request that overlaps another absence, requested or approved, of the same resource; an absence lasts 366 days at most.
A planner approves or refuses, only once: a decided absence no longer changes.
Nobody decides on their own absence, whatever their role: another planner or administrator takes care of it.
An approved absence blocks any new assignment that covers it; those that already existed remain, flagged as blocking alerts.
Lists absences, most recent first, filtered by status; a member sees only their own.
Displays the reason for the decision when one was given.

Resources and sites

A resource is a person being planned: a name, and contract hours per week given for information.
Linked to the person's Etrebil account, it opens their published assignments and absence requests to them; without a link, a member sees nothing, and the page says so.
A resource can be edited, deactivated and reactivated: once deactivated, it leaves the grid and the choice lists, its history remains.
A site has a unique name and an optional address; it can be deleted as long as no assignment uses it.
The Resources and sites page is reserved for planners and administrators.

Team, roles and settings

Three roles: member, planner, administrator; each has the rights of the previous ones.
The people of your Etrebil organization appear on their first visit, with no account to create; the organization's owners and administrators are administrators by default.
An administrator changes roles, suspends or restores a colleague; the organization always keeps an active administrator.
A suspended colleague, or a person without a license, can only consult; a banner says so.
The settings set five thresholds: minimum rest, maximum duration per day and per week, the duration beyond which a break is expected, and the minimum length of that break.
Starting values: 11 h of rest, 10 h per day, 48 h per week, a 20-minute break beyond 6 h; everyone can read them, only administrators change them.
Each organization sees only its own data; rights are checked by the services, not just hidden on screen.

AI agents and workflows

Nine MCP tools, which go through the same services as the pages: same rights, same rules.
Reading: list the resources, read the planning of a period, find the available resources, list the absences, report the alerts of a period.
Writing: create an assignment as a draft, publish it, cancel it, approve or refuse an absence with a reason.
Creation by an agent is refused if a rule blocks it, and returns the warnings; availability and alerts are reserved for planners.
Instants are exchanged in ISO 8601, in UTC by default; a time offset is converted. A period read covers 62 days at most.
Six events to Workflows (assignment created, published, cancelled; absence requested, approved, refused), written in the same transaction as the change and never for a refused change.
No HTTP API is open to other applications: they go through the MCP endpoint, with an agent token.

Tutorials

Plan an assignment: the resource, the post, then creation as a draft.
Request an absence: the first day, the last, then sending the request.
The tutorials guide you step by step on the application's screens.

On your devices

Web: the complete application, with single sign-on through your Etrebil account, license and data on the server.
No desktop application (Windows, Linux) and no Android application for now.
The common shell of Etrebil applications: modules on the left, folded into a drawer on phones, search across modules, feedback and theme in the top bar.

Good to know

The thresholds are indicative starting values, to be validated against your collective agreement and the applicable law; they do not replace the employer's responsibility.
A planning without alerts is not thereby validated with regard to labour law: Planning helps to spot issues, it does not qualify anything.
Everything is in UTC, with no time zone specific to the organization. Absences are counted in whole days, without half-days.
Does not take into account public holidays, weekly rest, night work, annualized part-time work or category-specific agreements.
Two shifts on the same day separated by a few hours trigger the rest warning.
A draft cannot yet be edited from the grid: you cancel it and create another one. The assignment log is kept in the database but cannot yet be viewed on screen.
Not available yet: notifying the people concerned, import and export, week templates.
The on-screen rendering has never been seen, the forms and tutorials have not been played in a browser, and the MCP endpoint has not been called with a real token.
Never deployed nor tried with a real organization or a real Workflows; the rules and their messages have been reviewed neither by a lawyer nor by staff representatives.