ACCESSPUBLICFOREveryone

How NextSet works

Everything in NextSet hangs off one idea: the room has a running order, the running order has a clock, and every screen and phone reads from that clock instead of from somebody's memory.

The problem

The running order lives in a printed sheet, a group chat and the owner's head. When something slips — a late speaker, a long round, a delayed first dance — every copy of the plan becomes wrong at a different speed, and the person on the microphone is the last to find out.

What NextSet does

There is one running order. Change it and every screen, every phone and every staff device updates at once, because none of them hold their own copy — they all read the same live clock.

The four moving parts

Almost every feature in the product is one of these four things, or something that feeds one of them.

Part	What it is	Who touches it
The running order	The ordered list of what happens, each item with a length. Called a Rundown, Class Plan, Timeline, Agenda or Order of Service depending on your room.	Built before the day by whoever runs it
The clock	A single countdown owned by the server, not by any one device. Start it, pause it, add five minutes to it.	One person during the event — the director
The screens	The big screen everyone sees, and optionally a second screen for whoever is up next. Both follow the clock with no operator.	Nobody, once they are open
The people	Members, guests, performers, staff. Checked in at the door, on a roster, or holding a ticket.	The door, the kiosk, or the guest themselves

What a day actually looks like

Before the day you build the running order once. On the day one person opens the director view on a laptop or phone, and one screen in the room opens the big screen view. Everything else follows.

When the day slips — and it always slips — you do one thing: change the running order, or add time to the clock. You do not re-tell anybody. The screen in the room, the person waiting to go on, and the staff member holding a phone all see the new answer within a second.

What NextSet is not

It is not a calendar, and it is not a document. A calendar tells you what is meant to happen; NextSet tells the room what is happening, right now, and keeps saying so as the plan changes.

It is also not automated. Nobody hands your night to a machine — a person presses next. The product's job is to make sure that one press reaches everything at once.

Where to go next

Never set anything up before? Your first event walks the whole thing end to end.
Want to see it running before you commit? The live demo is a real event you can drive.
Wondering what your building's version looks like? Your room, your words.