Holiday Management

Holiday Management defines non-working days used by business-day control, scheduling, due-date calculations, operational planning, and date-sensitive workflows.

Holiday setup should be maintained before a financial or operational period starts. Late changes can affect schedules and deadlines users may already have acted on.

Workspace Reference

Workspace	How Users Reach It	What Users Usually Do There
Holidays	Administration -> General Setup -> Holidays	Maintain holiday calendars, weekend rules, and specific holiday dates.
Calendar Policy And Fiscal Periods	Administration -> Financial Setup	Confirm business-day and fiscal-period behavior that holidays can affect.
Resource Capacity, Driving, Events, Inspections, Loans, And Payments	Service workspaces with schedules or due dates	Review scheduling, due-date, booking, lesson, inspection, and payment effects after holiday changes.

Holiday Calendars

A holiday calendar groups holiday rules for a country, region, tenant, business unit, or operating context.

Important calendar fields include:

• Calendar Code: a short uppercase reference such as UG_PUBLIC.
• Calendar Name: the user-facing name.
• Description: explains where the calendar should be used.
• Country: sets the country context.
• Weekend Days: the regular non-working days.
• Generate Weekends: determines whether weekends should be generated as non-working days.
• Active: controls whether the calendar is available for use.

When a country is selected, the form can suggest common weekend defaults. Review the suggested days before saving because some organisations operate on custom working calendars.

Holiday Dates

Holiday dates should include a clear name, date, and active status. Where a date is regional or service-specific, scope it carefully so it does not affect unrelated operations.

Examples include national public holidays, regional holidays, organisational shutdown days, and special service closure days.

What Holidays Affect

Holidays may affect:

• Business day opening and closing.
• Payment, collection, or repayment due dates.
• Scheduler expectations.
• Working-day calculations.
• Service availability.
• Resource scheduling.
• Operational planning and reporting.

Common Mistakes

• Creating one broad calendar when different regions follow different holidays.
• Forgetting to include weekends or using the wrong weekend pattern.
• Adding holidays after schedules have already been generated.
• Leaving expired or test calendars active.
• Applying a closure day too broadly across services.

Good Practice

Maintain holiday calendars annually, before users create large volumes of schedules. After updating holidays, review affected workflows such as business days, due dates, resource bookings, lessons, inspections, and payment schedules.