Skip to main content
Maintenance can be applied at different scopes, allowing you to model real operational interruptions without manually adjusting docks, zones, or equipment.

​
What Is a Maintenance Window

A Maintenance Window represents a planned period of downtime during which scheduling capacity is reduced or blocked. Maintenance windows are used to account for:
  • Facility downtime
  • Planned dock closures
  • Zone-level operational interruptions
  • Equipment or infrastructure maintenance
During an active maintenance window, Yardo automatically enforces availability restrictions during scheduling.

​
Maintenance Scopes

Maintenance windows can be applied at different scopes depending on the impact of the downtime.

​
Location-wide

Applies to the entire facility. Use location-wide maintenance for:
  • Full facility shutdowns
  • Power outages
  • Network or system maintenance
  • Holidays or planned closures
Location-wide maintenance blocks all scheduling capacity for the defined time window.

​
Zone

Applies only to a specific zone within a location. Use zone-level maintenance for:
  • Area-specific repairs
  • Specialized dock areas (e.g. refrigerated zones)
  • Temporary access restrictions
Only dock doors assigned to the zone are affected.

​
Dock Door

Applies to a single dock door. Use door-level maintenance for:
  • Individual dock repairs
  • Door equipment servicing
  • Temporary door closures
Other doors at the location remain available.

​
How to Create a Maintenance Window

Only administrators can create maintenance windows. To create a maintenance window:
  1. Navigate to Maintenance
  2. Select the maintenance scope (location-wide, zone, or door)
  3. Enter a title
  4. Confirm the time zone
  5. Add an optional description
  6. Select the date, start time, and end time
  7. (Optional) Enable recurring maintenance
  8. Click Add maintenance window
Maintenance windows take effect immediately once saved.

​
Time and Time Zone Behavior

Maintenance windows always use the location’s time zone.
If the end time is earlier than the start time, the window automatically extends into the next day.
This allows you to schedule overnight maintenance without manual date adjustments.

​
Recurring Maintenance

Recurring maintenance windows can be created using a repeating schedule. Examples include:
  • Weekly preventative maintenance
  • Monthly inspections
  • Regular cleaning windows

​
How Recurrence Works

  • Recurrence is defined using standard scheduling rules
  • Supported frequencies include daily, weekly, and custom patterns
  • A recurrence end date can be specified or left open-ended
Recurring maintenance creates future windows automatically and applies the same scheduling restrictions.

​
Impact on Scheduling

During a maintenance window:
  • New appointments cannot be scheduled in the affected scope
  • Existing appointments may be flagged or require rescheduling
  • Availability is recalculated in real time
Maintenance is enforced in combination with:
  • Location operating hours
  • Zone capacity rules
  • Dock door availability
  • Equipment constraints

​
Viewing Upcoming Maintenance

Upcoming maintenance windows are listed chronologically and can be filtered by scope. This view helps planners anticipate reduced capacity and adjust schedules proactively.

​
Editing or Removing Maintenance Windows

Maintenance windows can be edited or removed by administrators. Changes take effect immediately and may impact scheduling availability. Use caution when modifying maintenance windows that overlap with existing appointments.

​
Best Practices

  • Use location-wide maintenance sparingly
  • Prefer zone or door-level maintenance for targeted downtime
  • Schedule recurring maintenance for predictable operational interruptions
  • Communicate maintenance windows in advance to avoid last-minute rescheduling

​
Summary

Maintenance windows provide a structured way to account for planned downtime. By applying maintenance at the appropriate scope, organizations can preserve scheduling accuracy while minimizing operational disruption.