Skip to content
SteadyOn SteadyOn SteadyOn

Run a recurring action

Plenty of safety work is a rhythm, not a one-off — test the alarm monthly, service the harness every 90 days, check the first-aid kit each week. SteadyOn models these as a recurring action: one live occurrence at a time, with the next created when you close the current one. For the model behind this, see Recurring items — how scheduling works.

Make an action recurring

Section titled “Make an action recurring”

When you create an action, set the Repeat options (also available on the Assign tab of any existing action):

  • Frequency — Does not repeat (the default), or one of Daily, Weekly, Fortnightly, Monthly, Quarterly, Every 6 months, Annually, Every 2 years, or Custom date. Pick a repeating frequency and SteadyOn shows a live preview of the next due date (“Next: Mon 16 Jun”) so the cadence is clear before you save.
  • Basis (under Advanced) — how the next date is calculated:
    • Repeat on a fixed schedule (anchor) — the next due date counts from the previous due date, so the series stays pinned to the same calendar rhythm even if you finish late. The monthly alarm test stays on the 1st. This is the usual compliance pattern.
    • Repeat a set time after completion (recent) — the next due date counts from the day you actually complete it (“service every 90 days after the last service”). Use this when the gap matters more than the calendar slot.

Custom date lets you hand-enter each next date when you close the occurrence — there’s no automatic preview.

Advance the series

Section titled “Advance the series”

A recurring action doesn’t pre-fill a calendar. It advances when you close the current occurrence, using the schedule-next panel on the Assign tab:

  • Complete — marks this occurrence done and immediately creates the next one. The proposed next due (and scheduled) date show as editable fields, so you can nudge an awkward date before confirming.
  • Complete without repeating — completes it and ends the series. Use this for “that was the last time”.
  • Skip — closes this occurrence as Skipped (its own status and badge) without completing it, but still schedules the next one. For “site was shut this week — the check resumes next week”. A skip always advances on the fixed-schedule basis.
  • Cancel — ends the whole series; no next occurrence is created. The cadence rule stays on the row, so you can re-arm it by hand later.

After completing or skipping, use View next → to jump to the new occurrence.

What carries over

Section titled “What carries over”

Each new occurrence inherits the title, description, type, priority, assignee, site, and the recurrence rule. Notes and attachments start empty — they record what happened that time, so last month’s photo doesn’t carry forward. Any linked items (a hazard, an inspection) move to the new live occurrence.

Finding recurring actions in the list

Section titled “Finding recurring actions in the list”
  • A Repeat column and a Recurring badge mark series, showing the cadence and occurrence number (e.g. Weekly · #3).
  • Past (superseded) occurrences are hidden by default. A “N past hidden — show” toggle by the result count reveals them, dimmed. The choice is remembered on your device, and exports follow whatever’s visible.
  • The detail page carries a series strip — Recurring occurrence #N with ← Previous / Next → — to step through the history.

A recurring action only advances when someone completes or skips it. If nobody actions it, no future occurrence appears — it simply goes overdue. That’s deliberate: the schedule stays honest about what’s really outstanding.

See also

Section titled “See also”