Corporate AV Crew Scheduling: Four Rooms, One Weekend, No Spreadsheet

Corporate audiovisual work has a different shape from concert touring. The days are shorter, the rooms are more numerous, the client is in the building and changes their mind at 16:00 on Friday. A staging company in Orlando or Dallas might run four concurrent events across two hotels in a single weekend, each with a general session and six breakouts.

The scheduling problem is not scale. It is concurrency and churn.

What makes corporate AV scheduling different?

Corporate AV scheduling differs from touring in that a single technician may cover multiple rooms in a day, room schedules change with the client agenda rather than with a fixed show clock, and the same crew often turns a room between sessions. Schedules are built around a printed agenda that is still being edited.

Three consequences follow from that.

Rooms are the unit, not shows. A general session, six breakouts and a registration desk are one event to the client and seven staffing problems to you. Your schedule needs to hold them as one project with parts, so that when the client moves the keynote you are not editing seven unrelated entries.

Technicians float. In touring, a person is on a show. In corporate, a person might set two breakouts in the morning, run one in the afternoon and strike a third. Assignments are shorter and more numerous, which means more scheduling actions per revenue dollar than almost any other kind of production work.

The agenda is the schedule, and it moves. A client who shifts the keynote by ninety minutes has just changed six call times. If that costs you an hour of coordinator work and three rounds of texts, it happens every week and you never get ahead.

How do you schedule concurrent rooms without a spreadsheet per room?

Build from templates. A standard breakout set is the same every time: one technician, projector, screen, wireless handheld, four hours of setup, rehearsal window, session support, strike. Save it once. A weekend with six breakouts becomes six template applications plus edits, not six blank forms.

Hold the whole property as one project. One event record with multiple rooms and multiple call times, not seven separate events that happen to share a hotel. Everything downstream, the call sheet, the labor cost, the timesheet review, works better when the client's weekend is one thing in your system.

Stagger call times inside the event. The general session tech calls at 06:00 for a 08:00 rehearsal. Breakout techs call at 07:00. Registration at 07:30. One event, several call times, one call sheet where each person finds their own line. See how to write a call sheet.

Make the change once. When the keynote moves, change the schedule and let the call sheet, the notifications and the crew's phones follow. If you are editing a Word document afterwards, the system has not helped you.

Re-request after a material change. If a technician accepted a 06:00 call and it is now 08:00, that acceptance does not mean anything. Reset it and ask again. Crew who arrive at the wrong time because they were holding an old confirmation are a preventable cost.

Matching technicians to rooms

Corporate AV has a specific matching problem: proficiency with particular equipment matters more than general seniority. A technician comfortable on a specific switcher or a particular wireless system is not interchangeable with one who is not, even at the same rate.

Keep role tags granular enough to be useful and coarse enough to maintain. Audio A1, Audio A2, Video V1, Camera Op, Graphics Op, Projectionist, Breakout Tech is usually about the right resolution. Add equipment notes on the person where a specific system matters. Resist the urge to build a twelve-dimensional skills matrix; nobody updates it and within a season it lies to you.

Labor cost while the weekend is still running

The margin killer in corporate AV is the extended day nobody priced. A general session runs long, rehearsal pushes into the evening, and four technicians are now in overtime that was not in the estimate.

You want two numbers visible while the event is happening, not after: hours logged today, and labor cost today against what was scheduled. If the rehearsal is running two hours long, the moment to raise a change order with the client is that afternoon, while the client is standing in the room, not in an invoice ten days later that starts an argument.

Tinds puts both on the dashboard alongside who is currently clocked in, which is the view a coordinator should be able to glance at between rooms.

The Friday 16:00 problem

Every corporate AV company has a version of this. The client sends a revised agenda late on Friday for a Saturday start. Three rooms change, one session is added, one is cut.

The manual version: the coordinator recalculates call times, rewrites the call sheet, texts eleven people, and gets six replies. Saturday morning has two people at the old time and one no-show who never saw the message.

The version worth buying software for: change the three rooms in the schedule, the affected people get a notification that their call changed and must confirm again, the call sheet regenerates, and by 19:00 you can see which two have not answered and phone exactly those two. The work is the same size. The uncertainty is not.

Frequently asked questions

How many technicians can one coordinator schedule?
With spreadsheets and texts, most coordinators top out around thirty to forty active people across a weekend before confirmations start slipping. With templates and a confirmation workflow the ceiling is considerably higher, mostly because chasing replies stops being the job.

Should breakout rooms be separate events or one event?
One event with multiple rooms and call times, in almost every case. The client thinks of it as one program, your call sheet should present it as one program, and your labor cost should roll up to one job.

How do we handle a technician covering three rooms in one day?
As one assignment for the day with room-level detail in the notes or the run of day, rather than three separate shifts. Three shifts fragment their time card and make overtime calculation harder for no benefit.

What about hotel in-house AV restrictions?
An operational constraint rather than a software one, but the call sheet is where it belongs: note union jurisdiction, in-house rigging requirements and load-in restrictions in the access section so the crew head is not discovering it at the dock.

Related reading: How to write a call sheet for a live event, Stagehand scheduling software, How to stop crew no-shows.