Configuration freeze

A freeze period is a date range in which the organization has decided not to touch configuration — a fiscal year end, another system's go-live week, an audit period. It is defined in settings under Configuration freeze.

Each period has three fields: From date, To date and Description. The description is what appears beside the dates everywhere the period is visible, so phrase it the way someone else will read it — "Fiscal year-end freeze", not "Freeze 3".

A freeze is global: it applies to all scheduling, not to one system. It can be edited or deleted at any time.

What it actually does

The period surfaces in four places:

Where	How
The calendar	A marker on every day in the range, with the period's name
The scheduling wizard	A warning under the date selection, with the period's name and range
The event editor	The same warning, when an existing window is moved into the range
The context panel	In the Window risks card as "Inside a configuration freeze", and in the Upcoming freezes and holidays card with a day count

The warning in the wizard is re-checked on every change to the window and does not appear when there is no overlap. If the check itself is unavailable, no warning appears at all — so an absent warning is not proof that the window is clear.

Holidays

Israeli public holidays are computed and shown on the calendar alongside freeze periods, with the same day marker. They are not entered by hand and need no maintenance, and a window falling on a holiday is flagged in the Window risks card.

The difference between the two: a holiday is a fact of the calendar, a freeze is a decision of the organization. Both are shown, neither blocks.

Every creation, edit and deletion of a freeze period is recorded in the audit log.