Set Up a Recurring Job Schedule

Recurring Jobs creates repeatable work for a unit or common area. Set the cadence, local time, job subtype, and assignment policy once, then monitor the generated jobs.

What you will accomplish

By the end of this guide, you will be able to complete a recurring job schedule from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Confirm the unit and job subtype already exist.
• Decide whether generated jobs should be unassigned, assigned to a person, or assigned to a team.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open Recurring Jobs

Go to Cleaning Management > Recurring Jobs. Review existing rules first so you do not create a duplicate for the same unit and purpose.

Expected result: The schedule list and cadence filter are visible.

Step 2: Select Add recurring job

Open the creation form. Give the rule a label that describes the work, such as “Weekly linen room sanitation.”

Expected result: The rule can be recognized without opening it.

Step 3: Choose unit and subtype

Select the target unit or common area and the job subtype that controls the operational checklist.

Expected result: Generated jobs will use the correct location and workflow.

Step 4: Set the cadence

Choose Daily, Weekly, Monthly, or Every N days. Complete the weekday, month day, interval, or start date fields required by that cadence.

Expected result: The recurrence describes the intended pattern exactly.

Step 5: Set local time and timezone

Enter the time the job should start in the unit’s timezone. Check daylight-saving behavior for locations that observe it.

Expected result: The displayed local time is correct for the property.

Step 6: Choose assignment behavior

Leave the rule Unassigned when dispatch should choose each time, or select a specific eligible worker or team for automatic assignment.

Expected result: The assignment method matches how the work is managed.

Step 7: Save and review generated work

Save the rule and expand its generated-jobs section. Confirm the next fire date and active status.

Expected result: The rule is active and the next occurrence is reasonable.

Step 8: Verify on Cleaning Schedule

Open the schedule around the next occurrence and confirm the generated job appears once with the expected subtype and assignee.

Expected result: The recurring rule produces usable operational work.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.