CueProX
⌘K

Docscore-concepts

The hierarchy

How CueProX structures everything — from your account down to a single cue.

The hierarchy

CueProX organizes everything into six levels. They nest inside each other, from the broadest container down to the smallest unit of work.

Account
  └── Location
      └── Room
          └── Event
              └── Show
                  └── Cue

Here's what each level is, in plain terms.

Account

Your account is yours. It's created when you sign up, and you're the owner. Billing, overall settings, and top-level access all live here. You only ever have one account — though you can be a member of other people's accounts at the same time, using the same login.

Location

A location is a physical building or venue. Most organizations have one. A single-campus church has one location: its building. A multi-campus organization has one location per campus. A theater company running productions at two venues has two locations.

The location is mostly an organizational container. It holds your rooms, your teams, and your people list. You configure things at the location level, then run them at the room level.

Room

A room is a specific space within a location — and it's where the real work happens. A church might have a Main Hall and a Foyer, each running a different version of the service. A theater might have a Main Stage and a Studio that run separate productions. A conference center might have Ballroom A, Ballroom B, and a breakout session room.

Each room is fully independent. It has its own events, its own team configuration, its own outputs, and its own director view. What's happening in one room has no effect on another.

Event

An event is a single occasion. A Sunday service. A Saturday night performance. A conference breakout session. Events have a date and a status — they're active while the show is running, paused when things stop momentarily, and stopped when it's over.

An event can contain more than one show (see below), which is how you handle multi-part occasions where it makes sense to break the running order into logical blocks.

Show

A show is a logical block within an event. A Sunday service might have two shows: "Welcome & Worship" and "Message & Response." A concert might have "Set 1" and "Set 2." A conference session might have "Opening Remarks" and "Breakout Q&A."

Shows help you keep large running orders manageable. You can advance through one show, transition to a break, then start the next show fresh. The director decides when to move between them.

Cue

A cue is a single item in the running order — the smallest unit of work the director controls. A cue might be a song, a video, a speaker segment, a prayer, a Q&A moment, or anything else that needs to be tracked and called. The director moves from cue to cue as the show progresses. When a cue becomes active, the relevant outputs update automatically.

Cues can carry team-specific notes, so the sound team sees what they need, the lights team sees what they need, and the director sees the full picture.


Note

Don't worry about all six levels at once This hierarchy might seem like a lot at first. In practice, you'll rarely think about all six levels simultaneously. Most of your time is spent inside one room, looking at one event, watching the cues move forward. The structure is there when you need it and invisible when you don't.
Was this helpful?