How do I create a repeating maintenance schedule that skips nonworking days?
Quick answer
First decide whether maintenance repeats after a number of calendar days or working days. Then define the workweek and any dates to exclude, calculate each planned date using that calendar, and review dates that shift or conflict with other work. In Excel, WORKDAY.INTL can calculate dates using a chosen weekend pattern and a list of holidays, but you still need to set the maintenance rule and review exceptions yourself. [S1]
The question, the details, the next step.
I need a repeating maintenance schedule, but I don’t want tasks landing on days we don’t work. What should I decide first?
Decide what the interval means. “Every 10 days” can mean 10 calendar days, even if the next date falls on a nonworking day, or 10 working days, counting only days your team works. Those rules produce different schedules, so write down which one you intend before calculating dates.
Next, define the working calendar rather than assuming a standard Monday-to-Friday week. List the days your team does not work, plus any dates you want excluded, such as planned closures. Choose a policy for a date that lands on an excluded day: move it to the next working day, move it to the previous one, or flag it for review. The choice is yours; a date-calculation function cannot decide your maintenance policy.
A reusable rule might read: “Repeat every [number] [calendar/working] days from [starting date]. Do not schedule on [nonworking days] or [listed closure dates]. If a planned date is excluded, [move forward / move backward / review manually].”
Can I calculate those dates in Excel, including a workweek that isn’t Saturday and Sunday?
Excel’s WORKDAY.INTL function calculates a date a specified number of working days before or after a starting date. Its optional weekend setting lets you define which days count as nonworking, and an optional holidays range can exclude listed dates. The documented default weekend is Saturday and Sunday, so choose a weekend pattern that matches your calendar instead of relying on that default. [S1]
For example, suppose—purely as an illustration—the start date is Friday, Saturday and Sunday are nonworking, there are no listed holidays, and your rule is “one working day later.” The resulting date is Monday. If your actual workweek differs, set that pattern explicitly. [S1]
Keep the distinction between the calculation and your schedule rule clear: WORKDAY.INTL handles dates based on the calendar settings you provide; it does not decide whether maintenance repeats every calendar interval or working-day interval, nor how your team should approve a shifted date. [S1]
How do I set up the repeating rule so the schedule doesn’t drift or become confusing?
Write the recurrence in one consistent way and keep the original anchor date visible. For a working-day interval, calculate each occurrence from the previous scheduled date using the chosen number of working days. For a calendar-day interval, add the calendar interval, then apply your stated excluded-day policy. Don’t switch methods midway without recording the change; otherwise, later dates may no longer follow the original rule.
A simple schedule layout is:
- Task: [maintenance task]
- Anchor date: [date]
- Recurrence: every [number] [calendar/working] days
- Nonworking days: [days]
- Excluded dates: [list or maintained range]
- If excluded: [move forward / move backward / review]
- Next planned date: [date]
- Review status: [pending / approved / changed]
If using a spreadsheet, keep the workweek pattern and excluded-date list somewhere visible, and check that the date calculation uses them. WORKDAY.INTL can calculate from a start date with the selected weekend and optional holidays range; it does not create the recurrence policy or exception-review process for you. [S1]
What should I check when a scheduled date gets moved or clashes with another task?
Treat a shifted date as an exception to review, not as an invisible correction. Check why it moved, whether the new date is acceptable for that task, and whether changing it affects later occurrences under your chosen recurrence rule. If the right decision depends on the maintenance requirements or your organization’s procedures, route that decision to the responsible person rather than guessing.
For each exception, record the original date, proposed date, reason, decision, and who confirmed it using your organization’s normal process. Then update the schedule and make clear whether future dates still follow the original anchor or now follow the changed occurrence. That small note helps someone else understand the schedule without having to reconstruct the reasoning.
A practical checklist
Choose calendar-day or working-day intervals and record the anchor date.
List the actual nonworking days; do not rely on a default workweek.
Maintain the excluded-date list and confirm the date calculation uses it.
Set a clear rule for moving or reviewing dates that land on exclusions.
Review clashes and record the original date, proposed date, reason, and decision.
A few more useful answers
Does WORKDAY.INTL decide how often maintenance should repeat?
No. It calculates a date from a start date and working-day count using the selected weekend pattern and optional holidays range. You must define the recurrence rule and exception process. [S1]
What if our nonworking days change?
Update the calendar settings and excluded-date list, then review future planned dates for changes. Record when the calendar changed so reviewers can understand why dates shifted.
Should an excluded date move forward or backward?
Choose the direction that fits your maintenance policy and document it. If the appropriate choice is uncertain or depends on the task, flag the date for review by the responsible person.
Sources
References used for this guide.
- [S1] WORKDAY.INTL function support.microsoft.com · Checked