Cast List Order in a Theatre Programme: An Approval Matrix for Appearance Order and Alphabetical Listing

A cast list can be arranged in more than one defensible way. Some programmes list performers in order of appearance. Others list them alphabetically. Some show both in different places. Trouble starts when a designer and a company each assume a different order and nobody notices until proofs are printed. This article proposes an approval matrix to settle display order before layout is final. It is an example workflow, not a description of any real production, and every name below is fictional.

The two orders

Appearance order: roles listed in the sequence in which they first appear on stage.
Alphabetical order: listed by a stated sort key, such as role name or performer surname.

The choice of which to use, and which sort key, is the company's decision. The designer's job is to make that decision visible and checkable.

Inputs

The company's raw cast information: role names, performer names, and for each role, the scene of first appearance.
A written statement of the intended display order, for example: Appearance order, then alphabetical for ensemble.
If alphabetical is used anywhere, the sort key named explicitly: by role or by performer surname.
Any special groupings the company wants, such as Ensemble or Understudies.

The matrix

Build a table with one row per role and these columns:

Role
Performer
First scene
Position by appearance
Position alphabetically (by the stated key)
Position used in programme
Company initials to approve

The last two columns matter most. The programme position must match one of the two ordered columns, according to the stated rule, and the company approves it row by row.

Example with fictional names

Suppose a hypothetical play lists these roles: Captain Ardell (performer Maren Ostrow, first scene 1), Nell Brightwater (performer Tobin Hale, first scene 2), Old Percival (performer Ines Vardy, first scene 1, entering after the Captain), and Quill the Messenger (performer Dara Lund, first scene 3).

By appearance: Captain Ardell, Old Percival, Nell Brightwater, Quill the Messenger. Alphabetically by role: Captain Ardell, Nell Brightwater, Old Percival, Quill the Messenger.

The two orders differ in the middle. If the company stated Appearance order, the programme position column reads 1 Captain Ardell, 2 Old Percival, 3 Nell Brightwater, 4 Quill. If the company stated alphabetical by role, it reads the second list instead. The matrix makes this swap impossible to miss.

Decision branches

Two roles appear in the same scene with no stated entrance order: ask the company which comes first. Do not guess.
A performer plays two roles: decide whether they appear once with both roles, or twice. Record the decision in the matrix.
Alphabetical by performer surname with a prefix such as de or van: ask the company whether the prefix counts. Record the choice.
The company wants appearance order for principals and alphabetical for ensemble: split the matrix into two blocks, each with its own stated rule.

Stop conditions

Stop if the stated order is missing or contradictory. Layout should not start until one rule is written down.
Stop if any row lacks a first scene when appearance order is chosen.
Stop if a name is spelled differently in two company documents. Ask which spelling to print.
Stop if any row lacks initials when the company has asked for sign-off.

Small acceptance test

Take the finished programme draft and the approved matrix. Pick three roles at random, plus the first and last entries. Read the programme text aloud and compare each against the matrix column named in the stated rule. Pass if all five match and every row has initials. Then make one deliberate swap in a copy of the draft and check that someone using the matrix catches it. If nobody does, the matrix is not clear enough and needs a more visible rule line at the top.

Optional choices

Whether to show both orders, whether to add scene numbers to the printed list and how to group ensemble members are the company's choices. None is universally required.

Conclusion

Separating appearance order from alphabetical listing in a matrix turns a hidden assumption into a signed decision. State the rule, name the sort key, fill the columns, get row by row approval, and test the draft against the matrix before anything is finalised.