> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aciona.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up your first schedule

> Define who is on call, in which timezone, and with which rotation.

The schedule answers a single question: **who gets paged right now?**

## Creating one

<Steps>
  <Step title="Open Schedules and create a new one">
    Pick the team this schedule covers. A schedule belongs to one team.
  </Step>

  <Step title="Set the timezone">
    Use the timezone the team actually lives in — for example `America/Sao_Paulo`. Every handoff calculation uses it, including across daylight saving changes.
  </Step>

  <Step title="Choose the rotation type">
    * **24x7** — the same person covers around the clock until the handoff. Best way to start.
    * **Weekly** — responsibility moves to the next participant on a fixed weekday and time.
  </Step>

  <Step title="Add participants in order">
    Order matters: it defines both the rotation sequence and the escalation order when nobody acknowledges an incident.
  </Step>

  <Step title="Set the rotation start">
    The date and time from which the schedule applies. It is the anchor for every following handoff.
  </Step>
</Steps>

<Tip>
  For your first test, use **24x7** with yourself as the only participant. That way you are on call now and get the alert immediately.
</Tip>

## After creating it

* Check under **On-call** who aciona.me considers to be on call right now.
* Create overrides for vacations, days off and one-off swaps.
* Keep the schedule **active** — inactive schedules resolve nobody.

<Columns cols={2}>
  <Card title="Rotation and participants" icon="repeat" horizontal href="/en/on-call/rotation-and-participants" />

  <Card title="Overrides" icon="user-round-check" horizontal href="/en/on-call/overrides" />
</Columns>

<Card title="Next: create the alert source" icon="webhook" horizontal href="/en/getting-started/create-alert-source" />
