Manage the Act Directory

Create reusable performer profiles with contact details, default timings, files, structured technical requirements, completeness checks, and field-level audit history.

Article guidance

The act directory is the reusable record of performers, bands, DJs, speakers, comedians, dancers, workshop leaders, and other stage acts. A clean directory means future events can start from known contacts, timings, rider information, and files instead of rebuilding the same profile from old emails.

What an act record can include

Act type, act name, contact name, email, phone, website, biography, tags, colour, and status.
Default set length and default changeover length for first-pass scheduling.
Rider notes, production notes, and files such as stage plots, input lists, logos, press shots, or contracts.
Structured technical profile fields for stage plot, input list, microphones and DIs, monitoring or IEMs, backline, shared resources or crew, power, hospitality, access and load-in, and technical contact details.
Social links and internal notes for programming context.
Completeness signals such as missing contact, missing rider, missing technical requirements, missing availability, or review needed when the act is used on an event.
Field-level technical audit history when rider or technical information changes.

Create or update an act

Open Stage Manager > Acts: Use the act directory.
Choose Add act or edit an existing profile: Use one profile per real act unless there is a clear reason to separate variants.
Add core contact and performance details: Use current contact information, useful tags, sensible default set length, and realistic changeover length.
Complete rider and technical sections: Fill structured fields where possible and use free-text notes only for information that does not fit a field yet.
Attach useful files: Upload the documents production teams will actually need, and avoid burying important information inside a single unlabelled file.
Save and review completeness: Check missing-info badges before adding the act to a busy lineup.

Directory profile versus event override

Use the directory profile for reusable information that is normally true across events.
Use event-specific lineup overrides when one event has a different rider, technical profile, owner, due date, production note, review status, or availability requirement.
Applicant follow-up updates can refresh linked act contact and file details while also pushing event-specific technical changes into the relevant lineup row.
Event overrides should not silently erase useful defaults on the reusable act record.