โ† Course dashboard ยท Tier 1A ยท Module 2 of 6

Production Scheduling for Schools

Estimated reading + exercises: 90 minutes ยท Includes EasyScheduler widget access ยท Resource pack: 6 templates ยท CPD hours: 1.5
Listen to this module โ€” narrated by Daniel

Tip: you can listen while you read along, or close your screen and treat it as a podcast on the drive home.

Why this is Module 2. Module 1 put you in the chair as the production manager. Now you build the thing the whole production runs on: the schedule. This is where most school productions actually fall over โ€” not on the night, but weeks earlier, in a schedule that was never realistic. The risk register (Module 3), Compliance (Module 4) and Budget (Module 5) all read off the schedule, so getting this right is what makes the back half of the tier hold together.

The honest truth I'll keep repeating: you live and die by the SCHEDULE. If you don't have a schedule, you don't have a show โ€” it really is that simple. If you're not organised, everything goes out the window.

The two things everyone underestimates

Time. In a commercial world where we know exactly what we're doing, a show needs at least 24 weeks of lead time โ€” and in a school, where there are more checks and balances (show approval, cohort fit, rights, board sign-off โ€” see Module 1), it's often longer. Teachers almost always assume it'll take less than it does. It won't.

That the schedule changes in a heartbeat โ€” and you have to move with it. Theatre is an active environment. It changes constantly, and you have to be flexible with it. Children get sick. People's availability changes. The build runs late. None of that is a failure โ€” it's the job. You resolve it through open communication and by revisiting your priorities nightly.

Here's what that actually looks like. Say the scenic department needs major changes done tomorrow. That might mean cancelling a dress rehearsal โ€” so now you have to think it through: how does that impact wardrobe? Do they need another run to feel ready, or are they actually fine? Does sound need that time anyway? Maybe instead of a dress you run a walk-through or a sing-through out in the auditorium while set and lighting are being fixed on stage. The change cascades, and you work the cascade.

And the changes aren't always small. Sometimes it's major and completely unexpected โ€” a fire, a flood, a street power outage that takes the whole venue offline and nobody saw coming. The thing that saves you in every one of those cases is the same: having had the chat, having the communication open, and having a schedule everyone is already aware of before you head in. That's what buys you time. When everyone knows the plan, a change to the plan is a conversation, not a crisis.

This matters most in production itself, because you're in the venue for only a handful of days. Every night you recap how the day went, you re-plan tomorrow against the new reality, and you push that change out to everyone now โ€” not in the morning when half the crew is already in the car. EasyScheduler is built for exactly this: a live, shareable schedule you edit nightly and everyone sees instantly. But the principle holds whatever you use โ€” the schedule has to be live, shareable, and fast to change.

Real teardown โ€” what a missing schedule actually costs This is a recent school production I worked on as the venue manager โ€” not the production manager, which turns out to matter. Every problem below traces back to the same root cause: there was no hour-by-hour breakdown of the production week, and the people who needed to know things weren't told them. I'll keep the school out of it โ€” the point is the pattern, not the place.

Problem one โ€” nobody told the venue when the lighting truck was coming. I'd booked the theatre for the day and sent the lighting company a plan of the venue, but because I hadn't booked them โ€” the production manager had โ€” I had no idea what time they'd actually arrive. I assumed eight in the morning, so I made sure I was there. Sure enough, there was a truck and a crew standing around trying to work out how to get into the building. A single line on a schedule โ€” "lighting load-in, 8:00, stage door" โ€” would have fixed it.

Problem two โ€” I didn't know the size of the rig, so I was the wrong person on the wrong job. Nobody had told me how big the lighting rig was. I should have booked an extra crew member. Instead I got pulled away from supervising the safe installation and ended up up in the roof loading counterweight bricks while the crew hung lights on the bar. That's backwards. As the responsible person I should have been on the ground, supervising and operating the controls โ€” not the body up in the grid. That's a safety failure that came directly from a scheduling failure.

