Separate the date from its operational effect
A holiday calendar identifies dates that may be used as exceptions in a Lexoh site’s configured rules. The date definition and the action taken on that date are separate: adding a calendar entry does not, by itself, establish a closure, free parking or permission to enter. Review the rules linked to that entry.
Start with the site’s approved operating calendar. Identify the location, time zone, year, exceptional dates and responsible administrator. A staff holiday, a public opening day and a special parking tariff can require different treatment on the same date.
Use the date patterns and controls available in your deployed version. The patterns below explain what to specify and test; they do not establish that every installation supports all eight patterns, automatic annual renewal or the same preview interface.
Inspect dates and linked rules
A label such as “annual closure” does not prove recurrence. Read the stored rule and inspect more than one year. Likewise, a correct next occurrence does not prove that later years, leap days or weekend adjustments are correct.
- Select the correct site or organization. Record each calendar entry’s name, identifier, status and recurrence definition.
- Compare the next generated date with the approved operating calendar. If a preview exists, check the relevant year and time zone rather than relying on a countdown alone.
- Find every schedule or pricing rule that references the entry. Identify whether changing or disabling it affects more than one entrance, zone or service.
- Look for duplicate entries, old one-time events and dependencies on other dates. Retain the current configuration before preparing changes.
Write the calendar policy before configuring it
- Give the entry a clear purpose and location; include the year for a one-time event. Record who approved the date and where it came from.
- Choose a supported date pattern that matches the intended policy. Set the year or recurrence, reference date, offset and range boundaries where applicable.
- Decide whether the calendar represents the actual date, an observed operating date or both. Record any weekend adjustment explicitly.
- Review the generated dates and associated rules in the supported test workflow. If an inactive or draft state is available, confirm its behavior before using it to stage the change.
- Activate through the authorized process and verify when the affected rules receive the update. Keep the previous settings and recovery procedure available.
Understand the date pattern you are testing
Fixed month and day
A recurring month/day pattern is different from a single date that includes a year. For February 29, define the intended non-leap-year behavior and check the installed system’s handling.
A numbered weekday in a month
Specify the month, weekday and occurrence, such as the third Monday. A fifth occurrence does not exist in every month; decide how the rule should handle that case.
The last weekday in a month
“Last Monday” is not equivalent to “fifth Monday”. A month may have only four Mondays. Test both four-occurrence and five-occurrence months.
A weekday before a reference date
Specify whether “before” is strictly earlier or includes the reference date when it is already that weekday. If the reference itself moves each year, confirm how it is supplied or calculated.
An offset from another date
State the base entry and signed offset in calendar days. Check whether the offset uses the original date or a shifted observed date. Review the effect of editing, disabling or removing the base entry.
A date range
Specify the start and end, their inclusion and the time zone. Check ranges that cross a month or year boundary and whether the range repeats. A three-day closure is not automatically a recurring annual rule.
A one-time date
Include the complete date and year. Verify that it appears only in the intended year and does not change future calendars after it has passed.
A supported formula
Use only a formula supported and documented for the installation. Record its inputs and compare several years with an authoritative calendar. Do not assume an arbitrary formula or a lunar-calendar calculation is available.
Check dates with reproducible examples
These are illustrative Gregorian-calendar calculations for testing date patterns, not statutory-holiday recommendations or verified outputs from the Lexoh application. Compare each expected result with the supported preview or test workflow.
| Pattern to check | Expected calendar result |
|---|---|
| Third Monday of February 2027 | February 15, 2027 |
| Last Monday of February 2027 | February 22, 2027 |
| Fifth Monday of February 2027 | No such date in that month |
| Last Monday of May 2027 | May 31, 2027 |
| February 29 in 2028 | Valid date; Tuesday |
| February 29 in 2027 | No such date in that year |
What an invalid-date case proves
A missing fifth weekday or leap day needs a deliberate policy. Check whether the system rejects the rule, skips the occurrence or applies another documented behavior. Do not replace the missing date with a different day without approval.
Test the linked action separately
After checking the date, test an ordinary day and an exceptional day at the same time. For access, verify the expected decision for eligible and ineligible records. For pricing, verify the selected rule and charge. Include the moments around midnight and any visit spanning the boundary.
Use weekend shifts only when the policy requires them
A “move to Monday” option, if available, is a date transformation. It is not proof that a statutory holiday must be observed on Monday or that a site should close. Confirm the applicable operating policy and check whether the original date remains active after the shift.
For Quebec employment-holiday questions, consult the CNESST’s list and conditions. Its guidance distinguishes official holiday dates and compensatory leave; a blanket weekend-to-Monday rule is not an adequate substitute. Have the responsible person approve the operating dates before entering them.
Reference: CNESST — Jours fériés au Québec. https://www.cnesst.gouv.qc.ca/fr/conditions-travail/conges/jours-feries/liste-jours-feries
A collision worth testing
Under an illustrative policy that moves both Saturday and Sunday to the following Monday, December 25 and December 26, 2027 both produce December 27, 2027. This is calendar arithmetic, not a holiday-observance recommendation. Check how duplicate resulting dates and overlapping linked rules are handled.
Original date or adjusted date
For a rule defined as one day after another event, determine whether the offset is applied before or after a weekend shift. Those operations can produce different dates. Record the intended order and verify the actual result.
Validate, publish internally and maintain the calendar
For multiple sites, copy a calendar only after checking location, time zone, operating policy and linked rules. A working configuration at one facility is not evidence that the same dates or exceptions are appropriate elsewhere.
- Review at least the intended year and the next relevant recurrence. Include weekend dates, leap-year cases, missing fifth weekdays and year-crossing ranges where applicable.
- Record the calendar definition, expected dates, generated dates, linked rules and test results. Resolve unexplained differences before activation.
- Verify access decisions and charges through an approved test process. Do not use an unannounced customer charge or a live permission change as a test.
- Confirm the effective configuration on affected services or devices. Communicate approved operating changes to the site team and update customer-facing hours or tariffs where needed.
- Review the calendar before the next operating season and after policy changes. Before deleting or disabling an old entry, inspect dependencies and retain the records needed to explain previous behavior.