--- title: Event status & the lifecycle id: event-status description: Move an event through your own pipeline stages, customize them, and understand when the couple's checklist turns on. category: Features order: 12 tags: [inquiries, status, lifecycle, pipeline, booking, statuses] related: [booking-and-inquiries, per-event-view, checklist-and-forms] updated: 2026-08-03 --- Every event in SpinBook carries a **status** that tracks where it is in your pipeline — from a fresh lead off your booking form all the way to a wrapped-up event. You set the status yourself, so the dashboard always reflects reality. **Statuses are yours to customize** — rename them, recolor them, reorder them, or add your own in **Settings → Event statuses**. ## The default stages Every new account starts with this pipeline. Edit it to match how you work: | Status | What it means | |---|---| | **Lead** | Just came in from your booking form — nobody's touched it yet. | | **Call Scheduled** | You've booked a call with the couple. | | **Called** | You've spoken with them (quoting, answering questions). | | **Booked** | Confirmed. This is where the couple's checklist and planning tools switch on. | | **Not Booked** | They went another direction. | | **Not a Fit** | Not the right match. | | **Cancelled** | A booking that fell through. | | **Completed** | The event has happened. | You don't have to march through every stage in order — set whatever fits. ## Categories: what each status *does* Behind every status is a **category** that tells SpinBook how to treat it. When you rename or add a status you pick its category, so the app keeps behaving correctly no matter what you call things: | Category | What it drives | |---|---| | **Lead** | Counts toward the "new leads" badge on your dashboard; the default landing spot for new booking-form inquiries. | | **Working** | You're in conversation, not yet booked. The couple's portal stays gated. | | **Booked** | **Unlocks the couple's checklist + planning tools** and sends the booking email. | | **Lost / Closed** | Hides the event from the couple's view and the calendar (a lost lead or cancellation you're filing away). | | **Completed** | Shows the Completed badge; the portal stays visible (read-only feel). | So if you add a custom **"Deposit Pending"** status and tag it **Booked**, the couple's portal still switches on exactly as it should. ## Customize your statuses Go to **Settings → Event statuses** to: - **Rename** any status (including the defaults) and **recolor** it. - **Reorder** them with the up/down arrows so your dropdown reads the way you think. - **Add** your own stages — pick a label, a category, and a color. - **Deactivate** a status to retire it without losing events that used it (preferred over deleting). You can re-activate anytime. A few stages are load-bearing, so SpinBook keeps you from breaking them: you must always have at least one active **Lead**, **Booked**, and **Completed** status. A status that's still attached to events can't be hard-deleted — deactivate it instead. ## Change a status There's a status dropdown in two places: - On your **dashboard**, on each event row in your client list. - At the top of the **[per-event view](/per-event-view)**. Pick a new status and it saves immediately. New leads from your booking form are highlighted at the top of the dashboard so you never miss one. **Filter your dashboard by category** using the pills at the top — **Active** (the default: your live pipeline, hiding lost and completed events), **Leads**, **Working**, **Booked**, **Completed**, or **Lost**. Each shows a live count, so you can jump straight to "just the new leads" or "everything I've booked." Because the filters follow categories, they keep working even after you rename your statuses. **Search** sits beside the pills: type any part of a couple's name, event title, venue, or email and the list narrows as you type. Search and the pills combine, so "booked + smith" works exactly how you'd hope. **Group by status** (on by default) breaks the list into a section per status, in your own pipeline order, so the dashboard reads like your pipeline: leads at the top, booked below, each section with its own count. Toggle it off for one long list ordered by the **Sort by** dropdown (event date, couple, venue, or status). ## Booked turns on the checklist The couple's **checklist and planning tools stay hidden until the event reaches a Booked-category status.** Before that — while it's still a lead or in conversation — the couple just sees a friendly "we're reviewing your inquiry" note, and you see a reminder that the checklist appears once you book them. This keeps unconfirmed leads clean and stops couples from filling out planning forms for a date that isn't locked in yet. Once you set a booked status, the full [checklist](/checklist-and-forms) appears for both of you. On the dashboard, clicking a not-yet-booked event opens a **quick preview** instead of the full event: you see the **entire booking form the couple submitted** and can **edit any answer** (fix a typo'd email, update the venue, adjust the guest count) and **change the status** right there. Set it to a booked status and the full event view (checklist + planning) unlocks — open it from the same popup. The same full form lives on every event page under a collapsed **"Booking form"** section (just below the couple's name and date — expand it when you need it), so you can review or edit what the couple sent at any point in the event's life — not just while it's an inquiry. ## Automations Every status change fires an `event.updated` [webhook](/webhooks) with the new status **key**, so you can keep tools like Monday.com in sync. Because statuses are customizable, the webhook sends your status's key (e.g. `not-a-fit`) — if you add or rename statuses, update any automation that matches on specific status values. ## Checklist - [ ] Review new leads at the top of your dashboard - [ ] Tailor your pipeline in **Settings → Event statuses** - [ ] Mark an event **Booked** to switch on the couple's checklist and planning - [ ] Advance to **Completed** after the event, or a **Lost** status to file it away