Problem three โ€” the audio crew lost hours to a rehearsal nobody warned them about. We'd bumped in audio on the Tuesday. No one had told the audio company we had a rehearsal at 3:30. So they were mid-way through tuning the PA when the rehearsal started and they had to stop work โ€” four people standing around losing billable hours, waiting for the rehearsal to clear. Again: better communication and a shared schedule, and it never happens.

Problem four โ€” the 17.5-hour bill shock (the expensive one)

The audio contractor's quote was a single line dropped into an email: "rehearsal 3:30 to 7:30." Here's the rule every teacher needs burned in: when you send a contractor "3:30 to 7:30", they read it as cast on stage, ready to go, at 3:30. But for this show, the 3:30 actually included an hour of setup โ€” the kids had to get ready and eat first, so the rehearsal wasn't really starting until 4:30. That hour of pre-start was never written down anywhere.

Same thing at the back end. The rehearsal "finished" at 7:30 when the kids left โ€” but there's always half an hour to an hour of work after that: shut the system down, get the radio-mic batteries back on charge, wait for the haze to clear, kill the rig, answer the post-rehearsal questions. None of that padding was scheduled or budgeted.

So at the end of the period the business owner rang me: their staff member's timesheet was showing an extra 17.5 hours for the week โ€” about half a week's wages โ€” and they couldn't absorb it. They had to re-invoice for the hours actually worked. Then came the bill shock, the frustration, and the argument. And there was nothing to argue: the labour had been worked.

You must pay crew for the hours worked. You can't fight it in retrospect. The fix was never a negotiation at invoice time โ€” it was a schedule that wrote down the pre-start hour and the post-show pack-down before the contractor ever quoted.

What every one of those four would have cost: one line on a shared schedule Lighting load-in time. Rig size (so you crew correctly). The 3:30 rehearsal flagged to the audio team. The setup-hour and pack-down-hour written into the call. None of these are hard. They're just the things that don't happen when the production manager keeps the plan in their own head โ€” or worse, when there's no plan at all, only an email with a start time and a finish time. The cost of not writing them down was a roof-grid safety risk, hours of standing-around labour, and a five-figure argument.

The lever that moves everything

A bad production with a great schedule still opens. A great production with a bad schedule rarely opens, and when it does, it opens late, broken, and exhausted. Of all the production-management skills you'll teach, scheduling is the one that compounds โ€” every minute saved on a good schedule is paid out across the run.

This module is not about Gantt charts or project-management theory. It's about the practical question: how do I get sixty exhausted people through a Saturday bump-in without anyone going home crying. The honest answer is that it takes more planning than most teachers think, and almost none of it happens during the bump-in itself.

By the end of this module you'll be able to: structure a school production into its standard phases, build a defensible bump-in plan, write crew calls that actually result in people arriving when you need them, produce a run sheet that survives the second-week revisions, use EasyScheduler to coordinate it all, and read a contractor's labour-hours quote and challenge the over-billed lines.

Production meetings โ€” burn them into the schedule

Meetings are not overhead. They are the mechanism that keeps every department reading off the same schedule, and they need to be in the calendar from the start โ€” not called reactively when something has already gone wrong.

The standard rhythm: a production meeting with all key stakeholders, weekly for one hour, from six weeks out from production. Before that โ€” in the earlier weeks โ€” touch base once a fortnight or once a month to keep every department aligned across the whole show. Then, on top of those, run your HOD / designer / creative meetings as their own thread. The all-stakeholder meeting keeps the whole production synchronised; the HOD and creative meetings go deep where the detail lives. You need both, and both go into the schedule as fixed, recurring commitments โ€” not "we'll find a time".

Show calls โ€” get this right, and move it to the front of your head

Before anything else about call times, learn the show-call rule, because it governs the back half of the whole production and almost everyone gets it wrong by under-calling:

