Scheduling AI availability around Shabbos and Yom Tov

Let us be clear about scope at the outset. The halachic questions around technology and Shabbos are real, they are not simple, and they belong to your rav. Nothing here is a psak and nothing here should be read as one.

What this covers is the practical layer underneath: if a family or a school has decided a tool should be unavailable over Shabbos and Yom Tov, what does a scheduling feature have to get right to actually deliver that? More products get this wrong than you would expect.

Why a weekly window is not enough

Most parental-control scheduling offers a repeating weekly pattern: these hours, these days. That handles Shabbos approximately and Yom Tov not at all.

• Shabbos begins and ends at different times each week, and by a different amount depending on latitude. A fixed Friday cutoff is either early most of the year or late some of it.
• Yom Tov does not fall on the same weekday each year, so no weekly repeating rule expresses it.
• A two-day Yom Tov adjacent to Shabbos produces a three-day period that no weekly pattern describes.
• Chol hamoed sits between, and a family may want different treatment.

So a genuinely useful implementation needs either a calendar the product understands, or the ability to set a specific one-off period — and honestly, most products have neither.

The timezone problem, which is not optional

A window like "unavailable from 18:00 Friday" is meaningless without knowing whose clock. If a product stores the hours but not the zone, it evaluates them against its server's clock — and a family several hours away gets a window at the wrong time of day, every single week.

This is a common and quiet bug. The setting saves, the interface looks right, and the enforcement happens at the wrong moment. It is worth testing directly: set a window that should be active now and confirm the tool is actually unavailable.

The zone also has to be set by the adult and stored on the server. If it is taken from the child's device, a child who changes their device timezone changes the window.

What enforcement has to look like

For a scheduled unavailability to mean anything:

• It has to be checked on the server when a request is made, not counted down by an app. A second device otherwise has its own idea of the time.
• It has to apply to every tool, not only chat. A window that stops conversation but permits image generation is not a window.
• It should say why. A child who hits a silent failure concludes the product is broken; one who is told a guardian set these hours knows a boundary exists and who to ask.
• The child must not be able to change it, including indirectly through a device setting.

What a schedule cannot do

It governs one product. A phone with other applications on it is not addressed by any setting inside a single tool, and it would be dishonest to imply otherwise.

A scheduled window makes one tool behave the way a family has decided it should. Whatever else is on the device is a separate conversation, and mostly not a technical one.