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

# Create an event from scratch in the full editor

> Skip the onboarding template questions, open the Ticket Spot event editor, and configure your event's admission, schedule, tickets, and communications.

Choose **Start from scratch →** on **What are you hosting?** when you want to configure the event directly in the full editor. Selecting it skips the template questions and opens the new-event form; it does not create a blank event on your behalf.

## Create the initial draft

1. Select the correct workspace and open **Create Event**.
2. On the template picker, choose **Start from scratch →**.
3. Enter the required event name and description in the editor, then use **Create Event** to save the initial draft.
4. Complete the remaining editor steps once the draft exists. The [event creation guide](/event-management/create-event-overview) describes the full sequence.

Use an [event-type guide](./overview) as a settings checklist even when you do not use its onboarding template. For example, a self-configured theatre event still needs a published chart and category mappings before reserved seats can be sold.

## Decide the event structure

| Decision | Where to configure it |
| - | - |
| Ticket checkout, RSVP, an external link, or a listing without registration | **Event Details → Event Setup**; see [registration methods](/event-management/eventdetails#event-setup). |
| One occurrence, recurring dates, specific dates, or selectable time slots | **Dates & Times**; see [schedules](/event-management/datetime). |
| Physical venue or online joining details | **Venue & Location**. |
| General admission or reserved seats | **Tickets**, with a published [seating chart](/seating-charts/create-and-assign) for reserved seating. |
| Ticket tiers, pricing, quantities, and sale dates | **Tickets** and the [ticket options reference](/event-management/ticket-options-reference). |
| A whole-event pass and separate daily tickets | The schedule's whole-event offer and [date-specific ticket settings](/event-management/day-specific-tickets). |
| Registration questions and attendee requirements | **Additional Info** and [waiver settings](/event-management/waivers) where needed. |
| Confirmations, reminders, and language variants | **Email Communication** and [language/locale settings](/branding-and-design/language-and-locale). |

## Complete the saved event

Add your brand, event media, venue, and guest instructions. Connect the payment provider or storefront needed for paid admission. Configure optional waitlists, memberships, or add-ons only when they match the experience you intend to sell.

Changing a schedule after confirmed attendees exist can be restricted. Choose the event structure before opening registration. For a course package, use membership settings rather than assuming a ticket name or recurring schedule grants admission across every date.

## Verify and launch

* Inspect each public ticket offer, date/time, capacity, and price.
* Submit the intended registration form and review the attendee information and confirmation.
* For seating, check the exact seat and category price; for multiple dates, check more than one occurrence.
* Review [publishing and platform actions](/event-management/manage-events), then share the event when the saved configuration is ready.

For a guided start that asks only the initial questions, choose [Single Event](./single-event) or another named template instead.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.