No messages at eleven at night: the right to disconnect and communication windows

No messages at eleven at night: the right to disconnect and communication windows

France has just turned into an obligation what until now was a best-practice recommendation: the delivery of information in digital work environments and school management software is suspended by default from 8pm to 7am, and from Friday at 8pm until Monday at 7am. This is not a school policy: it is a requirement about how the tool itself must behave.

The framework in Spain

Spain has no equivalent mandate with fixed hours, but the problem is identical and the legal framework already brushes against it from two directions:

• Article 88 of the data protection act: recognises the right to digital disconnection for all employed staff and leaves its implementation to collective bargaining or an internal policy.
• Working time records: require documenting hours worked, which makes it hard to argue that answering messages at eleven at night is not work.

What is interesting is that this is not a problem a memo asking for common sense can solve. It is a product problem.

Why good intentions don't work

Almost every school that has tried to tackle this has done it the same way: a recommendation at a staff meeting not to write out of hours. It fails for a structural reason:

• A tutor preparing lessons on a Sunday afternoon will write on Sunday afternoon, because that is when the context is in front of them. Asking them to note it down and send it on Monday is asking them to do the work twice.
• A head of studies who resolves something at ten at night would rather close it than carry it forward.

The framing error is placing disconnection on the shoulders of the sender. The recipient's disconnection should not depend on the sender's discipline. That is exactly where the tool can do what goodwill cannot: let people write when they can and deliver when appropriate.

The three windows to define

An operational policy distinguishes three flows, because they do not get the same treatment:

• School to families: the easiest to bound and the one that generates most noise if left unbounded. Circulars, notices, payment reminders and absence alerts. A reasonable window runs from 08:00 to 19:00 on school days, and anything written outside it queues until the next opening.
• Families to school: they will write at any hour and it is legitimate that they do. What needs managing is not their sending but the expectation of a reply. An automatic acknowledgement confirming receipt and stating office hours resolves 90% of the friction, because the problem is rarely the delay and usually the silence.
• Internal, between staff: the most delicate flow because it touches the employment relationship. Here the window should be negotiated, not imposed, and should distinguish between what is sent and what requires a reply.

The exception channel

No disconnection policy survives without a clear procedure for urgent matters, because in a school urgent matters exist: an accident on a trip, a serious conduct incident, the activation of a safeguarding protocol.

The usual solution is to separate channels by nature rather than by hour. The platform handles routine matters, with its time windows, and the phone is reserved for the urgent. That separation has a very useful side effect: when the phone rings out of hours, everybody knows it matters. When everything arrives on the same channel at any hour, nothing seems urgent and everything interrupts.

Automated sends are the blind spot

This is where most schools fail without realising. A policy is agreed for communications written by people and the ones generated by the system are forgotten:

• An unpaid invoice reminder at 23:40 is technically impeccable and humanly terrible.
• An absence alert at seven on a Sunday morning triggers a worried call from the family.
• A grade notification published at midnight produces exactly the kind of family conversation nobody wants to provoke.

The rule is simple: time windows apply equally to automated and manual sends, without exception. And it is worth reviewing overnight processes in particular, which are usually scheduled in the small hours for technical rather than communication reasons.

How to introduce it without it feeling like a restriction

Three steps that work in this order:

• First, measure. Before setting any window, look at when messages actually go out. Most schools discover that between 10% and 20% of their communications leave outside reasonable hours, and that figure makes the conversation far easier than any argument.
• Second, agree the window with staff rather than announcing it. Disconnection that is imposed reads as control; disconnection that is agreed reads as protection.
• Third, configure it in the system rather than trusting it to memory. If the window exists only in a document, it is breached within three weeks.

Case study (Spain)

A school with two stages reviewed its sending data before deciding anything and found a clear pattern: 17% of communications to families went out after 20:00, and almost half of that share were automated payment reminders scheduled overnight.

The measure with the greatest impact was not restricting anybody: it was moving the execution time of automated processes to 09:00 and enabling queuing for manual sends outside the window. Teachers carried on writing whenever they wanted; families stopped receiving messages at odd hours.

The second change was an automatic reply to incoming messages out of hours stating when they would be dealt with. Complaints about unanswered messages fell without anybody replying any faster, because the real problem had never been the delay but the uncertainty.

Conclusion

The right to disconnect has stopped being a wellbeing debate and become a product obligation, first in France and foreseeably elsewhere after. A school does not solve it by asking staff for goodwill: it solves it with a tool that separates the moment of writing from the moment of delivery, applies the same rules to automated and manual messages, and keeps a clean channel for what is genuinely urgent.

Edena lets you schedule sends, define communication windows by message type and queue anything written out of hours, including automated payment and attendance alerts. Book a demo and we will configure your school's time window with you.