Schedule Repetition Types
Schedule repetition types control how a recurring schedule resets after each completion — specifically, when the next due date is set. Choosing the right repetition type ensures that scheduled work lines up with how your organization actually operates.
Key point: The same three repetition types apply across Equipment Schedules, Inspection Schedules, and Pig Schedules — understanding them once means you understand them everywhere.
Why Repetition Types MatterThe repetition type determines:
- When the next occurrence becomes due after a completion
- What happens if a schedule is missed entirely
- How flexible the schedule is in accommodating real-world timing
Choosing the wrong type can cause schedules to drift off-cycle, create false overdue flags, or miss the intent of regulatory or operational requirements.
The Three Repetition TypesDynamic
How it works: The next due date is calculated forward from the date the schedule was actually completed.
Example: An engine service is set to run every 90 days (dynamic). If it was last completed on March 1, the next due date is May 30. If it was completed late — on March 15 instead — the next due date is June 13, not May 30.
Use when: The schedule should always have the full interval between completions, regardless of when the last one was done. Most preventive maintenance schedules use this type.
Static
How it works: The next due date always resets to a fixed calendar day — typically a specific numbered day of the month (for example, the 1st, 15th, or last day). This fixed day forms the "anchor point" for the schedule, and is used regardless of whether the schedule repeats on a weekly, monthly, or yearly basis (depending on the selected frequency and frequency type). Unlike Window schedules, Static schedules let you consistently require tasks to be completed on, say, the 3rd of every month or the 15th of June each year.
Example: If you set a monthly static schedule to be due on the 15th, it will always be due on the 15th of the month–whether it is completed early or late. The next due date remains set for the 15th of the following month. This is useful for deadlines like reporting dates or billing cycles.
Completing a static schedule early: A static schedule moves on to the next period when it is completed on or after its due date, or at any point inside its warning period. If it is completed earlier than that, the work is still recorded but the due date does not move — the schedule stays due on its original date. This is deliberate: it stops a run of early completions from walking the schedule permanently off the calendar day it is supposed to land on. If a schedule genuinely needs the full interval between completions, it should be a Dynamic schedule instead.
Month lengths: If the anchor day does not exist in a given month — for example the 31st in a 30-day month — the schedule falls back to the last day of that month. Setting the anchor to the last day of the month handles 28, 29, 30, and 31-day months automatically.
Use when: Choose a static repetition type when work must always be due on a predictable, fixed day each period—regardless of when it’s completed—such as for regulatory requirements, billing cycles, or any scenario where a fixed date is important.
Window
How it works: The schedule is tied to a fixed period — month, quarter, 6 month, or year. The schedule opens at the start of the period and is due at the end. It can be completed any time during the open window.
Key behaviour:
- The schedule becomes visible to operators as soon as its window opens, not when a warning period starts. This is the biggest day-to-day difference from Dynamic and Static, and it is why a Window schedule can appear in the Upcoming list long before its due date
- The schedule is never flagged as overdue while its window is still open
- If the window closes without a completion, the record is saved as delinquent — permanently marking that the period was missed — and a new window opens automatically
- The window frequency is editable (e.g., a quarterly window can be changed to monthly)
Example: A quarterly safety audit uses a Window schedule. The window opens January 1 and closes March 31. Operators can complete it any time in Q1. If it isn't done by March 31, the Q1 record becomes delinquent and Q2 opens automatically.
Use when: The schedule must be completed within a period but has flexibility within that period — common for regulatory audits, quarterly inspections, and annual certifications.
Quick Comparison| Type | Next due date set from | Becomes visible to operators | Can go overdue? | Missed period recorded as |
|---|---|---|---|---|
| Dynamic | Actual completion date | Inside the warning period | Yes | Overdue / missed |
| Static | Fixed calendar point | Inside the warning period | Yes | Overdue / missed |
| Window | End of next period | As soon as the window opens | No | Delinquent |
The repetition type controls when a schedule starts showing up for operators, not just how its due date is calculated.
Dynamic and Static behave identically here. The schedule appears in the Upcoming list once it is within its warning period — the number of days before the due date set on the schedule — or once it is past due. Outside that window it is not shown, even though it exists and is active.
Window does not use the warning period to decide visibility. It appears as soon as its window opens and stays visible for the whole period. For a multi-year window this can be years ahead of the due date, which is expected behaviour rather than a fault. If a Window schedule appears in Upcoming with a due date far in the future, that is the window being open, not an error.
One consequence worth knowing: because Dynamic and Static visibility is driven entirely by the warning period, an unusually large warning period will make any schedule appear early regardless of its type. If a schedule is showing up sooner than expected, check its warning period first.
Where Repetition Types ApplyThe same three types are available across:
- Equipment Schedules - PM, calibrations, and general equipment maintenance
- Inspection Schedules - Recurring inspections on tanks, wells, plants, pipelines, and other items
- Pig Schedules - Pipeline pigging frequency tracking
- If your schedule should always allow the full interval between completions, use Dynamic
- If your schedule must hit the same calendar date every period, use Static
- If your schedule has a flexible completion window within a period and you want missed periods tracked as delinquent (not overdue), use Window
- If operators are asking why a schedule with a distant due date is already in their list, check the repetition type before anything else — a Window schedule is open for its whole period by design
- When in doubt about which type to use, contact your EZ Ops administrator — changing the repetition type after a schedule has been running will affect how future due dates are calculated
Remember: The repetition type is set when a schedule is created. Understanding the difference between Dynamic, Static, and Window ensures your schedules reflect how the work actually needs to happen — not just when the system expects it.