Burn these into the schedule the same way you burn in the meetings. "Never less; more always welcome" is the whole philosophy โ€” the cost of an extra half-hour of call is trivial next to the cost of a crew that wasn't ready when the cast walked on.

The four phases of a school production

Every production โ€” from a class assembly to a year-12 senior musical โ€” passes through four phases. Naming them stops you from doing phase-3 work in phase-1 and panicking later.

Phase 1: Pre-production (18-24 weeks out)

What happens: casting, design, budget, venue confirmation, music/script licensing, risk profile drafted, build estimate, lighting plot drafted, sound stack confirmed, calendar published.

What looks like work but isn't: making decisions you don't have enough information for yet. Choosing a colour palette before you've seen the lighting plot is decoration, not design.

What gets dropped: parent communications. You think the show is so far out that nobody needs to know. Wrong. Parents organise their lives 8 weeks in advance. The first email goes out in week 1 of pre-pro with the high-level calendar.

Phase 2: Build + rehearsal (18-2 weeks out)

What happens: scenic construction, costume make/buy, lighting plot finalised + rig drafted, sound system specified + booked, prop list + sourcing, rehearsals advance from sit-throughs to staging to runs.

The single hardest thing in this phase is keeping the rehearsal calendar honest. Directors will, with the best intentions, agree to one additional rehearsal a week that becomes three, that becomes a tech-staff problem when crew calls collide with band calls. Hold the line. The calendar is the contract.

Phase 3: Production week (bump-in โ†’ opening night)

What happens: bump-in, tech rehearsal, dress rehearsal, opening night. This is the phase the rest of the module covers in detail.

Tech is the only phase where the cost of a bad decision compounds in minutes rather than days. A lighting cue that wasn't tested in a 4-hour tech is one that won't work in the show โ€” but you'll find out at 7:45pm on opening night with a 280-seat house.

Phase 4: Run + bump-out + restore/pack-up

What happens: the show run itself โ€” nightly shows, daily notes, repairs to set/costume/electrics โ€” then the bump-out of the theatre, and then the part everyone forgets: the pack-up, restore, cleaning and reset. The venue has to go back to how you found it. The costumes and the set have to be cleaned, restored and packed back at the store so they're usable next time. That work is real, it takes hours, and it has to be scheduled and crewed like any other call.

Most schedules ignore phase 4 until it's happening. Then the debrief โ€” even a 20-minute one with student leadership the week after โ€” is what carries the lessons forward. Without it, every production starts from zero.

What the production week actually looks like

People hear "production week" and picture the shows. The shows are the easy bit. The week is bump-in, plotting, tech, dress, then shows, then bump-out โ€” and the shape of it changes completely depending on whether you own the venue or you're hiring one.

In the commercial world the rhythm is roughly: bump in Monday and into Tuesday; plot lighting Tuesday into Wednesday; piano dress rehearsals Thursday (often two calls in the day); orchestral rehearsals Friday; a final dress or general on Saturday afternoon; open Saturday night; then a run of shows through the following week; then bump out. A commercial musical might do eight shows a week. That's a comfortable fortnight when the venue is yours.

A school almost never gets that luxury, and here's the key distinction:

The hidden cost of a hired venue isn't the hire fee It's that a compressed week removes your slack. In your own theatre, if lighting runs late on Tuesday you pick it up Wednesday. In a hired venue, Tuesday's overrun eats Wednesday's tech, and Wednesday's tech is opening night. The fewer days you have, the more the schedule has to be right before you walk in โ€” there is no room to recover.

The bump-in plan

