Skip to content
Dashboard

Scheduling Tasks

Task scheduling lets you automatically create tasks based on reservation events or recurring time intervals. Instead of manually creating the same tasks for every check-in or running weekly inspections by hand, you define a schedule once and SuiteOp generates the tasks for you.


SuiteOp supports two types of task schedules:

Tasks are created when a specific reservation event occurs. For example, you can schedule a cleaning task to be created every time a guest checks out, or a welcome inspection 30 minutes before each check-in.

Trigger events:

EventWhen it fires
Check-inWhen a guest’s check-in date arrives
Check-outWhen a guest’s check-out date arrives
ConfirmationWhen a reservation is confirmed

Offset: You can shift the task creation time forward or backward from the trigger event. For example, setting an offset of -30 minutes on a check-in trigger creates the task 30 minutes before the guest arrives.

Tasks are created on a repeating time-based schedule, independent of reservations. Use this for routine operational tasks like weekly fire alarm checks or monthly deep cleans.

Recurrence options:

OptionDescription
DailyEvery N days
WeeklyEvery N weeks on specific days (e.g., Monday, Wednesday, Friday)
MonthlyEvery N months on a specific day of the month

You also set a time of day and timezone for when the tasks are generated, plus optional start and end dates to control the schedule’s active window.


  1. Open the scheduler

    Navigate to Tasks > Scheduler and click New Schedule.

  2. Choose the schedule type

    Select Reservation-based or Recurring. This determines the configuration options available in the next steps.

  3. Configure the trigger

    For reservation-based schedules:

    • Select the trigger event (check-in, check-out, or confirmation)
    • Optionally set an offset in minutes (negative values create the task before the event)

    For recurring schedules:

    • Choose the recurrence type (daily, weekly, or monthly)
    • Set the interval (e.g., every 2 weeks)
    • For weekly: select which days of the week
    • For monthly: select which day of the month
    • Set the time of day and timezone
    • Set the start date and optional end date
  4. Define the task blueprint

    Add one or more task items to the schedule. Each item defines a task that will be created when the schedule fires:

    • Task template or custom task name — use an existing template for consistency, or enter a one-off name
    • Department — which team handles this task
    • Priority — watch, low, medium, high, or urgent
    • Estimated cost and estimated time (optional) — for budgeting and planning

    You can add multiple task items to a single schedule. For example, a check-out schedule might create both a “Cleaning” task and a “Linen replacement” task.

  5. Set the property scope

    Choose which properties the schedule applies to. You can scope by:

    • Individual properties — select specific properties
    • Property groups — apply to all properties in a group
    • Tags — apply to all properties with a specific tag

    You must add at least one scope entry. You can combine multiple scope entries to cover different property sets.

  6. Save the schedule

    Review your configuration and click Save. The schedule starts generating tasks immediately for matching events.


The scheduler list page shows all your schedules with their status, type, and scope. Click any schedule to view its details and run history.

Toggle a schedule’s Active status to pause or resume it without deleting the configuration. Paused schedules do not generate new tasks.

Click Edit on a schedule’s detail page to modify its trigger, task blueprint, or property scope. SuiteOp shows a preview of what will change before you confirm the update.

Click Delete on a schedule’s detail page. SuiteOp shows a preview of how many linked tasks will be affected. Deleting a schedule does not delete tasks that have already been created.


Each schedule tracks its execution history. On the schedule detail page, the Runs section shows:

  • Timestamp — when the run executed
  • Status — success, skipped, or error
  • Trigger — what caused the run (e.g., a specific reservation event)
  • Action — what happened (e.g., task created, task updated, task cancelled)

Use run history to verify schedules are working as expected and to debug issues.