# Build and publish the schedule

> Add sessions to an event, choose how guests sign up for each one, and publish them so guests can see them.

- Do first: [Find the event and the people in it](https://www.attend.vip/help/agents/find-your-event.md)
- Attend MCP tools: `agenda_items__getScheduleBundle`, `locations__createLocation`, `agenda_items__createAgendaItem`, `agenda_items__updateAgendaItem`, `agenda_items__agendaItemPublish`, `agenda_items__agendaItemUnpublish`, `agenda_items__agendaItemCancel`, `agenda_items__createTrack`, `agenda_items__tagAgendaItemTrack`
- Updated: 2026-11-02

A schedule is a list of **sessions** (agenda items). Each session has a time, an optional place, and a sign-up style. Sessions start as **drafts** that guests can't see, and you publish them when they're ready.

## Steps

1. **Read what's there.** Call `agenda_items__getScheduleBundle` so you don't create duplicates.
2. **Places (optional).** Look up existing locations in the schedule bundle. To add one, use `locations__createLocation`.
3. **Create each session** with `agenda_items__createAgendaItem`. Required fields are `eventId`, `name`, `startsAt` and `endsAt`, as local times. Choose the sign-up style with `rsvpMode`:

   | `rsvpMode` | What guests see | Use it for |
   |---|---|---|
   | `required` | It's on their schedule; they can't decline | Welcome dinner, keynote, transfers. Pair it with `isRequired: true` |
   | `rsvp` | Confirm or decline; seats count | Limited-seat excursions. This is the only style where `capacity`, waitlists, the reservation window (`reservationsOpenAt`/`reservationsCloseAt`) and approval (`preApproved: false`) apply |
   | `optional` | A star to add it to their schedule | Open sessions with no limit |
   | `display` | Information only | Free time, "Bus departs lobby" |

   Call it with `dryRun: true` first. Cross-field rules are checked then; for example, `capacity` only works with `rsvp`.
4. **Edit** with `agenda_items__updateAgendaItem`. Send only the fields that change, and pass `null` to clear a field. Moving a session into or out of a choice group is a special case: see [Choice groups and activities](https://www.attend.vip/help/agents/choice-groups-and-activities.md).
5. **Publish** each session with `agenda_items__agendaItemPublish`; this is the only way to make it visible.
   - `agenda_items__agendaItemUnpublish` moves a session back to draft. It refuses if guests have confirmed.
   - `agenda_items__agendaItemCancel` cancels a session and releases every RSVP. Dry-run it first and tell the organizer how many guests lose their place.
6. **Tracks (optional).** Tracks are colour tags guests can filter by. They are not a way to make guests choose. Create one with `agenda_items__createTrack`, then tag sessions with `agenda_items__tagAgendaItemTrack`.

## Check the dry-run for

- Validation errors, such as a capacity on a non-`rsvp` session or an end time before the start.
- For a cancel, the number of RSVPs that would be released.

## Rules

- Never set `status` through an update. Use publish, unpublish or cancel.
- `visibility` (who can **see** a session) and `accessMode` (who may **sign up**) are different settings. See [Private sessions and invite lists](https://www.attend.vip/help/agents/private-sessions-and-invite-lists.md).
- Draft sessions are hidden from guests, but RSVPs that already exist still count.
