Skip to content
Product · Blueprint

Event setup

How an event gets made, from getting the organiser’s page to the night, drawn lane by lane. Every row is someone who has to act; every marker is a place where someone waits, carries a link by hand, or never hears about a change.

How to read it

Status (as on the UX map)
  • Live, real data
  • Partial or mock data
  • Promised, not built
  • Gap: nothing planned
Friction markers
  • Waits (6): Someone is blocked on someone else, and nothing chases it.
  • By hand (5): A person carries the link or the news between lanes.
  • Silent (7): An answer or change doesn’t reach the side that needs it.

Gaps are where markers cluster. Click a step for its code, or a gap below to light up its steps. Built from the routers and run end to end with a test organiser, venue and artist on 2026-11-14; see the UX map for the dancer journeys, and the meet new friends blueprint. This is job J6, run a great event.

Friction by phase

Get the page
⏳2 ✋1 🔇1 · 2/4 not live
Draft
⏳0 ✋0 🔇0 · 0/2 not live
Venue
⏳2 ✋1 🔇1 · 4/7 not live
Line-up
⏳1 ✋1 🔇1 · 2/7 not live
Flyer
⏳1 ✋0 🔇1 · 1/4 not live
Promote
⏳0 ✋2 🔇0 · 3/4 not live
Publish
⏳0 ✋0 🔇2 · 2/5 not live
The night
⏳0 ✋0 🔇1 · 3/3 not live

Lanes × phases

WhoGet the pageDraftVenueLine-upFlyerPromotePublishThe night
Organiser
Business → Events
WeDance
Server, AI, emails
Venue
Through /ask/<token>
Artist
Through /confirm/<token>
Dancers
City page, event page

Where it breaks

Each gap is a cluster of markers. Click one to light its steps on the blueprint.