← Dancecard home

East Coast Kink Events

Run the weekend from one backstage

You already juggle spreadsheets, PDF waivers, registration exports, and a group chat where everyone shares the same password. Dancecard is the organizer console for that work, plus the attendee dancecard your people actually open on their phones.

Camp weekends. Hotel takeovers. Any event where the schedule, the door, and the map need to stay in sync.

Free while in beta — pricing for organizers will be announced before general availability.

Already have a ticket? Open the attendee dancecard

Why organizers use Dancecard

Build the weekend

Map your venue, grid your program, pull in your spreadsheet. Publish when you are ready, not when the website finally cooperates.

Run the door and the crew

Check people in with waiver status in view. Print badges. Staff the shifts. Catch conflicts before they become hallway arguments.

One link for attendees

Announcements, live schedule, compare and reserve, ISO board, tent groups, signed policies, and your camp map. Same data you edited in the console.

What you get as an organizer

Scroll the real screens. Every screenshot is from our Sandbox Con demo. Click any image to blow it up. This is the toolkit your team runs on. The section after shows what your attendees see when you publish.

19 organizer tools, then the attendee experience.

Set up the event

Venue maps

Your floor plan, pinned once

Upload your floor plan once. Draw room zones with size and rotation. Attendees open the same map on their dancecard. You stop answering "which building is Dungeon B?" in the group chat. Rooms live in one place, and program and room tools use the same names.

Room availability

Your venue on one screen

See every room across the weekend on a time grid next to the map. Drag classes between columns or drop them on a pin. Orange alerts show monitor coverage gaps while you are still planning. Room mistakes and safety gaps show up before you publish, not during the play party.

Registration

Ticket types that match how you run the door

Set up weekend passes, staff comps, capacity, check-in windows, and comp codes. Turn on staff tools per ticket type so the right people get console access when they register. Ticket types, door rules, and permissions stay together. No side spreadsheet.

Event settings

Configure the weekend in one home

Basics, public page, registration, policies, rooms, and tracks live in one settings area. Configure once before you live in Program and People. New team members know where the event is configured.

Attendee profile

You choose what people share

Choose what registrants can add on Profile: photo, bio, FetLife, Discord, email on card, bio length, and the default prompt. You set how people connect. No developer needed. Community norms and privacy are your settings, not a custom build.

Build the program

Program grid

Build the schedule like you mean it

Drag workshops onto a multi-day grid. Keep unassigned classes in the sidebar until you are ready. The conflict banner checks rooms, presenters, and photo policy before attendees see a draft. Scheduling feels like planning the weekend, not fighting the website.

Import

Your spreadsheet, live in minutes

Connect Google Sheets or upload CSV or Excel. Stage program and staff imports separately so volunteer rows do not end up in your class list. Preview, fix, publish. Your existing spreadsheet is still the fastest way in.

Schedule changes

When you move a class, you pick who hears

After you move a session, see who has it on their dancecard and which presenters are on the block. Notify selected people in the app or copy an announcement. Personal dancecard times are not changed behind your back. You choose who hears about a change instead of blasting the whole camp.

At the door

People signups

The door, without the guesswork

Every ticket in one table with vetting, filters, and color-coded check-in (on site, late, early override). Approve vetting in the side panel. Export when finance asks. Registration, vetting, and gate status are one workflow.

Policies and signing

Waivers before the badge

Attendees sign waivers and conduct policies (ECKE Sign) before you print a badge. Legal name is stored. Door staff see completion on the signup record. Paperless door with a clear record, not a binder and guesswork.

Badges

Badges at the door, not at Kinkos at 2 a.m.

Upload a sharp logo. Search one person for a reprint. Bulk print by package with checked-in filters. Counts per ticket type stay current. Badge night is a button at the desk, not a panic run to Kinkos.

Your crew

Staff roster

Everyone on the weekend, one list

One list for presenters, volunteers, photographers, and anyone else you add. Scene names, pronouns, comp types, and service hours pull from signups. Filter by role when you need "who can DM?" Everyone who touches the weekend is easy to find.

Staff shifts

Shifts and hours on the board

Hours on the board shows scheduled hours vs expected hours per person. Add shifts with play space and role. Leave blocks open for volunteers to claim. Filter unstaffed and needs vetting. You see burnout and gaps before Friday morning setup.

