How to Manage a Theater Season from Auditions to Strike

Which season decisions come before auditions?

Confirm the production's rights, venue, performance dates, and responsible leads before recruiting performers. Identify unresolved dependencies explicitly. An audition form cannot fix a calendar built around an unconfirmed venue or a production the company has not secured permission to perform.

• Six or more months before opening: choose the show and venue window; confirm rights and budget; appoint production leads; identify major access, staffing, and space needs.
• About four to five months before opening: publish the audition notice with confirmed dates, rehearsal expectations, and performance dates; collect audition information and conflicts.
• About three to four months before opening: hold auditions and callbacks, notify performers, confirm the cast list, and start the rehearsal plan.
• About two to three months before opening: begin rehearsals; finalize scene and design plans; check costume, prop, and set inventories; recruit volunteers for build and performance shifts.
• About one to two months before opening: revise the schedule as needed; confirm technical and front-of-house staffing; request program bios and credits; track remaining production needs.
• Final month through opening: focus on technical rehearsals, dress rehearsals, safety and access checks, final program proofing, and confirming each performance shift.
• After closing: strike, return and inspect borrowed or inventoried items, record repairs and outstanding returns, thank volunteers, and capture notes for the next production.

Phase 1: Plan the theater season and open auditions

Before auditions, lock your calendar backward from each show's opening: performance dates, tech week, the rehearsal window, and the audition and callback dates. Sharing this timeline in your audition notice sets expectations and reduces conflicts before they happen.

Then open auditions with a public sign-up link so performers enter their own information — contact details, headshots, and crucially their conflict dates on a calendar. Collecting availability at sign-up is the single highest-value thing you can do this early, because it prevents scheduling disasters weeks later. Households sign up together, so family programs register multiple people in one pass.

Lakeside's timeline for The Music Man shows how far ahead this starts: they posted the audition notice on August 18, ran auditions August 30-31, held callbacks September 3, and posted the cast list September 5 — a full nine weeks before their November 6 opening. Fifty-one performers signed up for 34 roles, and because everyone entered their own October and November conflicts at sign-up, the schedule builder in Phase 3 started with real availability instead of guesses.

Phase 2: Cast the show and grow your season talent pool

Run callbacks, keep notes, and make your casting decisions inside the same list where performers signed up. When you promote your picks to the cast list, everything they entered — headshot, bio, measurements, conflicts — comes with them. There's no export-and-re-import step and nothing to re-type. Lakeside narrowed 51 sign-ups to 12 callbacks for the leads, cast all 34 roles in a single afternoon meeting, and had the cast list live the same evening.

Every performer who auditions becomes part of your talent pool, a roster that persists across shows and seasons. By your second or third production, returning performers already have profiles on file, so casting the next show starts from a database rather than a blank page. Nineteen of Lakeside's 34 cast members had performed with the company before, so their contact details and measurements were already on record before auditions even opened.

Phase 3: Build the season rehearsal schedule around conflicts

With casting done, build the rehearsal schedule around the conflicts you already collected. Set which cast members are required at each rehearsal, publish calendar views the whole company can see, and let people export dates to their own calendars so "I didn't know I was called" stops being an excuse.

As rehearsals run, mark attendance — present, absent, or late. Approved audition conflicts automatically appear as excused, and the season builds a per-person attendance history you can actually reference when it's time to talk to a chronically absent cast member. Lakeside scheduled 28 rehearsals across their 10-week window — two weeknights and one weekend block per week, ramping to nightly during the final tech week — and because they'd collected conflicts up front, they knew before publishing that their Harold Hill would miss three October Tuesdays and could plan those as ensemble-only nights.

Phase 4: Plan costumes, props, and set pieces for the season

Design work runs in parallel with rehearsals. Build a costume plot by act and scene, and give each cast member a checklist of pieces with an acquired status so you can see at a glance what's still outstanding. Because measurements carried over from auditions, your costume team isn't chasing sizes.

On the physical side, build "props needed" lists and link items to props inventory and set piece tracking as you acquire them — with photos, storage locations, and check-out history. Inventory that persists across shows means last season's set pieces and costumes are already cataloged and ready to reuse. Lakeside's Music Man needed about 120 costume pieces and 45 props; of those, 80 costumes and 30 props were pulled from existing inventory, which the costume team confirmed in an afternoon because each item already had a photo and a shelf location on file.

Phase 5: Coordinate theater volunteers for each production

No community theater runs without volunteers, and the season is when you organize them. Build volunteer teams per show with roles that have dates, times, locations, and slot counts, then share a public sign-up link so people claim shifts themselves. You can add manual sign-ups for the folks who'll never use a link, and export the whole schedule when you need a printout for front of house.

Coordinating volunteers this way early means you're not frantically staffing the concession stand the afternoon of opening night. Lakeside's eight-performance run needed 6 ushers, 2 box-office, and 3 concessions volunteers per night — 88 shifts in all — and by opening a public sign-up link three weeks out, they had 80 of those shifts claimed before tech week and filled the last 8 with manual entries.

Phase 6: Prepare the printable program for opening

Tech week is where everything converges. Your cast list, scene order, and volunteer roster are all in one place, which makes assembling the printable program straightforward — cast bios that performers submitted themselves assemble automatically into a foldable PDF booklet ready for the copy shop.

Do a final pass on every list: confirm the props table is set, costumes are checked off as acquired, volunteers are staffed for every performance, and the program is proofread. Then open the show knowing the paperwork won't bite you mid-run. Lakeside's stage manager ran a one-page pre-flight checklist the Monday of tech week — 34 bios in, 45 props on the table, 120 costumes checked off, 88 volunteer shifts filled — and cleared every item by Wednesday. For the step-by-step version of that booklet, see how to build a printable show program.

Phase 7: Strike and reset inventory for the next production

Strike goes fast when everything already has a labeled home. Return props and set pieces to their storage locations, check costumes back into inventory, flag anything damaged for repair, and note consumables to restock. Because inventory persists, you're not throwing knowledge away — you're filing it for next time.

Then close the loop: the talent pool, inventory, and volunteer roster you built roll straight into the next production. Managing your whole season in one workspace means each show starts further ahead than the last, and the playbook gets smoother every time you run it.