The bump-in is the moment the production moves from the workshop into the venue. It's also where most school productions lose half a day they can't afford. A good bump-in plan answers four questions, in order:

  1. What goes in first? Work top-down. Roof items first โ€” masking (legs, borders, tabs), flies โ€” because nothing should be going up overhead once there's set and people working below. Then lighting (or at the same time as the roof work, if you keep the two crews at opposite ends of the stage). Then the floor. Then set and props. A common exception: lighting focus sometimes waits until after the floor โ€” if it's a previously-laid, finished floor you don't want it chewed up by EWPs, scaffold and lifters, so you focus once the heavy gear is clear. It depends on the venue and the floor. The principle is fixed; the focus timing is a judgement call.
  2. What needs to be cleared by when, so the next thing can start? The lighting rig must be flown out by 11:00 so the orchestra can load in by 11:30. The audio FOH desk must be live by 14:00 so the band can soundcheck by 14:30. If these dependencies aren't on the schedule, they don't happen.
  3. Where are the natural breaks? Crews need food, and students need to be picked up by their parents by specific times โ€” those pickup times are hard constraints you schedule around, not nice-to-haves. A good schedule has a 30-minute lunch built in at the half-day mark, not at "whenever we get to a good stopping point" (you won't). And when the work doesn't allow a single clean break, stagger the lunches: send LX and the mechanist (MX) on break first so SX gets a quiet room to tune the PA, then send SX to lunch once the drills and noisy work start up again. The break has to serve the work, not just the clock.
  4. What's the contingency? If lighting is 90 minutes behind by lunch, what gets cut from the afternoon? If you don't decide this on Wednesday during the planning meeting, you'll decide it under stress at 3pm Saturday. The decision is always worse when made under stress.
The 70% rule Schedule for 70% of available time. If your bump-in window is 8 hours, fit 5.5 hours of work into it. The other 30% absorbs the inevitable surprises โ€” the loading-dock key that's missing, the iPad that won't connect to the lighting console, the principal who comes to take photos for the school newsletter. A schedule packed to 100% is fiction the day it's printed.

A sample bump-in schedule

Below is a real Saturday bump-in I've run for a 14-piece musical with 60 cast and crew. Read it as a template, then we'll dissect what's working.

TimeActivityWho
07:30Production team on-site. Coffee. Walk-through of the day with stage manager + heads of department.SM, PM, HODs (5 people)
08:00Daily safety brief at stage door. Sign-on. Helmets distributed.All crew
08:15Roof first: masking flown in (legs, borders, tabs) + flies set.Stage crew (8)
09:30Lighting rigging begins from LX1 to LX5. EWP active stage-right (opposite end to roof work).LX crew (4) + lighting tech
09:45Sound system tip-up: FOH PA, monitors, FOH desk run.Sound crew (3)
11:00Lighting bars in trim. Cabling done. Patch starts.LX crew
11:15Floor goes in (vinyl roll-out + tape) once overhead work is clear.Stage crew
11:30Orchestra load-in starts (rear stage door). Stands + chairs from EasyOrchestra plot.Orchestra (14) + 2 crew
12:00STAGGERED LUNCH. LX + MX break first โ†’ quiet room for SX to tune the PA.LX, MX
12:30SX lunch as drilling/noisy work resumes. Lighting focus begins (floor down, EWPs clear). Set + props load-in begins stage-left.SX off; LX + scenic crew on
14:00Audio mic check + radio mic pack distribution. FOH live.Sound + cast (10)
14:30Band soundcheck.Band + sound + MD
15:30Cast onstage for spacing call. Tech crew shadows their cues.Cast + all crew
17:00Stop work. Stage swept. Tomorrow's call posted.SM

Notice what this schedule does:

Reading a contractor's labour-hours quote

This is where the schedule directly hands you the BS-detector for the most common over-billing pattern in school production hire. Contractors quote labour in hours ร— hourly rate. If you don't know how long a task actually takes โ€” and your schedule shows you exactly that โ€” you can't push back on the line items. Here's the framework.

For every labour line in a quote, ask three questions:

  1. What dependency triggers this work? If the dependency hasn't started yet, the contractor doesn't need to be on-site yet. If the dependency is finished, they should have stopped billing.
  2. What is the realistic time-on-task for someone who's done this before? Not "worst case". Not "with overruns". The competent middle.
  3. Are you paying for work, or paying for waiting? A quick word on "standby" โ€” in Australia we do not charge standby rates. It's an hourly rate for everyone, or a day rate for some; the nature of the work (active vs waiting) doesn't change the rate. So if a contractor's "soundcheck supervision" is 30 minutes of input-line confirmation followed by 3.5 hours of sitting at FOH waiting for the cast, you don't argue the rate down โ€” you argue that the schedule should never have had them on-site for those 3.5 hours in the first place. If you're paying crew to wait because of a bad schedule, that's on you, not on them. The fix is upstream, in the call times, not in a discount rate.
One more on minimum calls โ€” round up, always You don't bill (or get billed) in fractional hours. A task that genuinely takes 3 hours 35 minutes is a 4-hour call โ€” round up to the minimum call. So when you're reading a quote, the question is never "is this 3.5 hours or 4?"; it's "should this crew member have been called at all for this block, and is the block the right length?"
Worked example: a 16-labour-hour sound quote on a 14-piece musical

Typical sound contractor quote on a school musical with a 14-piece band might read:

LineQuotedWhat's really happeningDefensible
Setup + system tip-up8 hrs @ $145Truck-in is 30 min; system tip-up (FOH + monitors + 6 radio mics) is realistically 3-4 hrs for a competent two-person crew. The other 4-5 hrs is contingency padding.Over-billed โ€” real work rounds up to a 4-hr call: A$580 vs A$1,160 quoted
Soundcheck supervision4 hrs @ $145Actual soundcheck for a 14-piece band is 90 minutes if the MD knows the score. The other 2.5 hrs is the contractor sitting at FOH waiting for the cast call โ€” a block your schedule should never have created.Should never have been called โ€” fold the 90 min of real work into the adjacent call rather than booking a separate block
Show staffing4 hrs @ $1452.5-hr show + 20-min interval = 2hr 50min in-room; +30-min pre-show check +15-min post-show shutdown = 3hr 35min of real work.Correct call โ€” rounds up to a 4-hr minimum call: A$580. This line is fair.

Quote: A$2,320. Defensible after challenge: ~A$1,160 (a 4-hr tip-up call + a 4-hr show call, with the soundcheck work folded in rather than separately booked). Same engineer, same gear, same outcome. You just refused to pay for time that was never going to be worked โ€” and you fixed it in the call structure, not by haggling the rate.

The negotiation here is NOT about quality, and it is NOT about discounting the hourly rate (in Australia the rate is the rate). It's about whether the calls on the quote match the calls your schedule actually requires. Show the contractor your bump-in schedule with their crew's real on-stage blocks, and the conversation becomes "your quote books three separate blocks; my schedule only needs two 4-hour calls โ€” let's reconcile" rather than "you're trying to rip us off" (which is unproductive and inaccurate; the contractor is quoting what their billing policy says, not maliciously over-charging).

Crew calls โ€” getting the right people in the right place

Before the format, the judgement. Crew calls are fluid โ€” there's no fixed number. How many people you call depends on the size of the show, the size of the set, and the size of the budget. Two principles hold across all of them:

Minimum crew โ€” what "enough people" actually looks like

"Fluid" doesn't mean guesswork. There's a realistic minimum for each scale, and you call to it (then add your slight overstaff on top). Two worked examples on the sound side:

The show-crew call

Once you're in the run, the main call is the show crew, and it has a standard shape. Two-hour call before the top of the show. So for a 7:00 show, that's a 5:00 crew call: an hour and a half to start up โ€” power on, props set, pre-show checks, line check, mic checks โ€” and then you're ready. The cast normally get an hour call: come in, costumes, mic up, warm up. House opens at 6:30, show runs 7:00 to roughly 9:00 or 9:30. Then half an hour post-show for crew โ€” clear the haze, shut down, tidy, make safe โ€” before they go home and do it all again tomorrow.

Who runs the room โ€” PM and SM work in conjunction Authority hands back and forth depending on whether cast are on stage. When the cast are NOT on stage, the PM controls the room โ€” bump-in, build, technical work, all of it. When the cast ARE on stage, the SM is in charge. The handover is explicit: the SM checks in with the PM to get to the top of the call, takes the handover, runs the room while the cast are on, calls the end of the call, and the PM steps back in. It's not a turf war โ€” it works in conjunction. Each one owns the part of the day they're built to own.
The five-hour show call is the industry standard โ€” build to it A complete show call โ€” start-up, the show run itself, and shut-down โ€” fits inside five hours, and that's the number to aim for. If you can't run a show with a school group inside a five-hour block, you're trying to do too much. You should not need 9am to 6pm on a Saturday; you should be able to get the show in between 12 and 5, or 10 and 3. And always buffer in a little extra time and a little extra money โ€” if you don't use it, great; if you suddenly need an extra wardrobe hand or an extra crew member because the hour-and-a-half pre-show isn't enough, the budget's already there and it doesn't come out of your pocket.

A crew call is a written summons to a specific call time. It tells each person three things: when they're called, where they report, and what role they're playing today.

A bad crew call: "Bump-in 8am Saturday, everyone." Nobody knows what to bring, what to wear, or where to go. Half the crew arrives at the wrong door. The other half doesn't arrive at all because they assumed 8am was approximate.

A good crew call:

"Saturday 4 May. Loadout door (stage-right alley). 07:45 in stage blacks + closed-toe shoes. You're on LX crew today rigging from LX1 to LX5. Expect harness work between 9:30-11:00. Lunch 12:00-12:30. Stop work 17:00. Reply 'Y' to confirm; reply 'N' if you can't make it. โ€” DG"

The reply-confirmation is the most important sentence. Without it, you find out who isn't coming on Saturday at 07:50, when the only thing left to do is divide that person's work among everyone else.

The 48-hour rule for changes Any change to a published call time within 48 hours of the call must be communicated directly (phone or text) to every affected person โ€” not just posted to the cast/crew group chat. Group chats are passive: people see them when they next pick up their phone. A 5am Saturday change posted Friday at 11pm will be missed by half the people you need.

The run sheet

A run sheet is the show-night timeline. It's calling-the-show reference for the stage manager and a survival document for everyone backstage. Standard structure: time, cue, who, where, what.

Run sheets exist at three resolutions: the season run sheet (whole performance run, weekly view), the show-day run sheet (the day of a performance, hour-by-hour), and the show run sheet (the performance itself, minute-by-minute through the show).

The most-overlooked component is the pre-show timeline โ€” the two hours between cast arrival and curtain. It's the dense, anxious, mistake-prone window where everything that goes wrong on the night was set up to go wrong. Sample:

TimeActivity
16:30House clear. Stage swept. SM on headset, comm check with all heads.
17:00Cast call. Sign-in at stage door. Costume + wig fitting.
17:30Mic check. Radio packs distributed and confirmed.
18:00Vocal warm-up (MD-led, stage). Band physical warm-up.
18:30Half-hour call. Cast in costume + makeup. Final mic line check.
19:00House open. Pre-show music UP. FOH begins seating the audience.
19:25Beginners call (5 min before start). Beginners onstage โ€” FOH should have most of the house in by now.
19:28Go-curtain warning. SM calls standby for cue 1.
19:30Show start. Curtain up.

The sequence here is deliberate: house open at 7:00, a 25-minute call to the cast, beginners at 7:25 (by which point front-of-house should have most of the audience in), and the show away at 7:30. The half-hour call and the beginners call are non-negotiable Broadway/West End conventions for a reason: they sequence the cast's nervous-system into performance state. Skip them and you get a first act of overshooting tempos and missed entrances.

The EasyScheduler widget

This module includes access to EasyScheduler โ€” the Suite's planning tool built specifically for the bump-in + tech-week problem. Open EasyScheduler in a new tab.

What it does: Day ร— Venue ร— Row hierarchy (Saturday/Sunday/Monday ร— Stage/Workshop/Foyer ร— LX/Sound/Stage Crew/Wardrobe/Props/Cast/Band). Crew counts roll up into a tally tab so you can see at a glance whether you've over-called or under-called. Budget tab forecasts labour cost based on editable hourly rates. PDF export prints a clean A4 schedule for the stage door. Share-by-link gives parents read-only access to the schedule for pickup planning.

EasyScheduler demo schedule
A demo bump-in schedule in EasyScheduler โ€” the same Saturday call laid out by day, venue and department, with crew counts and labour cost rolling up live as you edit.

It's designed to be filled in once and edited daily โ€” the schedule on Wednesday is rarely the schedule on Friday, and the schedule on Friday is never the one you actually use Saturday morning. Every change you make pushes straight out to everyone on the share link, which is exactly what you need when you're re-planning tomorrow on the back of how today actually went.

Exercise 2.1 โ€” Build a Saturday bump-in

Open EasyScheduler and build a Saturday bump-in for this scenario:

"Your school is mounting a Year-12 production of Hamilton. Cast 28, band 12, crew 16. Venue: school's 300-seat hall. Available time: 8am Saturday โ€” 5pm Saturday (one day only, with dress rehearsal Sunday afternoon). Power load and rigging done by you and a paid lighting tech. Director is anxious."

Your schedule should: identify dependencies between departments, include a lunch break, leave 30% buffer time, name every crew call with a confirmation requirement, end no later than 17:00. Export the PDF and review against the sample in the resource pack.

Exercise 2.2 โ€” Reconcile a contractor's quote to your schedule

Take the schedule you built in Exercise 2.1 and overlay the sound contractor's quote from the resource pack (an anonymised real quote for a similar-scale production). For each labour line in the quote, find the corresponding block in your schedule and compare hours. Flag any line where the quoted hours exceed scheduled hours by more than 25%.

Your output: a one-page reconciliation. Each line either reconciles (within 25%) or is challenged with the schedule-block as evidence. Save to portfolio.

Knowledge check

  1. Why does masking go in before lighting?
  2. You have 8 hours of bump-in time. What's the maximum amount you should schedule into it, and why?
  3. The director asks for "one more run-through" after a 9-hour Saturday. Walk through the decision criteria you'd apply.
  4. A parent's crew-call confirmation hasn't come in by Friday 5pm. What do you do?
  5. The 19:00 half-hour call shows two cast missing. List the three actions, in priority order, the stage manager takes.
  6. A lighting hire contractor quotes 12 hours of focus labour for a 60-fixture rig. Your schedule has the focus block at 4 hours. What three things do you ask before paying?

๐Ÿ“ฆ Resource pack โ€” templates packaged below

Note: the calling-the-show cue book is a stage manager's tool, not a scheduling tool โ€” you'll find it (and these run-sheet templates) as resource builds inside EasySM.

๐Ÿ“ฆ Resource pack

Tier 1A ยท Module 2 ยท 6 downloadable resources โ€” open in a new tab, print or save as PDF. (The calling-the-show cue book is an SM tool โ€” find it in EasySM.)

The CPD claim This module counts toward 1.5 hours of accredited Continuing Professional Development under VIT / NESA / QCT / WACOT registration frameworks. Your CPD certificate is auto-generated on module completion (provided you complete the quiz with โ‰ฅ70% and submit Exercises 2.1 + 2.2).

Put the schedule somewhere it can move. Everything in this module โ€” the meetings, the show calls, the bump-in order, the run sheet โ€” only works if the schedule is live, shareable and fast to change. That's exactly what the Suite's planning tool is built for.

Open EasyScheduler โ†’

Tier 1A ยท Module 2 ยท in progress
Mark this module complete to advance to the next.
โ† Dashboard ๐Ÿ“ Take quiz Next module โ†’