Skip to content

Glossary

Theaters and the app don’t always use the same word for the same thing. Use this page as a Rosetta Stone.

The set of players actually performing a show. SchedgeHog also calls this the lineup.

How many minutes before the show players need to arrive. Set per-show with optional per-date overrides.

A persistent group of players (e.g., “House Team Alpha”). Most theaters book by ensemble — the show date is assigned to one or more ensembles, and players for that ensemble get the availability ask.

A player who can manage scheduling for one or more ensembles, but is not a full theater admin. Permissions are derived from membership in the ensemble.

The player marked as running a particular show. There’s at most one per show date.

Same thing as cast — the set of players performing.

The date by which a lineup should be finalized. Computed automatically from the theater’s scheduling window cadence (or a per-show override). After this date, the show date appears in your “needs scheduling” pile.

The page where you assign players to roles for a specific show date.

The period before a show during which the lineup gets put together. See How scheduling windows work for the full picture.

A recurring property — “ComedySportz Friday Night” — that has many show dates.

A specific performance of a show, on a specific date and time.

A player who can manage one specific show without being a full admin or ensemble manager.

When a player who’s been assigned to a show can no longer make it and asks SchedgeHog to find a replacement. See How do I handle a sub request?.

The top-level container. Everything in SchedgeHog is scoped to one theater.