Recurring schedule exceptions for holidays

We've been using recurring work orders for our maintenance contracts—mostly monthly and quarterly service visits—and overall the team has found it to be a real time-saver. The challenge we're running into now is holiday scheduling.

We have several contracts that include specific day-of-week requirements (e.g., "first Monday of each month"). When that Monday falls on a federal holiday, our customers generally prefer we skip that week entirely rather than show up Tuesday. Right now, I'm manually reviewing the dispatch board at the start of each month and suspending individual jobs that fall on holidays, then remembering to reactivate them.

Is there a way to set a global holiday calendar that automatically pauses recurring schedules for those dates? Or at minimum, a way to bulk-suspend/recalculate recurring jobs around holidays without going one by one? The team is small and this manual review is becoming a real bottleneck at year-end when we're setting up the full January schedule.

Appreciate any guidance on current capabilities or recommended workflows.

Parents
  • Hi Paula—this is something that comes up fairly often in implementations I've worked on, especially for teams with strict SLA commitments around specific visit windows. Let me share what I've seen work best.

    In my experience, there are really three layers to think about here. First, there's the recurring work order engine itself, which is designed around interval-based scheduling (every 30 days, monthly on a specific date, etc.). That engine doesn't currently have a built-in holiday calendar you can reference, so it will continue generating instances regardless of holidays unless something intervenes.

    What I typically recommend is a combination approach. For the handful of customers with strict day-of-week requirements that can't flex, you can use the Pause Recurring Schedule option on individual work order series. This is found under the three-dot menu on any recurring parent work order—select Edit Series, then Pause Schedule with a date range. The key thing is that this pauses generation entirely, so if your pattern is "first Monday monthly" and you pause January 1-7, you won't get a January visit at all. That's usually what these customers want, but worth confirming.

    For customers who can flex slightly, there's another path. You can set the recurring pattern to "monthly on the first business day" rather than a fixed day, which will naturally skip weekends and holidays. This does require changing the pattern, which obviously needs customer agreement.

    The bulk approach you're looking for—where you define holidays once and have them respected across all recurring schedules—isn't available today, though I know it's been discussed. What some teams do as a workaround is export their recurring work order list via CSV export, identify which series have instances landing on holidays, then use the bulk edit feature to pause those specific series for the affected weeks.

    It's not fully automated, but it gets you down from individual job review to perhaps a dozen series to adjust per holiday. Happy to walk through the export format if that would help your process.

Reply
  • Hi Paula—this is something that comes up fairly often in implementations I've worked on, especially for teams with strict SLA commitments around specific visit windows. Let me share what I've seen work best.

    In my experience, there are really three layers to think about here. First, there's the recurring work order engine itself, which is designed around interval-based scheduling (every 30 days, monthly on a specific date, etc.). That engine doesn't currently have a built-in holiday calendar you can reference, so it will continue generating instances regardless of holidays unless something intervenes.

    What I typically recommend is a combination approach. For the handful of customers with strict day-of-week requirements that can't flex, you can use the Pause Recurring Schedule option on individual work order series. This is found under the three-dot menu on any recurring parent work order—select Edit Series, then Pause Schedule with a date range. The key thing is that this pauses generation entirely, so if your pattern is "first Monday monthly" and you pause January 1-7, you won't get a January visit at all. That's usually what these customers want, but worth confirming.

    For customers who can flex slightly, there's another path. You can set the recurring pattern to "monthly on the first business day" rather than a fixed day, which will naturally skip weekends and holidays. This does require changing the pattern, which obviously needs customer agreement.

    The bulk approach you're looking for—where you define holidays once and have them respected across all recurring schedules—isn't available today, though I know it's been discussed. What some teams do as a workaround is export their recurring work order list via CSV export, identify which series have instances landing on holidays, then use the bulk edit feature to pause those specific series for the affected weeks.

    It's not fully automated, but it gets you down from individual job review to perhaps a dozen series to adjust per holiday. Happy to walk through the export format if that would help your process.

Children
No Data