Trusted roles

Applications for roles that actually matter

Build questionnaires and publish apply links. Review submissions in one queue for dungeon monitor, safety lead, and similar roles. Approve here, assign shifts next. High-trust roles stop living in three Google Forms and a DM thread.

Coverage

See the gaps before the floor does

Set minimum lead and backup counts per window. The headcount grid turns red where you are short. Click a cell and assign from available staff. Play space coverage is visible. It is not tribal knowledge in one person's head.

Scheduling conflicts

Catch double-booking before Friday

If someone is already on setup that morning, you see it before you double-book. You can still assign them if you mean it. They get a nudge to check their dancecard. Fewer "where is my volunteer?" moments on the floor.

Shift swaps

Let volunteers trade shifts (on your terms)

Volunteers propose trades with a note. You see both shifts and approve or decline. Coverage rules stay yours. Volunteers get flexibility. You keep control of the board.

Safety and comms

Safety incidents

A log for safety leads, not the group chat

Log incidents with a short summary. Restricted notes stay visible only to safety role and owners. Timestamped history for handoffs between leads. Safety notes without a shared password spreadsheet.

Announcements

News that actually reaches everyone

Push updates like "pool closed" or "vendor row moved" to every attendee dancecard. Require acknowledgment when it must be read. Important news reaches phones, not a Discord channel half the camp muted.

What your attendees get on one link

When you hit publish, this is what shows up on their phones. Same schedule, same map, same policies you configured in the console. They get announcements, a live program, availability tools, compare and reserve, ISO board, tent groups, and sign-in at the door without you re-explaining the camp layout.

Live program

When you change the schedule, they know

Official schedule by day with ADD, presenters, and map links. When you publish changes, their timeline updates from the same data you edited in the console. One schedule for everyone. Fewer "nobody told me it moved" moments at the door.

My availability

Their calendar stays honest as they plan

Attendees block busy time, set buffers, share a link, and export to calendar. Green hours show when they are still free as they add classes. They handle their own calendar math. You are not in the middle of every "are you free?"

Compare

Compare schedules without spilling the tea

Two people compare in private. Mutual open windows show in green. Busy details stay hidden unless you allow it. They can pick a gap to reserve. Scene planning without posting class titles to the whole camp.

Reserve

Book scene time in a few taps

Tap a mutual open slot, confirm, and both dancecards update. They can add it to a calendar if they want. Scene time lands on both phones instead of a long Signal thread.

Reservations

Scene times in one list

Confirmed scenes show in one list. Reschedule or cancel and both sides update when the other person responds. Less "I thought we said noon?" confusion.

Profile

Profiles that match your event

Scene name, bio, contacts, badge line, and a live preview. They only fill in fields you turned on in settings. Attendees show up findable. You control how much they share.

ISO board

Connection posts without the feed

Posts for practice partners, meetups, shadow shifts, and similar. Threaded replies and profiles. No need to expose a full schedule to coordinate. Connection stays in the app. Staff can watch the board instead of scattered social posts.

Attendee groups

Tent cities and room blocks, self-serve

Tent cities and room blocks with expectations, chores, and bring lists. Owners approve who joins. Sub-camps organize themselves. You set expectations up front instead of micromanaging.

Three steps to your first event

  1. Create your organizer account

    Sign up with email. Confirm the link when it arrives. You are in.

  2. Create or join an event

    Start a new event from the hub, or ask the owner to add your email if you are joining an existing team.

  3. Import, schedule, go live

    Bring in your spreadsheet, place classes and rooms, check people in at the gate, and hand attendees one dancecard link.

Logins, email, and your team

Organizers sign in with email (password reset included). When you are ready to email registrants in bulk, you connect your mail provider in settings. No magic, just standard setup.

Setup guide for auth and email →

Bring the whole crew

Programming, registration, door, volunteers, and safety can each have their own login. Owners decide who can edit, who can only view, and who sees sensitive vetting notes. Nobody has to share one password in the org chat anymore.

Joining an event someone else owns? Ask them to add your email, or contact us.

And there is more where that came from

Messaging, exports, integrations, safety incident log, vetting workflows, and the public East Coast Kink Events calendar. We built this for the community we already show up for. Come see if it fits your next event.