Sixto
EN
EspañolEnglishPortuguês
See demo
Explore every Sixto workflow

Automatic tasks

Generate operational work from a stay’s arrival or departure using a rule with a clear scope and timing. Assignment, instructions and evidence requirements help the team understand the task, while completion remains a separate human outcome.

Before you start

Rule editing needs task-rule management permission. Confirm the selected property, units and responsible people.

  1. Open Tasks settings and automatic-task rules, then select the arrival or departure anchor and its timing. The rule needs a defined event so its work is attached to the relevant part of the stay.

    Choose the stay event
    Automatic tasks
    1 / 3
    RulesPreview

    Arrival or departure

    Rule anchor

    Tasks & tracking

    Offset from the selected event
    Rule anchor
    Arrival or departure

  2. Choose the units, supported assignment and task instructions together. Preview the rule before enabling it, including any required evidence, so generated work has a useful operational scope.

    Define the work and assignment
    Automatic tasks
    2 / 3
    To do1
    Replace lampSofia · Fri 23 Oct
    In progress1
    Repair water heaterMateo · Unit 402
    Done1
    Restock linenLuz · Unit 402
    Assignment
    Responsible people and evidence

  3. When a booking moves or cancels, inspect the existing generated work. Tasks already touched by the team may need review instead of silent rescheduling, preserving the context of work in progress.

    Follow changed stays
    Automatic tasks
    3 / 3
    RulesHistory
    1. Stay changeMoved or cancelled booking
      1
    2. Existing workReview touched tasks
      2

    Rule-generated tasks are not proof that an inspection happened. Completion and evidence still belong to the team.

    Stay change
    Moved or cancelled booking

Check the result

Qualifying stays have the rule’s task and timing; ineligible stays have no task from that rule, and touched work keeps any required review visible.

Limits and prerequisites

Rule-generated tasks are not proof that an inspection happened. Completion and evidence still belong to the team.