Features
Part of 5 things a run asks of stage and broadway actors
Stage and Broadway actor records: what decays fastest, what to verify
Stage and broadway actors updates 2027: why a live production's entry decays fast, which fields to recheck against IBDB, and how to handle corrections.
Stage and Broadway actor updates are only as good as the record they change. This page is about that record: which details of a stage entry go out of date fastest, which sources to check them against, and how to decide when an entry has gone stale.
It is a guide for keeping stage and Broadway records accurate, not a news list of cast changes.
What to take away
- A theater record decays for reasons a screen record does notruns end, casts rotate, and the source document was printed before either happened.
- Staleness is a property of a field, not of a page. Some fields are final on opening night and some are wrong within a fortnight.
- The date an entry was last checked against its source is more useful to a reader than the date the page was last edited.
Why a stage entry goes stale faster than a film entry
A film credit is fixed once the film is finished. A production entry describes something still happening.
While a run continues, the cast changes, the schedule changes, the closing date is unknown, and the count of performances rises every week.
An index that recorded the production on opening night and never returned to it will be wrong about most of that within a season, and it will not look wrong: the entry still reads as a confident statement of fact. The underlying reason a cast cannot be pinned to a year is set out in dating a production and its cast changes.
Which fields decay, and how fast
| Field | Settles when | Typical failure if never rechecked |
|---|---|---|
| Title, house, producing body | On opening | Rare, though a transfer to another house breaks it |
| Opening date | On opening | Stable, once you have recorded which date definition you used |
| Cast | Never, until the run closes | The opening cast presented as the whole run's cast |
| Closing date | Only when announced | Left empty, or filled with a guess that becomes a citation |
| Performance count | Only at closing | A number frozen at whatever week the entry was written |
| Credits and billing wording | On opening, then at each cast change | Billing quietly reworded and never updated |
The pattern is that the fields readers care most about are the ones that decay fastest. That is not bad luck. Those fields are interesting precisely because they are about a living production.
The longest-running Broadway show makes the point. The Phantom of the Opera opened at the Majestic Theatre on 26 January 1988, became the first Broadway musical to pass 10,000 performances on 11 February 2012, and closed on 16 April 2023. An entry written in any year of that run carried a performance count that was out of date within a week and a closing date that did not exist yet, while its title, house and opening date never changed.
Where to check each field
For Broadway, the main reference is the Internet Broadway Database (IBDB), operated by the research department of The Broadway League. It is an online database of Broadway productions and their personnel, including lengths of runs, lists of casts and creators, awards and nominations, and past box office grosses. Check the cast, closing date and run length there, then confirm anything it lacks against the production's own program or announcements. For a performer's union standing on stage work, the body is the Actors' Equity Association, the union for those who work in live theatrical performance.
Which fields decay and when
Settles when
- Title, house, producer
- On opening
- Opening date
- On opening
- Cast
- Never until close
- Closing date
- Only when announced
- Performance count
- Only at closing
- Credits and billing
- Opening, each cast change
Typical failure
- Title, house, producer
- Transfer breaks it
- Opening date
- Stable if defined
- Cast
- Opening cast shown as whole run
- Closing date
- Empty or guessed
- Performance count
- Frozen at writing week
- Credits and billing
- Reworded, never updated
A revision method that survives being ignored
Most indexes are maintained irregularly, so the method has to degrade well rather than assume attention.
Revision method that degrades well
- Store a checked date per entry
- Store the source alongside the claim
- Mark open ranges as open
- Keep a correction log
- Prefer removing a field to guessing
For a live production, the routine runs in this order:
- Store a checked date and a source on each field, not one date for the whole entry.
- While the run continues, recheck the cast, closing date and performance count; leave title, house and opening date alone unless the show transfers.
- When a closing is announced, record the date and keep the entry open until the final performance.
- At closing, update the performance count and closing date once against IBDB or the production's final announcement, then mark the entry closed.
- Record replacement casts as dated additions rather than overwriting the opening cast.
The same discipline applied to a screen index, where the drift is between a directory and a production's own records, is worked through in the fields a television record needs.
Corrections that come from readers
A stage index receives corrections from people with direct knowledge: a company member, a house archivist, a relative holding a program. This is genuinely valuable and needs a rule, because it is also how errors enter.
Handling a reader correction
Does a supporting document exist?
record it and log the change
record the disagreement, do not replace
Treat a correction as a claim with a source, exactly like the original entry. Ask what document supports it. Where the document exists, record it and log the change. Where it does not, record the disagreement rather than replacing one unsourced statement with another.
Archives describe this dependence on an unbroken chain from the object to the claim as provenance, and it is the same idea an index needs. Memory is honest and unreliable at the same time, and thirty years is a long time to hold a cast list. The general point about preferring the object over the recollection is made in tracing a stage credit to its source.
Removal requests
Someone will eventually ask for an entry to be taken down, and a policy written before the request arrives is worth more than one written after.
Removal request policy
Is the entry accurate?
No -> correct or remove on evidence
Yes -> keep, offer correction route
A workable one distinguishes accuracy from preference. An inaccurate entry is corrected or removed on evidence. An accurate entry about published professional work is a record of a public production, and the usual answer is that it stays, with a route to correct anything wrong in it.
Entries about people who were minors at the time, or anything that identifies someone with no public role, sit in a different category entirely, and the reasoning is in the notes on what belongs in a record involving young performers.
Reference projects that carry biographical material publish their own version of this reasoning, and the encyclopedic policy on material about living people is a well-argued example to read before writing your own. Publish whatever policy you settle on, because an unpublished policy is indistinguishable from having none.
Common questions
How often should a live production entry be rechecked?
Often enough that the checked date is not embarrassing. Monthly during a run is a reasonable target for the fields that move, and the checked date matters more than the frequency, because it tells the reader what they are holding.
Should closed productions be rechecked at all?
Once, at closing, to finalize the closing date and performance count. After that the entry is stable and only changes if new documentation appears.
What about productions that were announced and never opened?
Keep them, labeled as announced and not opened. They explain otherwise inexplicable references, and deleting them means the next researcher repeats the work.
Is an update page with a year in the title ever useful?
Only if it is a real change log with dated entries, each tied to a source such as IBDB. Without them, a year in the title invites trust in a page that has no idea how old it is. The pillar on rehearsal and the eight-show week is the more durable read.
